From owner-freebsd-current Sun Sep 20 07:49:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04847 for freebsd-current-outgoing; Sun, 20 Sep 1998 07:49:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04831 for ; Sun, 20 Sep 1998 07:49:28 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id HAA17774; Sun, 20 Sep 1998 07:48:22 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Peter Wemm cc: Timo Geusch , current@FreeBSD.ORG Subject: Re: DEVFS & SLICE? In-reply-to: Your message of "Sun, 20 Sep 1998 22:11:44 +0800." <199809201411.WAA02481@spinner.netplex.com.au> Date: Sun, 20 Sep 1998 07:48:22 -0700 Message-ID: <17770.906302902@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I for one am rather pissed off about the removal of SLICE. > > In particular, it's crippled a critical part of devfs at mountroot time, > although I'd argue that the parts that I'm most annoyed about the loss of > should have really been part of the DEVFS option than part of "SLICE". > The really sad part is that the existing geometry system isn't really up > to the task of booting without a real /dev. (ie: can't access /dev/da0s1a > via devfs to mount root unless an access to /dev/da0s1 happens first) Would it be possible to enhance DEVFS before release time to get back just those elements of the-code-formerly-known-as-SLICE necessary to make DEVFS itself useful again? I personally don't use DEVFS nor would I recommend it to the casual user (it's way too easy to crash your system with it), but for those who really want to, it seems worthwhile to try and make it at least minimally functional. Of course, the real problem here (IMO) is that DEVFS has neither an architect nor an owner. It is another one of our orphaned children, abandoned on FreeBSD's doorstep, and in order for it (or something different calling itself by the same name) to really succeed in FreeBSD, that's what really has to change first. Any takers? Hey, where'd everybody go? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message