Tiny Core Base > piCore Test Releases

piCore16 Beta

<< < (3/4) > >>

mung:

--- Quote from: patrikg on May 11, 2025, 06:59:41 AM ---Take a look at Alpine Linux I think you have only one big FAT partition for Rasberry Pi.

--- End quote ---

I think alpine is musl based, so probably makes more problem with cross compile rather than devrelop simple rasbian compile and copy to tinycore??

Not sure if it is a good strategy to direct your possible users to other dists, or maybe I am just a trouble maker :lol

Paul_123:
Partitions are kept small for distribution and imaging.  I increased them once, and users complained, so I put them back.

The second partition is because fat cannot be easily resized.  You can easily create a single partition image, if that is what you want. 

Don’t use windows and none of this is a problem.

Rich:
Hi mung

--- Quote from: mung on May 11, 2025, 06:46:57 AM --- ... but main thing I thought was why was the extension partition so small?? ...
--- End quote ---
So that the image file will fit on as many different devices as possible.


--- Quote --- ... I resized it, but it should not be necessary, and also it was not any size that made up a usual SD card size (i.e. 64m, 128m, 256m, ....) could have added another 32m to the partition and it been within the 128mb of SD card multiple. ...
--- End quote ---
When you dd the image onto a device you overwrite the partition table, effectively
destroying any previous contents and creating a dedicated piCore device. At that
point it makes sense to expand the partition to fill the device.


--- Quote --- ... That would just make it simpler to add the few extra tcz that I need. ...
--- End quote ---
Design decisions are made with the majority of users in mind, not individuals.
 

--- Quote --- ... Which is another annoyance I have about a seperate extensions partition, why have it? ...
--- End quote ---
After you boot, that partition is no longer used and gets unmounted.


--- Quote --- ... Why not just put the extensions on the main fat boot filesystem? ...
--- End quote ---
Persistent  /home  and  /opt  directories are also an option. Most likely they
would be placed alongside the  /tce  directory.  /home  and  /opt  should be
on an  ext  file system to preserve ownership and permission attributes.


--- Quote --- ... I know maybe there are reasons for security or file access speed etc, but it would be nice to have a 'standard' for dropping tcz packages into the windows accessable boot partition. I normally create a 'packages' directory and have a script to check. ...
--- End quote ---
I think the whole point of Tinycore (piCore) has always been to provide a
bootable environment that then allows you to tailor the system to your needs.
Coreplus attempts to provide required extensions for establishing a wireless
connection for x86 based systems. I believe piCore does something similar. At
that point you can install additional extensions. Once you have it running, you
can use that system to "create a 'packages' directory and have a script to check."
for any future systems.

Rich:
Hi Juanito

--- Quote from: mortegai on May 06, 2025, 01:34:18 PM --- ... Everything works correctly, except that exittc (TC Exit Options) defaults to Safe when I have the BACKUP="0" environment variable set.
--- End quote ---
This issue has been fixed and the git master updated. Only apps and exittc were affected.
Though problem was originally reported here, I did see the same behavior on TC16 x86_64.

Could you please update Xprogs when you have a chance?
Thank you.

mortegai:
Updated Xprogs.
"exittc" now works correctly.
Thanks everyone.

Navigation

[0] Message Index

[#] Next page

[*] Previous page