On 3/8/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote:
Lucas C. Villa Real wrote: > On 3/8/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote: >> Where does 60-modprobe.rules originally come from? It isn't in the >> module-init-tools tarball.. Is it needed? >> I don't have any updated script. I guess we could just comment out that >> line for now... > > It comes from the Module-Init-Tools recipe. It's on its > Resources/Defaults/Settings dir.Yes, but I meant where it comes from originally, where the recipe author got it from?
I suspect it came from a random google search, or even from inside udev's sample rules dirs for gentoo / fedora distros.
BTW, I have another problem with udev rules. My dvd writer (/dev/hda with links to dvd and cdrw) is owned by root.root, I'd like it to be root.cdrecord so that users in the cdrecord group can burn CD's... But the cdrecord group isn't even mentioned in any udev rules, but group "cdrw" is, but that group isn't in 013's /etc/group file and anyhow my /dev/hda still isn't owned by any other group than root... Or is the cdrecord group meant to be used for suid'ing cd burning software so they run as root? (that wouldn't be good...)
The only privileged executable on CDRTools is sbin/rscsi, but it only makes use of the setuid bit. There's nothing indicating the usage of setgid there: -rws--x--x 1 gobo gobo 83384 Sep 1 2006 rscsi CDRDAO, however, uses that: -rwsr-sr-x 1 gobo gobo 569100 Jul 16 2006 cdrdao But as you can see its group is set to 'gobo' instead of 'cdrecord'. I think we need a fix here.. maybe a PostInstall script can do the job correctly. Could anyone please provide a fixed recipe for CDRDAO? On the hda owner's problem, could you please test with the attached udev rules? I made some modifications on permissions (0666) and added group settings to the cdrom entries.
And, one more issue... When I connect my MIDI USB interface before my machine boots, the drivers and firmware isn't loaded. This is handled by /P/Midisport-Firmware/Settings/udev/rules.d/42-midisport-firmware.rules which works fine when connecting the interface after udev has started... But I thought that the udev Task should handle this and synthesize 'add' events for everything? Any ideas?
I never wrote this kind of rule. I'm out of ideas here. -- Lucas powered by /dev/dsp
50-udev.rules
Description: Binary data
_______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
