Kernel 2.4 vs 2.6 boot - /dev stuff

[intermilan]

Hi,

I have compiled Kernel 2.4, made a root file system and it worked fine. (on a powerpc of Xilinx FPGA).

Now, I'm trying Kernel 2.6.

I'm using exactly the same root file system - which is nothing but a few scripts, directories and compiled BusyBox. BusyBox compiling works OK for both 2.4 and 2.6 Kernel.

However, I have trouble in booting 2.6 kernel up. I get warnings and errors like "unable to open an initial console" ... can't find "/dev/null" ...

In my root file system, the /dev directory is almost empty - only ./pts and ./shm are there. The 2.4 kernel automatically build other /dev/* stuff and it boots up OK.

For the 2.6 kernel, I manually "mknod" for /dev/console and /dev/null, now the kernel boots up. However, still a lot of stuff is missing in /dev.

Is this a difference between Kernel 2.4 and 2.6? In kernel 2.4 configuration, there are the following options in "File System"[*] /dev file system support (EXPERIMENTAL)[*] Automatically mount at boot

While I do not find such options in 2.6 configuration. These options might play the role of "creating /dev/* stuff automatically"?

Thanks in advance for helping me with this newbie question.

[intermilan]

Is here the right place for my thread?
Or may sb help me forward my thread to somewhere more proper?

[coopstah13]

this is because kernel 2.6 introduced the use of udev
udev