Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!rex!uflorida!springs.cis.ufl.edu!pm0
From: pm0@springs.cis.ufl.edu (Patrick Martin)
Newsgroups: comp.sys.amiga.misc
Subject: Re: SKsh and A3000
Message-ID: <26746@uflorida.cis.ufl.EDU>
Date: 6 Feb 91 23:44:33 GMT
References: <37090001@hpfcdc.HP.COM> <26690@uflorida.cis.ufl.EDU> <1126@swrinde.nde.swri.edu>
Sender: news@uflorida.cis.ufl.EDU
Organization: UF CIS Dept.
Lines: 20

In article <1126@swrinde.nde.swri.edu> kent@swrinde.nde.swri.edu (Kent D. Polk) writes:
>In article <26690@uflorida.cis.ufl.EDU> pm0@springs.cis.ufl.edu (Patrick Martin) writes:
>>What you have to do to get it to run is:  1) Set it up like the directions
>>say then 2) Place a lock on the file s:.skshinit (You can do this by
>>loading .skshinit into an editor and putting the window into the background.
>>
>>I would like to know how to put a lock on the file without going to this
>>extreme.  (Still an Amiga novice)  Anyways, now run skshinit like you
                                                      ^^^^^^^^
                                         I meant to say sksh

>>normally would and it should run fine.  It does on my A3000 anyways.

>s:.skshinit to startup up Sksh on an A3000. I have tried various
>methods of putting a lock on s:.skshinit, and not all of them work.

Which ones do work?  I don't like the idea of running a dummy editor in the
background.

Pat