|
|
Post by bmarkus on Feb 17, 2014 3:54:00 GMT -8
In Tiny Core Linux applications are loop mounted from the package and symlinked to the file system. It works in 99.9% of programs with very few exceptions, including 8086tiny. It requires to copy emulator, bios and disk images to be copied to RAM otherwise symlinked support files not found. Would be good to follow symlinks in next release. |
|
|
|
Post by Adrian Cable on Feb 17, 2014 21:32:34 GMT -8
bmarkus,
Thanks for your note - unfortunately I am not familiar at all with Tiny Core Linux so I don't understand your description of the problem very well.
Can you write a little more detail including (A) your platform, (B) the behaviour you are seeing in enough detail for me to reproduce, and (C) what behaviour you would expect instead, and I will see what I can do?
Thanks!
-Adrian
|
|
|
|
Post by bmarkus on Feb 18, 2014 7:14:04 GMT -8
Hi Adrian Tiny Core Linux is a unique system. Its core is 10-12M and runs entirely in RAM. By default no any storage media used after boot. It can be extended with so called .tcz extensions. These are holding files in squash compressed format loop mounted after boot to /tmp/tcloop/tcz1, .... and than symlinked to / or copied to RAM depending on setting. Lets say you have myapp.tcz extension (package) with /usr/local/bin/mybin and /usr/local/share/myadata data file. They are mounted in /tmp/tcloop/myapp/usr/local/bin/mybin /tmp/tcloop/myapp/usr/local/share/mydata while /usr/loca/bin/@mybin /usr/local/share/@mydata are symlinks to /tmp/tcloop/myapp/... The question is, where mybin looks for mydata and opens it, in /usr/local/share or /tmp/tcloop/myapp/usr/local/share In first case few applications opens without following the symlinks, resulting file not available. Benefit of this solution in Tiny Core is that you can not distroy your system (extensions are read-only), after reboot you get the same system as before. It is ideal for development, testing or for example appliences when user sees just a black box and he/she can safely just unplug the power without any corruption  Of cource it is more complicated, but these are the basics. Hope it is more clear now. Bela |
|
|
|
Post by Adrian Cable on Feb 18, 2014 8:09:43 GMT -8
Bela,
Thanks for the detail. However, I still do not understand the problem in the context of 8086tiny. Can you explain what 8086tiny does that is incorrect in detail, and a description of what the application should do instead, and I will look into it?
Thanks!
-Adrian
|
|
|
|
Post by bmarkus on Feb 18, 2014 9:42:43 GMT -8
Hi
when it is installed loop mounted from an extension, I get an error message that bios not found. If runs in RAM, it is OK.
|
|
|
|
Post by Adrian Cable on Feb 18, 2014 10:31:50 GMT -8
Hi,
Can you provide a screenshot of your terminal to show where it goes wrong? 8086tiny itself doesn't produce any error messages if it can't find the BIOS so something more subtle must be happening. Thanks!
-Adrian
|
|
|
|
Post by bmarkus on Feb 22, 2014 15:24:27 GMT -8
Just a blank screen, nothing else.
|
|
|
|
Post by Adrian Cable on Feb 23, 2014 0:33:51 GMT -8
bmarkus,
Many apologies if I wasn't clear. Previously you said:
> when it is installed loop mounted from an extension, I get an error message that bios not found. If runs in RAM, it is OK.
It would be great to get a screenshot of the error message.
-Adrian
|
|
|
|
Post by netpipe on Nov 5, 2020 17:50:39 GMT -8
|
|
|
|
Post by netpipe on Nov 5, 2020 18:04:27 GMT -8
|
|
%e2%80%8c-%e0%b0%95%e0%b1%81%e0%b0%9f%e0%b1%81%e0%b0%82%e0%b0%ac%e0%b0%ae/?unapproved=410&moderation-hash=ccd094ff1e9bf2a16ade894b3746c1a8#comment-410Comprar