From owner-freebsd-current Tue Apr 28 01:06:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19206 for freebsd-current-outgoing; Tue, 28 Apr 1998 01:06:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19198 for ; Tue, 28 Apr 1998 01:06:32 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id IAA25517; Tue, 28 Apr 1998 08:05:28 GMT Date: Tue, 28 Apr 1998 17:05:28 +0900 (JST) From: Michael Hancock To: Joel Ray Holveck cc: ambrisko@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: DEVFS & sound drivers question In-Reply-To: <199804280735.CAA04409@detlev.UUCP> 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 On Tue, 28 Apr 1998, Joel Ray Holveck wrote: > >> Should DEVFS make these devices (MAKEDEV did)? > >> Should these be made as a sym-link and can DEVFS make a sym-link? > > DEVFS doesn't have a way to deal with user configured persistent data yet. > > Julian is talking about doing it with /etc/rc.devfs or something like > > that. > > The way refcounting works is confusing and has lead to tangents in the > > skeleton code for these ops, see VNSLEAZE. > > Would a union filesystem be a good thing here, or would it kinda just > defeat the purpose of devfs? Either rc.devfs or union is ok, handling persistent user configs in devfs is probably not worth the trouble. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message