Le mardi 25 janvier 2005 Ã 09:49 -0500, Dan Williams a Ãcrit : > On Tue, 2005-01-25 at 14:38 +0100, FÃliciano Matias wrote: > > Suppose I want to package the mga_vid driver, I'll use : > > /etc/makedev.d/mga_vid # /dev/mga_vid definition > > /etc/sysconfig/init-dev.d/mga_vid.dev # create /dev/mga_vid > > /etc/sysconfig/init-dev.d/mga_vid.module # load mga_vid > > /etc/modprobe.conf.d/mga_vid.conf # configure mga_vid > > /etc/security/console.perms.d/mga_vid # pam_console configuration > > Does it seem utterly _pathetic_ to anyone else but me that there would > have to be 5 different places to add information about a particular > hardware device, just to get it to load and work? Just a point of > observation. Do you prefer hacks and "Ooops" in order to configure /etc/modprobe.conf, /etc/rc.d/rc.local, /etc/security/console.perms ? If the driver support udev, doesn't need configuration, do not need pam_console, can be auto-loaded, ... all this stuff is useless. But sometimes... You know, the "real world". > On Tue, 2005-01-25 at 14:38 +0100, FÃliciano Matias wrote: > > Suppose I want to package the mga_vid driver, I'll use : Now suppose /etc/modprobe.conf.d/, /etc/sysconfig/init-dev.d/, ... exist and I created a rpm package for mga_vid. Just install it and enjoy.
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
