Date: Sun, 02 Jul 2000 11:55:04 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: John Baldwin <jhb@bsdi.com> Cc: hackers@FreeBSD.org Subject: Re: Why do we always create a malloc disk for md? Message-ID: <1213.962531704@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 01 Jul 2000 17:26:07 PDT." <395E8C1F.675AA7D1@bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <395E8C1F.675AA7D1@bsdi.com>, 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 phk@FreeBSD.ORG | 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 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?1213.962531704>