tinycore_v2.8rc3

[roberts]

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

tinycore_2.8rc3.iso
tinycore_2.8rc3.iso.md5.txt

Change log for Tiny Core v2.8

rc1:
* Updated tce-load to allow miltiple loading, e.g., tce-load -i *.tcz
* Updated tce-load to drop ".tcz" requirement.
* Updated appsaudit to allow  selective removal of items from "marked for deletion"
* Updated appsaudit to allow operation in tce directory as well as tce/optional directory, use File option.
* Updated appsaudit menu for smoother operation.
* Updated cd_dvd_symlinks.sh for better multiple cd and dvd devices.
* Cleanup of tce-setup & tce-update of l,m,lm, and ml code.
* Updated tce-fetch.sh to cleanup old dual repository support.
* Updated tce-update to prompt before beginning easy mode batch update operation.
* After much Team testing and input, the upx'ed kernel returns, prior kernel is in distribution files.
* Dropped symlinker by using builtin cp construct.
* Dropped GNU ftp from base.

rc2:
* Updated tce-update for selective interaction via CLI options "query", "list", and "update".
* Major updates to appsaudit including new "Updates" menu option to "check for updates and selectively update wired into the tce-update options.
* Updated and reorganized cpanel, added "TCE Update", "USB Install", "Run Command", "Xkill", and "Xvesa Setup"
* Dropped dropbearmulti from base.
* Updated appbrowser cleanup of l,m,lm,ml code.
* Updated rc.shutdown by reverse umount loops to support tcvd virtual drive.

rc3
This release candidate changes the storage of extensions to a single location, the optional directory located under your "tce" directory. Boot time loading of application extensions are provided by links into the optional directory. These links are easily maintained with the new OnBoot section of appsaudit.  This will better support the trend to use more "OnDemand" items, make it easy to "move" applicatons into and out of the "OnBoot", tce, directory. This also greatly improves systems resources by having a single copy of dependencies.  Having a single area to host all extensions & dependencies also greatly improves auditing and both batch and selective updating.

* Updated FLTK to v1.1.10.
* Updated FLWM with more traditional close button layout.
* Updated appbrowser to support new extension support structure.
* Updated appsaudit - new menu section OnBoot.
* Updated tce-setup, tce-load, and tce-audit to support new extension support structure.
* Updated 'ab' shell appbrowser for more consistent input handling.
* Updated udev rules for much quicker boot times with loop mount extensions.
* Updated rebuildfstab for faster response.
* Updated filetool.sh to ignore sockets.
* Updated tc-terminal-server typo.
* Standard kernel returns with upx'd kernel available in the distribution file area.

Notes:
For tiny core users to move to the new structure perform the following:
* boot base norestore
* mv your_tce_dir/*.tcz* optional/.
* appsaudit -> OnBoot

Select only those apps that you wish to have loaded upon boot.
Do not select dependencies, they will load from optional.
Your "tce" directory should have very few link items for your selected boot time apps.

Easy to change your mind using appsaudit OnBoot as
Left hand side panel selects item and creates link in "tce" dir
Right hand side panel deletes link from "tce" dir
Rebooting then loads items as selected.

We now have a single directory from which to audit dependencies, perform selective updates, and pick and choose our on boot selection of applications.

[bmarkus]

Is kernel still UPX'd?

EDIT by roberts: I added mention of the return to standard kernel to the change log.

[helander]

Hi Robert,

great news (the new extension storage structure). This is very much in line with a prototype a made last week.

I guess that if you are working with different system configurations, i.e. different sets of installed applications, you could create meta-packages that represents these sets (the .dep file lists the applications to be included) and then you just select one of these metapackages as OnBoot?

Is the boot time loading of extensions fully recursive? The prototype I made is fully recursive and it works very well.

A tip for users that have the repo synced to their system is to place the repo copy at tce/optional, i.e. no need for an extra copy and always the most up to date version available (if the repo is synced).

Thanks

Lars

[roberts]

Is kernel still UPX'd?

No standard kernel in the iso. The upx'd kernel is available in the distribution files download area.

[roberts]

Hi Robert,

great news (the new extension storage structure). This is very much in line with a prototype a made last week.

I guess that if you are working with different system configurations, i.e. different sets of installed applications, you could create meta-packages that represents these sets (the .dep file lists the applications to be included) and then you just select one of these metapackages as OnBoot?

Is the boot time loading of extensions fully recursive? The prototype I made is fully recursive and it works very well.

A tip for users that have the repo synced to their system is to place the repo copy at tce/optional, i.e. no need for an extra copy and always the most up to date version available (if the repo is synced).

Thanks

Lars

Dependency loading has not changed except for the new single location as specified in the change log.

[helander]

Would you consider a fully recursive load, both at boot and when installing via appbrowser, in the future? It would simplify creation and maintenance of .dep files.

/Lars

[roberts]

Although I don't see any impending need, sure. For consideration email me.

[bigpcman]

Great work Robert and team tinycore. I'll start testing this release today.

[bigpcman]

I noticed there's still an ftp indicator in the tool panel. Is this correct? I thought ftp was dropped from the base.

Also, any progress on the dropbear extension?

[bigpcman]

Just out of curiosity does "tce2tcz.sh" still work?

[bigpcman]

Regarding tce-load usage:

Code: [Select]

# Example usage:
# tce-load -i /mnt/hda1/tce/optional/nano.tcz   Loads local extension
# tce-load -w -i nano.tcz                       Download into tce/optional directory, links for OnBoot and installs
# tce-load -w nano.tcz                          Download only into tce/optional directory

I'm a little confused just what options cause the "boot link" to be created in /tce ? Are both -w and -i required?

Could a little more explanation be provided.

[bigpcman]

Could a few of the more complicated usage examples be provided for the tce-audit command.

Code: [Select]

Usage tce-audit: {builddb|dependson|requiredby|nodepends|audit|auditall|delete|marked} extname

[bigpcman]

Could a little more explanation be provided for tce-update easy mode and inplace batch mode.

Code: [Select]

# If not interactive then check for easy mode or inplace batch update

[bigpcman]

Is tce-setup used by anything other than tc-config ?

[roberts]

I noticed there's still an ftp indicator in the tool panel. Is this correct? I thought ftp was dropped from the base.

Also, any progress on the dropbear extension?

ftp was dropped. Where is ftp shown? AFAIK, not shown when booted base norestore. What window manager are you using?