public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Corry <corryk@us.ibm.com>
To: "James H. Cloos Jr." <cloos@jhcloos.com>
Cc: evms-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: EVMS announcement
Date: Wed, 6 Nov 2002 09:21:16 -0600	[thread overview]
Message-ID: <02110609211601.06245@boiler> (raw)
In-Reply-To: <m3iszblg0b.fsf@lugabout.jhcloos.org>

On Tuesday 05 November 2002 18:05, James H. Cloos Jr. wrote:
> >>>>> "Kevin" == Kevin Corry <corryk@us.ibm.com> writes:
> Kevin> In addition, this switch complicates having the root filesystem
> Kevin> on an EVMS volume.
>
> Actually, this isn't as much of an issue with 2.5-as-it-will-soon-be.
> The initramfs stuff solves the problem for booting, and is exactly
> where boot-time discovery should be.

Yep. This is what I was briefly trying to explain in the announcement. With 
initramfs stuff finally going into 2.5, root-on-complex-volume should become 
far less of an issue. For our users on 2.4, we will have to help them wade 
through initrd for the time being. My real hope is that initramfs will 
provide a much simpler method (compared to initrd) for adding new tools, 
scripts, etc to be run during early userspace. The info I've gathered about 
it so far seems to indicate this will be the case.

> You will need to ensure sufficient integration with hotplug to deal
> properly with such things as external devices (usb, 1394, cardbus/
> pcmcia, iscsi, docking stations, etc) and media bays.  But this should
> be relatively easy, yes?

Hopefully, yes. We will obviously want to take full advantage of hotplug, and 
any other device-level services that are available.

-- 
Kevin Corry
corryk@us.ibm.com
http://evms.sourceforge.net/

  reply	other threads:[~2002-11-06 15:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 22:19 EVMS announcement Kevin Corry
2002-11-05 21:00 ` [Evms-announce] " Mike Diehl
2002-11-05 21:11   ` Mike Diehl
2002-11-05 23:53     ` Rik van Riel
2002-11-06  0:21     ` Alan Cox
2002-11-06  9:34       ` [Evms-devel] " Hendrik Visage
2002-11-06 13:55         ` Alan Cox
2002-11-06  0:36     ` [Evms-devel] " Kevin Corry
2002-11-06  1:45       ` Mike Diehl
2002-11-06  4:48         ` Alexander Viro
2002-11-06  2:54           ` Mike Diehl
2002-11-06 13:47         ` Kevin Corry
2002-11-05 23:40   ` [Evms-announce] " Andres Salomon
2002-11-05 21:29     ` Mike Diehl
2002-11-06  0:18   ` Andrew Clausen
2002-11-06 21:33     ` Matthias Andree
2002-11-07 10:37       ` Joe Thornber
2002-11-05 23:37 ` Alan Cox
2002-11-06  0:03 ` [Evms-devel] " Eff Norwood
2002-11-06  1:13   ` Rik van Riel
2002-11-06  1:41     ` Eff Norwood
2002-11-06  1:57       ` Rik van Riel
2002-11-06  2:50       ` Alexander Viro
2002-11-06  0:05 ` James H. Cloos Jr.
2002-11-06 15:21   ` Kevin Corry [this message]
2002-11-06  0:16 ` [Evms-announce] " Lars Marowsky-Bree
2002-11-06 13:55   ` Alan Cox
2002-11-06 13:59     ` Arjan van de Ven
2002-11-06 14:24       ` Jens Axboe
2002-11-06 20:46     ` H. Peter Anvin
2002-11-06 21:21       ` Alan Cox
2002-11-06 21:58         ` H. Peter Anvin
2002-11-08 18:06           ` Alan Cox
2002-11-08 19:37             ` H. Peter Anvin
2002-11-06 15:08   ` Kevin Corry
2002-11-07 20:24 ` Christoph Hellwig

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=02110609211601.06245@boiler \
    --to=corryk@us.ibm.com \
    --cc=cloos@jhcloos.com \
    --cc=evms-devel@lists.sourceforge.net \
    --cc=linux-kernel@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