Bug#355074: [Yaird-devel] Bug#355074: yaird fails to load /dev/console for luks cryptoroot

[Mark Hedges]

On Fri, 3 Mar 2006, Jonas Smedegaard wrote:
> On Thu, 2 Mar 2006 19:52:37 -0800 (PST)
> Mark Hedges <hedges at ucsd.edu> wrote:
>
>> I do get a prompt to type the luks password.  Yay!
>>
>> But immediately I see:
>>
>> EXT3-fs: mounted filesystem with ordered data mode.
>> Switching root ...
>> /usr/lib/yaird/exec/run_init: opening console: No such file or
>> directory Kernel panic - not syncing: Attempted to kill init!
>>
>> It would appear that yaird is not putting the console device in?
>
> When manually creating a boot environment, you need also to manually
> copy/create the needed device nodes. It is too complicated for yaird to
> deal with device nodes (could be udev, could be udev now but not at
> next boot, could be... Just too complicated).

Sorry for being ignorant -- how do I do that?

Isn't this what the prologue template is supposed to do?

   TEMPLATE SET
       TEMPLATE prologue
       BEGIN
           # In principle, we don't want device files on the initrd
           # image: device numbers can change between kernels.
           # Instead, create device files at boot time based on info
           # in sysfs.  However, /dev/null and /dev/console are needed
           # to mount sysfs.
           FILE "/dev/null"
           FILE "/dev/console"
           FILE "/bin/dash"
           FILE "/bin/cat"
           ...

And from /usr/src/linux-source-2.6.15/Documentation/initrd.txt:

   We'll describe the loopback device method:
   ...
   4) create the console device (not necessary if using devfs, but it can't
      hurt to do it anyway):
      # mkdir /mnt/dev
      # mknod /mnt/dev/console c 5 1

There isn't much documentation.  What do I do?

Mark