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

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

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...
What is your concern there? I don't see a problem...

[...]
> >I thought about this at the gym, I think I can easily code that
> >in /sbin/pre_init, when I can manually change inittab (replacing the
> >default
> >runlevel with sed and grep) before starting init. That's under the
> >assumption, that once init runs, there is no point to doing that
> >(otherwise,
> >that could be done in a boot.d/ script before entering the runlevel)
>
> Do you need to code anything?
well, yes...
> Try just to add the "1" to the kernel boot parameters in the boot menu.
Do you want to duplicate all entries in isolinux.cfg to pass the runlevel to 
the kernel cmdline? I know that works with lilo, but the really handy part is 
that you can specify any parameters freely...is that possible with isolinux 
on CD?
> With a bit luck it's really that easy (should be at least)
well, an additional static runlevel config in isolinux.cfg is easy, but it's 
static...
Roland
-- 
ICQ UIN 49339118	Linux Counter #88774
GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...>