Tiny Core Base > Micro Core

Adding dynamic TC Autorun feature

<< < (2/3) > >>

jazzbiker:
Thanks, Rich,
I've missed that AlejandroPadrino talks about "remastering", which really means initrd which will reside in the RAM. Probably it's for the booting fast as possible.
But then where will reside /home? Persistent?

So here we can see an example of the choice:
1. Fast extensions and slow /home
vs
2. Slow boot and slower extensions and fast /home.

I put stupid questions because I choose fast /home )

Probably the need for additional extension tools is caused by very small drives capacity.

Thanks for the answer and sorry for the stupid questions!

Rich:
Hi jazzbiker

--- Quote from: jazzbiker on July 14, 2023, 04:02:02 PM --- ... But then where will reside /home? Persistent? ...
--- End quote ---
The initrd contains an empty home directory. If you have a persistent
home, it will be mounted under the home directory, /home/tc for example.
If your home was backed up, it will be restored to /home/tc for example, but
will reside fully in RAM.

jazzbiker:
Hi Rich,
But maximizing the size of initrd to fill the whole RAM will leave almost no free room for /home.
Probably this is normal for some use cases.

Rich:
Hi jazzbiker
If home is persistent, it only consumes a few hundred bytes
for a mountpoint, with everything else on persistent storage.

If your home was backed up, the kernel probably allocates
RAM to allow it to be restored.

If you manage to size the initrd to use all of the RAM, you
will likely have problems.  ::)

AlejandroPadrino:
Hello,

in my computers, the problem is loading all TC releases from DVD.  It can not start the X graphics server.  There is no problem loading from USB.  The limit of 341mb in custom core (.gz compressed) is for 2gb RAM.  Custom root filesystem uncompressed into RAM is about 942mb in size.

Hope this helps you, Jazzbiker.

Best.  :-)

Navigation

[0] Message Index

[#] Next page

[*] Previous page