From owner-freebsd-current Tue Feb 17 15:26:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19065 for freebsd-current-outgoing; Tue, 17 Feb 1998 15:26:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19015 for ; Tue, 17 Feb 1998 15:25:58 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA13845; Tue, 17 Feb 1998 16:25:51 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd013770; Tue Feb 17 16:25:43 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id QAA07146; Tue, 17 Feb 1998 16:25:39 -0700 (MST) From: Terry Lambert Message-Id: <199802172325.QAA07146@usr09.primenet.com> Subject: Re: devfs persistence To: sthaug@nethelp.no Date: Tue, 17 Feb 1998 23:25:39 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <22612.887749938@verdi.nethelp.no> from "sthaug@nethelp.no" at Feb 17, 98 10:12:18 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > - ln -s cuaa0 mouse > > > > This is somewhat non-sensical as well. The mouse should use a protocol > > virtualizer so that a /dev/mouse is reexported, and it doesn't matter > > what your physical mouse hardware is, the thing looks like a mousesystems > > (or other) mouse, always, so that programs don't have to care about this. > > Sure. But that makes XFree86 dependent on the mouse protocol virtualizer > also. Do you want to introduce more dependencies? (Just playing the > devil's advocate here.) Ask David Dawes. XFree86 already does this; it had to for SVR4. > > > Thus, if DEVFS is used, I want *some* way to have this happen > > > automagically when the machine is booted. /etc/rc.devices would be fine. > > > > You could do it this way, of course, but the permissions thing can > > be applied to the modules exporting the default attributes for a given clss, > > as a local configuration modification. > > That's fine. But no matter how you do it, you need some way of making > local modifications that stick, and that can be repeated at next bootup. Local transient modifications, or local build-time modifications? I would argue for build-time, and let you edit the class template data if you felt inclined to do it post-build. But I'm just being generous; there's no real reason for allowing that, especially in a first revision, since you always have rc.local. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message