From owner-freebsd-current Tue Feb 21 01:12:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id BAA12409 for current-outgoing; Tue, 21 Feb 1995 01:12:43 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id BAA12401; Tue, 21 Feb 1995 01:12:40 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Bruce Evans cc: obiwan!bob@uudell.us.dell.com, roberto@blaise.ibp.fr, current@FreeBSD.org, phk@ref.tfs.com Subject: Re: ATTENTION In-reply-to: Your message of "Tue, 21 Feb 95 17:55:53 +1100." <199502210655.RAA08777@godzilla.zeta.org.au> Date: Tue, 21 Feb 1995 01:12:35 -0800 Message-ID: <12396.793357955@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > The slice code will be mandatory but you won't see much evidence of > it. However, there is a lot of compatibility cruft to make the old > devices work transparently. I'd like this to go away soon. Devices > would have to be named differently in /etc/fstab and in config files, > e.g., /dev/sd0s2a instead of /dev/sd0a if /dev/sd0s2 is the first BSD > slice. (The partitions on the first BSD slice in the DOSpartition > table are aliased to /dev/[r]sd0[a-h]. This requires confusing Well, as far as I'm concerned the flag day has already been called and we can just do this in one jump. Slow transitions can be just as bad or worse than jumps, in my experience, and I'm keen to see this go forward so that we can start relying on the slice code for the new installation code. Jordan