[net.games.hack] safelock

ksl@hou2e.UUCP (a hacker) (08/15/85)

After I received hack, it says that "safelock" is not found.

What is safelock?

Thanks,
hou2e!ksl

[SvR2 hack1.0.2 3b]

ksl@hou2e.UUCP (a hacker) (08/28/85)

Now after all files are created, this is what happens:

$ hack
safelock: File exists
(screen is cleared QUICKLY)
Cannot link safelock
$

What does it mean?

Thanks
hou2e!ksl

kad@ttrdc.UUCP (Keith Drescher) (08/29/85)

In article <684@hou2e.UUCP> ksl@hou2e.UUCP (a hacker) writes:
>Now after all files are created, this is what happens:
>
>$ hack
>safelock: File exists
>(screen is cleared QUICKLY)
>Cannot link safelock
>$
>
>What does it mean?
>
>Thanks
>hou2e!ksl

I recently installed this stuff.  After wondering about the same
problem I noticed that the READ_ME file mentioned "perm - an empty
file used for locking purposes" (or some such nonsense).

Anyway, the solution is to "touch perm".  Sorry about the
long-winded explaination.
-- 
-------------------------------------------------------------------------
Keith Drescher (kad@ttrdc)          	   | ... You can check out any      
ATT Computer Systems Division, Skokie, Il. | time you like - but you can  
PATH: ...!ihnp4!ttrdc!kad                  | never leave ...
-------------------------------------------------------------------------

meier@srcsip.UUCP (Christopher M. Meier) (08/31/85)

>In article <684@hou2e.UUCP> ksl@hou2e.UUCP (a hacker) writes:
>>Now after all files are created, this is what happens:
>>
>>$ hack
>>safelock: File exists
>>(screen is cleared QUICKLY)
>>Cannot link safelock
>>$
>>
>>What does it mean?
>>Thanks
>>hou2e!ksl
>I recently installed this stuff.  After wondering about the same
>problem I noticed that the READ_ME file mentioned "perm - an empty
>file used for locking purposes" (or some such nonsense).
>
>Anyway, the solution is to "touch perm".  Sorry about the
>long-winded explaination.
>-- 
>Keith Drescher (kad@ttrdc)          	   | ... You can check out any      
When we brought up hack, we had this problem.  I took a look at the
directory permissions, and only root had write access.  Changing this
took care of it for us.
Christopher Meier (ihnp4!umn-cs!srcsip!meier)

ps: Even tho this gives everyone the ability to "cheat", we haven't
    had problems with cheating except by those with su power - and
    a wet noodle takes care of them very nicely :-)