Re: udev: how to do it right?
Sebastiaan <S.Breedveld@ewi.tudelft.nl> writes:
> it seems that it gets created later. On boot there is no such thing.
> However, when I make /dev/hda2 with mknod and then mount that partition,
> hda and hda1 get also created, along with /dev/ide/bus. So something is
> working, but udev needs to get 'triggered' as it looks like...
Do you have the ide-subsystem loaded as modules? Unlike devfs, udev
doesn't load modules, but rather when the modules are loaded
(automatically by /etc/modules or manually) the nodes are
created. Basically, different setup. The solution is to load the
ide-subsystem in /etc/modules.
> Another problem I have been running into are the permissions. I have a
> nvidia card, so I added this to links.udev:
> M nvidia0 c 195 0
> ...
> M nvidia7 c 195 7
> M nvidiactl c 195 255
>
> These get created on boot, but with the wrong permissions. Adding stuff to
> udev.permissions doesn't help in any way:
>
> nvidia*:root:root:0666
>
> It looks most like udev.permissions is completely ignored.
Check some of the other nodes, for instance your scsi drives, to see if
they have the correct permissions (should be something like
root.disk). I had this problem some time ago (with my memstick, I
think), but I don't remember for which udev version. I think the
problem is fixed later, but I'm not sure what kind of patches Marco (the
udev maintainer) might have added to the base udev source. If the other
nodes have correct permissions, but only nvidia has problems, send an
email to the debian maintainer and check with him.
--
John L. Fjellstad
web: http://www.fjellstad.org/ Quis custodiet ipsos custodes
Reply to: