From owner-freebsd-current Tue Jan 26 02:42:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13915 for freebsd-current-outgoing; Tue, 26 Jan 1999 02:42:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13904 for ; Tue, 26 Jan 1999 02:42:52 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id LAA25359; Tue, 26 Jan 1999 11:41:08 +0100 (CET) To: Doug Rabson cc: Archie Cobbs , Maxim Sobolev , current@FreeBSD.ORG, Julian Elischer Subject: Re: DEVFS, the time has come... In-reply-to: Your message of "Tue, 26 Jan 1999 09:25:21 GMT." Date: Tue, 26 Jan 1999 11:41:06 +0100 Message-ID: <25357.917347266@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> No, it doesn't have to be SLICE. In particular, if we're going the >> SLICE way, it should be done >right<, and Julians SLICE code didn't >> do that. (I know, I spent close to 6 months prototyping the concept >> and julian had my code to work from). > >Wouldn't it be possible to fit this into the device system? If we treat >disks as devices and partition types as drivers, most of the boring work >of matching drivers to devices and keeping lists and trees of objects will >happen automatically. Well, as long as you remember that it is not a strict hierarchy: I could slice two disks, mirror the slices and concatenate the mirrors if I wanted to. It's not tricky to get it right, once you know where the pitfalls are, the trick is to get it right AND make it elegant. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message