Maybe it has something to do with apt-get upgrade as well?
Glad to hear the issue disappeared!

2018-04-18 14:16 GMT+02:00 Joe Bogner <joebog...@gmail.com>:

> Arie, I followed your WSL steps on a newer machine and I don't see the db
> locking issue any more. Thanks! My other machine has the problem but its
> WSL is at least 6 months old - so maybe it was fixed in WSL since then or
> possibly something fixed/changed by following your instructions. Thanks,
> I'll do some additional testing later
>
> On Wed, Apr 18, 2018 at 6:23 AM, Arie van Wingerden <xapw...@gmail.com
> <xapwing@gmailcom>> wrote:
>
>> Hi Alex,
>>
>> 1) root mode was because I tried a lot of different things, but missed
>> the obvious family64.tgz 😡
>> 2) had a few problems with cd-ing into folders, because under Windows it
>> is a bit different
>>
>> So, after unpacking family64.tgz into a local folder in my home dir
>> everything works great!
>>
>> Now starting to really learn the PicoLisp language better.
>>
>> @Joe could you show me an example where db locking didn't work?
>>      Maybe I can test this and see if it does work correctly in the way I
>> now set up PicoLisp in WSL?
>>
>> Thx. again!
>> /Arie
>>
>> 2018-04-18 11:50 GMT+02:00 Alexander Burger <a...@software-lab.de>:
>>
>>> Hi Arie,
>>>
>>> > *   root@HP-Arie:/usr/share/doc/picolisp/doc# **pil family.l -main
>>> -go +*
>>> > ...
>>> > *!? (pool "family/" *Dbs)   "family/" -- Open error: No such file or
>>> > directory   ?*
>>>
>>> This is probably because the "family/" directory does not exist yet. Or
>>> did you
>>> unpack the file "family64.tgz"?
>>>
>>> In general, I would recommend not to run all this as user root. Better
>>> log in as
>>> a normal user, and do in any of your local directories:
>>>
>>>    $ tar xvfz /usr/share/doc/picolisp/doc/family64.tgz
>>>    family.l
>>>    family/
>>>    family/@
>>>    family/B
>>>    family/C
>>>    family/A
>>>    $ pil /usr/share/doc/picolisp/doc/family.l -main -go +
>>>
>>> ♪♫ Alex
>>>
>>> --
>>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>>
>>
>>
>

Reply via email to