General TC > Remasters / Remixes - Unofficial

InstantCore

<< < (3/8) > >>

jazzbiker:
Hi Rich!


--- Quote from: Rich on December 26, 2023, 09:33:12 AM ---Persistent  home  and/or  opt  don't need to be put on separate partitions.

Anytime I do a Tinycore install, it gets its own partition with:

--- Code: ---boot/  home/  lost+found/  opt/  tce/
--- End code ---
An entry for this install gets added to grubs  menu.lst  file.
Then home, opt, and tce get populated to suit my needs.

--- End quote ---

Thanks for the explanation, I must have remebered this :-) but I never use persistent /home or /opt.
But what must be the directory structure if You have several TC versions? Partition per version?

jazzbiker:
Probably directory per version:

--- Code: ---/boot
/lost+found
/tc10/home
/tc10/opt
/tc10/tce
/tc11/home
/tc11/opt
/tc11/tce
...

--- End code ---
?

Rich:
Hi jazzbiker
I typically do partition per version.
I have also done this when I want a choice of booting
to a 32 or 64 bit environment:

--- Code: ---/boot
    core.gz
    corepure64.gz
    vmlinuz
    vmlinuz64
/home
/lost+found
/opt
/tce
/tce64
--- End code ---
I use this for when I want to be able to run one of
my compile scripts to produce 64 bit binaries.

jazzbiker:
After playing a bit with InstantCore the simple, yet probably silly, question arose in my head:

Why, damn, OSes in general and TinyCore especially are not distributed in the form of really alive filesystems? What is the sacred meaning of dead iso-s?

It is so comfortable and convenient to:
1. dd it to some drive and instantly dive at the full depth.
2. Run it in qemu, perform some tweaking and return to the point 1.
3. Mount in rw mode and adjust manually.

Sorry for me being too emotiional, but I am really astonished.

CNK:

--- Quote ---Why, damn, OSes in general and TinyCore especially are not distributed in the form of really alive filesystems? What is the sacred meaning of dead iso-s?

--- End quote ---

Well I still write them to CDs. You could include all the functionality of your disk image in a dd-able ISO anyway, catering for the likes of me as well. Dual BIOS/UEFI booting is possible with dd-written ISOs, though it took me quite a while to figure out how to set that up right.

For PiCore I think it would be better to distribute an image as a ZIP containing the OS files which can be unpacked to a preformatted SD card (the default FAT, or re-formatted ext* by the user). Much easier than dealing with disk image writer tools and expanding partitions. I did that for a PiCore-based package that I developed.

But everyone has their own opinions. I believe Puppy Linux switched from ISOs to disk images a while ago, so your opinion isn't unique. That might have turned me off, except I already hadn't tried a new Puppy Linux version in many years anyway.

Navigation

[0] Message Index

[#] Next page

[*] Previous page