Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on October 25, 2012, 10:27:31 AM
-
The fourth release candidate of Core 4.7 is ready for public testing:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/release_candidates
Change Log:
- Updated ondemand to suport scm extensions and icons from both tcz and scm.
- Updated wbar - to support scm ondemand icons.
- Updated scmapps GUI for new ondemand maintenace and download option.
- Updated scm-load - new option -wo ondemand download.
- Updated tc-functions - added new support functions.
- Updated scm to interface to updated scmaps GUI.
- New scm-run to support scriptable load and launch scm style extensions.
- Updated filetool - New GUI access to ,filetool.lst, .xfiletool.lst, and backup options.
- Updated filetool.sh to interface to updated filetool GUI.
- Updated apps GUI - New Check Onboot Unneeded and changes required by ondemand scm support.
- New chkonboot.sh for cli Core only use.
- Updated tce-setup for consistency in handling onboot.lst and scmlist.lst.
- Updated loadcpufreq to allow blacklisting.
Note: Requires new wbar.tcz and Xprogs.tcz (apps, scmapps, filetool) also in the rc testing area until final release.
Note:
Having both scm and tcz in ondemand means changes to tcz ondemand.
- All ondemand items both scm and tcz will be available in the ondemand menu for supported window managers.
- From ondemand menu, item will be loaded and if specified by a freedesktop item will also be launched. The regular menu item and icon, if any, will be updated and displayed.
- Subsequent launching of the item will be via the regular menu or displayed icon.
- Subsequent ondemand menu selection for an scm item will unmount and remove the regular menu item, and associated icon if any.
- Subsequent ondemand menu selection for a tcz will produce no action, use regular menu item or icon.
- All ondemand items need to be re-created for the new format.
-
In APPS Select Mirror popups 'Must load morrors.tcz extension or have /opt/localmirrors in order...' however it works after Select fastest mirror. Please update popup message.
-
? The mirror picker installs mirrors.tcz, so the message is correct?
-
? The mirror picker installs mirrors.tcz, so the message is correct?
Tecnically yes, from user's view not. There are no any info displayed about mirrors.tcz fetch/install, it is just working :)
Also, based on message user is going to install mirrors.tcz which is not needed, see above. All together message is not useful or misleading for ordinary user.
-
hi friends,
i use microcore with Xvesa and fluxbox.
i was very happy with the v4.7rc3-cut, everything worked fine for me.
now i downloaded these v4.7rc4-files and changed just these four needed files from the release candidate section:
core.tgz, vmlinuz, Xprogs.tcz & wbar.tcz, all with its dep-files and md5sums.
i checked all md5sums, so these files are not corrupted.
nothing else of my proved configuration is changed, but when i reboot it with rc4 i get the message:
bash: startx not found
and no Xvesa-environment is started.
the manual command startx also doesn't work,
and i don't see any reason why my X-window-system doesn't start anymore.
do i need a new or changed onboot.lst after migrating from rc3 to rc4?
what more information do you need or do you have experienced something similar?
after changing these four files back to rc3 everything works fine again,
so it has something to do with rc4.
thanks for your help.
-
It would appear that you do not have fltk-1.1.10.tcz as per
http://forum.tinycorelinux.net/index.php/topic,14290.0.html
Therefore Xprogs.tcz did not load and thus Xlibs.tcz did not load
resulting in startx not found.
-
My problems were twofold.
First, after updating deps, getting missing deps and running updates I somehow ended up with two versions fltk-1.10 & fltk-1.1.10 didn't notice this at first so meanwhile ran MD5 checking, e2fsck on the volume, even restored the stable release version 4.6.2, Xprogs, wbar + deps, and created a new onboot lst, none were successful of course with every boot failing to install wbar and system apps. Exiting from X allowed the use of poweroff command in order to shutdown meantime.
Apparently we had acquired two versions of fltk. How this occurred is a mystery to me, but removing the earlier version seemed to resolve the issue (at least with 4.7rc4).
It didn't help failing for some reason to change owner/permissions on core 4.6.2, core files, Xprogs, wbar + deps from TinyCore-current.iso used during troubleshooting the missing wbar. Then attempting (unsuccessfully) to overwrite these files when returning to the desired 4.7rc4 versions later on. Simply deleting these 4.6.2 versions of the core files, Xprogs, wbar + deps, then replacing with new RC versions fixed this issue. I hate it when I'm not root, always leads to trouble.
-
Meanwhile, now that the system is operational again, apps are running smoothly and so far as intended. Nice work, thanks
-
Hi coreplayer2
I somehow ended up with two versions fltk-1.10 & fltk-1.1.10
Apparently we had acquired two versions of fltk. How this occurred is a mystery to me
This might have something to do with it:
http://forum.tinycorelinux.net/index.php/topic,14290.msg80597.html#msg80597
-
fltk-1.1.10.tcz has little to do with rc4 and everything to do with keeping your system updated.
Using the provided tools of Update .dep files, Fetch Missing Dependencies, and Check of Orphans would have had the fltk change working on existing versions of Core. Then rc4 would have been a breeze. It is always good to follow tce bug reports especially when dealing with system required extensions.
-
I agree thanks, was my mistake fltk-1.1.10 release was not related to rc4, was just the time I noticed the addition is all.
I think most these issue were self induced due to a reboot whilst updating, then became distracted chasing the missing wbar gremlin instead of completing the the update of deps files and missing dep's.