Tiny Core Extensions > TCE Q&A Forum

Tinycore libraries

(1/3) > >>

Yleisajattelija:
I think TCE Q&A is just right place for this. Is there tinycore library documentation somewhere? (the "Q" part). Probably it is never made (the "A" part).

So, now we need the "S" part, too, which means "the solution".

Without library documentation, distribution development is vere difficult.

So, lets start of the beginning of unix:

1) -----------------  "/" -------------------------

This is basic unix statement, and it includes actually very strong, definite and dangerous decicions:

a) Everything on unix are files and are located below root "/" directory
b) Becouse of a), very strong "vertical isolation" is declared. All code layers are separated (=OSI), no information is delivered vertically (eg. all HW signaling to appication layer and back missing totally)
c) Becouse of b) all unix systems are inhertly non-real time systems.
d) File structure is "one dimensional", eg. there is no other way to separate code&data
e) Becouse of a), b), c), and d) unix is very difficult environment for HW implementations.
f) Especially for b), linus torvalds was cabable to utilize huge unix software just by implementing lowest HW-layer for unix.


2)  -- ------------ "/var", "/bin", "/sbin" and "lib" ------------------------------------------------

a) Executable parts of code (read.only ROM-memory parts on embedded environment) are separated on "/bin" , low lever system code  on "/sbin" directory
b) Variables (read-write data on embedded environments RAM) are separated on "/var" directory
c) Common code for different applications are separated on "/lib" directory

3) -------------------- "/boot", "/etc", "/dev", "/proc", "/usr" ------------------------------------------------------

a) Booting code is placed "/boot" (includes all code&data for boot)
b) Configuration files for all applications "/etc"
c) Device files "/dev"
d) Runtime environment "/proc"
e) Everything else "/usr", this is secondary directory for "/" (again "/bin", )

4) ------------------- "/root" and "/home" -------------------------------------------------------------
a) One user system runlevel (data&code&scripts),  for non-TC "/root"
b) Users personal data and scripts "/home"

Above list tells the basic unix/linux problem, application code, data, config files, scripts and libs are scattered around file system.
One application can modify other application config file, and there is no reasonable way to fix it. TC-squeeze-ramdisk protects
application and system for this corruption.

But, files have to be there anyway. And the main problem is libraries on "/lib" and "urs/lib".

--------------------------------------- The Issue Itself -----------------------------------------------------
For application maintainer is essential to know, which TC-libraries are avilable on TC.5X version:

a) /lib
     (new, wonderful list of libaries which are already installed)
b) /usr/lib
     (new, wonderful list of libaries which are already installed)
c) /usr/local/lib
     (new, wonderful list of libaries which are already installed)

Juanito:
You can see the answer to your question by booting using the boot codes "base norestore" and looking under /lib, /usr/lib and /usr/local/lib

bmarkus:
Decompress initrd and see what is in /lib and /usr/lib

/usr/local/lib is poulated by .tcz extensions

Yleisajattelija:
This is "apriori" style problem. Looking for "/lib" helps to list solution, but what should be at those libararies is the problem.

And, debian has it all already, why not to use debian?

I did, and I found that there is "unix" decease added with "bash" decease and  finalized with "linux-gigantism" decease.

bmarkus:

--- Quote from: Yleisajattelija on September 18, 2014, 03:44:15 AM ---
And, debian has it all already, why not to use debian?


--- End quote ---

Yes, debian has it. As well as CentOS, Slackware, ARCH, MINT. All thes have libraries. If you prefer Debian, use Debian. It is simple.

Navigation

[0] Message Index

[#] Next page