From owner-freebsd-current Thu Oct 3 18:11:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 632EE37B401 for ; Thu, 3 Oct 2002 18:11:35 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4DF443E42 for ; Thu, 3 Oct 2002 18:11:34 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g941AwOo065334; Thu, 3 Oct 2002 21:10:59 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 3 Oct 2002 21:10:58 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Lars Eggert Cc: Poul-Henning Kamp , current Subject: Re: usermount with devfs In-Reply-To: <3D9C79A0.5040100@isi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 3 Oct 2002, Lars Eggert wrote: > So there is no more usermount under -current with devfs? Or is there > another way to have the symlinks be created with the different > permissions (since devfs rules don't seem to apply to them)? We used usermounts with devfs in our last TrustedBSD demo to our sponsor. In the demo, we manually manage the protections on the CD device -- since it doesn't disappear when the CD is inserted and removed, just when the device goes away, it works fairly well. We can also set protections at login for users as part of fbtab. I know that Warner's devd is more targetted at support newbus and device driver binding, but there was also (at one point) discussion of a devfsd that responded to device events. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message