[236] in athena10
Re: /svn/athena r23018 - trunk/debathena
daemon@ATHENA.MIT.EDU (Gregory Nathan Price)
Mon Jun 9 16:34:12 2008
Date: Mon, 9 Jun 2008 16:33:28 -0400
From: Gregory Nathan Price <price@MIT.EDU>
To: ghudson@mit.edu
Cc: athena10@mit.edu
Message-ID: <20080609203327.GD23318@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200806091804.OAA02067@drugstore.mit.edu>
On Mon, Jun 09, 2008 at 02:04:26PM -0400, ghudson@MIT.EDU wrote:
> +* clients: Provides clients (either locally-written, like athinfo and
> + Discuss, or configurations) for Athena services, as well as
> + Athena-specific utility programs like "jot". Configurations for
> + graphical client software are generally in the workstation package
> + instead, in order to make this package less intrusive.
> +
> +* standard: Implies locker and clients. Also provides Athena shell
> + customizations and dotfiles.
> +
> +* login: Implies standard. Configurations to merge the MIT user
> + namespace into the local machine namespace for the purpose of user
> + lookups and authentication.
> +
> +* workstation: Implies login. Configurations for the graphical login
> + system and graphical client software intended to provide a standard
> + X login experience using Athena home directories. Still in
> + development.
If I'm using Debathena on my laptop, I may want my graphical client
software configured for Athena printers and so forth even though I
don't use Athena home directories or logins. Perhaps these
configurations should be in standard.
Tim tells me those configuration packages wouldn't have to depend on
the graphical clients they configure, so this wouldn't interfere with
installing standard on a server.
Greg
PS - It'd be helpful to set the Reply-To on these commit messages to
athena10, if possible, so replies don't go accidentally to source-commits.
