From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Mike Fedyk <mfedyk@matchmail.com>,
Andreas Dilger <adilger@clusterfs.com>,
linux-kernel@vger.kernel.org
Subject: Re: RAID superblock confusion
Date: Thu, 18 Apr 2002 08:49:21 -0600 [thread overview]
Message-ID: <200204181449.g3IEnLE12555@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <15550.11818.429509.22486@notabene.cse.unsw.edu.au>
Neil Brown writes:
> 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.
But from a user perspective, it's a pain the in ass to have to
download yet another package to do what raidtools do, just do it
properly. And having multiple packages doing nearly the same thing is
really confusing. Users won't know which one to pick.
<rant>
Every wanker out there wants to write their own cool tool, and since
sound and graphics are both l33t, why not do both at once? The result
is that we have (to name one example) a plethora of audio mixer
control tools.
Since I'm not in the "in crowd", and I just want a tool that lets me
frob the mixer, I wasted lots of time downloading many different
tools, reading the README's and compiling ones that didn't depend on
some bloated library (glibc, KDE or Gnome). Then waste more time
finding out which ones actually worked properly.
If resources were pooled, rather than all this ego stroking, we might
have something that (most importantly) works, is lightweight and is
usable for everyone, not just the users of the One True Desktop[R].
</rant>
Please let's just have one set of MD utilities.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2002-04-18 14:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 15:33 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
2002-04-18 14:49 ` Richard Gooch [this message]
2002-04-19 13:42 ` Luigi Genoni
2002-04-19 13:48 ` Richard Gooch
2002-04-20 0:50 ` Luigi Genoni
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=200204181449.g3IEnLE12555@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--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
all inboxes | Powered by JetHome®