From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alexander E. Patrakov" Date: Sat, 30 Oct 2004 15:31:46 +0000 Subject: Re: ide.rc Message-Id: <200410302131.46884.patrakov@ums.usu.ru> List-Id: References: <20041029141509.GA9119@wonderland.linux.it> In-Reply-To: <20041029141509.GA9119@wonderland.linux.it> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Saturday 30 October 2004 13:14, Remco wrote: > Alexander E. Patrakov wrote: > > On Friday 29 October 2004 20:15, Marco d'Itri wrote: > >> I'm attaching a .rc script for hotplug which loads at boot time the > >> ide-* modules needed by the system (which, as everybody knows by now, > >> cannot be automatically loaded anymore when using udev). > > I didn't look at the script so it may be useful, but it doesn't seem needed > to me when it comes to loading additional modules. To load additional > drivers automatically in Linux 2.6 I use the /etc/modprobe.conf file of the > module-init-tools package. You'll have to create a rule for each and every > driver, but that also gives you the flexibility to create customised rules > on a per driver basis. Just adding ide-generic to /etc/modules (a Debian-specific file that lists modules to be unconditionally loaded on each boot) is much easier. > > Also, your script starts before pci.rc (because "i" is before "p" in the > > alphabet) and therefore will not find anything on my old server at all > > (the serverworks module is loaded by pci.rc). > > I think this also counts for the input.rc script. AFAIK input.rc always > runs before the other .rc scripts. So drivers for input devices will always > be loaded after input.rc has run. Therefore it seems to me that input.rc > never really does anything, unless I'm overlooking something. > I guess that running the hotplug rc scripts in alphabetical order will > never be the right thing to do, unless they get sequenced somehow. > e.g.: Maybe by adding some sequence number like udev-rules and > udev-permissions. In fact, if a module has been loaded by one rc script, agents should catch the resulting hotplug events. So the order _should_ not matter with good agents, except for the number of duplicate fake hotplug events. The problem is that there is no "ide.agent" file. Sorry for my initial not-very-correct description of this ordering problem. -- Alexander E. Patrakov ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id065&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel