All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: SCSI Patches - mostly on/off-line stuff
Date: Thu, 18 Jan 2001 23:10:03 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-97985932818703@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97925037703688@msgid-missing>

> > devfsd is at least already here. The existing /sbin/hotplug architecture
> > can't handle it. A new kind of event would be needed.
>
> A new event type doesn't change the architecture ... if
> that's all that's needed, the architecture is unchanged!

Ok, so we don't call an extension a change ;-)

But the required changes to other subsystems would be
larger. You'd need to call the helper at

- SCSI bus scanning
- Partition detection
- disk change detection
- module insertation/removal

at least. Possibly at other places too.
And you'd begin to get some issues, like
disk change -> helper script -> open device file -> disk change -> helper 
script -> etc ...

This is starting to get messy, IMHO.
I am not sure whether you can run these scripts in paralel.
And by the way some of this is needed for scsi<->usb bridges.

> To some folk, it won't even matter if the event comes from
> a devfsd thread or a kernel thread.  Implementation detail.
> Except maybe to the US Patent Office ... sigh.  (One
> iteration of USB hotplugging did just that:  devfsd called
> the same policy scripts as the kernel thread version.)

Devfs can give you a name to work on.
The kernel thread'll give you major/minor at best.
But that's a small difference.

> > Even so, you'll probably won't make the user happy if it works only
> > on plugging in and not when he puts in a new medium.
> > A look at supermount might be in order.
>
> Yep, lots of tools to choose from.  But again, not everyone
> runs supermount (or wants to) -- Yet Another Daemon, as I
> recall the situation.

It's a proper filesystem without a demon.
Why would a requirement to use a filesystem to enjoy a feature
be unreasonable ? If you can require usbdevfs you can require
supermount, too, IMHO.

	Regards
		Oliver

_______________________________________________
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

  parent reply	other threads:[~2001-01-18 23:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 21:56 SCSI Patches - mostly on/off-line stuff Douglas Gilbert
2001-01-11 22:43 ` Oliver.Neukum
2001-01-17 20:32 ` David Brownell
2001-01-18  0:08 ` Douglas Gilbert
2001-01-18  9:03 ` Oliver Neukum
2001-01-18  9:25 ` Miles Lane
2001-01-18 15:37 ` Eric Youngdale
2001-01-18 16:20 ` Venkatesh Ramamurthy
2001-01-18 16:49 ` Prasenjit Sarkar
2001-01-18 16:50 ` Venkatesh Ramamurthy
2001-01-18 17:03 ` Venkatesh Ramamurthy
2001-01-18 18:14 ` David Brownell
2001-01-18 19:12 ` Oliver Neukum
2001-01-18 19:20 ` Prasenjit Sarkar
2001-01-18 19:45 ` Miles Lane
2001-01-18 21:08 ` Douglas Gilbert
2001-01-18 21:41 ` Miles Lane
2001-01-18 22:07 ` David Brownell
2001-01-18 22:15 ` David Brownell
2001-01-18 22:45 ` Oliver Neukum
2001-01-18 23:10 ` Oliver Neukum [this message]
2001-01-18 23:25 ` Miles Lane
2001-01-18 23:37 ` Oliver Neukum
2001-01-19  2:08 ` David Brownell
2001-01-19  2:10 ` Bob Frey
2001-01-19  2:16 ` Venkatesh Ramamurthy

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-97985932818703@msgid-missing \
    --to=oliver.neukum@lrz.uni-muenchen.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.