From: "ibrahim via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: [9fans] 9vx, 9legacy
Date: Sun, 18 Apr 2021 10:44:40 -0400 [thread overview]
Message-ID: <16187570800.5bCe05dE3.356828@composer.9fans.topicbox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
While looking for a way to exchange files between a linux system and an hosted virtual machine running plan9 I found vx32 and 9vx. I couldn't master to compile it under a 64 bit Linux cause libX11 was missing as a compatible 32 bit library so I installed a 32 bit linux and everthing compiled without problems.
I started 9legacy with
9vx -r <rootpath> -u glenda "memsize=1536"
everything went fine and this is amazingly fast. I can exchange files between host and guest.
Now my questions :
a) When I typed fshalt I got an error that I don't have permissions to call /bin/echo. It seems like echo from the host system was called instead of echo from 9legacy. Is this a bug or did I forget something ?
b) How does the installation procedure work ? Usually during the installation of a distro lets say 9front I would have to partition a harddisk where the necessary things are installed.
c) I'm a bit confused about the licensing of 9vx and vx32. vx32 is LGPL and 9vx is/was licenced with the Lucent license while 9vx uses vx32 or am I wrong ?
Thanks in advance and 9vx is really an amazing tool.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tf651d537d5dbd117-M67a20cd6deb2da053b42096a
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2120 bytes --]
next reply other threads:[~2021-04-18 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 14:44 ibrahim via 9fans [this message]
2021-04-18 15:10 ` David du Colombier
2021-04-18 15:33 ` ibrahim via 9fans
2021-04-18 15:55 ` ibrahim via 9fans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16187570800.5bCe05dE3.356828@composer.9fans.topicbox.com \
--to=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).