Core v4.2rc1

[coreplayer2]

Did you try it with 4.2rc1?

yes it works great

[roberts]

Perhaps the issue is the booting of TinyCore-4.2rc1.iso and not the CorePlus iso.
I did not add the waitusb=5 to the default on TinyCore iso. In fact it *is* missing lst=xbase.lst which I will add.
But to boot the TinyCore iso from a dd'ed pendrive, or unetbootin, simply add the following two boot params.

lst=xbase.lst waitusb=5

HTH

[gerald_clark]

I booted CorePlus with 'tce=sdb1' option.
The optional directory was created root.root and tce-load -iw was unable to download into it.

[gerald_clark]

It would be nice if there was an additional CorePlus boot option that was just 'quiet waitusb=5'
After I dd CorePlus to a thumb drive, I like to add another partition with a custom tce directory.

[bmarkus]

Perhaps the issue is the booting of TinyCore-4.2rc1.iso and not the CorePlus iso.
I did not add the waitusb=5 to the default on TinyCore iso. In fact it *is* missing lst=xbase.lst which I will add.
But to boot the TinyCore iso from a dd'ed pendrive, or unetbootin, simply add the following two boot params.

lst=xbase.lst waitusb=5

HTH

Of course waitusb was there. Adding lst=xbase.lst result is the same.

[bmarkus]

Booting CorePlus with X/GUI no extensions (aka TC) from USB stick (sdc1) tce dir is in /tmp even if I have a tce dire manually created in the root of sdc1 (VFAT). tce=sdc1 has no influence.

Is it possible to setup a permanent tce dir as with previous versions?

[roberts]

You should be using TinyCore.iso.
boot:  tc waitusb=5 tce=sdc1   

Works as expected.


Your specs to CorePlus was no user extensions, i.e., lst=xbase.lst, therefore no user extensions were loaded.

[roberts]

It would be nice if there was an additional CorePlus boot option that was just 'quiet waitusb=5'
After I dd CorePlus to a thumb drive, I like to add another partition with a custom tce directory.

Typically dd'ing the iso image to a pendrive: 
dd if=CorePlus-4.2rc1.iso of=/dev/sdb bs=1M
results in a read-only device.

Unless you are using a different scheme dd'ing into a partition and messing with the boot record. Otherwise I am not following.

[gerald_clark]

Yes, but if you select the last option to boot cmdline only, you can add a partition, format it ext2, create a tce directory, and reboot.
Now when you edit the last boot option, remove the 'base' option, add 'waitusb=5' and boot, the second partition is mounted rw.
You can now mount the first partition and copy the desired Xprogs,Xlibs,Xvesa, window manager to the second partition, create an onboot.lst.
Now you have a custom boot partition that you can tce-load into for a utility boot.
The only thing missing is a boot selection that has "quiet waitusb=5" as the only boot options.

[roberts]

Booting CorePlus already searches for user tce directory and loads user extensions first before loading the extensions provided on the CorePlus media. This is done for two reasons:

1. User stored Extensions on a live drive will always be more recent than the "snapshots frozen" in the CorePlus iso.

2. Rarely used extensions in the CorePlus iso can easily be AppBroswer/Load Local when such might be needed.

CorePlus is not only an installation image but a utility resource for an existing system.

[gerald_clark]

The only menu option that finds the tce directory is "BootCore to command line only. No X/GUI or extensions", and
then only if I remove "base" and add "waitusb=5".

[roberts]

Case 1.
sda1 is a live working system from established tcedir on linux filesystem.
Booting CorePlus from sdb1 pendrive, finds and loads all extensions from sda1 before the CorePlus utility extensions.

Case 2.
I purposely rename the tce directory on sda1 so as to disable CorePlus from finding it.
I insert a second pendive with a FAT32 fielsystem and a tce directory.
Booting CorePlus from sdb1 finds and loads all extensions from sdc1 (second pendrive) before loading the CorePlus utility extensions.

Works as described and expected.

Would need more details to try to reproduce other than expected results.

[gerald_clark]

I do not misunderstand how CorePlus works.

I boot core plus from sdb1 using any of the first seven offered selections.
I have a tce directory on sdb2.  It is not found.
This is because sdb2 cannot be mounted if sdb1 is mounted.

I select the eighth selection "BootCore to command line only. No X/GUI or extensions" and hit the tab key.
I delete the "nobase" option and add "waitusb=5"
My tce directory is found, my extensions are loaded, and my backup is restored.
This is because sdb1 is not mounted, so sdb2 can be, but only if there is no "nobase" option.

I would like to have a core plus thumb drive, but don't want to waste the whole thing with just one 50M partition.
I would like to use the rest of the drive for a full core system.
I can only do this if I manually edit the options at each boot.

My suggestion is that it would be nice to have another boot selection:
"BootCore and scan for tce"  that only has the boot options: "quiet waitusb=5".

[roberts]

The whole point of offering these installation tools is to avoid manual setup.
However for the sake of using a disk image iso dd'ed onto a drive and then manual setup a second partition on the same drive.

On a single pendrive

Case 3:
1. dd if=CorePlus-42.rc1.iso of=/dev/sdb bs=1M
2. fdisk /dev/sdb
3. Create 2nd Linux partiion on the remaining unused drive.
4. hdparm -z /dev/sdb
5. mke2fs /dev/sdb2
6. mount /mnt/sdb2
7. mkdir -p /mnt/sdb2/tce/optional
8. chown tc.staff -R /mnt/sdb2/tce
9. copied sample extension, ace-of-penguins, to tce dir on sdb2 and onboot.lst
10 reboot.

Boot with no other drive with a tcedir other than sdb2 with CorePlus on sdb1
Works as expected with boot options 1-7. sdb2 scanned found mounted and ace-of-penguins loaded.
Followed by sdb1 mounted and CorePlus utilites mount loaded. Both sdb2 and sdb1 mounted in that order.

I am still unable to reproduce your case. You must be doing something else. 

[bmarkus]

You should be using TinyCore.iso.
boot:  tc waitusb=5 tce=sdc1   

Works as expected.

Boots to command prompt, no graphics. startx command doesn't exist.

/mnt/sdc1/tce created. ab works as expected, using /mnt/sdc1/tce

All together  tc waitusb=5 tce=sdc1 leads to mc instead of tc. WIthout tce=sdc1it boots to usual TC.