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'll comment out that for now. Thanks > for the tip. 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...) 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? -- /Jonatan -=( http://kymatica.com )=- _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
