From owner-freebsd-current Mon Mar 16 05:59:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18288 for freebsd-current-outgoing; Mon, 16 Mar 1998 05:59:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from netcom1.netcom.com (mvh@netcom15.netcom.com [192.100.81.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18228; Mon, 16 Mar 1998 05:59:49 -0800 (PST) (envelope-from mvh@netcom.com) Received: (from mvh@localhost) by netcom1.netcom.com (8.8.8/8.8.8) id FAA00815; Mon, 16 Mar 1998 05:59:33 -0800 (PST) (envelope-from mvh) Date: Mon, 16 Mar 1998 05:59:33 -0800 (PST) Message-Id: <199803161359.FAA00815@netcom1.netcom.com> From: "Michael V. Harding" To: ast@marabu.ch CC: current@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: <199803152315.AAA25361@marabu.marabu.ch> (message from Adrian Steinmann on Mon, 16 Mar 98 00:15:25 +0100) Subject: Re: HEADS UP / disk slicing: a MAKEDEV deficiency for slices>0 ? References: <199803152315.AAA25361@marabu.marabu.ch> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll concur on this one - with dual boot machines, FreeBSD is often on the second disk or second partitionm - this is why we saw boot fail. Not too hard to fixe once you know what you are doing, but it was awkward because I couldn't even check the FAQ until I got the system running again. I don't know if this is because I have two disks, also, but when I did an upgrade in place to 2.2.6 it ate the entire disk. I'm afraid to use anything but CVSUP now. Luckily I did have the important stuff backed up... Content-Type: text/plain X-Nextstep-Mailer: Mail 3.3 (Enhance 2.0b6) From: Adrian Steinmann Date: Mon, 16 Mar 98 00:15:25 +0100 cc: stable@FreeBSD.ORG X-Organization: Steinmann Consulting, Apollostrasse 21, 8032 Zurich X-Phone-Numbers: Switzerland, Tel +41 1 380 30 83 Fax +41 1 380 30 85 Sender: owner-freebsd-stable@FreeBSD.ORG X-UIDL: 4f9b60e355e64f6e873812ec122fccae I have been watching the escalation of this HEADS UP and must admit that I've become more confused than I was before. So I will add some more confusion myself ;-) It seems that, for now, 'make world' in -stable sets -DROOTSLICE_HUNT to maintain downward compatibility in the mount source files. Good. It also appears, though, that /dev/MAKEDEV only makes the [a-h] partitions for s0, so this might be why some people are having problems booting with their "new /etc/fstab" (in fact, I believe this would happen when their root partition is not on slice 0). I've tracked this feature of MAKEDEV back to revision 1.76: $ co -r1.76 -p MAKEDEV,v |grep s0h MAKEDEV,v --> standard output revision 1.76 for slicepartname in s0h s1 s2 s3 s4 $ co -r1.75 -p MAKEDEV,v |grep s0h MAKEDEV,v --> standard output revision 1.75 Where we read this comment: revision 1.76 date: 1995/03/04 12:22:14; author: bde; state: Exp; lines: +56 -70 For sd, vn and wd: Support sliced devices better. E.g.: `sh MAKEDEV sd0' creates [r]sd0 and [r]sd0s[1-4] as well as [r]sd0[a-h] (the extra devices created by default won't hurt apart from wasting inodes). `sh MAKEDEV sd0s1[a-h]' creates [r]sd0s1[a-h] (any partition creates all). `sh MAKEDEV sd0s5' creates [r]sd0s5. Support unit numbers 0-31 (was 0-6). Note, in particular, that '(cd /dev; ./MAKEDEV all)' will not make the [a-h] partitions on any slices > 0. Maybe it's time to change the line for slicepartname in s0h s1 s2 s3 s4 to for slicepartname in s0h s1h s2h s3h s4h so that /dev/MAKEDEV makes the [a-h] /dev entries for all slices? Adrian _________________________________________________________________________ Dr. Adrian Steinmann Steinmann Consulting Apollostrasse 21 8032 Zurich Tel +41 1 380 30 83 Fax +41 1 380 30 85 Mailto:ast@marabu.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message