Hi guys,I also did an emerge udev yesterday, and found out the hard way that this not only installs
i am still using devsf no 2.6.2 vanilla, but the other day i emerge udev, in order to give it a try, and this is what happened:
after emerging i restarted my computer, but it refused to boot...
the kernel boot was ok, the default init was also ok, but when it came
to autoloading modules, the computer just froze and it stayed frozen for
quite a long time until i did a hard reset. I then booted into 2.4.22-gentoo-r5 and everything was a-ok, since there
is no sysfs - udev support in 2.4 kernels.
Then i deleted all of the modules that i was loading at startup, booted into 2.6.2 again - and it froze again.
Then in unmerged udev in 2.4 and rebooted into 2.6 again and everything was ok again.
the daemon on the hard drive, but also disables devfs and activates udev. I unemerged the bastard
and switched back to devfs. The only problems I had though were missing devices in /dev.
So the question is: is there some conflict between devfs and udev? CanNo. Devfs and udev are incompatible and cannot be used at the same time.
they not co-exist together? Or, if this is not the case, does anyone
have an idea as to what might be causing this?
And another question: is udev "100 %" able to replace devfs in terms ofI'm not quite sure what you mean with that. Devfs and udev don't actually interact with the hardware,
application compatibility? To be specific - most of the usb stuff i use
relies on devfs entries - will this be ok with sysfs / udev?
they just make the hardware devices (kernel major/minor) visible in the file system as /dev nodes.
In principle, udev should be better for hotplugged devices, e.g. usb, since it can be made to "remember"
a device by its serial number, and create a specific /dev node for it, whereas devfs would just count
node numbers up in the order in which the devices were plugged in rsp. turned on.
-- [EMAIL PROTECTED] mailing list
