missing /dev/console in debootstrap --foreign, a bug or not ?

Scott James Remnant scott at canonical.com
Tue Jan 20 15:20:39 GMT 2009


On Tue, 2009-01-20 at 16:04 +0100, Loïc Minier wrote:

> On Tue, Jan 20, 2009, Oliver Grawert wrote:
> > What we found during work on this script is that the first stage of
> > debootstrap --foreign does not create a /dev/console node, so qemu
> > panics during boot if you ise it with a bare kernel image (it might be
> > different if you use an initramfs that spawns udev though, which we
> > currently not do for bootstrapping)
> 
>  What does exactly "panic"?  Can we fix some early userspace to not
>  require /dev/console until the regular boot (without initramfs) starts
>  udev which would create it?
> 
Is there an initramfs at all?  I had a vague belief that the default
in-kernel initramfs included a /dev/console?


> > currently the script simply calls mknod to add the device file to the
> > image, but we were discussing the issue in the mobile team and came to
> > the conclusion that running debootstrap --foreign might indeed often be
> > used like that. to me it is not clear if debootstrap --foreign shouldnt
> > create /dev/console in any case.
> 
>  I think it wouldn't hurt if debootstrap's second stage would create
>  /dev/console if it's required and missing, but I'm not sure whether we
>  can actually start debootstrap's second stage.
> 
debootstrap does call MAKEDEV with a few essentials (including console)
and unpacks this during the first stage.

Scott
-- 
Scott James Remnant
scott at canonical.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20090120/0b166c3e/attachment.pgp 


More information about the ubuntu-devel mailing list