InstantCore

[CNK]

How am I to accommodate? Offical ISOs can be downloaded form http://tinycorelinux.net/downloads.html, aren't they?

I mean accomodate CD users with your InstantCore release by using (dd-able) ISOs for them.

Or actually you originally asked:

Why, damn, OSes in general and TinyCore especially are not distributed in the form of really alive filesystems?

So I thought you were asking why Tiny Core shouldn't use disk images instead of ISOs for the official releases too.

Either way, I've said all I care to say about that now.

[jazzbiker]

Hi CNK!

InstantCore is not a kind of my release, it is compilation of official CorePlus-14.0 and TinyCorePure64-14.0 - talking about the content of the present InstantCore.img. My contributions are grub.cfg (3 kB) and inflate.sh (1 kB). The cornerstone is grub2 incorporated into the drive image according to an excellent Juanito's dual boot BIOS/UEFI HOWTO: http://forum.tinycorelinux.net/index.php/topic,19364.0.html.

So I propose to use "InstantCore" term for any image of the live drive with grub2 installed in the dual boot mode accordingly to the above mentioned HOWTO. In my case I used the grub.cfg I use by myself, as reliable and convenient, and applied it to the official ISOs content. One can change the grub.cfg and content to his/her taste and get the same-featured InstantCore image, which can be written into any USB flash drive or local drive and instantly obtain full-functional TinyCore system.

I mean accomodate CD users with your InstantCore release by using (dd-able) ISOs for them.

So I thought you were asking why Tiny Core shouldn't use disk images instead of ISOs for the official releases too.

CD users shouldn't pay attention to the InstantCore approach. They can download official ISOs and be sure they've missed nothing.

[jazzbiker]

Warning for new users!

Current InstantCore.img is based on the official CorePlus-14.0-iso and TinyCorePure64-14.0.iso.
Some important updates were applied recently to some extensions in the repos. The current 14.x repo structure is not fully consistent and in case You will download some extensions (i.e. mc.tcz) You need to perform certain sequence of maintenance commands:

Code: [Select]

tce-audit builddb
tce-audit updatedeps
tce-audit fetchmissing
tce-update
before installing them.

But! The last "tce-update" command demands too much free disk space, than it is accessible inside the original InstantCore.img and may be performed only after Your system will gain the access to the full USB drive room, which can be done choosing "base+resize" boot menu option and then running:

Code: [Select]

inflate.sh
sudo reboot

So if You will (undoubtedly) want to load new extensions, the please:
1. Boot into "base+resize"
2. inflate.sh
3.sudo reboot
4. After downloading (and before installing!) of any extensions please run

Code: [Select]

tce-audit builddb
tce-audit updatedeps
tce-audit fetchmissing
tce-update
5. Reboot

Sorry for inconveniences, will hope that in the new year and new TC versions things will become less complicated.

Congrats with upcoming holiday!

[jazzbiker]

Unfortunately even proposed maintenance sequence is not able to resolve all inconsistencies between extensions present in CorePlus-14.0.iso and the current repo state.

Sorry, in its present state InstantCore.img must not be recommended for new users, due to incompatibilities with repo state.

[gadget42]

@newbieCore: I'm glad to hear you've made it into the MMC (turning off CSM) - three entire pages of forum comments since my last visit :)

@newbieCore, You may try writing an image from http://forum.tinycorelinux.net/index.php/topic,26658.0.html this thread to /dev/mmcblk0 with the help of dd utility:
sudo dd if=InstantCore.img of=/dev/mmcblk0 bs=4M
It contains ready to use dual boot BIOS/UEFI filesystems with CorePlus14 and TinyCorePure64. If the case is UEFI, it may help. Just to try with low expectations.

@jazzbiker: Please refrain from up-selling third party custom releases of Tiny Core Linux on the Tiny Core Linux forum (such as your "Instant Core" as you've named it); this forum is focused on the content found strictly within repo.tinycorelinux.net; when you create your own custom "version" of TinyCore and make changes to how our packages install and/or operate, it makes it difficult, if not impossible for us to "support" end users as this now falls on your lap - and preferably your website and domain.  Please understand, also, that we have no way to babysit every package that has ever been created by users; thus we have no way to ascertain whether or not "Instant Core" is properly functional, or whether it's infested with errors, virus' or trojans, etc.  (Not saying you would -- but we have no way to prove that to users like @newbieCore and we cannot be held liable for malicious damages.)

@Rich, @curaga, @Paul_123: Need your $0.02 here.

might be nice to have a copy of that here as well...

[jazzbiker]

One more great post!

@jazzbiker, @newbieCore: YES, by all means! (sorry, more than one word!)

I see that communicating with @newbieCore I am violating something I don' t understand.

NO, communication isn't a problem in the least.

Actively promoting a remaster ON the forum as a replacement for the Tiny Core Linux project can become a problem, which I hope you understand why.

Let's say the next X number of people to stop by find your link and install your remaster instead of the real Core project...  and let's imply there are problems...  who do you think THEY will expect support from?
You?  Or the development and maintenance team from Tiny Core Linux which is what's at the top of the website they're looking at?
"I'm sorry, sir...  the release you installed is not supported..."  "...What do you mean it's not supported, I got it FROM you people - see, it's right here on your forum!!"
It doesn't end well.

Suggestion 1: If you feel strongly that your remaster is superior in any way, put together a website (there's plenty of free hosting services out there, so it doesn't even cost you anything) and describe your remaster accordingly; leave note on the site indicating it's not a TCL release, but instead an "awesome custom remaster" (how ever you want it worded) but that it's not affiliated with the Tiny Core Linux project AND offer your own contact information for if/when someone runs into trouble.  Avoid creating links to this forum - it's an SEO nightmare.  Instead, you're welcome to create links such as "...for more information on the Tiny Core Linux project, click here" -- that sort of direction, as long as you're not pretending to BE Tiny Core Linux or otherwise directly associated.

Return here to the initial thread you created regarding its release and update that thread with your website's URL.  In doing so, you cover the necessary bases and you've made it perfectly clear to someone downloading it that this is your project (a PORT of Tiny Core, so to speak.)  As long as the remaster still maintains the forum requirements (ie: spamming, marketing, abuse, piracy - all those types of issues) I don't mind in the least that you try to help people out using it -- as long as they are aware that it's your remaster... up front.

LEGALLY speaking, website and other similar trade-marked or identification based graphics should not be reused on third party websites without expressed, written permission... blah...  blah...  you'll want to come up with a fresh new look for "Instant Core" anyway.

Suggestion 2: If you really want to maintain a port of this project, here's a recommendation that works in your favor by limiting the amount of work that has to go into it:

• Download and extract the full TinyCore package that suits what you're building from
• Take all the files you've altered/created/etc. and create instant.gz (CPIO)
• Update extlinux.conf: APPEND: /boot/core.gz,/boot/instant.gz
• Repackage and upload to Google Drive

If you do things in this fashion, people can separate your work from TCL, verify core.gz is in fact untouched and if they wanted to check to ensure your efforts were clean and genuine, a look inside instant.gz makes it easy to do (without having to scan/scour a modified core.gz or root/modules.gz)  Also, when there's a new release (15.x for example) your "upgrade" is tremendously simple by merely updating extlinux.conf's APPEND line and repackaging.

might be nice to have a copy of that here as well...

I'm sure it deserves to be pinned in the Unofficial Remixes board ;-)