From owner-freebsd-hackers Sun Jul 2 2:55:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (beachbum.freebsd.dk [212.242.127.222]) by hub.freebsd.org (Postfix) with ESMTP id E747C37BA87 for ; Sun, 2 Jul 2000 02:55:15 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id LAA01215; Sun, 2 Jul 2000 11:55:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: hackers@FreeBSD.org Subject: Re: Why do we always create a malloc disk for md? In-reply-to: Your message of "Sat, 01 Jul 2000 17:26:07 PDT." <395E8C1F.675AA7D1@bsdi.com> Date: Sun, 02 Jul 2000 11:55:04 +0200 Message-ID: <1213.962531704@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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