In message <[EMAIL PROTECTED]>, John Baldwin writes:
>This ends up registering md1 with disk_create, and thus md1
>is returned as a disk through kern.disks into the list returned
>by Disk_Names(), and sysinstall blows up when it tries to open
>it. I think the reason it blows up is because /dev/md1 isn't
>around, although I think I may be able to fix that by adding
>'md' as a disk device in the table in sysinstall/devices.c.\
>However, I'm curious if md1 should be created in this case?
Your diagnosis is correct. sysinstall should ignore md* disks.
The reason md1 is created is that it is the beginning of an
"almost-clone" implementation.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
