[3253] in Release_7.7_team
Re: Dealing with Linux Athena and restricted packages.
daemon@ATHENA.MIT.EDU (Aaron M. Ucko)
Fri Apr 26 22:43:19 2002
To: Greg Hudson <ghudson@MIT.EDU>
Cc: Bill Cattey <wdc@MIT.EDU>, release-team@MIT.EDU
From: amu@alum.mit.edu (Aaron M. Ucko)
Date: 26 Apr 2002 22:43:10 -0400
In-Reply-To: <1019873167.5735.30.camel@error-messages.mit.edu>
Message-ID: <udlit6dkgjl.fsf@multics.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Greg Hudson <ghudson@MIT.EDU> writes:
> Not really. The only overlap in program names between transcript and
> psutils is psnup; that leaves:
>
> ps4014
> ps630
> pscat
> pscatmap
> psdit
> psdraft
> psfax
> pslpr
> psplot
> psrev
> psroff
>
> It may be that some of the same functionality exists in psutils with
> different interfaces; I don't know. I also don't know how often the
> above commands are used. But it's certainly not accurate to say that
> psutils provides painless equivalents of "much of the rest" of what's in
> Transcript.
Whoops, true; apologies for being sloppy. Looking at this list, I'd
say that groff takes care of psdit/psroff, pstops from psutils can do
the equivalent of psrev, and there seems to be a suite called psptools
with a replacement for pslpr; what's left seems pretty arcane.
I suppose yet another way to deal with transcript would be sticking
the binaries in a locker restricted to system:authuser (possibly with
"mit" thrown in) and providing attachandrun scripts.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
Finger amu@monk.mit.edu (NOT a valid e-mail address) for more info.
