Tiny Core Linux

Tiny Core Base => Corepure64 => Topic started by: labeas on November 01, 2019, 09:05:17 AM

Title: TCbook unsatisfactory.
Post by: labeas on November 01, 2019, 09:05:17 AM
I tried to post this to < a/the more general group > but failed.
The move of NNTP and mail to html is a disaster.
I fear this criticism will be unwelcome.
I KNOW, down to the level of transistors, bistables, NANDgates
how digital computers work, and can't bluff that they are well
represented by cartoons of paper-folders.
Let's analyse the TCbook, which IMO starts out badly.

> 1.1. Philosophies.
>As a quick summary, Tiny Core loads itself into RAM from storage,
>then mounts applications on storage, or installs applications to
>RAM from storage. An extension is said to be loaded or installed
>regardless of the method used (mount vs. copy to RAM).
> TC loads itself into RAM from storage
Yes: at power-on/reset the programCounter is hard-wired to point to
a ROM location, where the instructionBytes are fetched to the CPU and
executed, so as to eventually copy TC-code into RAM from my USBstik.
Which agrees with the first description of the TCbook.
> mounts applications on storage
?! how does this correspond to "mount's" 2 arguments ?!
or does it mean: "a dir/s of storage/USBstik, containing applications
 is mounted; thereby allowing said applications to be accessed/run" ?

> installs applications to RAM from storage.
OK: the original "loads itself/theOS into RAM from storage"
was done by the boot-loader.
And now TC/theOS loads *tcz to /tmp/tcloop/
 or not ?
Title: Re: TCbook unsatisfactory.
Post by: Rich on November 01, 2019, 09:22:26 AM
Hi labeas
Maybe these architecture diagrams will be of some help.

Mount mode:

Copy mode: