tinycore_2.3RC2

[roberts]

The Second Release Candidate of v2.3 (tinycore_2.3RC2.iso), is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates/

Change log for v2.3 Release Candidate 2

* Updated tc-config to support tcz extensions in /opt/tce for remasters.
* New tcz2ram.flg placed in your tce directory will cause all tczs to be loaded into ram.
* New tcz2ram.lst placed in your tce directory will result in those tczs specified in such be ram loaded.
* Updated tce-load, added getopts to support new options. Now use -w (was wget) , -i (to install), -r (force tcz to ram) and -f (force symlinker)
* Updated appbrowser to support the new tce-load option flags, and tcz2ram options, as well as both install and mount buttons for tczs.
* Dropped tce-wget. Use tce-load instead.
* Updated tce-load tee'd messages to support both CLI and appbrowser.

Note: Not all tczs may work loaded to ram. If you find such, please report in the extension area and not here. It is a goal to move to supporting only one type of extension for the next major release of Tiny Core,

[junan]

what mount do with tcz at appbrowser ?

[roberts]

tcz were made to be mounted.
The mount button does just that mounts the tcz extension.
Prior to 2.3 the install button's action was determined by extension type.
With a tcz the install button was mounting the tcz.
Now with 2.3 you have the choice, to continue to mount the tcz, use the mount button,
To extract the tcz entirely into ram, use the install button.

[bigpcman]

The Second Release Candidate of v2.3 (tinycore_2.3RC2.iso), is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates/

Change log for v2.3 Release Candidate 2

* Updated tce-load, added getopts to support new options. Now use -w (was wget) , -i (to install), -r (force tcz to ram) and -f (force symlinker)

* Updated tce-load tee'd messages to support both CLI and appbrowser.

Robert could you elaborate a bit on why the tce-load -f (force symlinker) option may be required.

Could you explain this a bit more as well: "Updated tce-load tee'd messages to support both CLI and appbrowser"

[roberts]

force as an option has been in tce-load for some time. It forces symlinker to overwrite existing files.
The new tce-load using getopts, i.e., flags, I simply changed the existing force code to execute upon finding the -f flag.  force symlink should rarely, if ever, be needed.

Originally, I wrote tce-load as the engine for appbrowser. Since tce-load is being used more from the command line as well as now having microcore, I need the messages to be shown upon command line invocation as well as swallowing them for appbrowser GUI display.

[jls]

why can't I use tce-load something, insetad of tce-load -i or -r...

[Kingdomcome]

I too will miss tce-wget 

[roberts]

Perhaps you didn't read that install can no longer be determined by extension type.
That offerings both mount and install for tczs required options to be specified.
Perhaps, in your specific domain, you will never need such. If that is indeed the case, then I suspect that you could easily create a wrapper