"No, systemd will not take over Linux, it's just a crazy conspiracy theory" is what I keep getting told by these so-called "Linux guru's" on YouTube... Between when I was told this lie for the first time and last time: * Cron is now being managed via systemd, because apparently regular Cron sucks? * Shutting down and rebooting the system is now done via systemd, because something's apparently wrong with "shutdown -h now"? * NTP is managed with systemd now * Network is managed with systemd now * Gnome is managed with systemd now What's next? systemctl changedirectory /usr/bin? systemctl listfiles /home/user? systemctl createdirectory foldername? It's beyond ridiculous! I can easily see GNU Coreutils being replaced by systemd-utild, and the Linux Kernel by systemd-linuxd. And let's replace GCC with systemd-compiled, because why not? On 2023年07月29日 10:37, David L. Craig wrote:
Devuan's DNG (Debian Not Gnome) list has a subthread going about systemd 254 changes related to deprecating sysv script support. I wanted to be sure CRUXers are aware of this. The complete thread (currently through July 28) is at https://lists.dyne.org/lurker/thread/20230728.071036.81291f54.en.html
----- Forwarded message from tito via Dng <dng@lists.dyne.org> -----
From: tito via Dng <dng@lists.dyne.org> List-Id: "The first mailinglist after debianfork.org" <dng.lists.dyne.org> To: dng@lists.dyne.org Date: Sat, 29 Jul 2023 08:13:22 +0200 Subject: Re: [DNG] New goodies from systemd
On Sat, 29 Jul 2023 14:30:36 +1000 onefang <onefang_devuan@sledjhamr.org> wrote:
On 2023-07-29 08:18:54, Alif Radhitya Wardana wrote:
Based on this changelog, what will happen in the future to SysV? I mean, if systemd forces people to create native systemd units, will people drop sysv scripts on their apps?
On July 29, 2023 3:20:17 AM GMT+07:00, tito via Dng <dng@lists.dyne.org> wrote:
Hi, A new, official systemd release (254) has just been tagged:
* Support for System V service scripts is now deprecated and will be removed in a future release. Please make sure to update your software *now* to include a native systemd unit file instead of a legacy System V script to retain compatibility with future systemd releases.
A wonderful excuse to remove the last init scripts from packages.
Do I have to resurrect my ancient LSB compliant SysV init code that could figure out dependencies, run things in parallel, and even work with init "scripts" written in ANY language? It was written as a busybox module, and could even cope with multiple other init "scripts" as modules in the same busybox binary. LSB compliance means it reads the headers, which in typical init scripts are shell comments in the first few lines of the script.
I could teach it how to grok shitsemDie units.
Hi, yes using the info contained in .service units would be a elegant solution, but they ship a lot of them (and timers, targets, etc) so I suspect that picking the right ones is not simple without hardcoding the names (not so elegant), also the command lines used are different as the ones in SysV init scripts (daemonizing, logging). I would like to see your busybox module as I love busybox code. I recall that something like what you propose maybe was attempted (as a GSOC?).
Ciao, Tito
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
----- End forwarded message -----
-- <not cent from sell> May the LORD God bless you exceedingly abundantly!
Dave_Craig______________________________________________ "So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe." __--from_Nightfall_by_Asimov/Silverberg_________________
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
-- lain. Did you know that? 90% of all emails sent on a daily basis are being sent in plain text, and it's super easy to intercept emails as they flow over the internet? Never send passwords, tokens, personal information, or other volunerable information without proper PGP encryption! If you're writing your emails unencrypted, please consider sending PGP encrypted emails for security reasons. You can find my PGP public key at: https://fair.moe/lain.asc Every good email client is able to send encrypted emails. If yours can't, then you should consider switching to a secure email client, because yours just sucks. My recommendations are Claws Mail or NeoMutt. For instructions on how to encrypt your emails: https://unixsheikh.com/tutorials/gnupg-tutorial.html