From owner-freebsd-hackers  Mon Jun 12 19:30:21 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id TAA00816
          for hackers-outgoing; Mon, 12 Jun 1995 19:30:21 -0700
Received: from rah.star-gate.com (bettina.star-gate.com [204.188.121.18])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA00794
          for <freebsd-hackers@freebsd.org>; Mon, 12 Jun 1995 19:30:19 -0700
Received: from localhost.v-site.net (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.6.11/8.6.9) with SMTP id TAA03660; Mon, 12 Jun 1995 19:17:39 -0700
Message-Id: <199506130217.TAA03660@rah.star-gate.com>
X-Authentication-Warning: rah.star-gate.com: Host localhost.v-site.net didn't use HELO protocol
X-Mailer: exmh version 1.6delta 4/7/95
To: Poul-Henning Kamp <phk@ref.tfs.com>
cc: freebsd-hackers@freebsd.org
Subject: Re: Extended DOS partition support? 
In-reply-to: Your message of "Mon, 12 Jun 1995 14:40:48 PDT."
             <199506122140.OAA23638@ref.tfs.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 12 Jun 1995 19:17:37 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: hackers-owner@freebsd.org
Precedence: bulk

>>> Poul-Henning Kamp said:
 > > [extended DOS parts]
 > > 
 > > Actually, it stop working a while back and I can't no longer mount
 > > my dos partition. My DOS disk does not have a BSD label. A while
 > > back Julian gave me a patch to synthetize a BSD label from a DOS label.
 > > It all work fine till a few weeks ago. I believe that Julian submitted
 > > his patch a while ago.
 > 
 > Amancio, in a friendly and constructive manner I'd like to suggest you
 > RTFM/RTFS before you start confusing people more than needed.
 > 
 > It works, it works well, all you have to do is mount /dev/wd0s5 for instance
     .

I am curious where is this slice stuff documented.
On my system, which I suped and "make world" on saturday.
MAKEDEV does not create a /dev/wd0s5 so I created one. When I tried
mount -t msdos /dev/wd0s5 , the system claims that the device is not 
configured. Fine, so I went down the list  till /dev/wd0s1 which seems to work
on my system over here.

This is what I have on my system:
brw-r-----  1 root  operator    0, 131074 Jun 12 18:56 /dev/wd0s1
brw-r-----  1 root  operator    0, 196610 Jun 12 18:56 /dev/wd0s2
brw-r-----  1 root  operator    0, 262146 Jun 12 18:56 /dev/wd0s3
brw-r-----  1 root  operator    0, 327682 Jun 12 18:56 /dev/wd0s4
brw-r-----  1 root  operator    0, 393218 Jun 12 18:56 /dev/wd0s5

	Amancio