Tiny Core Linux
Tiny Core Base => TCB News => Final Releases => Topic started by: roberts on February 17, 2012, 10:11:18 PM
-
Team Tiny Core is proud to announce the release of Core 4.3.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/release (http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/release)
Change log:
The major theme for Core v4.3 is self contained mountable/unmountable applicaton extensions.
Change log:
* New scm-load for scm new extension type supports icon removals and menu updates for all supported window managers.
* New scm an 'ab' like command line tool to maintain scms, browser repo, list local, install, uninstall, add to boot, and remove from boot, etc.
* New scmbrowser an FLTK GUI to manage your scm extensions.
* New scm-fetch.sh and scm-search new internally used support programs for scms.
* Updated tce-setup to load/mount scm via scmboot.lst
* Updated busybox with latest password patch.
* Updated tce-update to use md5.db file for quick updating and checking with AppsAudit.
* Updated tc-functions to correct virtual disk mounting.
* Updated tc-config to support CSV in blacklist boot code.
* Updated rc.shutdown to allow persistent home & opt inside a virtual loop mounuted disk.
* Updated tc-terminal-server for new core name.
* wbar.tcz new icon for scmbrowser, code cleanup in rm icon and nohup to wbar.sh
* Xlibs.tcz added Sytem Tools menu for scm.
* Xprogs.tcz for new scmbrowser.
* Updated appbrowser mirror/search GUI anomaly and writable TCEDIR as reported.
* Updated Xlibs.tcz, Xprogs.tcz, and wbar.tcz to support Xprogs.tcz OnDemand.
* Minor adjustments to freedesktop items as requested.
Note must update Xlibs.tcz, Xprogs.tcz, wbar.tcz, and supported window manager as may be required.
-
Thanks for the update, many changes to peruse :)
-
runing TinyCore-4.3.iso under virtual box
starting appbrowser
shows message box "fatal error:TCE directory is not writeable "
appbrowser did not open
..
after loading scm using scmbrowser appbroser will start without error
-
Heads Up! Reposted 4.3 release to correct as reported by dubcore.
-
Minor adjustments to freedesktop items as requested.
I saw this in RC2 but have not found any thread to which this refers, although am still looking. meanwhile I'm guessing this may refer to a change for scm's?
Is there a link available to read about the issue which has been changed please?
-
Minor adjustments to freedesktop items as requested.
I saw this in RC2 but have not found any thread to which this refers, although am still looking. meanwhile I'm guessing this may refer to a change for scm's?
Is there a link available to read about the issue which has been changed please?
A request was for OnlyShownIn=old to tinycore-scm.desktop and tinycore-wbarconf.desktop as they are not needed in DE like LXDE or Xfce4.
See: http://forum.tinycorelinux.net/index.php/topic,12455.msg67446.html#msg67446 (http://forum.tinycorelinux.net/index.php/topic,12455.msg67446.html#msg67446)
-
Thanks
-
http://distro.ibiblio.org/tinycorelinux/ (http://distro.ibiblio.org/tinycorelinux/) and the News iframe need an update. Download page looks good.
Side question on News: Does it deserve trimming and/or another page (either archived news or all news)?
-
Thanks Robert for addressing the AppBrowser issue where a non-writable TCE directory was triggering a possibly confusing popup message. The new version in TC 4.3 is much clearer and will keep more newbies and not-so-newbies being cavalier out of trouble. ;)
-
Hello,
can somebody make a quick HOWTO for an update from 4.2.1 to 4.3?
(last update to 4.2 was not so easy for me).
a) keep the kernel 3.0.3
b) overwrite the core.gz?
c) Keep the tce directory?
d) ...
-
Copy over the new core.gz
Use AppsAudit->Updates->Check for Updates.
-
Copy over the new core.gz
Use AppsAudit->Updates->Check for Updates.
This would be a VERY useful piece of info to include in the release announcements.
A simple reminder of the upgrade process from the previous release would do no harm to be included each time as a reminder for those of us who are not in the development loop & using the process regularly, but whose focus is more on just using TC as an end-user.
-
4.2 to 4.3 is just a minor update.
The same repo is used with the same versions.
This should not require a How To.
-
On my 4.3 install to USB (using tc-install from CorePlus), the boot directory is under /mnt/sda1/tce/, whereas previously it was under /mnt/sda1/. Did something get messed up or is this how it's supposed to be? It works fine anyway.
-
On my 4.3 install to USB (using tc-install from CorePlus), the boot directory is under /mnt/sda1/tce/, whereas previously it was under /mnt/sda1/. Did something get messed up or is this how it's supposed to be? It works fine anyway.
That is how it is supposed to be.
It was like that some time ago if you used grub4dos.
-
Using a single directory for all things Core ensures that Core can easily run embedded with another Linux distrubtion, i.e., no conflicts with a /boot directory typically used by most traditional Linux distributions. You can use our installation program to easily install "embedded" without disturbing an existing Linux install, adjust boot loader and go. That is the reason for the change.
-
Booting latest tinycore-current.iso (4.3 dated Feb 19 2012) with base boot code and attempting to download tc-install using app-browser results in
fatal error:TCE directory is not writable
Opening scm browser as previously stated did not fix issue, however after downloading an scm app the issue is temporarily fixed.
-
Was fixed Feb 25 and is in 4.4rc1. Work-a-round:
$ mkdir -p /tmp/tce/optional
-
Thanks for the workaround. will remember to look here
-
I had the same fatal error:TCE directory is not writable starting AppBrowser
My TCE directory is on a writable NFS share hosted on another computer, it's contents were originally copied there from the cde directory from the TinyCore CD.
Solved it:)
Check the user write permissions on the 'optional' subfolder inside TCE are set. I've somehow managed to have that autocreated user read-only. Maybe I muddled up permissions on the parent doing my initial copy.
BTW Silly question, I'm new to this. How do I get the Core version number of what's installed? A command?
-
BTW Silly question, I'm new to this. How do I get the Core version number of what's installed? A command?
The command is "version"