From: Mike Fedyk <mfedyk@matchmail.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RAID superblock confusion
Date: Wed, 17 Apr 2002 19:59:39 -0700 [thread overview]
Message-ID: <20020418025939.GG574@matchmail.com> (raw)
In-Reply-To: <200204101533.g3AFXwS09100@vindaloo.ras.ucalgary.ca> <20020410184010.GC3509@turbolinux.com> <200204101924.g3AJOp113305@vindaloo.ras.ucalgary.ca> <20020410193812.GE3509@turbolinux.com> <200204102037.g3AKbmT14222@vindaloo.ras.ucalgary.ca> <15540.59659.114876.390224@notabene.cse.unsw.edu.au> <200204131926.g3DJQGI06532@vindaloo.ras.ucalgary.ca> <15550.10053.834276.18723@notabene.cse.unsw.edu.au> <20020418021053.GF574@matchmail.com> <15550.11818.429509.22486@notabene.cse.unsw.edu.au>
On Thu, Apr 18, 2002 at 12:23:38PM +1000, Neil Brown wrote:
> On Wednesday April 17, mfedyk@matchmail.com wrote:
> > On Thu, Apr 18, 2002 at 11:54:13AM +1000, Neil Brown wrote:
> > > On Saturday April 13, rgooch@ras.ucalgary.ca wrote:
> > > > If there was only a "do as I say, regardless" mode, I would be happy.
> > > > This programmer-knows-best attitude smacks of M$.
> > >
> > > mdadm will do as you say, reguardless - if you ask it to. Have you
> > > tried mdadm?
> > > http://www.cse.unsw.edu.au/~neilb/source/mdadm/
> >
> > Niel, do you plan to merge mdadm into the raidtools package? It sounds like
> > it belongs there.
>
> No.
> If distributions want to distribute mdadm together with the stuff from
> raidtools, then that is up to them.
> But from a development perspective, I don't see any value in making a
> single source distribution.
Why's that? Don't they compliment each other, or is mdadm a replacement?
If it's not a replacement, combining it with raidtools2 would probably get
it into distributions faster and people have already been taught with
countless how-tos that you need the raidtools package...
Hmm, checking now debian has already packaged mdadm for debian 3.0 (woody),
so raidtools just may become obsoleted so my argument is probably moot...
ehh, what's one more message on lkml anyway? ;)
Mike
next prev parent reply other threads:[~2002-04-18 2:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 15:33 RAID superblock confusion Richard Gooch
2002-04-10 18:40 ` Andreas Dilger
2002-04-10 19:24 ` Richard Gooch
2002-04-10 19:38 ` Andreas Dilger
2002-04-10 20:37 ` Richard Gooch
2002-04-10 21:36 ` Mike Fedyk
2002-04-10 21:39 ` Richard Gooch
2002-04-10 22:09 ` Mike Fedyk
2002-04-10 22:49 ` Richard Gooch
2002-04-10 23:36 ` Mike Fedyk
2002-04-11 10:07 ` Luigi Genoni
2002-04-13 19:29 ` Richard Gooch
2002-04-13 23:55 ` Mike Fedyk
2002-04-14 0:00 ` Richard Gooch
2002-04-14 0:17 ` Mike Fedyk
2002-04-11 1:38 ` Neil Brown
2002-04-11 2:41 ` Mike Fedyk
2002-04-11 6:42 ` Keith Owens
2002-04-11 8:37 ` Helge Hafting
2002-04-13 19:26 ` Richard Gooch
2002-04-18 1:54 ` Neil Brown
2002-04-18 2:10 ` Mike Fedyk
2002-04-18 2:23 ` Neil Brown
2002-04-18 2:59 ` Mike Fedyk [this message]
2002-04-18 14:49 ` Richard Gooch
2002-04-19 13:42 ` Luigi Genoni
2002-04-19 13:48 ` Richard Gooch
2002-04-20 0:50 ` Luigi Genoni
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 3:18 Neil Brown
2002-04-11 10:19 ` Luigi Genoni
2002-04-11 20:18 ` Mike Fedyk
2002-04-18 3:05 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=20020418025939.GG574@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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