From: William Thompson <wt@electro-mechanical.com>
To: Samuel Flory <sflory@rackable.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: PDC20267 + RAID can't find raid device
Date: Fri, 7 Jun 2002 15:58:23 -0400 [thread overview]
Message-ID: <20020607155823.S7291@coredump.electro-mechanical.com> (raw)
In-Reply-To: <20020606111918.F7291@coredump.electro-mechanical.com> <1023391095.3423.112.camel@flory.corp.rackablelabs.com> <1023463727.25522.39.camel@irongate.swansea.linux.org.uk> <1023479646.3700.174.camel@flory.corp.rackablelabs.com>
> > > One major issue for me is that you can use, and mount both the
> > > /dev/ataraid/d0 devices, and the /dev/hd devices. This makes for lots
> > > of fun in the Red Hat installer, and Cerberus.
> >
> > Stupidity management for the superuser is a user space issue in Unix
> > systems. If the RH installer does let you do stupid things, please
> > bugzilla it.
>
> Actually I was looking at what it would take to add support for
> ataraid in the RH installer. Is there some simple way to determine that
> a device is a part of an ataraid array? Parsing dmesg makes for some
> really ugly and easily broken code.
The controller IIRC writes this information on the disk. I'm pretty sure
it's toward the end of the disk though.
next prev parent reply other threads:[~2002-06-07 20:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 15:19 William Thompson
2002-06-06 19:18 ` Samuel Flory
2002-06-06 19:20 ` William Thompson
2002-06-06 19:32 ` Samuel Flory
2002-06-06 19:44 ` William Thompson
2002-06-07 13:44 ` William Thompson
2002-06-07 15:28 ` Alan Cox
2002-06-07 19:54 ` Samuel Flory
2002-06-07 19:58 ` William Thompson [this message]
2002-06-06 19:47 ` Alan Cox
2002-06-06 19:10 ` William Thompson
2002-06-07 15:36 ` William Thompson
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=20020607155823.S7291@coredump.electro-mechanical.com \
--to=wt@electro-mechanical.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sflory@rackable.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
all inboxes | Powered by JetHome®