I was trying out the new experimental stages and env-update gives this error: [] bash: line 1: /dev/null: No such file or directory I went to look in dev and I saw there was no /dev. I made dev and mounted devfs on it and continued with the install. When I went to mount portage from my nfs server there was no /usr/portage dir either. Made it and the system is bootsraping now. Reproducible: Always Steps to Reproduce: 1.Use 20040123 stage 1 2.env-update 3. Actual Results: [] bash: line 1: /dev/null: No such file or directory Expected Results: no errors and have /dev booted off gentoo-2004.0-x86-20040123.iso
livewire doesn't do the livecd's anymore, and I don't know if he ever did the stages
Personnaly, I create the dev directory and after null character node like this : mknod /dev/null c 1 3. After, I continue my installation without these type of messages. The baselayout package is able to create the other nodes (/dev/floppy, /dev/rtc, etc...) for the installation success. Olivier Mondoloni Stage1-20040123 used with LiveCD 20040123
Bug was a (honestly : my ) mistake in catalyst-setup.
Additional Info : /usr/portage is created at the first "emerge sync", the stages aren't included on the CD since this is only the "small" livecd.
Reopeing this bug since I think that this problem is something related to catalyst. In fact I built new stages today - again no /dev inside stage1. It could be possible to edit the docs to tell the users that they have to bind-mount /dev into the stage or - the clean method, but more work is required - look where that problem origins from and solve it.
In my hardened stages, I have a /dev directory that is populated. On stages 2 and 3 though, I have an unpopulated /dev directory. I am assuming that /dev is unpopulated because baselayout is not remerged in stages 2 and 3. Beejay, perhaps your problem is that baselayout is not getting emerged during stage1 creation?
I now tried different stages (2/3) with different datestamps (beginning with 20031102 and ending with 20040128) - There is _never_ a /dev in stage1. Without a /dev users have to bind-mount their original /dev into the chroot when installing. But shouldn't catalyst be supposed to build a /dev into any stage? This issue has to be fixed asap. Dear catalyst-guys - I am awaiting your input....
looking into this ..
*** Bug 39735 has been marked as a duplicate of this bug. ***
*** Bug 39940 has been marked as a duplicate of this bug. ***
*** Bug 40313 has been marked as a duplicate of this bug. ***
We have a fix for this bug now that will take effect with the next test-stages.
Closing this one then
I had this same problem today with stage1-amd64-20040223.tar.bz2. I had to "mkdir /dev" and "mknod /dev/null c 1 3" in order for this to work. This occurs after the January stage1's that have been listed here previously.
