From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Tvx update
Date: Wed, 26 May 2010 16:58:51 -0700 [thread overview]
Message-ID: <AANLkTil8ikU5mi5AoX0NwlusThs0Kr4T-Yfyv_KI2pUk@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinMNvEOZ7sSpvClWEqjarnJw5g66ag0Kvf0kV7A@mail.gmail.com>
On Wed, May 26, 2010 at 11:02 AM, Nick LaForge <nicklaforge@gmail.com> wrote:
> I tried it and it is very fast to boot and run. However, the wrapper
> did not copy Tvx-root to my home dir. Option 2 links to the package
> install in /usr/local, but option 1 also links, but to the package
> loopback mount in /tmp.
Is this because option 2 is the persistent install and option 1 is
not? Note the loopback mounts are readonly squashfs mounts.
> The only files in my home are in the top
> directory (the license, etc.). Writing to the symlinks fails. And so
> does reading utf8 filenames.
Be careful .. did you set up a persistent /home? I'm not sure what you
have done. There's no substitute at some point for seeing how things
work at tinycore.org.
cd /sys/doc
ls | grep 8
8
cd 8
Can't cd 8: '8' file does not exist
cd 8½
Can't cd 8½: '8½' file does not exist
cd 8?
ls 8?.ms
8�.ms
touch 9½
ls 9½
9½
That's an interesting problem. I wonder if it is some artifact of the
use of squashfs. The sam and venti directories are fine.
This may be a flaw in tinycore ... we'll talk to them.
Thanks for the testing. I have found one thing out ... I don't think
9vx is SMP-safe. I've had some real problems building in /sys/src,
where 9vx gets a segv on "cpu 5" or whatever. If I boot with only one
cpu, there are no problems. Worth keeping in mind ... I may modify my
version of 9vx to wire itself to cpu 0, as well as its children, and
see if the failures I'm seeing go away. That's a pointer at least to
where the issues may be.
Also ...
>sed '43 s/H/L/' Tvx
Sorry, you lost me.
>Why are there TWO ways for cp to follow symlinks? Why are there
>symlinks it all? (That should do it.)
They're not going away I bet, but what are you talking about here?
ron
next prev parent reply other threads:[~2010-05-26 23:58 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 18:46 EBo
2010-05-25 19:34 ` Nick LaForge
2010-05-25 19:57 ` EBo
2010-05-26 18:02 ` Nick LaForge
2010-05-26 18:17 ` erik quanstrom
2010-05-26 20:35 ` EBo
2010-05-26 20:42 ` EBo
2010-05-26 23:31 ` Nick LaForge
2010-05-26 23:53 ` erik quanstrom
2010-05-26 23:58 ` ron minnich [this message]
2010-05-27 1:50 ` Nick LaForge
2010-05-27 2:51 ` ron minnich
2010-05-27 4:19 ` EBo
2010-05-27 5:03 ` Nick LaForge
2010-05-27 5:18 ` EBo
2010-05-27 7:17 ` EBo
2010-05-27 14:30 ` hiro
2010-05-27 18:14 ` Jorden M
2010-05-27 19:26 ` EBo
2010-05-28 3:42 ` ron minnich
2010-05-27 5:48 ` ron minnich
2010-05-27 7:02 ` EBo
2010-05-27 14:39 ` ron minnich
[not found] ` <5147DCD3-BD95-4D54-96B7-30DCA4D113DA@mit.edu>
2010-05-27 19:59 ` Chad Brown
2010-05-27 20:16 ` Bakul Shah
2010-05-28 3:41 ` ron minnich
2010-05-28 10:34 ` erik quanstrom
2010-05-28 11:04 ` Ethan Grammatikidis
2010-05-28 11:51 ` Ethan Grammatikidis
2010-05-28 11:59 ` erik quanstrom
2010-05-28 12:19 ` Ethan Grammatikidis
2010-05-28 13:20 ` erik quanstrom
2010-05-28 15:09 ` Steve Simon
2010-05-28 16:21 ` Ethan Grammatikidis
2010-05-28 16:26 ` erik quanstrom
2010-05-28 16:38 ` Ethan Grammatikidis
2010-05-28 16:04 ` Bakul Shah
2010-05-28 16:13 ` erik quanstrom
2010-05-28 16:53 ` Ethan Grammatikidis
2010-05-27 20:20 ` EBo
2010-05-27 4:54 ` EBo
2010-05-27 6:57 ` ron minnich
2010-05-27 7:07 ` EBo
2010-05-27 14:38 ` ron minnich
2010-05-27 19:11 ` EBo
2010-05-28 3:44 ` ron minnich
2010-05-28 10:24 ` erik quanstrom
2010-06-13 8:43 [9fans] tvx update EBo
2010-08-19 2:39 ` Ryousei Takano
2010-08-19 3:02 ` EBo
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=AANLkTil8ikU5mi5AoX0NwlusThs0Kr4T-Yfyv_KI2pUk@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=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).