DebianThis forum is for the discussion of Debian 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.
So I am using Sid and it pulls systemd tainted packages that remove sysvinit and replace it with systemd as default init. So I want to go back to using sysvinit since systemd is a buggy blackbox and frezzes my system sometimes on boot and shutdown.
So whats the best way of removing systemd as init. I know I still need the piece of poop known as systemd on my system with all the new hard dependencies because of sellouts in the Debian TC.
I understand I can reinstall sysvinit and remove systemd as init but my searches have not come up with something current.
stick to the facts. If you don't want to use systemd then don't. You're free to choose from multiple init systems. Did you try to remove the systemd package and install sysvinit? Ie
The package that most likely is the cause for pulling in systemd is libpam-systemd, which depends on (systemd-sysv | systemd-shim), which means that to satisfy this dependency you must either have systemd-sysv installed (which you don't want) or the systemd-shim package, which will not pull in systemd.
So you should be able to install sysvinit and remove systemd with after installing systemd-shim.
Be aware that sysvinit compatibility of Debian is only guaranteed for the upcoming Jessie release, after that no one can say to which extend you will be able to avoid systemd. If systemd really is a no-go for you it is time to think about switching distros.
stick to the facts. If you don't want to use systemd then don't. You're free to choose from multiple init systems. Did you try to remove the systemd package and install sysvinit? Ie
Code:
apt-get install sysvinit systemd-
Did this not work?
Evo2.
Thanks it worked like a charm been running for a few weeks without a snag now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.