If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
No announcement yet.
Linux Kernel Developers Fed Up With Ridiculous Bugs In Systemd
"...ignoring the complexity and fragility of the scripts framework..." - that so-called foundation(of simple init scripts) has been in place, and has worked flawlessly for over 30 years, in the "real" unix/linux world.
Your "systemd", has to learn to curb their arrogance and admit their mistakes, and then FIX they're buggy crap, or else.
Cause nobody wants a potential "systemd" heartbleed, ...
My god, the shear ignorance displayed here is staggering.
All this hate because someone dares to come up with new boot code! I've been playing with systemd for the past week, it's been like a new toy to me to learn my way around. Since I mantain a private package for unlocking multiple encrypted disks, I figured why not install systemd, learn my way around it, and then port my package to work with it.
OK, here's my results: With systemd on the root volume and the older Upstart/initramfs-tools initrd, it works fine so long as there are no invalid but present entries in /etc/crypttab (not used by my package. With a systemd using version of Dracut instead, I can unlock all disks and boot, but not with my own code and a single passphrase call yet, nor have I gotten my custom Plymouth theme working in Dracut's initrd yet.
It's been an interesting hackfest, and I do expect to get my code working the systemd way, probably by having my script check for all devices present before calling the passphrase to unlock any of them, exiting non-zero if any have yet to appear so it can recycle as a Dracut hook. If I can't get the hooks to work, I will have to find out how to write a generator that would work like the cryptsetup/systemd generator but call the passphrase my way to unlock all the disks at once. I expect sucess, not having it yet means I haven't learned enough about systemd and dracut yet, it does NOT mean they suck!
I benchmarked a dracut/sustemd boot into a unencrypted test partition on an SSD at 13 seconds with a 4.5 GHZ AMD FX-8120. I think systemd has a lot of potential to be a very fast booter and surely the various new code bugs will be swatted one at a time as the code matures.