From owner-freebsd-current Tue Sep 15 15:40:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27252 for freebsd-current-outgoing; Tue, 15 Sep 1998 15:40:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27191 for ; Tue, 15 Sep 1998 15:40:31 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA00358; Tue, 15 Sep 1998 15:30:19 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdnHN351; Tue Sep 15 22:30:18 1998 Date: Tue, 15 Sep 1998 15:30:12 -0700 (PDT) From: Julian Elischer To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: Help, DEVFS/MFS is broken... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's all irrelevent now as someone deleted all the SLICE stuff out of the kernel tree. Apparently phk an sos are now doing all the work to make devices dynamic. They will probably delete all the devfs code as well so that they have a clean slate to work on.. (I only discoverd it when all my slice files were deleted from my tree on 'cvs update') It seems that an abstracted disk layer is not considered important enough to work on.. On Mon, 14 Sep 1998, Andrzej Bialecki wrote: > Hi, > > This is yet another call for help to all those who know the filesystems, > to help fix this bug before 3.0-R... This is a genuine bug which panics [...] > > Andrzej Bialecki julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message