Same here, the bootstrap is via porteus.cfg and tinycore and puppy are mere menu entry to handle those.nanZor wrote: ↑08 Nov 2021, 23:11TinyCore? I find Porteus to be an excellent boot host for that. I download only two distribution files from the X86_64 port (vmlinux64 and corepure64.gz), place them into my syslinux directory, edit the porteus.cfg with a menu entry to handle those, and when I feel like getting all TC, I boot that way using Porteus as the intial boot host.
![Smile :)](./images/smilies/smile.gif)
Thought I could look into TC (=TinyCore) more, at least their x86-64 modules were 100% compatible with Porteus (should have been around the time of 5.0rc1 or 5.0rc2, and some TC modules have been amazingly small.
Unlike Porteus or forum.porteus.org TC has very strict and long-listed rules on how to make modules you have to adhere to if you want your module to be approved by TC; so I myself registered on their forum, but not even once managed to create one single TC module… because of the many TC module creation rules they demand all be followed, of course.
That has advantages and disadvantages.
Disadvantages: Noobs to the TC rules for modules like me can be put off completely on creating own modules for TC since the sheer amount of rules is overwhelming.
On the other hand, I presume the amazingly small size of some of their modules most probably is at least in part because of the long list of rules…
In short: transferring such strict module creating rules over to Port: strict adherence to such rules could increase the quality and ensure smallest possible module size but would also most likely ensure less modules get created overall. Way less modules I'd say. So, no, we at Porteus should keep our way of doing like we did it all these years.
Or in other words: one more reason why forum.porteus.org is my main Linux home and no other Live Linux distro even comes close.
![Magic :magic:](./images/smilies/magic.gif)
![Juggling :juggler:](./images/smilies/sporty98.gif)