[2087] in SIPB bug reports

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

xscreensaver -> rs6000, mark I

daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Tue Sep 10 22:38:40 1991

Date: Tue, 10 Sep 91 22:37:58 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: bjaspan@MIT.EDU
Cc: bug-sipb@ATHENA.MIT.EDU
In-Reply-To: "Barr3y Jaspan"'s message of Sun, 8 Sep 91 23:52:33 -0400 <9109090352.AA05119@w20-575-2.MIT.EDU>

   Date: Sun, 8 Sep 91 23:52:33 -0400
   From: "Barr3y Jaspan" <bjaspan@MIT.EDU>
   Sender: bjaspan@ATHENA.MIT.EDU

   I attempted to port xscreensaver to the RS/6000 tonight (used one of
   them in the w20 cluster).  It *mostly* worked.  Problems:

Well, I'm glad you did it, and not me :-).
   o I had to comment out PASSWORD_PORT because I couldn't find
   sys_errlist in a .h file (xsaver.h is local in the rsaix directory)

The RS/6000 probably has the ANSI/POSIX (I forget which it is)
strerror() function, and sys_errlist shouldn't be used on it.  The
changes should be minor.

   o I had to #ifdef something on PASSWORD_PORT.

What?

   o I modified xsaver.h to define COMPILE_SETENV (also in the local
   version).  How does one identify this machine via cpp?

I think you need to look in /etc/xlc-config or /etc/xlc.config or
something like that.  I believe it describes which symbols are defined
for each name the compiler is called as.

   For some reason I will not begin to think about, everybody's passwd
   field in /etc/passwd is !, not *.  Therefore, when you lock the
   screen, xscreensaver prompts you to enter a password.  I'm too tired
   to figure out the Right Thing to do.

Shadow passwords.  Prompting for a password is probably the right
thing to do for now; people who don't want it to prompt can set an
encryptedKey resource in their X resources.

   Blanking or locking the screen does not actually blank the screen.
   The floating icon starts floating, but the actual contents remain
   visible (and are slowly blacked out by the floating icon).

Very, very strange.  I can't explain this at all, other than a bug in
the RS/6000 X libraries.  If xscreensaver were at fault, then the
slowly blackiong out wouldn't take place.

  jik

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