Hello everyone!
First of all, thank you for this great project!
I stumbled over what I believe is a bug in the Linux boot image: /dev/null is
not created as
a device, and so everything that is put into it is returned when reading it.
As I see it, /dev/null is first written to in /etc/master,
Johannes Singer escribió:
> I stumbled over what I believe is a bug in the Linux boot image: /dev/null is
> not created as
> a device, and so everything that is put into it is returned when reading it.
>
Johannes,
very...very nice investigation.
I guess that some how I need to create /dev/nul
Inside devices.txt is:
dev/null c 1 3
which, if you are using mknod-cpio.pl with devices.txt as the input to append
the devices to your initrd, should work...
Steven
From: Juan Jose Pablos [mailto:jua...@apertus.es]
Johannes Singer escribió:
> I stumbled over what I believe is a bug in the Li
Steven Blackery escribió:
> Inside devices.txt is:
>
> dev/null c 1 3
>
> which, if you are using mknod-cpio.pl with devices.txt as the input to append
> the devices to your initrd, should work...
>
Steven,
that is exactly how is done it when building the iso image (I did not know):
## devic
Jeremy Brown escribió:
> I burned the ISO for 4.9 from the testing directory. The CD won’t boot.
> Get message Could not find kernel image: menu.c32.
>
> I really use the tftp boot but I wanted to let everyone know. Hope it
> wasn’t a bad burn.
Jeremy,
I found out the problem and it is fixed on
