When changing kernel from 2.6.7 to 2.6.10 i decided to ditch devfs in favor of udev. After the reboot i noticed that /dev looked like the "classic" /dev. With classic i mean fully populated, with i.e disk-partitions i didn't have, or disks i didn't have for that matter. /dev/mouse did'nt exist either so i symlinked it to /dev/psaux to fix it.
Bootscripts told me everything went fine, and when using udevinfo, it tells me that for example /dev/hda is in place and working, while /dev/hdd is not in the database, but sure as hell is in /dev.
Anything I could've forgotten to do? the udev-config(s) are untouched.
This thread is placed here since i suspect a malfunctioning rc-script somewhere.
Malfunctioning udev?
Message
Malfunctioning udev?
Bus error - Driver executed
The chances are you are using a udev-TAR.
Basically udev has the option to make a tar file of your /dev directory. This is unzipped every boot.
This is probably why you have all those extra nodes.
check out
/etc/conf.d/rc
there is a:
Bit I have set it to No since I dont want a tarball made.
Also as to the mouse, making a symlink is not the best way to do it. that symlink will stay there once you shutdown and thus you will not have an empty /dev (the point of udev)
I had a similar problem with my xorg and udev with respect to my mouse.
udev made /dev/input/mouse0 but I had in xorg /dev/usbmouse.
so what I did was made a udev rule to make the nessasary symlinks
as you can see with the
KERNEL="mice", NAME="input/%k", SYMLINK="usbmouse"
I get udev to make a symlink called "usbmouse" for the device in /dev/input/
Basically udev has the option to make a tar file of your /dev directory. This is unzipped every boot.
This is probably why you have all those extra nodes.
check out
/etc/conf.d/rc
there is a:
Code: Select all
# UDEV OPTION:
# Set to "yes" if you want to save /dev to a tarball on shutdown
# and restore it on startup. This is useful if you have a lot of
# custom device nodes that udev does not handle/know about.
RC_DEVICE_TARBALL="no"
Also as to the mouse, making a symlink is not the best way to do it. that symlink will stay there once you shutdown and thus you will not have an empty /dev (the point of udev)
I had a similar problem with my xorg and udev with respect to my mouse.
udev made /dev/input/mouse0 but I had in xorg /dev/usbmouse.
so what I did was made a udev rule to make the nessasary symlinks
Code: Select all
jrb@Fluid / $ cat /etc/udev/rules.d/10-local.rules
############################
# Local Machine Udev rules #
############################
BUS="scsi", KERNEL="sd*", SYSFS(serial)="B8177840FE1CB499", NAME="%k", SYMLINK="usbkey"
#BUS="usb", KERNEL="ub*", SYSFS(serial)="B8177840FE1CB499", NAME="%k", SYMLINK="usbkey"
BUS="usb", SYSFS{serial}="509DLT", NAME="usb/%k", SYMLINK="canon_i550"
KERNEL="mice", NAME="input/%k", SYMLINK="usbmouse"
KERNEL="js*", NAME="input/%k", SYMLINK="%k"
KERNEL="mice", NAME="input/%k", SYMLINK="usbmouse"
I get udev to make a symlink called "usbmouse" for the device in /dev/input/
#define HelloWorld int
#define Int main()
#define Return printf
#define Print return
#include <stdio>
HelloWorld Int {
Return("Hello, world!\n");
Print 0;
#define Int main()
#define Return printf
#define Print return
#include <stdio>
HelloWorld Int {
Return("Hello, world!\n");
Print 0;