Date: Sat, 01 Jul 2000 17:26:07 -0700 From: John Baldwin <jhb@bsdi.com> To: phk@FreeBSD.org Cc: hackers@FreeBSD.org Subject: Why do we always create a malloc disk for md? Message-ID: <395E8C1F.675AA7D1@bsdi.com>
next in thread | raw e-mail | index | archive | help
I'm attempting to resolve why sysinstall keeps dying in -current
at the moment. It seems that the problem is that md_drvinit()
always creates a malloc disk during initialization:
static void
md_drvinit(void *unused)
{
...
[ load preloaded disks such as mfsroot.tgz from install floppy ]
printf("md%d: Malloc disk\n", mdunits);
mdcreate_malloc();
}
This results in having two md devices during boot:
md0: Preloaded image </mfsroot> mumble bytes at 0xmumble
md1: Malloc disk
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?
--
John Baldwin <jhb@bsdi.com> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?395E8C1F.675AA7D1>