On Sunday June 17, [EMAIL PROTECTED] wrote: > > Hi! A quick opinion if you do not mind.. I never mind hearing opinions (though I might choose to ignore some). > > What is a sysadmin thinking when something is wrong with the raid array > he installed two years ago, and he has forgotten what is the name of the > driver and everything about it? He thinks 'how can I check about this > RAID stuff? How about some program called "raid"-something?' Hmm. What is a sysadmin thinking when (s)he allows hir self to forget how to maintain a critical system? I agree with the comments of others that "man -k raid" if where they could start looking, and it should give the right answer. Another "obvious" place to look would be /etc/init.d (or /etc/rc.d/init.d for those with non-standard file systems:-). I would hope that ls /etc/init.d/*raid* would find a script that would aid in starting, stopping, and otherwise managing the raid arrays on the system. > > I think md driver as the most popular software raid solution in Linux > deserves to use command names like raid*. "raidctrl" stands out to > panicking sysadmin instantly. Think about humans using your technology, > it's not the only thing they do for a living! A fair comment, but I think that it simply isn't possible to pick a name what will be *right* for everyone. "raidctrl" would stand out to the panicking owner of a firmware raid solution too, but it wouldn't help them. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED]
