[4024] in testers
Re: xss not ready for prime time
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue May 18 19:06:12 1999
Message-Id: <199905182306.TAA29541@small-gods.mit.edu>
To: Joseph Sokol-Margolis <seph@MIT.EDU>
Cc: testers@MIT.EDU
In-Reply-To: Your message of "Tue, 18 May 1999 18:09:33 EDT."
<199905182209.SAA09941@oliver.mit.edu>
Date: Tue, 18 May 1999 19:06:00 EDT
From: Greg Hudson <ghudson@MIT.EDU>
> if you try and run xss-button, it should tell you to run xss-button
> instead of xss (okay, this isn't really a bug)
"Huh?" Is there a mistake in that sentence?
> it writes it's preferences to $HOME/.xscreensaver as it's installed
> as xss, it should probably save to $HOME/.xss
This was intentional. The configuration file should be interoperable
with a normal installation. (Or does it dump a bunch of program names
in there?)
> xlock seems a little weird. on the sgi's xlock is installed locally
> without read permissions, so I can't stat it. on the suns it's
> installed on the packs, with read permission. I don't actually know
> if this is a bug.
You can stat local files which don't have read permission; you just
can't read them. (In AFS that's not the case.) It's annoying when
operating system ship non-world-readable files, but it's not a bug
that we leave them that way.
The rest of the stuff looks like real bugs.
