Tiny Core Linux
Tiny Core Base => Corepure64 => Topic started by: tinycorelinux on November 20, 2020, 06:40:54 AM
-
I would like to know how the data in all folders under the root directory is deleted after every system shutdown. How does this work? Using scripts? Change mount mode? Modifying kernel code? Now we need to customize our own operating system based on TCL, so we really want to know this, and This is the only question I can ask you, because these operating systems were developed by you, you know them better than others, thank you.
-
It’s not deleted - either it’s in ram and lost on shutdown or loop mounted and unmounted on shutdown.
-
in ram?How can we change this behavior?
I'm talking more about how do you get it to work the normal way like any other distribution?
-
Add the files you’d like to keep to your backup.
-
I don't think it's wise to do that, it doesn't suit the needs of most users...
Is it in your interest that I ask this question?
-
My guess :)
The system starts up, assuming there is always a backup directory.
If the routing directory is not created, the system will reset itself.
As such, permanence either occurs or does not occur, depending on the desire!
in ram?How can we change this behavior?
I'm talking more about how do you get it to work the normal way like any other distribution?
-
Your assumption is actually TCL's backup and restore principle, but that's not what I want to know.
-
@All members of TinycoreLinux Team
If you think my question is going to touch your interests and your technology patents, Please tell me,I'll never ask it again.
-
for permanence
tce-setdrive
in ram?How can we change this behavior?
I'm talking more about how do you get it to work the normal way like any other distribution?
-
You can install tinycore in traditional “scatter” mode.
-
Hi ONE
The root file system is RAM based.
It is provided by the initrd (core.gz).
It gets rebuilt from scratch every time you boot.
Here is a diagram of how it works:
http://distro.ibiblio.org/tinycorelinux/architecture.html
The only folders that can be permanent are /home and /opt.
This is by design, and will not be changed.
in ram?How can we change this behavior?
I'm talking more about how do you get it to work the normal way like any other distribution?
By switching to any other distribution that works in the normal way.
You can install tinycore in traditional “scatter” mode.
If you go down this road, you are on your own.
We do not provide support for this mode of operation.
I don't know what other problems it will cause, but it will break the package manager.
-
It’s not deleted - either it’s in ram and lost on shutdown or loop mounted and unmounted on shutdown.
"Scatter" mode？How I do？
-
Following TCL's design philosophy, how do you solve the performance problem of creating a large number of file links? With the increasing amount of software installed on the machine, TCL needs to spend a lot of time to create a large number of links for all files in each mounted TCZ. Is there any way to solve this problem? I wonder if TCL Team has ever considered such a question?
-
compressing files is a matter of preference
as it is not as fast as a regular hdd or ssd ram
I do not detect any lag time in between.
The system only reads the system files required at boot.
reads files on optional applications.
An optional auto save is created after the application or system shutdown request.
In summary, if we study the system; Applications that are subject to the literacy process of perhaps 1 million times,
How quickly you forget that system storage space is shortening its useful life! :)
Following TCL's design philosophy, how do you solve the performance problem of creating a large number of file links? With the increasing amount of software installed on the machine, TCL needs to spend a lot of time to create a large number of links for all files in each mounted TCZ. Is there any way to solve this problem? I wonder if TCL Team has ever considered such a question?
-
The system only reads the system files required at boot.
reads files on optional applications.
However, the system needs to create links for all files in each mounted TCZ every time, so the startup speed is slow
-
In a sense, the links created for all the files in the loaded TCZ are repeated every boot, because the location and rules of the TCZ mount will not change, so the file links will not change. I suggest that the TCL team should pay attention to this problem and try to improve it. I think the performance will be improved a lot.
It is recommended that links be re created for all files in TCZ only if necessary.
-
From your comments, I assume you've given up on a traditional (scatter) install, which is not recommended on tinycore.
Many users make the mistake of downloading all their extensions to load "onboot". If you only set a few extensions "onboot" and set the ones you use occasionally "ondemand", tinycore will boot a lot quicker.
In tinycore's early days some time was spent to optimise the creation of extension symlinks, but any patch suggestions that make things quicker would be gratefully received.
-
instantaneous loss is minimal; but the overall gain is high.
The loss rate you think is too small to think !!! :)
The system only reads the system files required at boot.
reads files on optional applications.
However, the system needs to create links for all files in each mounted TCZ every time, so the startup speed is slow
-
...tinycore will boot a lot quicker.
It's not just the boot speed that matters. Tinycore is one of the fastest in the world.
if all TCZ is manually loaded, but it will slow down the extension startup software because TCZ has to be loaded and symbolic links are created for all the files in the extension before it can be started.
Don't forget that TCZ also needs to do the same thing above for all its unloaded dependencies, not just the software you're using.
In tinycore's early days some time was spent to optimise.
I don't know. "local" whether the bootcode is for that purpose, I'm also curious about what it does, but I don't seem to understand what wikipedia says.
but any patch suggestions that make things quicker would be gratefully received.
Ok, I'll have a try.
-
I don't know. "local" whether the bootcode is for that purpose, I'm also curious about what it does, but I don't seem to understand what wikipedia says.
I'm pretty sure the boot code [local] is obsolete.
-
is obsolete.
Thanks for the warning. I guess I'm on my own.
-
http://forum.tinycorelinux.net/index.php/topic,24514.0.html
In tinycore's early days some time was spent to optimise the creation of extension symlinks, but any patch suggestions that make things quicker would be gratefully received.
-
Hi !
I'm just too lazy to read all of this thread but I did read some of it and am answering this. TinyCore is always loaded into RAM and RAM works as a temporary storage. After a shutdown, RAM loses power and just forgets all of its data unlike an HDD or SSD where data is written on the drive. Hence, data on TCL is just gone after you shut it down.
The best thing you can do to actually get the files stored on HDD or SSD without the backup is using "home and opt" bootcodes.
See FAQ for more info. home and opt bootcodes allow the files to be written directly to SDD unlike traditional backup method.