[2106] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: Linux-Athena issue status

daemon@ATHENA.MIT.EDU (Thomas Bushnell, BSG)
Mon Feb 7 20:12:34 2000

To: Greg Hudson <ghudson@MIT.EDU>
Cc: release-team@MIT.EDU
From: tb@MIT.EDU (Thomas Bushnell, BSG)
Date: 07 Feb 2000 20:12:26 -0500
In-Reply-To: Greg Hudson's message of "Mon, 7 Feb 2000 17:16:27 -0500"
Message-ID: <u1h900wbipx.fsf@pusey.mit.edu>

Greg Hudson <ghudson@MIT.EDU> writes:

> 	   To fix this, we need to modify athena-ws.rc and rebuild the
> 	   athena-ws package.  Right now athena-ws.rc only lives in
> 	   Thomas's local working directory on kempis (a machine which
> 	   I have remote access to, but not root access).  I can
> 	   rebuild athena-ws by making a copy of the relevant parts of
> 	   his working directory, but I'm worried about further
> 	   confusing an already not-settled process.

My copy is entirely checked in (I just checked); are you sure you are
looking at the athena-8_3-linux branch?

In any case, the present problem is the initially installed version;
the maintenance fixup of the file is much less urgent, it seems to
me. 

> 	   The installer script (phase2) should probably initialize
> 	   the passwd and shadow files as well.  The source for this
> 	   script lives in /mit/als/src/installer, which I do not have
> 	   write access to and which uses only numbered emacs backup
> 	   files for version control.  I do have write access to the
> 	   production location for the installer script, of course.

Yes; that seems entirely fine.

> 	2. The floppy and CD-ROM devices are more fascist than we'd
> 	   like, at least on public machines.  We have a couple of
> 	   options here depending on what we want to have happen, but
> 	   probably the best choice is to make the installer phase2
> 	   script chmod the devices.

I believe this is entirely the correct approach.

Thomas

home help back first fref pref prev next nref lref last post