linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Did you try devlabel
Date: Sun, 15 Sep 2002 23:51:36 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-103213413216828@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-103185682023240@msgid-missing>

Greg KH wrote:
> On Fri, Sep 13, 2002 at 03:52:24PM -0500, Gary_Lerhaupt@Dell.com wrote:
> 
>>So, in the meantime for us 2.4 folks, would it not be best to add the
>>patches as I have them and then work it differently for the 2.5
>>implementation?
> 
> 
> That's David's call, not mine :)
> 
> thanks,
> 
> greg (pass the buck) k-h

Gee thanks Greg... ;)


The functionality is needed, and will be needed even more in the
future.  So I'm keen on having it in some form.

The hard question is how, and my preferred answer would be to
focus all user mode tools/training/docs on what'll be the 2.5
solution ("disk" hotplug), with the 2.4 based solution mostly
a "workalike" or even backport.  Certainly "evolve together"
so the end-user (and sysadmin) experience isn't of two rather
divergent solutions, but just one (that likely works better on
2.5 systems but behaves also on 2.4).

Sounds to me like a 2.5ish start isn't that far away, so
a short delay seems reasonable to me.  So far as I can tell,
"devlabel" is in that interesting stage where it's not got
that many users (yet) and so it's easy to change based
on experience/feedback ... and we really ought to seek that
feedback and use it to improve both 2.4 and 2.5 based systems.

So I'll install devlabel and run it myself for a while.  And
I encourage other folk to do so, and submit feedback to this
list over the next month or so.  At which point I think it'll
be more practical to decide in detail what the next steps are.

Gary, can you work with that approach?  And in any case,
could you provide a short email describing how devlabel
would work on different kinds of Linux systems?  I have
in mind a range, including desktop, small server, larger
servers, and so on.  Aren't there other volume management
tools a "devlabel" would need to play with?

- Dave







-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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:[~2002-09-15 23:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12 18:46 Did you try devlabel Gary_Lerhaupt
2002-09-12 21:20 ` Gary_Lerhaupt
2002-09-12 22:15 ` Greg KH
2002-09-12 23:21 ` Gary_Lerhaupt
2002-09-12 23:26 ` Greg KH
2002-09-12 23:38 ` Gary_Lerhaupt
2002-09-13  5:50 ` Greg KH
2002-09-13 14:41 ` Gary_Lerhaupt
2002-09-13 19:18 ` David Brownell
2002-09-13 19:40 ` Gary_Lerhaupt
2002-09-13 19:52 ` Greg KH
2002-09-13 20:18 ` David Brownell
2002-09-13 20:39 ` Greg KH
2002-09-13 20:52 ` Gary_Lerhaupt
2002-09-13 21:02 ` Greg KH
2002-09-15 23:51 ` David Brownell [this message]
2002-09-16 22:54 ` Gary_Lerhaupt

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-103213413216828@msgid-missing \
    --to=david-b@pacbell.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).