This sounds really interesting.  I just started playing with a Pi3 and it seems 
pretty cool.  A lot of power packed into a tiny box.  I think Picolisp could 
really make the most of the pi ;-)

Note that some of the default memory cards to drive the pi are Debian based.  
Note Picolisp is available in the testing branch for arm64: 
https://packages.debian.org/buster/picolisp.

On Thu, Jun 14, 2018 at 03:39:12PM +0900, Jean-Christophe Helary wrote:
Now, I'm thinking, what if I get a Raspberry 3 (64bit arm processor) ? I'd have 
a dedicated machine, no virtualization overhead and I'd just need to ssh to it 
from the Mac to access picolisp.

Anybody has run picolisp in such an environment?

Jean-Christophe

On Jun 14, 2018, at 15:20, Jean-Christophe Helary <brandel...@gmail.com> wrote:

Alexander,

What I'm finding is interesting. When I start pil and just stay inactive, 
TinyCore uses about 5-6% of the cpu on qemu, while Debian works at about 3-4%. 
In both cases I only installed a minimal system and I work on the CLI.

Jean-Christophe

On Jun 14, 2018, at 1:26, Alexander Williams <a...@unscramble.co.jp 
<mailto:a...@unscramble.co.jp>> wrote:

Sorry for the late reply.

JC I think you probably downloaded TinyCore 32-bit (x86) by accident. You need the 
64-bit version: http://www.tinycorelinux.net/9.x/x86_64/release/ 
<http://www.tinycorelinux.net/9.x/x86_64/release/>

Get the ISO file "TinyCorePure64-9.0.iso" (27MB) and boot your VM from that. If you only want 
"headless" (no X), then you can try the "CorePure64-9.0.iso" (14MB).

Another option, if you don't mind paying, you can rent a VPS server for US 
$5/mo from Linode (or maybe OVH?). I was connecting to that over SSH for my 
64-bit PicoLisp development (Debian 64-bit).


AW

On Tue, 12 Jun 2018, Jean-Christophe Helary wrote:


On Jun 12, 2018, at 18:42, Jean-Christophe Helary <brandel...@gmail.com 
<mailto:brandel...@gmail.com>> wrote:
The only issue with this setting is that to run picolisp I have an overhead of 
~5% cpu use just to run VB headless.

Trying to do everything again in qemu, to see the total cpu use...

Ok, debian is *super slow* to install under qemu. The positive thing is that 
the cpu overhead seems to hover around 3% and there is no need to access the 
headless machine via rdp (which adds yet another overhead + a messed up 
keyboard layout once the machine is available in Xquartz).

I so wish picolisp were running on macos directly, but I guess that will do for 
now...

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com <http://mac4translators.blogspot.com/> 
@brandelune




--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe 
<mailto:picolisp@software-lab.de?subject=Unsubscribe>

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com <http://mac4translators.blogspot.com/> 
@brandelune



Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune



--
Joe Golden
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Reply via email to