Bug#223840: md0 in kopt line

[Jamie Wilkinson]

So I just migrated a sid box to RAID-1 and thus I wanted the kopt line
to include my raided root partition, like so:

## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/md0 ro

And of course I get the same message as Brendon:

/dev/md0 does not have any corresponding BIOS drive.

which is all well and good, and so I thought "well I'll just fake it in
the device.map"...

(hd0)	/dev/md0

and that *seems* to fix it :-) ... it runs and claims to have set up the
kernels properly but there's an expr error which I traced to convert()
around line 141 could be modified to let md0 match in the sed command.

So most of this is just speculation... the groot option still sets the
default grub root device so the kopt root should only affect what gets
passed to the kernel during boot, so it should be fine... but of course
I haven't rebooted this machine yet and thus can't guarantee anything. 
At least the menu.lst looks right after adding 'm' to the right place in
the sed above.

-- 
Jamie Wilkinson
Systems Administrator, Anchor Systems