From owner-freebsd-fs Mon Sep 18 14:26:55 2000 Delivered-To: freebsd-fs@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id C0B7D37B422; Mon, 18 Sep 2000 14:26:50 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id BAA27523; Tue, 19 Sep 2000 01:26:42 +0400 (MSD) Message-Id: <200009182126.BAA27523@aaz.links.ru> Subject: Re: device naming convention In-Reply-To: from "Marc Tardif" at "Sep 18, 0 04:31:03 pm" To: intmktg@CAM.ORG (Marc Tardif) Date: Tue, 19 Sep 2000 01:26:41 +0400 (MSD) Cc: dcs@newsguy.com, freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marc Tardif writes: > > > This is what I have in fdisk (from /stand/sysinstall): > > > Offset Size End Name PType Desc Subtype Flags > > > 0 63 62 - 6 unused 0 > > > 63 1937565 1937627 wd0s1 3 freebsd 165 C > > > 1937628 191268 2128895 - 6 unused 0 > > > > > > At this point, the second slice does not exist yet so I can't use it. For > > > problems in defining a slice, see next question. > > > > Really? I wouldn't expect FreeBSD to worry about the type being > > "unused". > > > If I try the following command as root, nothing is output: > # hd /dev/rwd0s2 | head > > Also, I tried writing a little c program to mmap(2) and, if that fails, > read(2) the device. Unfortunately, that didn't work either. It seems I do > actually need to define the slice as some type. The reason is maybe to > define the limits of the device. Therefore, the actual type is of little > importance but knowing where the device starts and stops could be > important for some reason. To make the system happy, I then defined the > slice as "partition type" 0, but fdisk still displayed "unused". Maybe > some obscur type which doesn't appear in the bootloader would be > preferable, if I find one... If this kind of information is relevant to > the mailing list, I'll post what I find. Use fdisk. See at begin and size of slices - nothing else affect until you boot or have another OS on your computer. in sysinstal last string mean that entryes for wd0s2, wd0s3 and wd0s4 are all size 0. So you can read EOF only. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message