| View previous topic :: View next topic |
| Author |
Message |
localghost
Apprentice
Joined: 28 Oct 2004
Posts: 185
Location: Sint-Niklaas, Belgium
|
 Posted: Thu Aug 18, 2005 4:31 pm Post subject: bootchart can't find /dev/null at boot |
 |
|
At boot, bootchart tells me it can't find /dev/null or something like that.
This does not disrupt the operation of bootchart: the charts are generated as they should.
I also noticed that after boot, just when I want to log in, I get the following messages:
| Code: | Parsing /var/log/bootchart.tgz
Wrote image /var/log/bootchart.png |
My guess is that this is &1 output that should go to /dev/null, but can't because /dev/null isn't there yet so early in the boot process.
How can I fix this cosmetic problem?
_________________
411 /0µr 84$3 4r3 8310n9 70 µ$. |
|
| Back to top |
|
 |
helmutvandeshaft
Tux's lil' helper
Joined: 23 Sep 2004
Posts: 90
Location: Amsterdam
|
| Posted: Fri Aug 19, 2005 11:34 am Post subject: |
|
|
emerge unmerge udev && rm -rf /etc/udev && emerge udev
This worked for me when I had /dev/null problems
Try to emerge a package and see if it fails with permission denied /dev/null, if so then the above might work. |
|
| Back to top |
|
|
tomvollerthun
Guru
Joined: 19 Mar 2005
Posts: 316
|
| Posted: Fri Aug 19, 2005 11:36 am Post subject: |
|
|
The documentation holds an answer to this problem as well:
The section "Checking for essential device nodes" of http://www.gentoo.org/doc/en/migration-to-2.6.xml says:
| Documentation wrote: | | Code: | mkdir -p /mnt/temp
mount -o bind / /mnt/temp
cd /mnt/temp/dev
ls -l console null |
If the above ls command reported that either console or null do not exist, then you must create them yourself, as shown below.
| Code: | mknod -m 660 console c 5 1
mknod -m 660 null c 1 3 |
You should now unmount your bind-mounted root partition, even if you did not have to create those devices:
| Code: | cd
umount /mnt/temp
rmdir /mnt/temp |
|
cu, tom
<edit>If I was you, I wouldn't go as far as removing configuration files.
Re-installing the package and checking the files should be enough!
As well I wouldn't remove udev: you might get trouble with your device nodes and I don't even want to think about what happened if you had to reboot in that very moment!</edit>
_________________
Computer science is no more about computers than astronomy is about telescopes.
Dijsktra
---------------
Don't believe my "Guru" status! |
|
| Back to top |
|
|
localghost
Apprentice
Joined: 28 Oct 2004
Posts: 185
Location: Sint-Niklaas, Belgium
|
| Posted: Tue Aug 23, 2005 9:01 pm Post subject: |
|
|
I have those device nodes - by the way I always had a 2.6 kernel.
I'm emerging udev right now - but I'm not going to reboot yet because that would be bad for my uptime! 
_________________
411 /0µr 84$3 4r3 8310n9 70 µ$. |
|
| Back to top |
|
|
tomvollerthun
Guru
Joined: 19 Mar 2005
Posts: 316
|
| Posted: Wed Aug 24, 2005 6:54 am Post subject: |
|
|
| localghost wrote: | | I have those device nodes |
Well, someone in your computer seems to be missing them ;)
Did you check with the bind-mounted root if the device nodes are there as well? Because at boot udev has not populated the /dev directory, so either the nodes need to be "hardwired" on your root-partition as described above, or they're simply not there.
| localghost wrote: | | by the way I always had a 2.6 kernel. |
That does not necessarily mean that you have as well always had a properly set up device-node manager: The symptom you've described above is caused by a missing device node, so the device node is missing and that's it.
To get rid of the message, you must provide the device node and that's it. How ever you do that, when the node is there, the problem will be gone for sure.
cu, tom
_________________
Computer science is no more about computers than astronomy is about telescopes.
Dijsktra
---------------
Don't believe my "Guru" status! |
|
| Back to top |
|
|
localghost
Apprentice
Joined: 28 Oct 2004
Posts: 185
Location: Sint-Niklaas, Belgium
|
| Posted: Sat Aug 27, 2005 7:15 pm Post subject: |
|
|
| Code: | saruman ~ # mkdir -p /mnt/temp
saruman ~ # mount -o bind / /mnt/temp
saruman ~ # cd /mnt/temp/dev
saruman dev # ls -l console null
crw------- 1 root tty 5, 1 mei 2 19:06 console
crwxrwxrwx 1 root root 1, 3 mei 2 19:06 null
saruman dev # mknod -m 660 console c 5 1
mknod: `console': Bestand bestaat
saruman dev # mknod -m 660 null c 1 3
mknod: `null': Bestand bestaat
saruman dev # cd
saruman ~ # umount /mnt/temp
saruman ~ # rmdir /mnt/temp
|
What do you recommend?
_________________
411 /0µr 84$3 4r3 8310n9 70 µ$. |
|
| Back to top |
|
|
tomvollerthun
Guru
Joined: 19 Mar 2005
Posts: 316
|
| Posted: Tue Aug 30, 2005 6:30 am Post subject: |
|
|
I am not sure about what to do now, since both devices are available.
The only thing that seems unusual to me are the permissions. But really, that shouldn't be a problem since root has read and write permission on both and that's all a boot process should need.
So the only thing I can think of is stupid: adjust the permissions of the files by bind-mounting the root filesystem as you did before and | Code: | | chmod 660 console null |
before you umount it.
Apart from that, I don't know what else to do.
Sorry, tom
_________________
Computer science is no more about computers than astronomy is about telescopes.
Dijsktra
---------------
Don't believe my "Guru" status! |
|
| Back to top |
|
|
|
Unsupported Software
