From: Greg KH <greg@kroah.com>
To: Kevin Corry <corryk@us.ibm.com>,
linux-kernel@vger.kernel.org, evms-devel@lists.sourceforge.net
Cc: Alexander Viro <viro@math.psu.edu>, torvalds@transmeta.com
Subject: Re: EVMS Submission for 2.5
Date: Thu, 3 Oct 2002 09:13:20 -0700 [thread overview]
Message-ID: <20021003161320.GA32588@kroah.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0210031042210.15787-100000@weyl.math.psu.edu>
On Thu, Oct 03, 2002 at 10:51:39AM -0400, Alexander Viro wrote:
>
>
> On Thu, 3 Oct 2002, Kevin Corry wrote:
>
> > > I might agree with something along the lines of
> > > * when evms is initialized, it's notified of all existing gendisks
> > > * whenever disk is added after evms initialization, we notify evms
> > > * whenever disk is removed, we notify evms
> >
> > This sounds like it would be exactly what EVMS needs. The only thing we would
> > want to add to this list is: "*whenever a disk is modified, notify evms". For
> > example, with removable media drives (such as Zip and Jaz), when a cartidge
> > is changed, the capacity of the drive might change, and we would like to be
> > notified of that event.
>
> Umm... OK. There were some plans to add a notifier chain for such events
> and EVMS looks like a possible user of that beast. However, it's not
> obvious whether we need to do any of that in the kernel - we definitely
> can have userland up and running before _any_ block devices are initialized,
> so it might be a work for userland helper.
/sbin/hotplug already gets called for _every_ device that is added to
the system as of 2.5.40, so you should probably use that as your
userspace notifier event. If there's anything that the /sbin/hotplug
call misses, that you need for evms, please let me know.
thanks,
greg k-h
next prev parent reply other threads:[~2002-10-03 16:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 21:33 EVMS Submission for 2.5 Kevin Corry
2002-10-02 22:14 ` Alexander Viro
2002-10-02 22:03 ` Kevin Corry
2002-10-02 23:02 ` Alexander Viro
2002-10-03 13:04 ` Kevin Corry
2002-10-03 14:51 ` Alexander Viro
2002-10-03 14:53 ` Kevin Corry
2002-10-03 15:37 ` Alexander Viro
2002-10-03 16:13 ` Greg KH [this message]
2002-10-03 16:21 ` Alexander Viro
2002-10-03 16:30 ` Greg KH
2002-10-03 17:00 ` David Lang
2002-10-03 17:27 ` Greg KH
2002-10-03 19:52 ` [Evms-devel] " Oliver Neukum
2002-10-03 21:37 ` Greg KH
2002-10-03 21:02 ` Oliver Neukum
2002-10-03 22:56 ` Greg KH
2002-10-03 23:03 ` Alexander Viro
2002-10-04 8:07 ` Oliver Neukum
2002-10-05 0:06 ` Greg KH
2002-10-03 16:55 ` Patrick Mochel
2002-10-03 19:24 ` Linus Torvalds
2002-10-02 22:27 ` Shawn
2002-10-02 22:19 ` Shawn
2002-10-02 22:43 ` Greg KH
2002-10-03 12:13 ` Kevin Corry
2002-10-03 16:23 ` Greg KH
2002-10-03 16:51 ` Linus Torvalds
2002-10-03 21:56 ` Kevin Corry
2002-10-03 23:07 ` Greg KH
2002-10-04 0:39 ` Kevin Corry
2002-10-04 13:06 ` Alan Cox
2002-10-04 13:07 ` [Evms-devel] " Kevin Corry
2002-10-04 17:29 ` Kai Henningsen
2002-10-03 14:32 ` Christoph Hellwig
2002-10-03 14:59 ` [Evms-devel] " Michael Clark
2002-10-03 15:08 ` Christoph Hellwig
2002-10-03 15:03 ` Shawn
2002-10-03 15:31 ` Christoph Hellwig
2002-10-03 15:41 ` [Evms-devel] " Mike Tran
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=20021003161320.GA32588@kroah.com \
--to=greg@kroah.com \
--cc=corryk@us.ibm.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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.