Bug#442289: 25configure_init: misunderstood?
- Subject: Bug#442289: 25configure_init: misunderstood?
- From: fboiteux at calistel.com (Frédéric BOITEUX)
- Date: Wed, 4 Jun 2008 07:35:42 +0200
- Message-id: <20080604073542.5e1f6a12@Prem3s.lanvoc>
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org>
Le ven 30 mai 2008 15:26:12 CEST, "Alex Owen" <r.alex.owen at gmail.com> a
> I think 25configure init is misunderstood by some.. or maybe it is just me!
> Some time ago I wrote casper-getty which is now live-getty.
> The idea is that where ever /sbin/getty appears in the default debian
> inittab 25configrue init replaces it with /sbin/casper-getty (or now
> /sbin/live-getty) and you get to login on the VGA console.
> I then extended the idea to detect from kernel command line if a
> serial console is in use.
> If a serial console is in use then a serial console line is written
> into the default debian /etc/inittab using /sbin/casper-getty (or now
> /sbin/live-getty) and your serial console will JUST WORK!
> So in summary:
> Do you use casper of liveinitramfs to boot?
> CASPER: Have you tried booting with "casper-getty" on the kernel command line?
> LIVEINTRAMFS: Have you tried booting with "live-getty" on the kernel
> command line?
> NB: don't try and add a serial console line to /etc/inittab if you
> boot like this...
> The code in 25configure init will determine if a serial console is in
> use and generate a line in /etc/inittab at boot time.
I just didn't know about 'live-getty' cmd line option. I've tested
it, it works, so I leave my /etc/inittab's patch and also the
live-initramfs patch previously proposed :-)