linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Remco <remco@d-compu.dyndns.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: ide.rc
Date: Sat, 30 Oct 2004 07:14:24 +0000	[thread overview]
Message-ID: <clvf0u$vu0$1@sea.gmane.org> (raw)
In-Reply-To: <20041029141509.GA9119@wonderland.linux.it>

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.

examples: (see man modprobe.conf)
install atkbd /sbin/modprobe --ignore-install atkbd && { /sbin/modprobe
i8042; }

install psmouse /sbin/modprobe --ignore-install psmouse && { /sbin/modprobe
i8042; /sbin/modprobe mousedev; }

install hid /sbin/modprobe --ignore-install hid && { /sbin/modprobe
mousedev; }

install hpt366 /sbin/modprobe --ignore-install hpt366 && { /sbin/modprobe
ide-cd; /sbin/modprobe ide-disk; }

install pdc202xx_new /sbin/modprobe --ignore-install pdc202xx_new &&
{ /sbin/modprobe ide-cd; /sbin/modprobe ide-disk; }

install pdc202xx_old /sbin/modprobe --ignore-install pdc202xx_old &&
{ /sbin/modprobe ide-cd; /sbin/modprobe ide-disk; }

install piix /sbin/modprobe --ignore-install piix && { /sbin/modprobe
ide-cd; /sbin/modprobe ide-disk; }

install via82cxxx /sbin/modprobe --ignore-install via82cxxx &&
{ /sbin/modprobe ide-cd; /sbin/modprobe ide-disk; }

options aha152x io=0x0140 irq\x11
install aha152x /sbin/modprobe --ignore-install aha152x && { /sbin/modprobe
sd_mod; /sbin/modprobe sr_mod; }


P.S.: the above lines may be wrapped !!!

> This script would be probably a bit wrong for my old server. This server
> has a LSI Logic SCSI adapter (with two hard disks attached) and a
> ServerWorks IDE adapter with one attached CD-ROM drive. For some strange
> reason, to use this CD-ROM, I must have both serverworks, ide_generic and
> ide_cd modules loaded. Your script won't load ide_generic. The kernel is
> 2.6.7-1-686.

I hope the above can help you create a customised rule for your device.

> 
> 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.




-------------------------------------------------------
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

  parent reply	other threads:[~2004-10-30  7:14 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 ` Remco [this message]
2004-10-30 15:31 ` ide.rc Alexander E. Patrakov
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='clvf0u$vu0$1@sea.gmane.org' \
    --to=remco@d-compu.dyndns.org \
    --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).