On Tue, Aug 21, 2007 at 10:26:25AM +0200, Andrea Rossato wrote:
As you see it is suggested to use some other alternatives till slock will get fixed.[1]
I wrote an alternative myself, in Haskell. Actually because I wanted to familiarize with the FFI infrastructure (it took me far more to understand how to pass an option to the linker then importing the C function...;-_). It is not slock, thought: since I didn't find a way to hide the pointer I found a nice font for it. To run must be set suid root (as slock). In the headers instruction on how to build. Works only with shadow passwords. Well, guess what? It has the same slock problem. The very same issue. Interesting I would say! At least now I have some code that I can understand and may be I can even find where the problem is. I doubt though. Andrea PS: Dons, I know you won't like the code. But I'm sure that someone wrote that Haskell is the best imperative language ever. And I'm trying to provide scientific evidence of that!