From owner-freebsd-bugs Tue Mar 28 21:21:54 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA21566 for bugs-outgoing; Tue, 28 Mar 1995 21:21:54 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA21558; Tue, 28 Mar 1995 21:21:53 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id VAA01004; Tue, 28 Mar 1995 21:21:15 -0800 Message-Id: <199503290521.VAA01004@precipice.shockwave.com> To: "Jordan K. Hubbard" cc: freebsd-bugs@freefall.cdrom.com Subject: Re: kern/280: new slice manager totally confused about old slice disks In-reply-to: Your message of "Tue, 28 Mar 1995 19:23:25 PST." <4104.796447405@freefall.cdrom.com> Date: Tue, 28 Mar 1995 21:21:15 -0800 From: Paul Traina Sender: bugs-owner@FreeBSD.org Precedence: bulk From: "Jordan K. Hubbard" Subject: Re: kern/280: new slice manager totally confused about old slice dis >>ks > 1) It looks like the implicit label stuff for unlabeled disks is > non-functional? I cannot ask disklable to read the pseudo-label off > of sd1 Maybe if you specify /dev/sd0d explicitly? Works for me! root@precipice$ disklabel /dev/sd1d disklabel: /dev/sd1d: Invalid argument root@precipice$ disklabel sd1 disklabel: ioctl DIOCGDINFO: Invalid argument However, I was very wrong about the disk never having a label. It used to be my old root drive, and I think a FreeBSD 1.1 label might still exist having not been overwritten, even though the entire disk is now a DOS drive... this leads me to wonder... sd1s1: start 32, end = 819199, size 819168: OK sd1s2: start 819200, end = 2041855, size 1222656: OK sd1s5: start 819232, end = 2041855, size 1222624: OK > 2) All of this slice stuff is really verbose and I think gratuitous. > Note: I am using older boot blocks that don't support -v, so it Agreed! > 2) When the system is booting, it whines loudly about partitions not being > inside slices... this may indeed be an error condition, but that's the > way FreeBSD 2.0 did things, so you're going to have a hell of a support > problem with these new slice changes. Agreed again. We're going to need to deal with this somehow, or users are going to SCREECH. Bruce is safe over there in OZ, but I know that folks like Poul and I are going to get hundreds of mails in our boxes! :-( > 3) Oh where oh where has my MSDOS partition gone? Oh where oh where > can it beeeeee? Try copying the new MAKEDEV over and doing a ./MAKEDEV sd0, then try: mount -t msdos /dev/sd0s1 /dos Assuming, of course, that slice 1 is the DOS partition. This is actually a very GOOD part of the change and I'm happy that we have it. It will make auto-detecting and mounting the DOS partition from the install much easier (I can just look to see what partition is a DOS partition and then mount the corresponding slice). I'm a little fuzzy on something, what is a slice vs a partition? Is a slice one of the one of four (recursive) classic DOS partitions or is a slice a UNIX disklabel partition?