swraidctl - yes, it is long, but is it much longer than apachectl? No, it is
exactly the same length. It is much more descriptive than raidctl as it
specifies that this is software raid, and it is more obvious than mdctl. I
know I and others I work with were generally confused at first with the
OK...I'll stick my (worthless) opinion in here.
I personally like root-based packages...so all I have to do is type
raidtab to see all my raid commands:
Already OK:
raidstart
raidstop
raidhotadd
raidhotremove
raidsetfaulty
raid0run
Need:
raidmk (instead of mkraid)
raidmdctl
raidmkpv (instead
On Tue, 12 Jun 2001, Micah Anderson wrote:
swraidctl - yes, it is long, but is it much longer than apachectl? No, it is
exactly the same length. It is much more descriptive than raidctl as it
specifies that this is software raid, and it is more obvious than mdctl. I
know I and others I
On Tue, 12 Jun 2001, Mike Black wrote:
Need:
raidmk (instead of mkraid)
raidmdctl
Why raid+md? Either stick with md or with raid.
If we asume that all commands should start with raid, I'd like
to see a
raidctl
or
raidctrl
command, not a raidmdctl!
Just my 2 euro cents :)
--
MfG /
I agree the patch isn't a complete solution to all that potentially ails
raidtools. All the patch does is address one specific case -- the case
where /sbin/raidstart gives up when it can't get a superblock from the first
entry in raidtab, even though it could have read the superblock from one of
