Linux From Scratch ends SysVinit support
411–416 of 416 posts
Re: Linux From Scratch ends SysVinit support
#412Earlier quoted context omitted.
> No software is perfect Especially when it's a giant blob of buggy C code written by a known hack who has multiple decades' worth of history of foisting shit code upon a less than enthused public. > At least for me systemd is a net positive For the moment. Just wait until it finds a way to fuck you. It's plotting and scheming behind your back to do so as we speak. Systemd for some reason seems to uniquely be the epi…
> Systemd for some reason seems to uniquely be the epicenter of giant facepalm bugs like LEAVING THE SYSTEM FIRMWARE VULNERABLE TO AN RM -RF COMMAND I am very sorry to inform you but efivarfs is something coming from the Linux kernel. Being able to rm -rf it is squarely something that is entirely on the kernel implementation, WHICH THE AUTHOR OF EFIVARFS EVEN ADMITS[0] [0]: https://lwn.net/Articles/978640/
#facepalm
Re: Linux From Scratch ends SysVinit support
#413Earlier quoted context omitted.
> Implements an init system; does not replace DNS, syslog, inetd, or anything else Neither does systemd its init. Unknowledgeable people keep confusing systemd the init and systemd the daemon / utility suite. You can use just the init system without pulling in resolved or networkd or whatever. Systemd is the Unix philosophy of lots of modularity. But because all the systemd daemons come from the same shop, you get a…
> because all the systemd daemons come from the same shop, you get a lot of creature comforts if you use them together. Nothing bad about that. That's how vendor lock-in works, in which a myth is propagated that having it all come from under one roof is best. In fact, it is a guarantee that best-of-breed alternative solutions cannot be used. Interoperability is thwarted. This is why sensible Unix admins historically…
Think about it, you can't obligate the systemd folks to maintain codebases that aren't theirs.. would be madness.
Re: Linux From Scratch ends SysVinit support
#414Re: Linux From Scratch ends SysVinit support
#415Earlier quoted context omitted.
> .. and that opinion is a great explanation of why systemd won. Completely wrong and ignorant. > Turns out, a lot of people are not happy with "Come on man. It's been done for decades." attitude, and they wanted something new and much better. And then they got systemd. LOL Like Dr. Phil said, "How's that workin out for ya?" LOL > And so when something new came up, they jumped on it with both feet. You just did what…
wow, you don't really get what "open source" or "working together with others" is, do you?
Re: Linux From Scratch ends SysVinit support
#416All I want is init scripts and X11, but the horizons are shrinking. I've already compromised with systemd, and I don't like it. I see BSD in my future, or at least a linux distro from the list here https://nosystemd.org/ - probably Gentoo. Nothing to stop me, absolutely nothing at all. I just need a few days free to backup/wipe/reinstall/reconfigure/restore_data and I'll be good. Better make that a few weeks. Maybe o…
Not at all, and I'm not sure why so many people have this perception. It's never been this way. LFS is the tutorial you follow to get a full GNU/Linux system. In LFS, not having a base that can theoretically support the latest desktop environments is considered a fatal bug. It's just a conventional distro but in document format.
This is good for its comprehensiveness and as a way of documenting what existing Linux distros are doing, but it limits its utility as a learning aid as well as for embedded development. Most people interested in barebones Linux should instead start with a kernel and busybox and ignore most GNU packages.