On Wed, 26 May 2010 16:58:51 -0700, ron minnich <rminn...@gmail.com> wrote: > On Wed, May 26, 2010 at 11:02 AM, Nick LaForge <nicklafo...@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.
that sounds like the the persistent home or local is not set up. It should have been there by default when it was rebooted. The three most likely problems is missing persistent home or usbwait, but it might also require persistent local (but I did not things so -- I'll try to remember to test that after some rest) >> 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. I haven't seen anything like this, but there are some weird things which can happen when not setting up the proper boot flags. Another one that can cause oddities is not adding usbwait=5 or maybe 10. This forces the boot sequence to let the usb drive state catch up with the rest of the machine. Try adding that too and see if it helps. > 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. One of the things I noticed fairly consistently. When recompiling the system various programs are rebuilt/installed while the system is running. Unfortunately 9vx does not deal gracefully with this and sometimes segfaults. The solution that has always worked for me, as gross as it is, is to simply restart 9vx and restart the build. I forget how often I had to do this before it completely rebuilt the system but I think ti was either two or three. Once it rebuilt everything I can run a mk clean and then mk all and install then it works without incidence. I wonder if there is some weird interaction between my build settings and the target machine. Maybe I/we can explore that avenue. > 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? If you are referring to the symlinks in the /tmp directory, not that is by TCL's design and they consider it a feature not a bug. So, no I do not think that TCL will ever get rid of them. EBo --
