[solved] Special files

ConnorBehan · 2009-01-26 02:57:19

EDIT: This problem magically went away when I upgraded to kernel 2.6.33. I since downgraded to 2.6.31 again because of ATI KMS issues but the problem didn't come back. The messages display perfectly for me. Thanks.

For awhile when I was mad at framebuffer drivers not detecting my second video card, I was trying to create /dev/fb devices myself with mknod and map them to PCI devices somehow by creating a bunch of files in /dev and /sys. Obviously it was a disaster and I found a much better solution to this problem - radeon KMS. So when I wanted to get rid of all the random files I had lying around, I mounted sda2 to /some/dir/ in a liveCD so that all of my necessary device nodes were in /dev not /some/dir/dev and I just deleted /some/dir/dev thinking that it only contained my crap. However it contained the necessary node /dev/console.

When I tried to boot into my system again I was rudely told that there was no /dev/console and that the kernel was panicking. So I went back into the liveCD and created /dev/console and now my system boots again. However once it says "passing control to kinit" I don't see anything else until "entering runlevel 3". The Archlinux message saying copyright whatever years Judd Vinet and Aaron Griffin doesn't show up and neither do the lines about modules, acpi modules and udev uevents. The modules are loaded of course, but the only [BUSY] [DONE] lines I see pertain to daemons. So I'm pretty sure there was another node I foolishly deleted as well. Does anyone know what that might be? Thanks.

Last edited by ConnorBehan (2010-06-16 04:34:13)

pyther · 2009-01-26 03:47:13

I think /dev/null is another that you need, I remember seeing a list of items that were need in /dev somewhere before, but I can't seem to find that list anymore :-/

Ghost1227 · 2009-01-26 03:57:13

I just realized you're actually using my avatar pyther looks good on you

ConnorBehan · 2009-01-26 05:04:08

Creating /dev/console, /dev/null and /dev/zero the same way they're created in /etc/rc.sysinit doesn't fix this. Are those the three files you're supposed to see when you mount your root partition in a liveCD?

kludge · 2009-01-26 05:33:39

those should be the only three device nodes you need to create by hand, yeah.

_alexmyself · 2009-03-02 00:55:29

someone knows how to create those three dev/ console null zero?

those are not created by any base package installation, ConnorBehan said nor by the rc.sysinit way, so what? are those directly provided by a magic way?
i know arch have many magic items, but magic is ever undocumented

magician? are there any magician there?

_alexmyself · 2009-03-03 21:39:44

google provided me the magic!

mknod -m 600 /dev/console c 5 1
mknod -m 666 /dev/zero c 1 5
rm -Rf /dev/null
mknod -m 666 /dev/null c 1 3

ConnorBehan · 2009-12-22 20:04:34

I tried to fix this problem again this week. I noticed that on Arch systems that had no problem displaying the boot messages, console had 644 permissions but my own console had 600 permissions. I eventually figured out that I had to edit 50-udev-default.rules in order to change it. Now console is created with 644 on my machine but the messages still don't show up until runlevel 3. Any other ideas?

Arch Linux

#1 2009-01-26 02:57:19

[solved] Special files

#2 2009-01-26 03:47:13

Re: [solved] Special files

#3 2009-01-26 03:57:13

Re: [solved] Special files

#4 2009-01-26 05:04:08

Re: [solved] Special files

#5 2009-01-26 05:33:39

Re: [solved] Special files

#6 2009-03-02 00:55:29

Re: [solved] Special files

#7 2009-03-03 21:39:44

Re: [solved] Special files

#8 2009-12-22 20:04:34

Re: [solved] Special files

Board footer