SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Please forgive me my ignorance, as well as the needless extension of yet another systemd thread, but shouldn't it be possible to start systemd so that hard dependencies (such as udev) are satisfied, and then have systemd launch the classic init?
Please forgive me my ignorance, as well as the needless extension of yet another systemd thread, but shouldn't it be possible to start systemd so that hard dependencies (such as udev) are satisfied, and then have systemd launch the classic init?
No. Because systemd run everything in its very own cgroup container, so, launching another init from systemd pid1, you'll end in something similar with a LXC container.
Hmm ... I think it might soon get harder and harder to hold out. It since looks like Ubuntu just folded as well. That doesn't leave many distros not on the systemd bandwagon. Just us and Gentoo? Or have I missed others?
Hmm ... I think it might soon get harder and harder to hold out. It since looks like Ubuntu just folded as well. That doesn't leave many distros not on the systemd bandwagon. Just us and Gentoo? Or have I missed others?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,015
Rep:
Quote:
Originally Posted by ruario
Hmm ... I think it might soon get harder and harder to hold out. It since looks like Ubuntu just folded as well. That doesn't leave many distros not on the systemd bandwagon. Just us and Gentoo? Or have I missed others?
the kernel is all we really need
and the kernel has a rule that goes something like "don't break shit"
combined with the mentality of "every bug is of same importance" i don't think Linus will allow systemd devs to break the kernel (i know one tried)
Fortunately Slackware project does not suffer from similar BS like executive committee, regulations, voting, bigmouth promises like "guaranteed" release cycle you can "rely" on, big-corporate money back-up and arising own interests from etc.
Just the long-term almost 10 years positive experience matters. The rest are just words, noise..
I didn't become involved in many endless debates about this RedHat's cancer. Yep, I don't like it and personally see no one serious reason which can justify so wide and deep system changes its adoption causes.
I'd wish Slackware would avoid it as far as all important upstream software included in distribution allows to be packaged without too much hassle.
This is a major intervention and for our business it does mean even to ditch Linux completely. Fortunately there are still free BSD systems, however narrower hardware support complicates things a bit for the lasting contracts but they are already being solved.
It seems they considered developing udev but only time will tell
Quote from Pat:
Quote:
"...Concerning systemd, I do like the idea of a faster boot time (obviously), but I also like controlling the startup of the system with shell scripts that are readable, and I'm guessing that's what most Slackware users prefer too. I don't spend all day rebooting my machine, and having looked at systemd config files it seems to me a very foreign way of controlling a system to me, and attempting to control services, sockets, devices, mounts, etc., all within one daemon flies in the face of the UNIX concept of doing one thing and doing it well. To the typical end user, if this results in a faster boot then mission accomplished. With udev being phased out in favor of systemd performing those tasks we'll have to make the decision at some point between whether we want to try to maintain udev ourselves, have systemd replace just udev's functions, or if we want the whole kit and caboodle...."
One thing I completely dislike about systemd is that literally it acts as a locked hypervisor to the GNU OS. There's no shell interaction with systemd at all because it's completely self-contained unlike every other init system out there that interacts with the system shell. There's near-zero administrator level inside of systemd unlike bsdinit, sysvinit, runit, s6, upstart or any other init system.
I think honestly people have gone insane over this software being viable. The guy from CRUX made a good hint. Mdev is a step back in time, but maybe that's what needs to be done. Maybe this is a metaphor and clear message to say in order to see where we stand, we have to take a step back to see not just our present but our future as well.
Maybe it's time those distributions that don't want systemd need to start working together.
Systemd reminds me of the question, if everyone jumps off the bridge to their deaths should you jump as well? The answer clearly... Is NO.
On the switching to *BSD argument, if you feel the need to do so, start learning now. Don't forget there's also Solaris, Illumos, and other UNIX branded distributions also.
RHEL7 will have systemd, and it's made my RHEL/CentOS/ScientificLinux-using sysadmin friends grumpy. They don't want to talk about it, and they don't want to think about it, because they don't want to be "angry all the time" (an exact quote from one of them).
It's made me think this might be an opportunity for a Slackware-for-the-Datacenter project. Eventually some of these professionals are going to look around for viable systemd-free alternatives for their business. I don't think there currently are any. It would be very nice to have one to offer them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.