From owner-freebsd-current Sun Mar 8 22:46:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16583 for freebsd-current-outgoing; Sun, 8 Mar 1998 22:46:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16567 for ; Sun, 8 Mar 1998 22:46:40 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id HAA08109; Mon, 9 Mar 1998 07:41:54 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199803090641.HAA08109@ocean.campus.luth.se> Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-Reply-To: <199803090201.SAA12336@dingo.cdrom.com> from Mike Smith at "Mar 8, 98 06:01:12 pm" To: mike@smith.net.au (Mike Smith) Date: Mon, 9 Mar 1998 07:41:54 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Mike Smith: > > Also, on my other machine I have a SCSI disk for freebsd, and a IDE disk > > for Win95. Computer boots from the ide, and then I use booteasy there to > > boot from the SCSI disk. The SCSI disk is not "dangerously dedicated", > > but it's just one big BSD slice. So... will I need "sd0s1a" on that, > > or just "sd0a"? > > The changes I have made *only* affect the boot device. The remainder > of the "compatability slice" implementation remains. > > Note, however, that when you move to DEVFS, there will not be any sd0[a-h] > nodes *in* /dev/, so you wouldn't be able to mount them even if you > wanted to. Ok, let's see if I got this right. :-) * Only the boot device is affected. ( even when boot != FreeBSD root ) * Above point is only effective until you start using DEVFS. * Dedicated disks ARE affected by this change. * "Dangerously dedicated" disks are NOT affected by this change. How many right? :-) /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message