Re: [Devil-linux-develop] [PATCH] boot

[Roland P. <pa...@ta...>]

On Thursday 04 March 2004 22:32, Roland Pabel wrote:
> On Thursday 04 March 2004 22:12, hzu...@ra... wrote:
> > On 03/04/2004 03:49:05 PM Roland Pabel wrote:
> > >On Thursday 04 March 2004 20:09, Heiko Zuerker wrote:
> > >> > Hi,
>
> [...]
>
> > I probably understood it wrong.
> > My main concern is that insserv is able to order the scripts in boot.d,
> > that's all.
>
> well, insserv is able to do that. But it ordered the 6 scripts in my vmware
> session to the exact same sequence as they were in my (running) 1.0.4...
let me clarify this: The 6 scripts are
S01checkfs -> ../checkfs
S02mountfs -> ../mountfs
S03setfileperm -> ../setfileperm
S04localnet -> ../localnet
S05setclock -> ../setclock
S06loadkeys -> ../loadkeys
and were linked by insserv in /etc/init.d/rcS.d/ because of their header entry
# Default-Start:  S
They were called from inittab by "/etc/init.d/rc S".
All I did was move them over to /etc/init.d/boot.d/, which insserv does 
conveniently when writing
# Default-Start:  B
instead. They are now called from /etc/init.d/boot at the end (which itself is 
started by init), so we don't need to create a link for that file 
in /etc/init.d/rcS.d/ explicitly. (insserv definitely can't mess 
with/etc/init.d/boot, it got no INIT INFO header...)
So whatever concerns you have with insserv and boot.d/ must have been present 
with rcS.d, too...Or haven't they? 
The only problem I could think of is: If a user adds a script to this mode, it 
might be called before mountfs...but that shouldn't happen very often, most 
people only need 'boot.local' and don't add scripts (especially scripts with 
proper INIT INFO declarations)
Roland
-- 
ICQ UIN 49339118	Linux Counter #88774
GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...>