From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a05071713584cc07bc0@mail.gmail.com>
Date: Sun, 17 Jul 2005 16:58:02 -0400
From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] First-timer help
In-Reply-To: <1157967bfafe737b9fd95aac5e417557@plan9.ucalgary.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <42DABCF0.9060708@moseslake-wa.com>
	<1157967bfafe737b9fd95aac5e417557@plan9.ucalgary.ca>
Topicbox-Message-UUID: 695f7d9a-ead0-11e9-9d60-3106f5b1d025

> generally -- yes.  only its owner (the user who started the file
> server) can access the administrative "area" on a file server, i.e.
> /srv/fscons.  there's only a single point of entry to allow one to
> modify files belonging to other users and that is the rather
> complicated dance of connecting to /srv/fscons, changing permissions
> of a file, disconnecting and then modifying it.
>=20
> if you feel adventurous you can set up an old-style (ken fs, as they're
> called) file server which completely disallows the running of any user
> processes.  on such machine there's no way to modify another user's
> files unless you're behind the keyboard/console of the machine or the
> user changes permissions to allow you to do so.

you can just as easily set up a fossil server that doesn't let
users cpu into the machine, and it will be just as isolated=20
as an old ken fs.

russ