From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: ide.rc
Date: Sat, 30 Oct 2004 15:31:46 +0000 [thread overview]
Message-ID: <200410302131.46884.patrakov@ums.usu.ru> (raw)
In-Reply-To: <20041029141509.GA9119@wonderland.linux.it>
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.
<snip examples>
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_id\x12065&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
next prev parent reply other threads:[~2004-10-30 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 14:15 ide.rc Marco d'Itri
2004-10-30 2:36 ` ide.rc Alexander E. Patrakov
2004-10-30 7:14 ` ide.rc Remco
2004-10-30 15:31 ` Alexander E. Patrakov [this message]
2004-11-01 1:47 ` ide.rc Marco d'Itri
2004-11-01 3:01 ` ide.rc Alexander E. Patrakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200410302131.46884.patrakov@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).