From: Douglas Gilbert <dougg@torque.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [experimental] scsiinfo driver
Date: Thu, 08 Mar 2001 23:26:05 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98409435524480@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98324837123691@msgid-missing>
Bill Nottingham wrote:
>
> David Brownell (david-b@pacbell.net) said:
> > Looks like a promising direction, especially if (as you'd
> > suggested offline) very similar models can work for IDE.
> >
> > What would the job of /etc/hotplug/scsi.agent be? I'm not
> > quite clear -- modprobe "sd" or "sg"? Mount partitions
> > in the appropriate filesystem locations?
>
> - modprobe whatever scsi modules are appropriate
> - create appropriate mount points & entries in /etc/fstab
> - signal whatever thing is creating desktop icons to add new ones
> (if it's not watching /etc/fstab)
>
> We've got something here that we're using to do the second
> of these; it is currently getting called on pcmcia/usb events
> for storage things, but it runs into the problem that requires
> this SCSI event system (race between device creation, userland
> notification, and partition table reading...)
I have added a simple scsi.agent script that modprobes
the various scsi upper level drivers (e.g. sr and st) based
on the scsi type of the newly added device. See:
http://www.torque.net/scsi/scsiinfo.html
Can anyone think of a better name than "scsiinfo" as H.
Peter Anvin doesn't like it?
Doug Gilbert
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-03-08 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 4:21 [experimental] scsiinfo driver Douglas Gilbert
2001-03-01 5:07 ` David Brownell
2001-03-01 5:24 ` Bill Nottingham
2001-03-08 23:26 ` Douglas Gilbert [this message]
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=marc-linux-hotplug-98409435524480@msgid-missing \
--to=dougg@torque.net \
--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).