From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <AANLkTinMNvEOZ7sSpvClWEqjarnJw5g66ag0Kvf0kV7A@mail.gmail.com>
References: <32ae739c22eb486931dd7bb207949f0e@swcp.com>
	<AANLkTinURHV0Nq-tgGjbwwTc0h6jheRI1TRjwRFH3_Mb@mail.gmail.com>
	<79c8278e45da12f71df95a90c8df246f@swcp.com>
	<AANLkTinMNvEOZ7sSpvClWEqjarnJw5g66ag0Kvf0kV7A@mail.gmail.com>
Date: Wed, 26 May 2010 16:58:51 -0700
Message-ID: <AANLkTil8ikU5mi5AoX0NwlusThs0Kr4T-Yfyv_KI2pUk@mail.gmail.com>
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Tvx update
Topicbox-Message-UUID: 2ab59826-ead6-11e9-9d60-3106f5b1d025

On Wed, May 26, 2010 at 11:02 AM, Nick LaForge <nicklaforge@gmail.com> wrot=
e:
> I tried it and it is very fast to boot and run. =C2=A0However, the wrappe=
r
> did not copy Tvx-root to my home dir. =C2=A0Option 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.

>=C2=A0The only files in my home are in the top
> directory (the license, etc.). =C2=A0Writing to the symlinks fails. =C2=
=A0And 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=C2=BD
Can't cd 8=C2=BD: '8=C2=BD' file does not exist
cd 8?
ls 8?.ms
8=EF=BF=BD.ms
touch 9=C2=BD
ls 9=C2=BD
9=C2=BD

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