Re: Do we want a server on `/servers/machine' (or similar)?

--===============0410989508==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-ScQyUZTDyhrK/11w7nk5"


--=-ScQyUZTDyhrK/11w7nk5
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2007-05-11 at 00:06 +0200, Thomas Schwinge wrote:
> Now, if Roland suggests to separate the i/o port and memory access
> interfaces then we could (for example) simply have the suggested
> `/servers/ioperm' and a `/servers/mem' (or `/dev/mem'? -- but our thing
> is more advances than the usual Unix system's `/dev/mem' is, so we'd
> rather put it into `/servers/', I think).

/dev/mem is a specific thing; writes to /dev/mem are supposed to write
physical memory addresses directly.  Nothing prevents such an interface
being used for this purpose, but it doesn't seem to me that it would be
possible to have fine-grained control over /dev/mem and still maintain
that interface.

Thomas


--=-ScQyUZTDyhrK/11w7nk5
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBGQ9PmqMsB9b6fcOoRAvbiAJ0UDaOG9dLWrzv0w2cGZ8Hw8abeVwCdHRJ8
FVd+cXeNhR1K1CYkNEEjMG0=
=Q1e8
-----END PGP SIGNATURE-----

--=-ScQyUZTDyhrK/11w7nk5--






--===============0410989508==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hurd-devel-readers mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/hurd-devel-readers

--===============0410989508==--