Mailinglist Archive: opensuse (982 mails)

< Previous Next >
Re: [opensuse] Getting rid of systemd and putting sysv back
Felix Miata wrote:
David Haller wrote on 2014-09-29 01:43 (UTC+0200):

On Sun, 28 Sep 2014, Felix Miata wrote:

Ruben Safir wrote on 2014-09-28 04:32 (UTC-0400):

It just needs to to store information so that the machine can BOOT
and then mount all mount pointed listed in fstab

And what exactly do you think is responsible for unmounting at shutdown time?

RTF init-scripts. E.g. /etc/init.d/boot.localfs (prior to systemd[0]).

Sorry for neglecting to excise the reference to storing anything. My comment
was not about process details. I only meant to point out what was responsible
for controlling the shutdown process on a system controlled by sysvinit.

I think I begin to understand why so many people jump on the systemd-train.

I'm not on the systemd train. Like many others, I've simply realized resistance
became futile once the snowball was too big to stop. The horse left the barn
long


If everyone who just gave up, despite having objections, would speak up
against this catastrophe-in-the-making, that snowball would get melted
quite quickly (say, 24 months).

Cowardice facilitates evil.

ago. Until something as big and powerful as RedHat provides something promising
to be better than systemd, openSUSE is destined to continue using systemd.

[0] I'll gladly put the one from oS 12.1 on paste.opensuse.org,
if you're unable to find it

Maybe you forgot yourself:
os114host:~ # ls -lgG /etc/init.d/b*/*S*
lrwxrwxrwx 1 12 Oct 3 2011 /etc/init.d/boot.d/S01boot.proc -> ../boot.proc
lrwxrwxrwx 1 12 Oct 3 2011 /etc/init.d/boot.d/S01boot.udev -> ../boot.udev
lrwxrwxrwx 1 16 Oct 3 2011 /etc/init.d/boot.d/S02boot.rootfsck ->
../boot.rootfsck
lrwxrwxrwx 1 13 Oct 3 2011 /etc/init.d/boot.d/S03boot.clock -> ../boot.clock
lrwxrwxrwx 1 21 Oct 3 2011 /etc/init.d/boot.d/S04boot.device-mapper ->
../boot.device-mapper
lrwxrwxrwx 1 19 Oct 3 2011 /etc/init.d/boot.d/S04boot.loadmodules ->
../boot.loadmodules
lrwxrwxrwx 1 16 Oct 3 2011 /etc/init.d/boot.d/S04boot.localnet ->
../boot.localnet
lrwxrwxrwx 1 10 Oct 3 2011 /etc/init.d/boot.d/S07boot.md -> ../boot.md
lrwxrwxrwx 1 15 Oct 3 2011 /etc/init.d/boot.d/S10boot.localfs ->
../boot.localfs
lrwxrwxrwx 1 15 Oct 3 2011 /etc/init.d/boot.d/S12boot.cleanup ->
../boot.cleanup
lrwxrwxrwx 1 13 Oct 3 2011 /etc/init.d/boot.d/S12boot.cycle -> ../boot.cycle
lrwxrwxrwx 1 12 Oct 3 2011 /etc/init.d/boot.d/S12boot.klog -> ../boot.klog
lrwxrwxrwx 1 12 Oct 3 2011 /etc/init.d/boot.d/S12boot.swap -> ../boot.swap
lrwxrwxrwx 1 18 Oct 3 2011 /etc/init.d/boot.d/S12boot.udev_retry ->
../boot.udev_retry
lrwxrwxrwx 1 16 Oct 3 2011 /etc/init.d/boot.d/S13boot.ldconfig ->
../boot.ldconfig
lrwxrwxrwx 1 14 Oct 3 2011 /etc/init.d/boot.d/S13boot.sysctl -> ../boot.sysctl
lrwxrwxrwx 1 16 Oct 3 2011 /etc/init.d/boot.d/S14boot.ipconfig ->
../boot.ipconfig

Do you know why they exist, and why they are named as they are?


--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
This Thread