linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Thomas Horsten <thomas@horsten.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: New mailing list for 2.6 Medley RAID (Silicon Image 3112 etc.) BIOS RAID development
Date: Mon, 9 Feb 2004 13:11:44 +0100	[thread overview]
Message-ID: <20040209121144.GA24503@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0402091155040.8715-100000@jehova.dsm.dk>

[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]

On Mon, Feb 09, 2004 at 12:01:55PM +0000, Thomas Horsten wrote:
> On Mon, 9 Feb 2004, Arjan van de Ven wrote:
> 
> > > The reason I insist on autodetection is that I think it's important that if
> > > the BIOS will reckognise the drive without additional intervention, so will
> > > Linux. This will make the entry route for newbies much simpler.
> >
> > do you call running devicemapper tools from the initrd autodetection ?
> 
> Probably not. I am working with several ways of doing it, and that's why I
> wanted to have a discussion about this.
> 
> Ideally I'd want something like the MD autodetect code, so that the whole
> thing can be set up by the kernel at boot-time if the necessary drivers
> are compiled in (by reading the Medley superblock the same way it's done
> for 0xfe partitions).

I (and I suspect a lot of other folks) rather get rid of such autodetect and
move it to userspace. Either via initrd or initramfs.

> Having autodetection at kernel level would make it possible to boot from a
> kernel on a floppy disk without initrd support, and in general make a
> system easier to set up.

initrd/initramfs is increasingly becoming mandatory sort of, and it's
actually easy if not even default to set up. (Eg on Fedora / Red Hat even
just typing make install will auto-create this for you)

> But the reason I wanted this discussion is to figure out the best way to
> go about it, and if there are some good arguments against autodetecting in
> the kernel I'll listen to them.

It doesn't really belong there.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-02-09 12:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-09  1:23 New mailing list for 2.6 Medley RAID (Silicon Image 3112 etc.) BIOS RAID development Thomas Horsten
2004-02-09  2:47 ` Neil Brown
2004-02-09  2:56   ` Thomas Horsten
2004-02-09  9:50 ` Arjan van de Ven
2004-02-09 12:01   ` Thomas Horsten
2004-02-09 12:11     ` Arjan van de Ven [this message]
2004-02-09 12:37       ` Thomas Horsten
2004-02-09 16:57         ` Jeff Garzik
2004-02-09 17:54           ` Dominik Kubla
2004-02-09 22:39         ` Neil Brown
2004-02-09 18:00       ` Thomas Horsten
2004-02-09 22:40         ` Neil Brown

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=20040209121144.GA24503@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=thomas@horsten.com \
    /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).