From owner-freebsd-arch Tue Oct 31 19:34:42 2000 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1132537B479; Tue, 31 Oct 2000 19:34:35 -0800 (PST) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eA13YVn27377; Tue, 31 Oct 2000 20:34:31 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id eA13YlV41951; Tue, 31 Oct 2000 20:34:47 -0700 (MST) Message-Id: <200011010334.eA13YlV41951@billy-club.village.org> To: John Baldwin Subject: Re: Like to commit my diskprep Cc: arch@FreeBSD.org In-reply-to: Your message of "Tue, 31 Oct 2000 11:31:23 PST." References: Date: Tue, 31 Oct 2000 20:34:47 -0700 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message John Baldwin writes: : : On 31-Oct-00 Warner Losh wrote: : > Before anyone asks, the biggest difference between my diskprep and : > Matt's recent changes are that diskprep doesn't introduce a new api : > into the kernel and doesn't pollute disklabel with functions it : > traditionally hasn't done. Matt's changes put functionality into : > edisklabel and the kernel. : : Actually, I would think that creating a virgin disklabel would be : part of disklabel's job. After all, doesn't it make sense to use : the disklabel program to create/edit disklabel's? The problem is that FreeBSD/i386 needs to put two different labels on the disk. One is for the BIOS/legacy OSes that run on i386. The other is for FreeBSD. FreeBSD/alpha doesn't have this problem because it doesn't need the second set of labels. Other FreeBSD porst might need to have different things done in the future to make them co-exist with other native platforms. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message