--6Nae48J/T25AfBN4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Oct 26, 2005 at 07:14:03PM +0100, Rui Paulo wrote:
> On 2005.10.26 10:22:52 -0700, Bill Studenmund wrote:
> | On Mon, Oct 24, 2005 at 10:35:47PM +0200, Hans Petter Selasky wrote:
> | >=20
> | > Main features:
> | >=20
> | > - Implements FreeBSD's devfs on NetBSD.
> |=20
> | In the past, we (NetBSD folks) have talked about a devfs. One issue tha=
t=20
> | has come up (I'll be honest, I've raised it a lot) is a desire to retai=
n=20
> | permission changes across boots, and to tie devices (when possible) to =
a=20
> | device-specific attribute rather than a probe order.
> |=20
> | Does FreeBSD's devfs support locators and persistent information? Are=
=20
> | there plans to support something like that, if not?
>=20
> I remember Linux's devfs having a configure file for that particular
> objective. The user would set the permission flags in (I can't recall
> if this is the real name) /etc/devfsd.conf and let devfsd do the job.
>=20
> You could also use another directory for permissions, like /dev-state,
> but personally, I don't like this method.
>=20
> http://www.atnf.csiro.au/people/rgooch/linux/docs/devfs.html#persistence

He actually mentions a number of the things I thought about. Like devfs=20
being a layer and using the underlying nodes to hold the permissions.

Take care,

Bill

--6Nae48J/T25AfBN4
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFDYCGYWz+3JHUci9cRAho6AJ97QSqmPqdoL8mgoKPw1K9rg41xaACfSE7v
xTLzTmImWUUpJFLI4f4YdQE=
=c1U5
-----END PGP SIGNATURE-----

--6Nae48J/T25AfBN4--