[2101] 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 (Garry Zacheiss)
Mon Feb 7 18:02:59 2000

Message-Id: <200002072302.SAA491762@opus.mit.edu>
To: Greg Hudson <ghudson@MIT.EDU>
cc: release-team@MIT.EDU
In-Reply-To: Your message of "Mon, 07 Feb 2000 17:16:27 EST."
             <200002072216.RAA01668@egyptian-gods.mit.edu> 
Date: Mon, 07 Feb 2000 18:02:02 -0500
From: Garry Zacheiss <zacheiss@MIT.EDU>

>> 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.

   I think we'd like to have this fixed if at all possible for
tomorrow's deploy, and I know Bill and Jonathon have expressed interest
in having the passwd problem fixed ASAP.   Having to copy Thomas's
source tree is a problem, but as long as you get the changes to him when
he shows gets back into town, it should be ok.  I'm in favor of
rebuilding the athena-ws package.

>> 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.

   I think it would be reasonable for you to force the acl on the als
locker in this instance.  

   I can set up /afs/athena/system/config/passwd/i386_linux22 (or
whatever) later this evening if we decide to go through with these
changes tonight.

>> 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.

   Agreed.  Modifying phase2 to chmod 666 all of the fd devices and
whatever is pointed to by the /dev/cdrom link sounds like the right
answer here.

Garry

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