Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on April 28, 2010, 02:12:50 AM
-
The Third Release Candidate of v2.11 (tinycore_2.11rc3.iso), is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates
tinycore_2.11rc3.iso
tinycore_2.11rc3.iso.md5.txt
Change log for Tiny Core v2.11
RC1
* New freedesktop system menu and extension support for flwm, LXDE, XFCE, jwm, and hackedbox.
* Updated flwm_topside_initmenu for freedesktop support
* Updated flwm_topside_makemenu for freedesktop support
* Updated desktop.sh for freedesktop support
* New tc2freedesk for freedesktop support
* New wbar_icon_upd.sh for freedesktop support
* Added new "Power Off" (exit) button to wbar.
* New OnDemand support for flwm, LXDE, and XFCE, jwm, and hackedbox.
* Updated ondemand script to accept argument now callable from appbrowser/tce-load & appsaudit.
* Updated appbrowser with "Mirrors", and "OnDemand" menu creation.
* Updated appsaudit with "OnDemand" selection/creation from existing downloaded extensions.
* Updated appsaudit "Update Dependencies" to support recursion, and separate "Build Database" option.
* New "Services" added to system menu and required /etc/init.d/services.
* New optional zsync update support for faster extension updates.
* Updated tc-config waitusb added optional LABEL/UID, e.g. waitusb=30:LABEL=tinycore
* Updated wallpaper added center option.
* 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 flwm_topside tile fonts.
* Updated /root/.profile to use login instead of su -
* Fixed utc TZ bug in tc-config
* Re-organized cpanel removing OnDemand, TCE MIrrors, and daemons now handled by Services.
* Updated appbrowser, moved ab2tce.fifo pipe to /tmp.
* Added /var/run/utmp and /var/log/wtmp to support "who" reporting.
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
Note: For jwm and hackedbox release candidate extensions see the Microcore announcment.
http://forum.tinycorelinux.net/index.php?topic=5801.0
RC2
* Updated busybox to 1,16,1
* Moved "Power Off" exit button to first position in wbar.
* Updated tc2freedesk to handle multiple menu items.
* Updated flwm & _topside to handle multiple .desktop items in an extension, via naming convention.
* Fixed Appsaudit OnDemand Exit menu name.
* New .X.d/ directory for startup X programs. See wbar as an example of sourced in items.
* Updated Appsaudit to fold in capitialized extension names.
* Updated getTime.sh with -p (print only) and simplied busybox date format.
Files that have changed in this RC:
.xsession Now uses .X.d/
Note also that several window managers have freedesktop and ondemand support. Their release candidate versions are in the microcore announcement:
http://forum.tinycorelinux.net/index.php?topic=5843.0
RC3
* Updated wallpaper changed label Scale to Full and added Fill (Stretch)
* Updated setbackground for hsetroot -full and -fill options.
* Updated cpanel label change Netcardconfig to Network
* Updated netcardconfig renamed to network.
* Updated flwm, flwm_topside permission update after System Tools menu generation.
* Updated wbar to trim % options from freedesktop Exec elements.
* Updated busybox, fgconsole, six hotfixes, and vi editing mode.
Files that have changed likely in your backup:
.setbackground
-
All working perfectly.
A huge thank you to Robert and the team - I LOVE this distro!! Nothing else even comes close! :D
-
The symlinks could be updated (no fgconsole link)
-
I did notice one thing - on booting, my preferred background didn't come up, just black screen. Invoking the wallpaper button worked as expected, but on next boot it was back to the black screen again.
[edit] the hsetroot statement in .setbackground has an -image argument which is not recognised.
-
Another step forward. Thanks to all involved.
Just curious as to why there are three "/sbin/udevd --daemon" processes running after bootup.
-
I did notice one thing - on booting, my preferred background didn't come up, just black screen. Invoking the wallpaper button worked as expected, but on next boot it was back to the black screen again.
[edit] the hsetroot statement in .setbackground has an -image argument which is not recognised.
Since .setbackground is in home dir and -image has been replaced with -fill, then once set via Wallpaper or edit and a backup is performed, should be OK. -image should not return unless from existing backup.
I should mention this in files that have changed.
-
I did notice one thing - on booting, my preferred background didn't come up, just black screen. Invoking the wallpaper button worked as expected, but on next boot it was back to the black screen again.
[edit] the hsetroot statement in .setbackground has an -image argument which is not recognised.
Since .setbackground is in home dir and -image has been replaced with -fill, then once set via Wallpaper or edit and a backup is performed, should be OK. -image should not return unless from existing backup.
I should mention this in files that have changed.
This is getting interesting... I do have persistent /home but am not backing it up, so .setbackground is not backed up or restored. I thought it would remain as is for the next boot but somehow it reverts... is it being overwritten freshly each time?
-
This is getting interesting... I do have persistent /home but am not backing it up, so .setbackground is not backed up or restored. I thought it would remain as is for the next boot but somehow it reverts... is it being overwritten freshly each time?
Check if there is a leftover mydata.tgz somewhere that is writing over your persistent /home.
-
No it's not that. I found the reason - in .xsession, the statement
setbackground image /opt/backgrounds/"$BACKGROUND"
results in the image being written into the .setbackground on each boot. If I change image to full, it works over boots.
-
Correct. You must be using a boot option to set background. Good find. Thanks.
-
Thank you to the Core team for now including VI editing mode in BusyBox. I now need to get used to the fact that it's available.
I did some more of my "poking around" with this RC and I'd like to raise a few other points. As typical for me I was booting from a "plain" ISO file, no persistence and without any backup (i.e. "cloud mode"):
(1) In addition to 'fgconsole' there are a couple of other BusyBox applets that don't appear to have a symbolic link:tc@box:~$ busybox | sed '1,/functions:$/d' \
> | tr -d ' \t\n' | tr ',' '\n' | while read F ; do
> L=$(which $F)
> T=$(ls -l $L 2> /dev/null | sed -e 's#.* -> ##' -e 's#.*/##')
> [ -z "$L" ] && echo "no softlink for $F"
> [ -n "$L" ] && [ "$T" != "busybox" ] && echo "$L not using busybox"
> done
no softlink for chrt
no softlink for dnsdomainname
no softlink for dumpleases
no softlink for fgconsole
no softlink for linuxrc
I wonder if those are intended to be "hidden", or to which degree their appearance is a bug of the BusyBox build process.
(2) There are still cases of applications that are not getting represented in '~/.wmx/Applications' (e.g. 'midori', 'shiretoko', ...). Looking a bit closer into it lead me to '/usr/bin/flwm_topside_makemenu' where I changed writeFLWMitem "$FREEDESK" to writeFLWMitem "${FREEDESK}/${1}.desktop" This seem to have fixed it for me.
(3) The issue with "% options from freedesktop Exec elements" has also an impact on files in '~/.wmx/Applications'. I guess applying the change done for '/usr/bin/wbar_icon_upd.sh' to '/usr/bin/flwm_topside_makemenu' should fix it.
-
Thanks for the feedback! Corrected for 2.11 final.
-
Small Appbrowser cosmetics;
Trying to install extension already downloaded with more than one dot in the name like graphics-2.6.29.1-tinycore.tcz status message is
graphics-2 is already downloaded!
instead of
graphics-2.6.29.1-tinycore is already downloaded!
-
Linuxrc shouldn't have a symlink (it just calls init anyway), but the others should.
-
I am confused... I can't lsusb, it reports lsusb not found... I'm sure I used this before?
-
I am confused... I can't lsusb, it reports lsusb not found... I'm sure I used this before?
Install usb-utils.tcz, it is not in the base.
-
Thanks, the other time I used it, usb-utils must have been mounted. I thought it had something to do with the new busybox which lists lsusb as a new applet.
-
They are not included in our config, because they are fairly useless to users.
They can't take advantage of the id databases, only print the id numbers. And that data is already available in /proc.
-
Small Appbrowser cosmetics;
Trying to install extension already downloaded with more than one dot in the name like graphics-2.6.29.1-tinycore.tcz status message is
graphics-2 is already downloaded!
instead of
graphics-2.6.29.1-tinycore is already downloaded!
Fixed! Thanks for the report.
-
I don't know who made the /usr/share/pixmaps/power.png icon and I don't want to insult anybody, but could I suggest a replacement for it? I made an exit icon for TC (attached) and I think it looks better than the current one. But that's just my opinion. Thanks.
-
No copy/paste in Appbrowser :( I just wanted to visit a WEB listed in the info file.
-
No plans to add the bulk of editor capabilities to Appbrowser.
As a work around you could always deal with the currently available local copy of the .info file, as appbrowser quite simply loads up such file for its display.
-
No plans to add the bulk of editor capabilities to Appbrowser.
As a work around you could always deal with the currently available local copy of the .info file, as appbrowser quite simply loads up such file for its display.
Why not remove the line:
status_out->deactivate();It's an output box, so one can not change the contents of it, and a quick test shows that one can copy from an active Fl_Output. Small change, huge improvement in usability.
Also since I'm posting here, what are the chances of getting a more useful mnttool included in the base? All I'm really asking for is a change in the way the info is displayed. I've already made the changes I need to make mnttool useful to me, but it would be nice for it be part of the base. My mnttool is only 1KB bigger than the one in base anyway. See http://forum.tinycorelinux.net/index.php?topic=5870.msg31197 (http://forum.tinycorelinux.net/index.php?topic=5870.msg31197)
-
hello everybody,
thnx for all the improvements done to TC.
@roberts
please can you consider these suggestions please:
[Appbrowser]
1- will it be feasable to add the possibility to download straight from appbrowser the 'latest TC's distribution files, either release or final (reason is appbrwser is here from the start, and it's a point-and-click, so no need to any other app/utility to achieve this).
2- Is it possible to homogenize the colors used as visual helpers, (ie Red-Orange-Green):
like using red when there is an error, orange/yellow when action is going on, and finally green when everything went OK? (so when applied to appbrowser, appbrowser starts with orange, keep the color orange as long as it's still processing - this can half replace the need to have a progress bar-, and finally color turns to red or green (instead of the actual yellow) according to the result.
this will lead to simplify things as in 'mnttool' as an example:
[mnttool]
switch the buttons:
- the upper one keeps the same behavior, ie to go to the next drive to mount ( this button can be splitted to two buttons : previous-next )
- the lower button will show the drive name on a RED background, and toggles to GREEN if and when mounted, keeping its status to the next toggle.
So no more need to show the words 'mounted/unmounted, anymore, specially that if we are using this utility is effectivelly is to mount and unmount drives, no need to read cause colors are faster to provide the meaning.
@althalus
this simplification can be applied to your mnttool.
I think one button is sufficient for all three needs from this tool: show a label, reflect a status info and provide action. (this will reduce the size of the dialog too).
[default keymap]
Is it possible to use 'us-acentos.kmap' as the default one?
thank you
-
Keep in mind that all non-current RC issues are not appropriate for threads in this section. Please use a suitable section to continue discussion.
-
I don't know who made the /usr/share/pixmaps/power.png icon and I don't want to insult anybody, but could I suggest a replacement for it? I made an exit icon for TC (attached) and I think it looks better than the current one. But that's just my opinion. Thanks.
And smaller in size too. Thanks for your effort. Will be in next cut.
-
Probably issue I noticed has nothing to do with the core but rather with extensions, but since it is RC forum I think this is the right place to report...
What I am experiencing (after many repetitive tests) is that with Hackedbox, after loading Xorg (which is necessary for resolution) if Chromium is installed (or sometimes Firefox), it messes up the Wbar, effectively making it useless and necessitating reboot...
Steps to re-create:
1. Boot TC
2. Install Xorg
3. Install Hackedbox
4. CTRL+ALT+Backspace
5. startx
6. Install Chromium (or Firefox, depending on Hackedbox theme)
After this the Wbar is quite messed up to the point of useless if you try to start Chromium of Firefox.
It is possible it might be specific to my hardware but at this point it does not look like it...
This problem does not happen with Openbox.
-
I can confirm the hackedbox problem but it can be reproduced with Xvesa ie a clean TC and hackedbox. It has to do with the background fake transparency of wbar but is not a problem with other WMs.
It is also not limited to tc2.11rc3.
-
:) The problems I experienced before in RC1 and RC2 are almost gone.
1. VirtualBox folder sharing with Windows - OK
2. Installing ("installing"= selecting the application tcz in the application browser, clicking "install" and wait for the downloading and installation of all dependencies and the application itself) applications are achieved until completion without interruptions
Remaining stuff which I don't know if are meant to stay as an option of the developers and community:
3. Some applications, after being installed ("installing"= selecting the application tcz in the application browser, clicking "install" and waiting for the download and installation of all dependencies and the application itself), are shown in the Applications menu (e.g. XFE, XFW, XFI, XFV) while others don't (e.g. Abiword, Shiretoko, Midori), despite, for the later ones, their icons being displayed in the dock bar. I got this around by putting the later ones as "On Demand" (I suppose I don't need to explain how I did this), which even improved the boot speed without sacrificing to much the starting speed of the applications.
4. In live mode, with 400 MB of RAM allowed for the VB virtual machine, I installed the gnome icon themes (as recommended) and epiphany (again, "installation= ...."), which didn't show nor in the Applications menu nor in the dock bar, and when I tried to run it from the terminal (by writing "epiphany" at the terminal prompt and waiting for it to run), I got:
- 3 lines in terminal displaying each the same next text:
"Xlib: extension "Generic Event Extension" missing on display ":0.="
- a pop up window displays:
as Title: Could not start Gnome Web Browser
as explaining text: Startup failed because of the following error: Failed to create directory "/home/tc/gnome2/epiphany"
That's all.
Meanpt
-
Following the report from meanpt I'd like to add my 2 cents ...
I believe that the 3. point reported is the same as in reply #10, point (2). And I think Robert has made a change for it already.
Furthermore WRT 'epiphany.tcz' I guess the menu and wbar problems are a consequence from the fact that the 'epiphany.desktop' file doesn't contain an 'X-FullPathIcon' entry. I had a bit of a look over some other extensions and it appears that there are quite a few to which this also applies. I assume that there will be a fuller migration of all extensions as time progresses.
Another point is the (already know) fact that 'webkit.tcz' (which 'epiphany.tcz' depends on) is currently "broken" due to the rebuild of 'icu.tcz'. In my test I therefore did not even get as far as seeing a window pop up.
-
It has already been requested to post freedesktop extension related issues in a different thread.
http://forum.tinycorelinux.net/index.php?topic=5800.msg30845#msg30845
But note too, that while we were implementing the freedesktop standard, both in base and extensions, a last minute change request occurred. So please be patient, as extensions are updated. Check if a newer version of the extension is already posted. If you are still having an issue then please post here:
http://forum.tinycorelinux.net/index.php?topic=5810.0
In 2.11 it is not mandatory to have freedesktop items, but if such exist, they need to be compliant as Jason has posted, and such items trump the older jwm/wbar specs. 2.11 will still support our existing jwm/wbar menu/icon specs to be backward compatible with the 2.x series. In the 3.x series we will no longer be supporting jwm/wbar as menu/icon specifications.
-
Maro and roberts,
Thanks for the feed-back. As a mere user and pretty newbie to Linux I only wish to report what, as a user, I found confusing in the new release and seemed to not work as "expected", in relation to what I was used with the distro. I know there is a wiki, FAQ an other documention but already gave up using them as much as before, cause they have not been updated, including some critical tools even for a user, e.g. Application Browser and Control Panel, as well as the ... well ... historical behaviour of the graphical environment. And this is the core reason for posting here, this is, the basic environment is not behaving as expected and I do not know whether this is "normal" or not. This question is: what should I expect for the final 2.11 to be regarding the way menus and the bar icons will behave.
And I do this because in some way we all (have reasons to and) do care about it. But, of course, anything regarding applications will be reported in the due area of the forum.
Regarding webkit.tcz, seems that midori also depends on it and for the time being midori installed and is running fine. But on RC2, the installation of midori usually froze while webkit.tcz was being installed as a dependency.
By the way, is there a "cooking" or snapshot version of the RC3?
Regards,
Meanpt
-
In the 3.x series we will no longer be supporting jwm/wbar as menu/icon specifications.
Is it the plan to drop wbar? (I hope not.) Or do you intend to have scripts to populate the wbar config file from freedesktop entries?
-
Or do you intend to have scripts to populate the wbar config file from freedesktop entries?
This. Less work for extension creators (at least with things that have .desktop files), should make using other icon managers easier.
-
No plans to drop wbar. Like Curaga said, it will be even easier for extension makers.
Most applications now come with freedesktop items. So to support wbar and legacy window mangers all one needs to do is to add the X-FullPathIcon= line to an existing .desktop item. No need to learn the JWM menu format. No need to learn the wbar menu format. Legacy window manager menu and wbar icons will automatically populated as before.