RE: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes

[Jean Blignaut]

>> No mistake as far is I can tell after checking the /etc/inittab on
the
>> booted gnap virtual machine I decided to try  changing runlevels from
>> 3 to 4 and back again this seems to have worked cause I havn't seen
>> the message since [...]

> well, a reboot, changing runlevels or at least a "telinit q" is
> necessary to make init aware of the changed inittab. I didn't mention
> this before...

>> -- this leads me to believe that some thing else is
>> enabling the s0 tty, something that ignores inittab
>> As a matter of interest: the I/O error hasn't shown up in the logs
>> since I first commented out s0 line in inittab

> OK, then it worked. But please note that the "s0" is the name of the
> inittab entry (read "man inittab") and doesn't per se specificate a
> device. That's done in another place and the correct device name is
> ttyS0 (capital "S"). The line could have a totally different name.

I had a feeling that might be the case

> Anyway, the inittab issue seems to be gone for you

Not quite. See I DID reboot because I made a new GNAP iso image with my
version of inittab in the overlay etc directory -- it STILL boots with
the 'INIT: Id "s0" respawning too fast: disabled for 5 minutes' message
showing up every 5 minutes.
It only seems to stop after I change the runlevel by hand I'm confused
as to why this is the case does GNAP first use its own version of
inittab BEFORE replacing it with the one from the overlay?
Or is there some other mechanism that's attempting to start the console
on ttyS0?

ps aux shows tty[123456] but no ttyS0

...hang on I just caught it while it had a tts/0 tho running
/sbin/agetty -L -I 19200 ttys0 vt100 

-- 
gentoo-embedded@g.o mailing list