From owner-freebsd-current  Tue Sep 22 20:44:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA17593
          for freebsd-current-outgoing; Tue, 22 Sep 1998 20:44:06 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17448;
          Tue, 22 Sep 1998 20:43:05 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA22172;
	Wed, 23 Sep 1998 13:42:45 +1000
Date: Wed, 23 Sep 1998 13:42:45 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199809230342.NAA22172@godzilla.zeta.org.au>
To: bde@zeta.org.au, tlambert@primenet.com
Subject: Re: DEVFS & SLICE?
Cc: abial@nask.pl, current@FreeBSD.ORG, jkh@time.cdrom.com,
        peter@netplex.com.au, sos@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> Now I remember why it is not such a good idea :-).  Removable disks may
>> not be there, and some disk drivers spew printfs when they are not there.
>> This was especially annoying for floppy disks under SLICE.  Keeping the
>> list in userland allows better control.
>
>Not only better control, but also the ability to become desynchronized
>from the current kernel, just like libkvm.  A highly desirable
>feature?

In a way.  Decoupling of libkvm from the currently running kernel helps
keep it working on dead kernels.  A desirable feature.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message