i notice that kernel 2.6 has sysfs support. currently i do compiled it to my kernel but i didnt modify my system to get this file system to run(which was taught by thomer.com/linux/migrate-to-2.6.html) coz i notice that it said devfs is sysfs so i dont mess around with it and continue on using my redhat 9 devfs.

currently i dont have /dev/fd0, /dev/cdrom and etc and on when i boot into kernel 2.4.20-8 i can see hundreads of charater device in my /dev/ folder but in kernel 2.6 it is much less then 2.4.

where do all those device go?

i dont have sysfs, so do it has to do with the problem that i have that i dont get cdrom and floppy drive?

should i follow the steps thought by thomer.com/linux/migrate-to-2.6.html
to enable sysfs?

It's my understanding that devfs and proc are being deprecated in favor of udev and sysfs.

they're still in 2.6 for compatibility, so making the crossover isn't absolutely necessary. But I'd take the plunge if I were you - sounds like it's only a matter of time.

--Rounan

i dont enabled sysfs and will that be the cause of my linux dont have cdrom, floppy drive and etc in /dev?

AFAIK, sysfs just replaces proc as a virtual filesystem used to gain information about the running system and kernel.

And problems with devices are probably due to udev. Do you have udev installed? 2.6 does require that to work properly.

Do you have access to floppy, cd-rom, etc? Have devices just changed names, or can you not use hardware?

--Rounan

fd0 and cdrom character device cant be found in /dev

Do you have udev installed?

Do you have access to floppy, cd-rom, etc? Have devices just changed names, or can you not use hardware?

hey i went into compilation xconfig to enable sysfs or udev but i dont seems to find one.

where is it located?

sysfs does not replace proc.

The problems with /proc stem from the fact that it is being used for purposes that were never intended. /proc was originally only supposed to be a virtual filesystem describing the processes that were running within the system. Over time, however, it was generalized and is now used fror all manner of things, resulting in a fragmented, complex, fragile namespace.

sysfs fixes that by being designed from the outset for the display of internal kernel information; its tight integration with kobjects makes it easy for drivers, filesystems and other internal kernel pieces to display information without too much trouble. The only problem with sysfs ATM is that it doesn't match the amount of information that /proc has.

By the time 2.8/3.0 arrive, /proc will only have process information, and sysfs will have everything else.

You will need it if you want to use lm_sensors with 2.6.x

TheOneKEA - Thanks for the clarification! I wasn't aware /proc was staying put. Makes sense now.

Demmylls - I seem to recall sysfs being a kernel option... not 100% sure, but check the config again, I think it's there.
Udev, however, is a userspace program, not a kernel feature. You need to grab a udev RPM and install it in order for devices to work properly in 2.6

--Rounan

do you mean this:
http://kernel.org/pub/linux/utils/ke...ev-016.tar.gz?

I'd get the RPM, but yeah, that's udev alright.