martin f krafft wrote: > [...] > I am talking to upstream about removing them...
I think that this would be a good choice. > Do note that I *could* trojan the box even before it went live. Of > course, I won't, but you have to take my word for it. > > Then again, you're installing software I compiled. :) > > I just want you to be aware of that. Having said this, this wouldn't > be the first time I got root access to some machine to debug > a problem. > > Cheers, I know, Martin. This will be true until I'll trust you... and I definitely need to trust somebody until I can't check all of the code by myself, that means... never! If I'll ever get enough skills to do that, I'll still have not enough time... furthermore, I'm pretty sure that _you_ will never do that. Anyway, let's see the output of # sh -x /etc/init.d/mdadm-raid you can find it attached here. At line 127 you will read: + set -- mdadm: /dev/md1 assembled from 1 drive - need all 2 to start it '(use' --run to 'insist).' It seems that the behaviour of mdadm with and without --scan option is the opposite of what manpage says: without --scan the devices can be started immediately, whereas with --scan also --run is required. A quick test I made confirms exactly this behaviour; by adding --run to line 33 in /etc/init.d/mdadm-raid I could boot successfully with only 1 drive active. Mau
sh_x_mdadm-raid_start.gz
Description: GNU Zip compressed data
