From owner-freebsd-current  Sat Apr 15 14:26:53 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id OAA01814
          for current-outgoing; Sat, 15 Apr 1995 14:26:53 -0700
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA01806
          for <freebsd-current@FreeBSD.org>; Sat, 15 Apr 1995 14:26:52 -0700
Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id OAA22122; Sat, 15 Apr 1995 14:24:35 -0700
From: Poul-Henning Kamp <phk@ref.tfs.com>
Message-Id: <199504152124.OAA22122@ref.tfs.com>
Subject: Re: 0412-SNAP is FUBAR
To: jkh@freefall.cdrom.com (Jordan K. Hubbard)
Date: Sat, 15 Apr 1995 14:24:35 -0700 (PDT)
Cc: kargl@crosby.apl.washington.edu, bde@zeta.org.au,
        freebsd-current@FreeBSD.org
In-Reply-To: <1389.797980391@freefall.cdrom.com> from "Jordan K. Hubbard" at Apr 15, 95 02:13:11 pm
Content-Type: text
Content-Length: 671       
Sender: current-owner@FreeBSD.org
Precedence: bulk

> > When is the scsi version of the slice code scheduled for prime time use?
> 
> The minute you see the commit messages go into sysinstall saying
> "make this utility understand slices" :-)
> 

More like, "you can grab the sd.c and wd.c from current and recompile
your kernel".

Sysinstall is only a tool for loading FreeBSD onto the disk, the kernel
is all fine and ready to use slices.

Problem is, until we fix sysinstall, we cannot use the "new" sd.c and wd.c
on the distribution  :-(

-- 
Poul-Henning Kamp <phk@login.dknet.dk> -- TRW Financial Systems, Inc.
'All relevant people are pertinent' && 'All rude people are impertinent'
=> 'no rude people are relevant'