Off-Topic > Off-Topic - Tiny Core Lounge

An alternative setup for a Linux OS.

(1/2) > >>

SunBurnt:
hiro and I were discussing this in another thread.

The idea is much like TC, but uses a Squash file in ram rather than loose files.
This makes the read-only files in ram secure and it also saves 17 MB of ram.
And it keeps writable files loose on a persistent drive rather than in a .tgz .
I think I have the directories r-w and r-o correct, but there may be errors.

###      An alternative setup for a Linux OS.

#   The read-only directories are in the Squash file.
#   Persistant read-write directories are on the HD.
#   Nonpersistant read-write directories are in RAM.

#   The Squash file is mounted at: /SQ
#   The HD partition is mounted at: /mnt/(part.)

File System in ram: Directories and links ( -> ).
=======================================
/SQ   ( Squash file in ram, mount point )
/bin ----> /SQ/bin
/dev
/etc ----> /mnt/(part.)/OS/etc
/home -> /mnt/(part.)/OS/home
/lib  ----> /SQ/lib
/mnt
 /opt ---> /SQ/opt
/proc
/root ---> /mnt/(part.)/OS/root
/sbin  --> /SQ/sbin
/sys
/tmp
/usr  ---> /SQ/usr
/var

hiro:
You'd have to create directories and then create links only for files (like it's done for extensions currently). Else you can't load other extensions.

I don't accept security as an argument, like I already said, but I agree this would save a little bit of RAM.

SunBurnt:
Hi hiro; When you say "load" you mean "mount" app. Squash files?
The "extention" Squash files are mounted on dirs. in /tmp. Right?
The file system I show has /tmp as a dir. in ram. This what you mean?

hiro:
With load I mean mount into /tmp/tcloop like you said + link the contained files into /
The last step is only possible if the directories are writable.

SunBurnt:
I must not understand how the extension files work then.

I thought the extension files were used through their mount points directly,
with no attempt to merge their files with the main file system. Wrong?

Navigation

[0] Message Index

[#] Next page