Tiny Core Linux

Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on April 23, 2010, 11:38:16 AM

Title: tinycore_v2.11rc2
Post by: roberts on April 23, 2010, 11:38:16 AM
The Second Release Candidate of v2.11 (tinycore_2.11rc2.iso), is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates

tinycore_2.11rc2.iso
tinycore_2.11rc2.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
Title: Re: tinycore_v2.11rc2
Post by: jur on April 23, 2010, 04:07:18 PM
I'm having trouble understanding .X.d:

I renamed my .xsession so tc wouldn't find it. After booting I found a newly created .xsession, with a new .X.d statement at the end, but no .X.d directory - searching didn't find it. Where is it located? I don't see in in /~...
Title: Re: tinycore_v2.11rc2
Post by: maro on April 23, 2010, 04:25:18 PM
Good stuff Robert (+ Core team)!!

I've just re-tested the "funny" behaviour (http://forum.tinycorelinux.net/index.php?topic=5800.msg30948#msg30948) of 'appbrowser', and can report that this appears to be now fixed.

It's nice to see a new version of BusyBox. I was wondering whether it could be compiled with the VI editing mode (http://forum.tinycorelinux.net/index.php?topic=4909.0) enabled. Another question would to to potentially include new applets like lspci and lsusb.

@jur: Did you do ls -la ~/.X.d? I at least "see" this directory and the 'wbar' file (which is now part of the initrd in the form of '/etc/skel/.X.d/wbar').
Title: Re: tinycore_v2.11rc2
Post by: bigpcman on April 23, 2010, 04:48:54 PM
Confirmed Opera10 now installs with wbar icon present.
Title: Re: tinycore_v2.11rc2
Post by: roberts on April 23, 2010, 07:17:01 PM
Good stuff Robert (+ Core team)!!

I've just re-tested the "funny" behaviour (http://forum.tinycorelinux.net/index.php?topic=5800.msg30948#msg30948) of 'appbrowser', and can report that this appears to be now fixed.

It's nice to see a new version of BusyBox. I was wondering whether it could be compiled with the VI editing mode (http://forum.tinycorelinux.net/index.php?topic=4909.0) enabled. Another question would to to potentially include new applets like lspci and lsusb.

@jur: Did you do ls -la ~/.X.d? I at least "see" this directory and the 'wbar' file (which is now part of the initrd in the form of '/etc/skel/.X.d/wbar').

As I have been quite busy with the freedesktop implementation, I did not compile the new busybox. I will however pass along your request and see if it can be done for the next RC.
Title: Re: tinycore_v2.11rc2
Post by: tim2092008 on April 23, 2010, 08:57:12 PM
Ive ben around tinycore before version 2.2. Just waiting for my sound and wifi to work with a clean install. And it still does not work. At my house i can only access my neighbors internet wirelessy. So i cannot download extensions without wireless. It would be nice to have a page on this site that you can just download extensions and load then to a tiny core install usb or cd..doesnt matter. Ive ben waiting so loong to use tiny core and still can not.
Title: Re: tinycore_v2.11rc2
Post by: jur on April 23, 2010, 10:25:53 PM
@jur: Did you do ls -la ~/.X.d? I at least "see" this directory and the 'wbar' file (which is now part of the initrd in the form of '/etc/skel/.X.d/wbar').
Code: [Select]
tc@box:~$ ls -la ~/.X.d
ls: /home/tc/.X.d: No such file or directory
Title: Re: tinycore_v2.11rc2
Post by: gerald_clark on April 24, 2010, 12:21:20 AM
In appbrowser -> mirrors, you cannot edit the mirror URL at the bottom.
I use my own mirror, and I have to edit tcemirror manually.
Title: Re: tinycore_v2.11rc2
Post by: maro on April 24, 2010, 12:34:32 AM
@tim2092008: I don't think that this is a suitable thread for you to get help with your wireless card problem. I'd suggest you open a new one and specify exactly your hardware (using the 'lspci' command from the 'pci-utils.tcz' extension might allow you to provide us with some details).
Title: Re: tinycore_v2.11rc2
Post by: sci_fi on April 24, 2010, 04:23:33 AM
Good Morning:

Two questions/comments re rc2

1. I load all my extensions into RAM. While loading extensions with rc2 I get an error message for each extension:

 Error: Could not umount /mnt/test Permission denied.

I then find many (apparently one per extension) "/mnt/test" mounted.

I did not change anything from rc1 so something is different here.


2. I also do not understand .X.d/
The directory is there containing wbar file with one line relating to wbar. My .xsession file is there and everything seems to work as before. To test,  I renamed .xsession and restarted x. I then got a new .xsession fine which was fine except my own customizations (starting xscreensaver) are not present (as expected).

Should I copy my working .xsession into .X.d/wbar and delete .xsession  going forward. Is something else required?

Thanks and best regards,

sci_fi
Title: Re: tinycore_v2.11rc2
Post by: curaga on April 24, 2010, 04:55:51 AM
Good Morning:

Two questions/comments re rc2

1. I load all my extensions into RAM. While loading extensions with rc2 I get an error message for each extension:

 Error: Could not umount /mnt/test Permission denied.

I then find many (apparently one per extension) "/mnt/test" mounted.

I did not change anything from rc1 so something is different here.

Good find. This is from the busybox update, now it behaves more properly like the GNU versions, and we had depended on the old behavior.

The point being that random loop mounts cannot be unmounted by users. Adding sudo there should fix it.

Quote
--- tce-load   2010-04-24 14:49:42.000000000 +0300
+++ tce-load.new   2010-04-24 14:53:45.000000000 +0300
@@ -55,7 +55,7 @@
          yes n | sudo cp -ai /mnt/test/. / 2>/dev/null
          [ -d /mnt/test/usr/local/lib/modules ] && MODULES=TRUE
       fi
-      busybox umount -d /mnt/test
+      sudo busybox umount -d /mnt/test
    fi
 }
 

Quote
2. I also do not understand .X.d/
The directory is there containing wbar file with one line relating to wbar. My .xsession file is there and everything seems to work as before. To test,  I renamed .xsession and restarted x. I then got a new .xsession fine which was fine except my own customizations (starting xscreensaver) are not present (as expected).

Should I copy my working .xsession into .X.d/wbar and delete .xsession  going forward. Is something else required?

Thanks and best regards,

sci_fi

You can put new files there for autostarting with X. For example you could create a new file there to start xscreensaver, and so not need to change anything in .xsession between core updates.
Title: Re: tinycore_v2.11rc2
Post by: jur on April 24, 2010, 05:09:59 AM
Any idea why the /.X.d is not present in my persistent /home? wbar does load despite its absence.
Title: Re: tinycore_v2.11rc2
Post by: curaga on April 24, 2010, 05:18:04 AM
If you already had persistent home, it is not touched during updates. You'll need to manually check against /etc/skel if you wish to change something.
Title: Re: tinycore_v2.11rc2
Post by: jur on April 24, 2010, 08:56:57 AM
If you already had persistent home, it is not touched during updates. You'll need to manually check against /etc/skel if you wish to change something.
But when I renamed .xsession, a fresh one WAS copied across to my persistent /home. So why not /.X.d?
Title: Re: tinycore_v2.11rc2
Post by: curaga on April 24, 2010, 09:02:44 AM
That would be a special case, if .xsession does not exist, it's restored by xsetup (which is run by startx if .xsession is not there). More bullet-proof X that way ;)
Title: Re: tinycore_v2.11rc2
Post by: jur on April 24, 2010, 09:38:57 AM
To make upgrading from previous versions smoother, may I suggest /.X.d also be included in xsetup if it does not exist?
Title: tinycore_v2.11rc2: experienced shortcomings
Post by: meanpt on April 24, 2010, 05:37:46 PM

Hi,

1. installed applications are not shown under the Applications heading menu
2. midori did not installed correctly, despite the icon being shown in the dock
3. shiretoko installed on the third attempt
4. Vboxadditions is not working - when trying file sharing with the Windows system with the shared vbox folder with "mount .-t vboxsf -rw windowsSystemFileFolder TCDirectory, keeps responding "No such device". Currently using VBox 3.1.4

Regards,

Mean
Title: Re: tinycore_v2.11rc2: experienced shortcomings
Post by: roberts on April 24, 2010, 06:23:25 PM

Hi,

1. installed applications are not shown under the Applications heading menu
2. midori did not installed correctly, despite the icon being shown in the dock
3. shiretoko installed on the third attempt
4. Vboxadditions is not working - when trying file sharing with the Windows system with the shared vbox folder with "mount .-t vboxsf -rw windowsSystemFileFolder TCDirectory, keeps responding "No such device". Currently using VBox 3.1.4

Regards,

Mean
What does showbootcodes display?
Title: Re: tinycore_v2.11rc2
Post by: maro on April 24, 2010, 09:04:05 PM
As I was surprised to read
Quote
4. Vboxadditions is not working
I did a re-test with TC 2.11rc2 along the lines of what I did here (http://forum.tinycorelinux.net/index.php?topic=4831.msg26049#msg26049) and have to report that all mounting attempts appeared to have worked without an issue for me. Could it be that the required module was not loaded (with sudo modprobe vboxvfs) as mentioned in the .info file?

I'm also not quite sure what is supposed to be wrong with 'midori': The installation works fine for me and the application is usable. The only (in my view entirely cosmetic) issue might be the fact that at the very first start a bit a garbled message might appear ("Error - %u    The page '%u' couldn't be loaded.    URL cannot be shown"). It appears that this happens when midori gets started via the wbar icon, and does not happen when started from the command line. A quick look into '/usr/local/tce.wbar' shows that indeed 'c: exec midori %u' appears to be the "culprit" here. I guess that OTOH might be a consequence of the 'Exec=midori %u' entry in '/usr/local/share/applications/midori.desktop'.

Likewise 'shiretoko' worked OK for my test. It's "just" fairly memory-hungry (ca. 23M downloaded extensions lead to ca. 50M extracted extensions). So running it on a system with only 128M would be pretty much pointless. But I fail to see what could be the issue re. TC 2.11rc2.

What I can confirm is the reported issue about applications not "showing up" via '~/.wmx/Applications'

I believe I've spotted one yet un-reported issue: the ownership of the files in '/home/tc/.wmx/SystemTools' is 'root:staff' even though a command in '/usr/bin/flwm_topside_initmenu' (i.e. chown tc.staff -R /home/"$USER"/.wmx) tries to change this. I guess that command might have to be moved after the loop over the files in '/usr/share/applications/tinycore-*' to have the desired effect.
Title: Re: tinycore_v2.11rc2
Post by: roberts on April 24, 2010, 10:14:23 PM
Quote
I believe I've spotted one yet un-reported issue: the ownership of the files in '/home/tc/.wmx/SystemTools' is 'root:staff' even though a command in '/usr/bin/flwm_topside_initmenu' (i.e. chown tc.staff -R /home/"$USER"/.wmx) tries to change this. I guess that command might have to be moved after the loop over the files in '/usr/share/applications/tinycore-*' to have the desired effect.

I am curious how you are getting root.staff on System Tools.

Using base norestore the permissions are OK. In fact I now recommend, as posted in the announcement, that .xfiletool.lst contain home/tc/.wmx therefore my .wmx is recreated upon each boot. I cannot reproduce the permission issue. System Tools should have no effect on Applications. I have tested with typically home in ram (base norestore) and with persistent home on ext2 filesystem.

Have you changed .xfiletool.lst to include home/tc/.wmx ?

What happens if you exit X and
rm -rf .wmx and then startx

Check permissions.

What filesystem is hosting /home ?

For user, meanpt, I again ask to see the output of showbootcodes, as I would like to know what window manager you are using and what  persistent options if any.

Title: Re: tinycore_v2.11rc2
Post by: roberts on April 24, 2010, 10:28:27 PM
Quote
I'm also not quite sure what is supposed to be wrong with 'midori': The installation works fine for me and the application is usable. The only (in my view entirely cosmetic) issue might be the fact that at the very first start a bit a garbled message might appear ("Error - %u    The page '%u' couldn't be loaded.    URL cannot be shown"). It appears that this happens when midori gets started via the wbar icon, and does not happen when started from the command line. A quick look into '/usr/local/tce.wbar' shows that indeed 'c: exec midori %u' appears to be the "culprit" here. I guess that OTOH might be a consequence of the 'Exec=midori %u' entry in '/usr/local/share/applications/midori.desktop'.

Yes, I will have to stip and trailing % options for wbar. I was not aware of such data, Good find. Thanks!
Title: Re: tinycore_v2.11rc2
Post by: maro on April 25, 2010, 12:45:57 AM
Robert, the 'root:staff' appears for me when booting from the "plain" TC 2.11rc2 ISO image. I don't use any form of persistence, have no backup, and no extensions whatsoever. As I'm using TC so far more as a study object I operate most of the time in "cloud" mode. My private TCZ mirror allows me to reasonably quickly test a variety of test cases without having to consider the impact of previous activities. Most of the time I just boot a new VM (using VirtualBox or QEMU) and TC is better than any other distribution for this due to the minimalistic concept.

The ownership of 'root:staff' is also appearing after removing '~/.wmx' and a restart of X. I've even done a re-boot just with the plain ISO, and used boot codes 'base norestore' (which I guess is the same thing twice over) and the ownership of those files is again 'root:staff'.

I tend to agree that the (initial) ownership of those files is probably not critical, since I guess in the case of a persistent '/home' after the next re-boot the 'chown' command will change things to 'tc:staff'.

The way I explain the finding to myself is: In '/usr/bin/startx' the command sequence of [ `which "$DESKTOP"_initmenu` ] && sudo "$DESKTOP"_initmenu  leads to the execution of '/usr/bin/flwm_topside_initmenu' in which the following code snippet can be found:
    chown tc.staff -R /home/"$USER"/.wmx
    TARGET="$SYSMENU"
    for D in `ls /usr/share/applications/tinycore-*`; do
       writeFLWMitem "$D"
    done
At the first run of this code block on a "plain" system there are no files in '~/.wmx/SystemTools' and the 'chown' command has no effect. After the loop has run the files in '~/.wmx/SystemTools' have been created, but due to the execution as super-user the files are owned by 'root'. Moving the 'chown' command after the loop should lead to the desired outcome.
Title: Re: tinycore_v2.11rc2
Post by: roberts on April 25, 2010, 07:00:15 AM
No problem to change the code. I just like to reproduce the reported condition so to better understand the actual envirments in which it occurs.
Title: Re: tinycore_v2.11rc2: experienced shortcomings
Post by: meanpt on April 25, 2010, 07:08:26 AM

Hi,

1. installed applications are not shown under the Applications heading menu
2. midori did not installed correctly, despite the icon being shown in the dock
3. shiretoko installed on the third attempt
4. Vboxadditions is not working - when trying file sharing with the Windows system with the shared vbox folder with "mount .-t vboxsf -rw windowsSystemFileFolder TCDirectory, keeps responding "No such device". Currently using VBox 3.1.4

Regards,

Mean
What does showbootcodes display?

a) Bootcodes

Showbootcodes on terminal only displays "quiet", although during the booting I can see the "kernel /boot/bzImage quiet" and "initrd /boot/tinycore.gz" lines.

b) wm
I'm using the default wm/desktop - suppose it's flwm ...


c) Other things / Live session
During the a live session (this one, from where I'm posting) could install shiretoko which was shown on the dock but not on the Applications menu label. But if I install Xfe.tcz, the later is both shown on the dock and listed in the Applications menu.
Title: Re: tinycore_v2.11rc2
Post by: meanpt on April 27, 2010, 02:29:34 AM
Hi

I installed TC again on the virtual hd and I'm having more trouble in downloading and installing. Moreover, when even not choosing to backup, it stills backup something.

I tried to download firefox, leave it during the night to download it and it froze, despite letting it installing all night.

Tried to download shiretoko, it seems it was installed (shiretoko.tcz ok under the yellow background) but when clicking on the docked icon nothing happened. Then tried to call it from the terminal and it was "not found".

Tried to install epiphany, it froze somwhere and I pushed again the Install button. Then, installation  seemed to continue and I got a "epiphany.tcz ok" but didn[t get the docked icon. Again, when calling epiphany in the terminal, it was "not found".

Unthicked the back-up for the logout, logged out and after booting again I found epiphany.tcz was still available in "local". When  tried to mount it, there was a dependency missing (expat2.tcz. not found).

The awkward is that I can install and run shiretoko as well as firefox in live mode but usually on a second or third installation trial.


Title: Re: tinycore_v2.11rc2
Post by: maro on April 27, 2010, 07:34:59 PM
@meanpt: You are reporting problems with the "installation" that are a bit difficult to investigate. It is (at least for myself) not easy to differentiate what is a "download" (e.g. networking) and what is an "installation" issue.

May I suggest that you use the command line next time and post all messages of your failed attempts back here. The command to use would be tce-load -wi shiretoko (or choose any other extension name instead).
Title: Re: tinycore_v2.11rc2
Post by: althalus on April 27, 2010, 10:27:52 PM
Tried to install epiphany, it froze somwhere and I pushed again the Install button. Then, installation  seemed to continue and I got a "epiphany.tcz ok" but didn[t get the docked icon. Again, when calling epiphany in the terminal, it was "not found".

I'll let others try and assist you with your other problems, however this particular one is a problem I've been meaning to mention myself.

Start downloading an extension, click Install or Download a second time before the first operation has finished, and you end up with missing dependencies. I think this is caused by recursive dependencies.

A.tcz depends on B.tcz depends on C.tcz.

The pattern SEEMS to go like this: Start downloading A.tcz, it realises it needs B.tcz. Installation of B.tcz is interrupted, and installation of A.tcz starts again. It thinks B.tcz is already there, and fails to check that B.tcz is missing one of IT's dependencies.


And as maro pointed out, it is always helpful for people to be able to see the entire error message.