FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 05-27-2010, 07:13 PM
Sven Joachim
 
Default Dependency based boot sequence conversion

On 2010-05-27 20:26 +0200, Hugo Vanwoerkom wrote:

> I just finished a dist-upgrade (1107 packages) and found out that Sid
> is moving (has moved?) to a dependency based boot sequence.

This happened quite some time ago, yes.

> That explains why the prior dist-upgrade was a failure because the
> partition became unbootable. I since overlaid that partition so I
> cannot research whether insserv was involved or not, but what happened
> is the boot sequence in /etc/rc<x>.d was altered by something and you
> could not boot anymore. It felt unsafe to proceed so I abandoned the
> upgrade.
>
> This time luck would have it that:
>
> ...
> dpkg: considering deconfiguration of sysv-rc, which would be broken by
> installation of insserv ...
> dpkg: yes, will deconfigure sysv-rc (broken by insserv).
> ...

This is normal, no need to worry.

> and
>
> ...
> Setting up sysv-rc (2.88dsf-5) ...
> info: Checking if it is safe to convert to dependency based boot.
>
> error: Unable to migrate to dependency based boot sequencing.
> error: Problems detected:
> ...

I suspect this will happen to many people. If you don't purge removed
old packages, it is expected to have old init scripts around that lack
the LSB headers with the necessary dependency information.

> So I have corrected the errors but before I commit myself with
> 'dpkg-reconfigure sysv-rc' I want to know what the new boot sequence
> *will look like*.

The numbers in the [SK][0-9[0-9]* links will be lower, and the order
will differ somewhat. "Start" links in /etc/rc[06].d will be converted
to stop links.

> I have looked at the dependency graph per
> http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
> but that is too unwieldy: it doesn't fit the screen and doesn't answer
> my question:
>
> What will the boot sequence be when I convert?

This really depends on which init scripts you have.

> Anybody know how to wring that out of insserv?

Try the following (you don't have to be root for that):

$ cp -a /etc/{init,rc?}.d /tmp/
$ /sbin/insserv -p /tmp/init.d/

And inspect the /tmp/rc?.d directories.

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 8739xd9mzd.fsf@turtle.gmx.de">http://lists.debian.org/8739xd9mzd.fsf@turtle.gmx.de
 
Old 05-28-2010, 12:30 AM
Joey Hess
 
Default Dependency based boot sequence conversion

Sven Joachim wrote:
> > What will the boot sequence be when I convert?
> > Anybody know how to wring that out of insserv?
>
> Try the following (you don't have to be root for that):
>
> $ cp -a /etc/{init,rc?}.d /tmp/
> $ /sbin/insserv -p /tmp/init.d/
>
> And inspect the /tmp/rc?.d directories.

I recently converted a fairly stock desktop system to dep based boot.
Here's how git describes the changes (thanks to using etckeeper):

[master c392728] dep based boot
Author: root <root@localhost>
298 files changed, 107 insertions(+), 58 deletions(-)
create mode 100644 init.d/.depend.boot
create mode 100644 init.d/.depend.start
create mode 100644 init.d/.depend.stop
delete mode 100644 init.d/.legacy-bootordering
rename rc0.d/{K11anacron => K01anacron} (100%)
rename rc0.d/{K11atd => K01atd} (100%)
rename rc0.d/{K74bluetooth => K01bluetooth} (100%)
rename rc0.d/{K95collectd => K01collectd} (100%)
rename rc0.d/{K11cron => K01cron} (100%)
rename rc0.d/{K41fuse => K01fuse} (100%)
rename rc0.d/{K20hostapd => K01hostapd} (100%)
rename rc0.d/{K20kerneloops => K01kerneloops} (100%)
rename rc0.d/{K89klogd => K01klogd} (100%)
rename rc0.d/{K15mpd => K01mpd} (100%)
rename rc0.d/{K14mpdscribble => K01mpdscribble} (100%)
rename rc0.d/{K23ntp => K01ntp} (100%)
rename rc0.d/{K20openbsd-inetd => K01openbsd-inetd} (100%)
rename rc0.d/{K80openvpn => K01openvpn} (100%)
rename rc0.d/{K20policycoreutils => K01policycoreutils} (100%)
rename rc0.d/{K20postfix => K01postfix} (100%)
rename rc0.d/{K20saned => K01saned} (100%)
rename rc0.d/{K20termnetd => K01termnetd} (100%)
rename rc0.d/{S30urandom => K01urandom} (100%)
rename rc0.d/{K50alsa-utils => K02alsa-utils} (100%)
rename rc0.d/{K86avahi-daemon => K02avahi-daemon} (100%)
rename rc0.d/{K88network-manager => K02network-manager} (100%)
rename rc0.d/{K21spamassassin => K02spamassassin} (100%)
rename rc0.d/{K90sysklogd => K03sysklogd} (100%)
rename rc0.d/{S20sendsigs => K04sendsigs} (100%)
rename rc0.d/{S31umountnfs.sh => K05umountnfs.sh} (100%)
rename rc0.d/{K20nfs-common => K06nfs-common} (100%)
rename rc0.d/{S32portmap => K06portmap} (100%)
rename rc0.d/{K25hwclock.sh => K07hwclock.sh} (100%)
rename rc0.d/{S35networking => K07networking} (100%)
rename rc0.d/{S36ifupdown => K08ifupdown} (100%)
rename rc0.d/{S40umountfs => K09umountfs} (100%)
rename rc0.d/{S50lvm2 => K10lvm2} (100%)
rename rc0.d/{S60umountroot => K11umountroot} (100%)
rename rc0.d/{S90halt => K12halt} (100%)
rename rc1.d/{K11anacron => K01anacron} (100%)
rename rc1.d/{K11atd => K01atd} (100%)
rename rc1.d/{K74bluetooth => K01bluetooth} (100%)
rename rc1.d/{K95collectd => K01collectd} (100%)
rename rc1.d/{K11cron => K01cron} (100%)
rename rc1.d/{K80cups => K01cups} (100%)
rename rc1.d/{K16hal => K01hal} (100%)
rename rc1.d/{K20hostapd => K01hostapd} (100%)
rename rc1.d/{K20hotkey-setup => K01hotkey-setup} (100%)
rename rc1.d/{K20kerneloops => K01kerneloops} (100%)
rename rc1.d/{K89klogd => K01klogd} (100%)
rename rc1.d/{K15mpd => K01mpd} (100%)
rename rc1.d/{K14mpdscribble => K01mpdscribble} (100%)
rename rc1.d/{K23ntp => K01ntp} (100%)
rename rc1.d/{K20openbsd-inetd => K01openbsd-inetd} (100%)
rename rc1.d/{K80openvpn => K01openvpn} (100%)
rename rc1.d/{K20policycoreutils => K01policycoreutils} (100%)
rename rc1.d/{K20postfix => K01postfix} (100%)
rename rc1.d/{K20saned => K01saned} (100%)
rename rc1.d/{K20termnetd => K01termnetd} (100%)
rename rc1.d/{K86avahi-daemon => K02avahi-daemon} (100%)
rename rc1.d/{K88network-manager => K02network-manager} (100%)
rename rc1.d/{K21spamassassin => K02spamassassin} (100%)
rename rc1.d/{K90sysklogd => K03sysklogd} (100%)
rename rc1.d/{K20nfs-common => K06nfs-common} (100%)
rename rc1.d/{K81portmap => K06portmap} (100%)
rename rc1.d/{S30killprocs => S01killprocs} (100%)
rename rc1.d/{S70bootlogs => S06bootlogs} (100%)
rename rc1.d/{S90single => S07single} (100%)
rename rc2.d/{S20hostapd => S01hostapd} (100%)
rename rc2.d/{S30mpd => S01mpd} (100%)
rename rc2.d/{S75sudo => S01sudo} (100%)
rename rc2.d/{S10sysklogd => S01sysklogd} (100%)
rename rc2.d/{S12acpid => S02acpid} (100%)
rename rc2.d/{S89anacron => S02anacron} (100%)
rename rc2.d/{S89atd => S02atd} (100%)
rename rc2.d/{S95collectd => S02collectd} (100%)
rename rc2.d/{S89cron => S02cron} (100%)
rename rc2.d/{S12dbus => S02dbus} (100%)
rename rc2.d/{S20hotkey-setup => S02hotkey-setup} (100%)
rename rc2.d/{S11klogd => S02klogd} (100%)
rename rc2.d/{S05loadcpufreq => S02loadcpufreq} (100%)
rename rc2.d/{S31mpdscribble => S02mpdscribble} (100%)
rename rc2.d/{S23ntp => S02ntp} (100%)
rename rc2.d/{S20openbsd-inetd => S02openbsd-inetd} (100%)
rename rc2.d/{S50rsync => S02rsync} (100%)
rename rc2.d/{S19spamassassin => S02spamassassin} (100%)
rename rc2.d/{S16ssh => S02ssh} (100%)
rename rc2.d/{S20termnetd => S02termnetd} (100%)
rename rc2.d/{S14avahi-daemon => S03avahi-daemon} (100%)
rename rc2.d/{S25bluetooth => S03bluetooth} (100%)
rename rc2.d/{S20cpufrequtils => S03cpufrequtils} (100%)
rename rc2.d/{S24hal => S03hal} (100%)
rename rc2.d/{S20postfix => S03postfix} (100%)
rename rc2.d/{S16openvpn => S04openvpn} (100%)
rename rc2.d/{S50cups => S05cups} (100%)
rename rc2.d/{S30gdm => S05gdm} (100%)
rename rc2.d/{S20saned => S05saned} (100%)
rename rc2.d/{S70bootlogs => S06bootlogs} (100%)
rename rc2.d/{S43portmap => S15portmap} (100%)
rename rc2.d/{S20nfs-common => S16nfs-common} (100%)
rename rc2.d/{S20policycoreutils => S19policycoreutils} (100%)
rename rc2.d/{S99rc.local => S20rc.local} (100%)
rename rc2.d/{S99rmnologin => S20rmnologin} (100%)
rename rc2.d/{S99stop-bootlogd => S20stop-bootlogd} (100%)
rename rc3.d/{S20hostapd => S01hostapd} (100%)
rename rc3.d/{S30mpd => S01mpd} (100%)
rename rc3.d/{S75sudo => S01sudo} (100%)
rename rc3.d/{S10sysklogd => S01sysklogd} (100%)
rename rc3.d/{S12acpid => S02acpid} (100%)
rename rc3.d/{S89anacron => S02anacron} (100%)
rename rc3.d/{S89atd => S02atd} (100%)
rename rc3.d/{S95collectd => S02collectd} (100%)
rename rc3.d/{S89cron => S02cron} (100%)
rename rc3.d/{S12dbus => S02dbus} (100%)
rename rc3.d/{S20hotkey-setup => S02hotkey-setup} (100%)
rename rc3.d/{S20kerneloops => S02kerneloops} (100%)
rename rc3.d/{S11klogd => S02klogd} (100%)
rename rc3.d/{S05loadcpufreq => S02loadcpufreq} (100%)
rename rc3.d/{S31mpdscribble => S02mpdscribble} (100%)
rename rc3.d/{S23ntp => S02ntp} (100%)
rename rc3.d/{S20openbsd-inetd => S02openbsd-inetd} (100%)
rename rc3.d/{S50rsync => S02rsync} (100%)
rename rc3.d/{S19spamassassin => S02spamassassin} (100%)
rename rc3.d/{S16ssh => S02ssh} (100%)
rename rc3.d/{S20termnetd => S02termnetd} (100%)
rename rc3.d/{S14avahi-daemon => S03avahi-daemon} (100%)
rename rc3.d/{S25bluetooth => S03bluetooth} (100%)
rename rc3.d/{S20cpufrequtils => S03cpufrequtils} (100%)
rename rc3.d/{S24hal => S03hal} (100%)
rename rc3.d/{S26network-manager => S03network-manager} (100%)
rename rc3.d/{S20postfix => S03postfix} (100%)
rename rc3.d/{S16openvpn => S04openvpn} (100%)
rename rc3.d/{S50cups => S05cups} (100%)
rename rc3.d/{S30gdm => S05gdm} (100%)
rename rc3.d/{S20saned => S05saned} (100%)
rename rc3.d/{S70bootlogs => S06bootlogs} (100%)
rename rc3.d/{S43portmap => S15portmap} (100%)
rename rc3.d/{S20nfs-common => S16nfs-common} (100%)
rename rc3.d/{S20policycoreutils => S19policycoreutils} (100%)
rename rc3.d/{S99rc.local => S20rc.local} (100%)
rename rc3.d/{S99rmnologin => S20rmnologin} (100%)
rename rc3.d/{S99stop-bootlogd => S20stop-bootlogd} (100%)
rename rc4.d/{S20hostapd => S01hostapd} (100%)
rename rc4.d/{S30mpd => S01mpd} (100%)
rename rc4.d/{S75sudo => S01sudo} (100%)
rename rc4.d/{S10sysklogd => S01sysklogd} (100%)
rename rc4.d/{S12acpid => S02acpid} (100%)
rename rc4.d/{S89anacron => S02anacron} (100%)
rename rc4.d/{S89atd => S02atd} (100%)
rename rc4.d/{S95collectd => S02collectd} (100%)
rename rc4.d/{S89cron => S02cron} (100%)
rename rc4.d/{S12dbus => S02dbus} (100%)
rename rc4.d/{S20hotkey-setup => S02hotkey-setup} (100%)
rename rc4.d/{S20kerneloops => S02kerneloops} (100%)
rename rc4.d/{S11klogd => S02klogd} (100%)
rename rc4.d/{S05loadcpufreq => S02loadcpufreq} (100%)
rename rc4.d/{S31mpdscribble => S02mpdscribble} (100%)
rename rc4.d/{S23ntp => S02ntp} (100%)
rename rc4.d/{S20openbsd-inetd => S02openbsd-inetd} (100%)
rename rc4.d/{S50rsync => S02rsync} (100%)
rename rc4.d/{S19spamassassin => S02spamassassin} (100%)
rename rc4.d/{S16ssh => S02ssh} (100%)
rename rc4.d/{S20termnetd => S02termnetd} (100%)
rename rc4.d/{S14avahi-daemon => S03avahi-daemon} (100%)
rename rc4.d/{S25bluetooth => S03bluetooth} (100%)
rename rc4.d/{S20cpufrequtils => S03cpufrequtils} (100%)
rename rc4.d/{S24hal => S03hal} (100%)
rename rc4.d/{S26network-manager => S03network-manager} (100%)
rename rc4.d/{S20postfix => S03postfix} (100%)
rename rc4.d/{S16openvpn => S04openvpn} (100%)
rename rc4.d/{S50cups => S05cups} (100%)
rename rc4.d/{S30gdm => S05gdm} (100%)
rename rc4.d/{S20saned => S05saned} (100%)
rename rc4.d/{S70bootlogs => S06bootlogs} (100%)
rename rc4.d/{S43portmap => S15portmap} (100%)
rename rc4.d/{S20nfs-common => S16nfs-common} (100%)
rename rc4.d/{S20policycoreutils => S19policycoreutils} (100%)
rename rc4.d/{S99rc.local => S20rc.local} (100%)
rename rc4.d/{S99rmnologin => S20rmnologin} (100%)
rename rc4.d/{S99stop-bootlogd => S20stop-bootlogd} (100%)
rename rc5.d/{S20hostapd => S01hostapd} (100%)
rename rc5.d/{S30mpd => S01mpd} (100%)
rename rc5.d/{S75sudo => S01sudo} (100%)
rename rc5.d/{S10sysklogd => S01sysklogd} (100%)
rename rc5.d/{S12acpid => S02acpid} (100%)
rename rc5.d/{S89anacron => S02anacron} (100%)
rename rc5.d/{S89atd => S02atd} (100%)
rename rc5.d/{S95collectd => S02collectd} (100%)
rename rc5.d/{S89cron => S02cron} (100%)
rename rc5.d/{S12dbus => S02dbus} (100%)
rename rc5.d/{S20hotkey-setup => S02hotkey-setup} (100%)
rename rc5.d/{S20kerneloops => S02kerneloops} (100%)
rename rc5.d/{S11klogd => S02klogd} (100%)
rename rc5.d/{S05loadcpufreq => S02loadcpufreq} (100%)
rename rc5.d/{S31mpdscribble => S02mpdscribble} (100%)
rename rc5.d/{S23ntp => S02ntp} (100%)
rename rc5.d/{S20openbsd-inetd => S02openbsd-inetd} (100%)
rename rc5.d/{S50rsync => S02rsync} (100%)
rename rc5.d/{S19spamassassin => S02spamassassin} (100%)
rename rc5.d/{S16ssh => S02ssh} (100%)
rename rc5.d/{S20termnetd => S02termnetd} (100%)
rename rc5.d/{S14avahi-daemon => S03avahi-daemon} (100%)
rename rc5.d/{S25bluetooth => S03bluetooth} (100%)
rename rc5.d/{S20cpufrequtils => S03cpufrequtils} (100%)
rename rc5.d/{S24hal => S03hal} (100%)
rename rc5.d/{S26network-manager => S03network-manager} (100%)
rename rc5.d/{S20postfix => S03postfix} (100%)
rename rc5.d/{S16openvpn => S04openvpn} (100%)
rename rc5.d/{S50cups => S05cups} (100%)
rename rc5.d/{S30gdm => S05gdm} (100%)
rename rc5.d/{S20saned => S05saned} (100%)
rename rc5.d/{S70bootlogs => S06bootlogs} (100%)
rename rc5.d/{S43portmap => S15portmap} (100%)
rename rc5.d/{S20nfs-common => S16nfs-common} (100%)
rename rc5.d/{S20policycoreutils => S19policycoreutils} (100%)
rename rc5.d/{S99rc.local => S20rc.local} (100%)
rename rc5.d/{S99rmnologin => S20rmnologin} (100%)
rename rc5.d/{S99stop-bootlogd => S20stop-bootlogd} (100%)
rename rc6.d/{K11anacron => K01anacron} (100%)
rename rc6.d/{K11atd => K01atd} (100%)
rename rc6.d/{K74bluetooth => K01bluetooth} (100%)
rename rc6.d/{K95collectd => K01collectd} (100%)
rename rc6.d/{K11cron => K01cron} (100%)
rename rc6.d/{K41fuse => K01fuse} (100%)
rename rc6.d/{K20hostapd => K01hostapd} (100%)
rename rc6.d/{K20kerneloops => K01kerneloops} (100%)
rename rc6.d/{K89klogd => K01klogd} (100%)
rename rc6.d/{K15mpd => K01mpd} (100%)
rename rc6.d/{K14mpdscribble => K01mpdscribble} (100%)
rename rc6.d/{K23ntp => K01ntp} (100%)
rename rc6.d/{K20openbsd-inetd => K01openbsd-inetd} (100%)
rename rc6.d/{K80openvpn => K01openvpn} (100%)
rename rc6.d/{K20policycoreutils => K01policycoreutils} (100%)
rename rc6.d/{K20postfix => K01postfix} (100%)
rename rc6.d/{K20saned => K01saned} (100%)
rename rc6.d/{K20termnetd => K01termnetd} (100%)
rename rc6.d/{S30urandom => K01urandom} (100%)
rename rc6.d/{K50alsa-utils => K02alsa-utils} (100%)
rename rc6.d/{K86avahi-daemon => K02avahi-daemon} (100%)
rename rc6.d/{K88network-manager => K02network-manager} (100%)
rename rc6.d/{K21spamassassin => K02spamassassin} (100%)
rename rc6.d/{K90sysklogd => K03sysklogd} (100%)
rename rc6.d/{S20sendsigs => K04sendsigs} (100%)
rename rc6.d/{S31umountnfs.sh => K05umountnfs.sh} (100%)
rename rc6.d/{K20nfs-common => K06nfs-common} (100%)
rename rc6.d/{S32portmap => K06portmap} (100%)
rename rc6.d/{K25hwclock.sh => K07hwclock.sh} (100%)
rename rc6.d/{S35networking => K07networking} (100%)
rename rc6.d/{S36ifupdown => K08ifupdown} (100%)
rename rc6.d/{S40umountfs => K09umountfs} (100%)
rename rc6.d/{S50lvm2 => K10lvm2} (100%)
rename rc6.d/{S60umountroot => K11umountroot} (100%)
rename rc6.d/{S90reboot => K12reboot} (100%)
rename rcS.d/{S02mountkernfs.sh => S01mountkernfs.sh} (100%)
rename rcS.d/{S03udev => S02udev} (100%)
rename rcS.d/{S04mountdevsubfs.sh => S03mountdevsubfs.sh} (100%)
rename rcS.d/{S05bootlogd => S04bootlogd} (100%)
rename rcS.d/{S02hostname.sh => S07hostname.sh} (100%)
rename rcS.d/{S08hwclockfirst.sh => S07hwclockfirst.sh} (100%)
rename rcS.d/{S26lvm2 => S07lvm2} (100%)
rename rcS.d/{S10checkroot.sh => S08checkroot.sh} (100%)
rename rcS.d/{S31hibernate => S09hibernate} (100%)
rename rcS.d/{S11hwclock.sh => S09hwclock.sh} (100%)
rename rcS.d/{S18ifupdown-clean => S09ifupdown-clean} (100%)
rename rcS.d/{S20module-init-tools => S09module-init-tools} (100%)
rename rcS.d/{S12mtab.sh => S09mtab.sh} (100%)
rename rcS.d/{S30checkfs.sh => S10checkfs.sh} (100%)
rename rcS.d/{S39ifupdown => S11ifupdown} (100%)
rename rcS.d/{S35mountall.sh => S11mountall.sh} (100%)
rename rcS.d/{S36mountall-bootclean.sh => S12mountall-bootclean.sh} (100%)
rename rcS.d/{S37mountoverflowtmp => S13mountoverflowtmp} (100%)
rename rcS.d/{S40networking => S14networking} (100%)
rename rcS.d/{S30procps => S14procps} (100%)
rename rcS.d/{S36udev-mtab => S14udev-mtab} (100%)
rename rcS.d/{S70x11-common => S14x11-common} (100%)
rename rcS.d/{S45mountnfs.sh => S15mountnfs.sh} (100%)
rename rcS.d/{S43portmap => S15portmap} (100%)
rename rcS.d/{S46mountnfs-bootclean.sh => S16mountnfs-bootclean.sh} (100%)
rename rcS.d/{S44nfs-common => S16nfs-common} (100%)
rename rcS.d/{S48console-screen.sh => S17console-screen.sh} (100%)
rename rcS.d/{S49console-setup => S18console-setup} (100%)
rename rcS.d/{S50alsa-utils => S19alsa-utils} (100%)
rename rcS.d/{S55bootmisc.sh => S19bootmisc.sh} (100%)
rename rcS.d/{S34fuse => S19fuse} (100%)
rename rcS.d/{S47lm-sensors => S19lm-sensors} (100%)
rename rcS.d/{S20policycoreutils => S19policycoreutils} (100%)
rename rcS.d/{S70screen-cleanup => S19screen-cleanup} (100%)
rename rcS.d/{S55urandom => S19urandom} (100%)
rename rcS.d/{S99stop-bootlogd-single => S20stop-bootlogd-single} (100%)

--
see shy jo
 
Old 05-28-2010, 05:28 AM
Phil Requirements
 
Default Dependency based boot sequence conversion

On 2010-05-27 20:30:09 -0400, Joey Hess wrote:
>Sven Joachim wrote:
>>> What will the boot sequence be when I convert?
>>> Anybody know how to wring that out of insserv?
>>
>> Try the following (you don't have to be root for that):
>>
>> $ cp -a /etc/{init,rc?}.d /tmp/
>> $ /sbin/insserv -p /tmp/init.d/
>>
>> And inspect the /tmp/rc?.d directories.
>
>I recently converted a fairly stock desktop system to dep based boot.
>Here's how git describes the changes (thanks to using etckeeper):
>
>[master c392728] dep based boot
> Author: root <root@localhost>
> 298 files changed, 107 insertions(+), 58 deletions(-)
> create mode 100644 init.d/.depend.boot
> create mode 100644 init.d/.depend.start
> create mode 100644 init.d/.depend.stop


I think the short answer is the rc directories will look almost
exactly the same, but the numbers change.

I changed to dependency-based booting a while back. Some time later, I
wanted to make MySQL not start at boot. I looked in the rc dirs and
thought, "What the heck? I thought these were going to change?"
They looked the same as ever.

I was expecting them to go away and be replaced by a ???
Maybe some kind of binary config file? Held only in memory??
What does it mean, this awful sounding 'dependency-based booting'?

Glad to find out it didn't change too much.

Phil


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100528052809.GA13916@kasploosh.net">http://lists.debian.org/20100528052809.GA13916@kasploosh.net
 
Old 05-29-2010, 05:12 PM
Hugo Vanwoerkom
 
Default Dependency based boot sequence conversion

Sven Joachim wrote:

On 2010-05-27 20:26 +0200, Hugo Vanwoerkom wrote:


I just finished a dist-upgrade (1107 packages) and found out that Sid
is moving (has moved?) to a dependency based boot sequence.


This happened quite some time ago, yes.


That explains why the prior dist-upgrade was a failure because the
partition became unbootable. I since overlaid that partition so I
cannot research whether insserv was involved or not, but what happened
is the boot sequence in /etc/rc<x>.d was altered by something and you
could not boot anymore. It felt unsafe to proceed so I abandoned the
upgrade.

This time luck would have it that:

...
dpkg: considering deconfiguration of sysv-rc, which would be broken by
installation of insserv ...
dpkg: yes, will deconfigure sysv-rc (broken by insserv).
...


This is normal, no need to worry.


and

...
Setting up sysv-rc (2.88dsf-5) ...
info: Checking if it is safe to convert to dependency based boot.

error: Unable to migrate to dependency based boot sequencing.
error: Problems detected:
...


I suspect this will happen to many people. If you don't purge removed
old packages, it is expected to have old init scripts around that lack
the LSB headers with the necessary dependency information.


So I have corrected the errors but before I commit myself with
'dpkg-reconfigure sysv-rc' I want to know what the new boot sequence
*will look like*.


The numbers in the [SK][0-9[0-9]* links will be lower, and the order
will differ somewhat. "Start" links in /etc/rc[06].d will be converted
to stop links.


I have looked at the dependency graph per
http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
but that is too unwieldy: it doesn't fit the screen and doesn't answer
my question:

What will the boot sequence be when I convert?


This really depends on which init scripts you have.


Anybody know how to wring that out of insserv?


Try the following (you don't have to be root for that):

$ cp -a /etc/{init,rc?}.d /tmp/
$ /sbin/insserv -p /tmp/init.d/

And inspect the /tmp/rc?.d directories.



Sven, That is exactly the trick that I was looking for.
The result looks scary :-(

Hugo


















--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: htrhts$ubq$1@dough.gmane.org">http://lists.debian.org/htrhts$ubq$1@dough.gmane.org
 
Old 05-29-2010, 05:59 PM
Sven Joachim
 
Default Dependency based boot sequence conversion

On 2010-05-29 19:12 +0200, Hugo Vanwoerkom wrote:

> Sven Joachim wrote:
>> On 2010-05-27 20:26 +0200, Hugo Vanwoerkom wrote:
>>
>>> Anybody know how to wring that out of insserv?
>>
>> Try the following (you don't have to be root for that):
>>
>> $ cp -a /etc/{init,rc?}.d /tmp/
>> $ /sbin/insserv -p /tmp/init.d/
>>
>> And inspect the /tmp/rc?.d directories.
>>
>
> Sven, That is exactly the trick that I was looking for.
> The result looks scary :-(

Why? Only because it is unfamiliar? Or do you have concrete indication
that the boot order is not correct?

I've been using insserv for almost two years, and when I now look at the
backup of /etc/rc?d which it made, _that_ looks scary to me, because the
order of the symlinks and their numbers appear to be without logic,
almost random.

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87hblq1tdx.fsf@turtle.gmx.de">http://lists.debian.org/87hblq1tdx.fsf@turtle.gmx.de
 
Old 05-30-2010, 02:07 PM
Hugo Vanwoerkom
 
Default Dependency based boot sequence conversion

Sven Joachim wrote:

On 2010-05-29 19:12 +0200, Hugo Vanwoerkom wrote:


Sven Joachim wrote:

On 2010-05-27 20:26 +0200, Hugo Vanwoerkom wrote:


Anybody know how to wring that out of insserv?

Try the following (you don't have to be root for that):

$ cp -a /etc/{init,rc?}.d /tmp/
$ /sbin/insserv -p /tmp/init.d/

And inspect the /tmp/rc?.d directories.


Sven, That is exactly the trick that I was looking for.
The result looks scary :-(


Why? Only because it is unfamiliar? Or do you have concrete indication
that the boot order is not correct?

I've been using insserv for almost two years, and when I now look at the
backup of /etc/rc?d which it made, _that_ looks scary to me, because the
order of the symlinks and their numbers appear to be without logic,
almost random.



It just is not correct. This is what the start sequence in /etc/rc6.d
before using insserv looks like:


S20sendsigs [1]
S30rsyslog
S30urandom
S31umountnfs.sh
S35networking
S36firehol
S36ifupdown
S40umountfs
S60mdadm-raid
S60umountroot


S90reboot

and this is what it looks like after insserv:

S01reboot [2]
S01sendsigs
S01umountfs
S01umountnfs.sh
S01umountroot
S02rsyslog
S03mdadm-raid
S11ifupdown
S14networking
S15firehol
S19urandom

Reboot first before anything else?
So I changed that to S90reboot but still something went wrong: the root
fs was not unmounted right because at reboot he complained.
So I changed it back to what it was before as in [1] by hardcoding the
priorities.


Secondly insserv got invoked when I wasn't looking: by the VMware server
installer :-( I had rebooted using kernel 2.6.34 from kernel.org and
installed the VMware server, to see if he had problems with that new
kernel version. Unbeknownst to me, he invokes insserv so dependency
based boot was no longer only a test: it was a fact.


I have tried for the last 3 hours to make [2] look like [1] using the
script headers, but no luck thusfar, I'd be grateful for some pointers,
how does one make [2] look like [1] not by hardcoding the priorities but
by using the script headers?


Even if you manage that, you are changing data that you then have to
track at every upgrade.


Thanks.

Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: httreq$qaj$1@dough.gmane.org">http://lists.debian.org/httreq$qaj$1@dough.gmane.org
 
Old 05-30-2010, 02:36 PM
Sven Joachim
 
Default Dependency based boot sequence conversion

On 2010-05-30 16:07 +0200, Hugo Vanwoerkom wrote:

> Sven Joachim wrote:
>> On 2010-05-29 19:12 +0200, Hugo Vanwoerkom wrote:
>>
>>> The result looks scary :-(
>>
>> Why? Only because it is unfamiliar? Or do you have concrete indication
>> that the boot order is not correct?
>>
>> I've been using insserv for almost two years, and when I now look at the
>> backup of /etc/rc?d which it made, _that_ looks scary to me, because the
>> order of the symlinks and their numbers appear to be without logic,
>> almost random.
>>
>
> It just is not correct. This is what the start sequence in /etc/rc6.d
> before using insserv looks like:
>
> S20sendsigs [1]
> S30rsyslog
> S30urandom
> S31umountnfs.sh
> S35networking
> S36firehol
> S36ifupdown
> S40umountfs
> S60mdadm-raid
> S60umountroot
>
> S90reboot

The fact that you actually have any Snn* links in /etc/rc6.d is an
artifact of the old boot system with fixed numbers. When you migrate to
dependency-based boot system, these will be converted to Knn* links (the
initscripts package special-cases runlevels 0 and 6, calling all scripts
with a stop argument, even for "start" links).

> and this is what it looks like after insserv:
>
> S01reboot [2]
> S01sendsigs
> S01umountfs
> S01umountnfs.sh
> S01umountroot
> S02rsyslog
> S03mdadm-raid
> S11ifupdown
> S14networking
> S15firehol
> S19urandom

This is indeed not correct, but the conversion will turn these into Knn*
links first, and then you'll get a very different order. Here's mine
for reference:

,----
| $ ls -1 /etc/rc6.d
| K01alsa-utils
| K01anacron
| K01atd
| K01gpm
| K01lpd
| K01nfs-kernel-server
| K01postfix
| K01stop-readahead-fedora
| K01timidity
| K01urandom
| K01xdm
| K02bind9
| K03sendsigs
| K04rsyslog
| K05umountnfs.sh
| K06nfs-common
| K06portmap
| K07hwclock.sh
| K07networking
| K08ifupdown
| K09umountfs
| K10umountroot
| K11reboot
| README
`----

> Secondly insserv got invoked when I wasn't looking: by the VMware
> server installer :-( I had rebooted using kernel 2.6.34 from
> kernel.org and installed the VMware server, to see if he had problems
> with that new kernel version. Unbeknownst to me, he invokes insserv so
> dependency based boot was no longer only a test: it was a fact.

I'm sorry that this happened to you.

> I have tried for the last 3 hours to make [2] look like [1] using the
> script headers, but no luck thusfar, I'd be grateful for some
> pointers, how does one make [2] look like [1] not by hardcoding the
> priorities but by using the script headers?

By running "dpkg-reconfigure sysv-rc". Note that this will convert S*
links in runlevels 0 and 6 to K* links, but as I tried to explain, this
is what you want.

> Even if you manage that, you are changing data that you then have to
> track at every upgrade.

You don't have to do that, insserv does it for you.

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87fx1978yh.fsf@turtle.gmx.de">http://lists.debian.org/87fx1978yh.fsf@turtle.gmx.de
 
Old 05-30-2010, 04:00 PM
Hugo Vanwoerkom
 
Default Dependency based boot sequence conversion

Sven Joachim wrote:

On 2010-05-30 16:07 +0200, Hugo Vanwoerkom wrote:


Sven Joachim wrote:

On 2010-05-29 19:12 +0200, Hugo Vanwoerkom wrote:


The result looks scary :-(

Why? Only because it is unfamiliar? Or do you have concrete indication
that the boot order is not correct?

I've been using insserv for almost two years, and when I now look at the
backup of /etc/rc?d which it made, _that_ looks scary to me, because the
order of the symlinks and their numbers appear to be without logic,
almost random.


It just is not correct. This is what the start sequence in /etc/rc6.d
before using insserv looks like:

S20sendsigs [1]
S30rsyslog
S30urandom
S31umountnfs.sh
S35networking
S36firehol
S36ifupdown
S40umountfs
S60mdadm-raid
S60umountroot


S90reboot


The fact that you actually have any Snn* links in /etc/rc6.d is an
artifact of the old boot system with fixed numbers. When you migrate to
dependency-based boot system, these will be converted to Knn* links (the
initscripts package special-cases runlevels 0 and 6, calling all scripts
with a stop argument, even for "start" links).


and this is what it looks like after insserv:

S01reboot [2]
S01sendsigs
S01umountfs
S01umountnfs.sh
S01umountroot
S02rsyslog
S03mdadm-raid
S11ifupdown
S14networking
S15firehol
S19urandom


This is indeed not correct, but the conversion will turn these into Knn*
links first, and then you'll get a very different order. Here's mine
for reference:

,----
| $ ls -1 /etc/rc6.d
| K01alsa-utils
| K01anacron
| K01atd
| K01gpm
| K01lpd
| K01nfs-kernel-server
| K01postfix
| K01stop-readahead-fedora
| K01timidity
| K01urandom
| K01xdm
| K02bind9
| K03sendsigs
| K04rsyslog
| K05umountnfs.sh
| K06nfs-common
| K06portmap
| K07hwclock.sh
| K07networking
| K08ifupdown
| K09umountfs
| K10umountroot
| K11reboot
| README
`----


Secondly insserv got invoked when I wasn't looking: by the VMware
server installer :-( I had rebooted using kernel 2.6.34 from
kernel.org and installed the VMware server, to see if he had problems
with that new kernel version. Unbeknownst to me, he invokes insserv so
dependency based boot was no longer only a test: it was a fact.


I'm sorry that this happened to you.


I have tried for the last 3 hours to make [2] look like [1] using the
script headers, but no luck thusfar, I'd be grateful for some
pointers, how does one make [2] look like [1] not by hardcoding the
priorities but by using the script headers?


By running "dpkg-reconfigure sysv-rc". Note that this will convert S*
links in runlevels 0 and 6 to K* links, but as I tried to explain, this
is what you want.


Even if you manage that, you are changing data that you then have to
track at every upgrade.


You don't have to do that, insserv does it for you.



Thanks Sven, Good explanation! I will back up the system and
"dpkg-reconfigure sysv-rc" and see what happens. My lack of
understanding of sysv-rc, thanks again for your time.


Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: htu22m$ema$1@dough.gmane.org">http://lists.debian.org/htu22m$ema$1@dough.gmane.org
 
Old 05-30-2010, 06:01 PM
Hugo Vanwoerkom
 
Default Dependency based boot sequence conversion

Hugo Vanwoerkom wrote:

Sven Joachim wrote:

On 2010-05-30 16:07 +0200, Hugo Vanwoerkom wrote:


Sven Joachim wrote:

On 2010-05-29 19:12 +0200, Hugo Vanwoerkom wrote:


The result looks scary :-(
Why? Only because it is unfamiliar? Or do you have concrete
indication

that the boot order is not correct?

I've been using insserv for almost two years, and when I now look at
the
backup of /etc/rc?d which it made, _that_ looks scary to me, because
the

order of the symlinks and their numbers appear to be without logic,
almost random.


It just is not correct. This is what the start sequence in /etc/rc6.d
before using insserv looks like:

S20sendsigs [1]
S30rsyslog
S30urandom
S31umountnfs.sh
S35networking
S36firehol
S36ifupdown
S40umountfs
S60mdadm-raid
S60umountroot
S90reboot


The fact that you actually have any Snn* links in /etc/rc6.d is an
artifact of the old boot system with fixed numbers. When you migrate to
dependency-based boot system, these will be converted to Knn* links (the
initscripts package special-cases runlevels 0 and 6, calling all scripts
with a stop argument, even for "start" links).


and this is what it looks like after insserv:

S01reboot [2]
S01sendsigs
S01umountfs
S01umountnfs.sh
S01umountroot
S02rsyslog
S03mdadm-raid
S11ifupdown
S14networking
S15firehol
S19urandom


This is indeed not correct, but the conversion will turn these into Knn*
links first, and then you'll get a very different order. Here's mine
for reference:

,----
| $ ls -1 /etc/rc6.d
| K01alsa-utils
| K01anacron
| K01atd
| K01gpm
| K01lpd
| K01nfs-kernel-server
| K01postfix
| K01stop-readahead-fedora
| K01timidity
| K01urandom
| K01xdm
| K02bind9
| K03sendsigs
| K04rsyslog
| K05umountnfs.sh
| K06nfs-common
| K06portmap
| K07hwclock.sh
| K07networking
| K08ifupdown
| K09umountfs
| K10umountroot
| K11reboot
| README
`----


Secondly insserv got invoked when I wasn't looking: by the VMware
server installer :-( I had rebooted using kernel 2.6.34 from
kernel.org and installed the VMware server, to see if he had problems
with that new kernel version. Unbeknownst to me, he invokes insserv so
dependency based boot was no longer only a test: it was a fact.


I'm sorry that this happened to you.


I have tried for the last 3 hours to make [2] look like [1] using the
script headers, but no luck thusfar, I'd be grateful for some
pointers, how does one make [2] look like [1] not by hardcoding the
priorities but by using the script headers?


By running "dpkg-reconfigure sysv-rc". Note that this will convert S*
links in runlevels 0 and 6 to K* links, but as I tried to explain, this
is what you want.


Even if you manage that, you are changing data that you then have to
track at every upgrade.


You don't have to do that, insserv does it for you.



Thanks Sven, Good explanation! I will back up the system and
"dpkg-reconfigure sysv-rc" and see what happens. My lack of
understanding of sysv-rc, thanks again for your time.




Did the reconfigure. Boots and halts/reboots faster.
Thanks again Sven.

Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: htu964$4ld$1@dough.gmane.org">http://lists.debian.org/htu964$4ld$1@dough.gmane.org
 

Thread Tools




All times are GMT. The time now is 08:24 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org