Re: Runnlevels are not entered (LILO prompt)
An update.
On Sun, Jun 10, 2018 at 08:03:31PM +0300, Reco wrote:
> Hi.
>
> On Sun, Jun 10, 2018 at 07:06:57PM +0300, Michelle Konzack wrote:
> > Am 2018-06-10 hackte Reco in die Tasten:
> > > Hi.
> > >
> > > On Sun, Jun 10, 2018 at 02:25:30PM +0300, Michelle Konzack wrote:
> > >> Good day,
> > >>
> > >> I run Stretch on my Laptop with sysvinit.
> > >>
> > >> I had setup some profiles and tried to start them by passing 2, 3,
> > >> 4, 5 at the end of the Kernel commandline (I use LILO) but the
> > >> appropriated runnlevel ist not entered.
> > >>
> > >> Do I mis something?
> > >
> > > Whatever you did to LILO you did it wrong.
> >
> > I have this parameter in "append" of each kernel section since ages!
> > to be more precise, since Woody and it was working!
>
> Multiple exclamation signs are not a valid substitute for a
> configuration file. Please show an appropriate lilo.conf snippet.
Installed fresh Debian stretch installation.
Installed lilo.
Added this to lilo.conf:
append = "4"
Ran /sbin/lilo. Rebooted.
> > > Check your /proc/cmdline
> > > after the boot.
> > > Every init I've tested assumes a runlevel passed as a last argument of
> > > /proc/cmdline.
> >
> > It show at the end 2/3/4 depending how I boot, but after login I am
> > in the default runlevel 2.
>
> Again, show, do not tell.
> Install bootlogd, attach fresh /var/log/boot to your e-mail.
> Show /proc/cmdline. Post the output of 'who -r'.
After the reboot, /var/log/bootlogd contained:
INIT: Entering runlevel: 4
"who -r" showed current runlevel 4, last runlevel S.
Therefore, lilo worked as intended.
Took me 15 minutes to do all this.
Reco
Reply to: