I get cannot create /dev/null file exists cannot create /dev/zero file exists on every startup and I don't know why
you forgot to post `emerge info` *when* do you see those lines displayed ?
Created attachment 89441 [details] emerge info attaching emerge info AND I DIDN'T FORGET. It's an unnecessary in some cases. beyound that. I believe it's after populating dev with udev or something. I'll look that up later. Alec Warner (antarus) is familiar with the bug as well.
forgot to reopen
you'll have to track this down some more on your side
(In reply to comment #4) > you'll have to track this down some more on your side > bleh... I've no time to track it down further. just an annoying message that I see on boot that shouldn't be there. It's not my fault if udev isn't checking for the files. If you'd like something more of information let me know however telling me to track it down tells me nothing.
and you telling us you get some warning gets us nowhere add RC_BOOTLOG=yes to /etc/conf.d/rc and emerge app-admin/showconsole to get a /var/log/boot.msg for us to review
(In reply to comment #6) > and you telling us you get some warning gets us nowhere > > add RC_BOOTLOG=yes to /etc/conf.d/rc and emerge app-admin/showconsole to get a > /var/log/boot.msg for us to review > hate to tell you this log is useless the error happens before this right after populating /dev with needed nodes "I think" anyway I'm tired of all the issues I get from this install... I'm reinstalling. * Activating (possible) swap ... [ ok ] * Checking root filesystem ... /dev/sda3: clean, 468333/2741760 files, 2245454/5474148 blocks [ ok ] * Remounting root filesystem read/write ... [ ok ] * Setting hostname to slave-i ... [ ok ] * Calculating module dependencies ... [ ok ] * Setting up dm-crypt mappings ... [ ok ] * Checking all filesystems ... /dev/sda6: clean, 6904/16302080 files, 10589737/32597885 blocks Reiserfs super block in block 16 on 0x807 of format 3.6 with standard journal Blocks (total/free): 152608/99262 by 4096 bytes Filesystem is clean Replaying journal.. Reiserfs journal '/dev/sda7' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished /dev/sda8: clean, 794/287424 files, 368119/580340 blocks /dev/sda1: clean, 35/8032 files, 6953/32096 blocks [ ok ] * Mounting local filesystems ... [ ok ] * Mounting USB device filesystem (usbfs) ... [ ok ] * Activating (possibly) more swap ... [ ok ] * Setting up dm-crypt mappings ... [ ok ] * Setting system clock using the hardware clock [UTC] ... [ ok ] * Configuring kernel parameters ... [ ok ] * Updating environment ... [ ok ] * Cleaning /var/lock, /var/run ... [ ok ] * Cleaning /tmp directory ... [ ok ] * Coldplugging input devices ... [ ok ] * Coldplugging isapnp devices ... [ ok ]
Annoying boot messages coming from >= sys-fs/udev-078 We have and need resident nodes for null and zero or boot claims for and go to fix /etc/issue. This workaround works for me. $ su -c 'rm -f /lib/udev/devices/{null,zero}'
thanks for the info
I think that this bug is a duplicate of the reopened bug 128302.
*** This bug has been marked as a duplicate of bug 128302 ***
