On Fri, Sep 19, 2008 at 04:11:12PM +0200, Frans Pop wrote:
> On Friday 19 September 2008, Frans Pop wrote:
> > With the new rootskel I get an endless repetition of:
> > steal-ctty: No such file or directory
>
> Running with set-x gives a bit more info:
> + -f /var/run/console-device !
> + cat /var/run/console-device
> + exec /sbin/steal-ctty /dev/ttyS0 /sbin/debian-installer
> steal-ctty: No such file or directory
>
> This repeats endlessly. Note that the first line is mangled a bit because
> of the "!" in the if statement.
reopen-console is writing in /var/run/console-device the console that
was found in the first run, so the result would be more meaningful if
the "set -x" was add by using BOOT_DEBUG=3 and then running something
like "/sbin/reopen-console echo" manually.
> There seem to be various issues:
> - trying /dev/ttyS0 is just plain wrong for s/390: /dev/ttyS0 does not
> exist, which explains the error from steal-ccty
Indeed. Could you look at kernel messages for anything related to the
console? Using "dmesg -s 65535 | grep console" should probably do the
trick.
I might have misunderstood the meaning of the "console handover" line
and that's probably where the /dev/ttyS0 line came from, as
reopen-console defaults to /dev/console if no console can be found.
> - steal-ctty's error message should include the name of the file that does
> not exist
True.
> - the program should not end in a loop
The loop is caused by init trying, as told in inittab, to respawn the
process. It don't really feel like an issue for me, because this should
not happen. What could be done is a final check in reopen-console for
the existence of the device file, though…
Cheers,
--
Jérémy Bobbio .''`.
lunar@debian.org : :Ⓐ : # apt-get install anarchism
`. `'`
`-
Attachment:
signature.asc
Description: Digital signature