microcore_v2.11rc2

[roberts]

The Second Release Candidate of Micro Core v2.11 (microcore_2.11rc2.iso), is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates/microcore/

microcore_2.11rc2.iso
microcore_2.11rc2.iso.md5.txt

Change Log for Micro Core v2.11

RC1
* New optional zsync update support for faster extension updates.
* Updated tc-config waitusb added optional LABEL/UID, e.g. waitusb=30:LABEL=tinycore
* Updated tc-functions CMDLINE to not require kernel specific options before tinycore options
* Updated tce-load to trap mount errors.
* Updated tc-config PXE to support DOS/Windows created lists.
* Updated /root/.profile to use login instead of su -
* Fixed utc TZ bug in tc-config
* Added /var/run/utmp and /var/log/wtmp to support "who" reporting.

When adding X support to microcore note:
* Updated Xprogs.gz
* Updated flwm.tcz
* Updated flwm_topside.tcz
* Updated wbar.tcz

See announcement for Tiny Core v211 RC1 for change log regarding updates that affect X.
http://forum.tinycorelinux.net/index.php?topic=5800.0

Also the release candidate versions supporting freedesktop and OnDemand of:
* Updated jwm.tcz
* Updated hackedbox.tcz


Notes: Files that have changed and are likely in your backup or persistent store.
/opt/.xfiletool.lst       change home/tc/.wmx/Applications to home/tc/.wmx
/home/tc/.setbackground   the location of logo.png has changed to /usr/share/pixmaps
                           either edit this file or use Control Panel-Wallpaper-Color-OK

RC2
* Updated busybox to 1.16.1
* Updated getTime.sh with -p (print only) and simplied busybox date format.

Note when adding X the following have been updated:
* Xprogs.gz
* wbar.tcz
* flwm.tcz
* flwm_topside.tcz
* jwm.tcz
* hackebox.tcz
* fluxbox.tcz

Also see the Tiny Core v211rc2 announcment for other X releated announcements.
http://forum.tinycorelinux.net/index.php?topic=5842.0

[Juanito]

I tried loading the bluez extension (which has dbus as a dep)

Opening the services box shows both dbus and bluez as started, when neither of them is started.

If I click both dbus and bluez boxes to change them from green to grey and then click on the bluez box, it turns green, but not the dbus box, when in reality starting bluez starts dbus.

[Juanito]

Using microcore and the *gz files, the ~/.X.d folder is not populated with wbar and if I add a file to start dbus (named dbus), it is not executed

[curaga]

I tried loading the bluez extension (which has dbus as a dep)

Opening the services box shows both dbus and bluez as started, when neither of them is started.

No status function in the init.d script, or not returning a code. Please add

If I click both dbus and bluez boxes to change them from green to grey and then click on the bluez box, it turns green, but not the dbus box, when in reality starting bluez starts dbus.

True, there's only a full scan on the start. With more than a couple services it can take seconds to check the status of every service.

I'm sure having an UI freeze that long is not preferable. Constant polling would use cpu without much gain (but be the only way to get the status of a service started from elsewhere), and multithreading would introduce much complexity for such a simple app IMO.

[roberts]

Using microcore and the *gz files, the ~/.X.d folder is not populated with wbar and if I add a file to start dbus (named dbus), it is not executed

True, wbar as part of Tiny Core versus wbar as an extension.
I have updated the startup script for wbar and tested OK with wbar starting as expected.

Good find. Thanks!