Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on March 15, 2010, 03:23:59 PM
-
The Second Release Candidate of v2.10 (tinycore_2.10rc2.iso), is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates
tinycore_2.10rc2.iso
tinycore_2.10rc2.iso.md5.txt
Change log for Tiny Core v2.10
Release Candidate 1
* Updated Appbrowser - no popups - GUI redesign, added Status bar.
* Updated Appbrowser/tce-load - much improved recursion support.
* New hsetroot replaces Esetroot for improved logo png support.
* New background and logo.
* Updated Backgrounds/wallpaper for hsetroot support.
* Updated exittc to not call exitcheck, backup occurs within exittc.
* Added missing rule for mmc support.
* Added directory indicator for improved appsaudit "On Boot" selection.
* Updated tc-config PXE tftp http for onboot.lst support.
* Updated appsaudit/tce-audit to download dep to /tmp then move to tce dir.
* Removed unneeded libthread_db* from base.
* Removed full paths from cpanel.
Files that have changed that are likely in your backup:
/home/tc/.setbackground
Note: If you boot an existing system and get a black screen with no logo then
you need to:
cp /etc/skel/.setbackground /home/tc/.setbackground
then either exit to prompt and startx or type
./.setbackground
Release Candidate 2
* Deleted unneeded udev rules
* Fixed typo in setbackground for tile
* Major updates to tce-load for better recursion support.
* Updated appbrowser, added color to status area to indicate operations are complete.
* Updated logo image.
-
Hi Robert!
Tinycore 2.10rc2 seems just great. Good job!
Have fun making tinycore better and better,
meo
-
'Exit to prompt' in exittc doesn't work after Xorg-7.4.tcz installed, system has to be restarted. In other situations including Xorg running it works as expected.
-
'Exit to prompt' in exittc doesn't work after Xorg-7.4.tcz installed, system has to be restarted. In other situations including Xorg running it works as expected.
have u tried ctrl+atl+F1?
-
'Exit to prompt' in exittc doesn't work after Xorg-7.4.tcz installed, system has to be restarted. In other situations including Xorg running it works as expected.
have u tried ctrl+atl+F1?
Yes. It exits to prompt, but startx doesn't start X. After reboot Xorg starts and works as expected.
-
'Exit to prompt' in exittc doesn't work after Xorg-7.4.tcz installed, system has to be restarted. In other situations including Xorg running it works as expected.
have u tried ctrl+atl+F1?
Yes. It exits to prompt, but startx doesn't start X. After reboot Xorg starts and works as expected.
when u are at the propt u can kill Xorg
-
'Exit to prompt' in exittc doesn't work after Xorg-7.4.tcz installed, system has to be restarted. In other situations including Xorg running it works as expected.
have u tried ctrl+atl+F1?
Yes. It exits to prompt, but startx doesn't start X. After reboot Xorg starts and works as expected.
when u are at the propt u can kill Xorg
Yes, I can do many different thing.
It was not a question but a bug report for Robert.
-
Hi bmarcus!
You don't think that the problem is caused by the Xorg extension? I've had similar problems before with the Xorg extension.
Have fun scrutinizing tinycore,
meo
-
Hi bmarcus!
You don't think that the problem is caused by the Xorg extension? I've had similar problems before with the Xorg extension.
Have fun scrutinizing tinycore,
meo
Meo@
Maybe Xorg, do not know. I did not check it with 2.9 or 2.8.1 but it was working a while ago. In 2.10 exittc is changed, this is why I reported the observationhere.
-
Appbrowser status line shows '...tcz OK' with the previous downloaded extension name while downloading next. Showing '...tcz download in progress' for the current extension would be more informative; display 'OK' when all download finished only.
BTW, I like the yellow highlight at the end :)
-
I like the appbrowser update as well.
Wishlist:
However on larger downloads it would be nice to see a progress meter.
-
However on larger downloads it would be nice to see a progress meter.
Next to your wish. Maybe in 2.11 :) There are some crucial new features in 2.10 so would be good to see final now.
-
Supporting alternate X servers have not changed recently.
The major changes occured in v1.3 and then slightly in v2.3 see the announcemets and change log.
Trying to install Xorg from within and existing X, be Xvesa or Xfbdev, means you would have to:
1. Ctrl-Alt-Bksp to exit from Xvesa or Xfbdev
2. run xsetup.sh This will update your .xsession
3. startx
If you are lucky Xorg will run confless.
Typically, I must copy xorg.conf.vesa to xorg.conf before I can run Xorg
sudo cp /etc/X11/xorg.conf.vesa /etc/X11/xorg.conf
- or-
As instructed in the Xorg info file, run sudo Xorg -config
Either way, running Xorg is not always seamless.
-
Hi y'all!
I totally agree with curaga. It would be very nice to have a progress meter in the app browser, It would benefit especially those using old computers (like me) and perhaps can't use the computer during the download. I usually do other things and take a peek now and then to see if the download is ready. So I think it would be a good feature that would be most appreciated (at least by me).
Have fun making tinycore progress,
meo
-
Robert, my problem is not Xorg but exittc which doesn't exit to prompt. Simply nothing happens, system countinues to work as before. BTW, on my systems confless does the job, no configuration is need.
-
The startup script of Xorg changes /etc/sysconfig/Xserver which is used to indicate the current Xserver, the one that exittc to uses to exit from.
Typically, I do not try to install Xorg from within any other Xserver, instead, I exit to prompt and use
ab Xorg
Early versions of exittc used a shotgun approach and tried successively Xvesa, Xfbdev, and finally Xorg. But such approach limits and is specific to the above collection.
-
Wishlist:
However on larger downloads it would be nice to see a progress meter.
Perhaps not optimal, but if you have a terminal window open, you can see what's going on from the wget commands echoed.
Again wishlist, but some sort of indication of progress on apps audit (where there's no indication in a terminal window) and things might take a while would be good.
Edit: a bit hard to tell as my connection is so poor, but I would guess update/check for updates did not find anything in /tce/optional that needs updating, but there's no indication of this?
-
The startup script of Xorg changes /etc/sysconfig/Xserver which is used to indicate the current Xserver, the one that exittc to uses to exit from.
Thanks, it was my suspect as well but had no time to go into details. Just checked Xorg-7.4.info instructions and while not explicitely refers to "Exit to prompt' instructions are not very precise how to install and start using. It would be good to enhance a bit :)
I will do it with my WIKI article too.
-
When 'Install Local Extension' used '... alerady installed' status message highlighted with yellow background, while finished installation is white. It just reversed compared to installation from remote repository.
-
When 'Install Local Extension' used '... alerady installed' status message highlighted with yellow background, while finished installation is white. It just reversed compared to installation from remote repository.
I find that the yellow final status is also interesting in the 'Install Local Extension' but with white starting, so after a download with 'connect to repository' is necessary a white refresh from the status message for the next apps load.
-
I think the DEFAULT_BACKGROUND var in tc-config is now unused.
-
That is true. Removed.
Speaking of some cleanup...
Someone had mentioned jwmTheme in .xsession
[ -n "$THEME" ] && cp /opt/jwmThemes/"$THEME" .jwmrc-themeSince jwm is an extension this option should be noted in the jwm extension info file.
And while we are at it.
Both flit and watcher are both extensions, so...
[ $(which flit) ] && flit &
[ $(which watcher) ] && watcher -g +0-0 &
Should also be removed and noted in their respective info files.
I had left them in .xsession only as a convience and possible example of both testing existence and starting extension upon startuo of X.
But if we are cleaning up a single unused variable, then these extension references should be removed from .xsession.
-
Talking of cleanups: I guess '/etc/inittab-save' is another candidate for removal. Bye the way, this file indicates to me that some time ago multiple terminals were used (which could be selected by Ctrl-Alt-Fn). I wonder if it would make sense to have at least one or two additional terminals available. I know, I could create a changed '/etc/inittab' file (and e.g. re-master the initrd) to (hopefully) achieve this. I just curious what lead to the decision to drop all but one.
With regards to the removal of entries from '/etc/skel/.xsession': I'd suggest to not merely mention something in some info files, but ensure that the '/usr/local/tce.installed' start-up scripts are adding those entries into '${HOME}/.xsession'. For a moment I thought of '/root/.xsession' as well, but since root should typically not start a X server, I'll now consider this a silly idea.
-
Watcher info file edited.
-
I have problems with the new colors in the appbrowser, see attached screenshot
-
I have problems with the new colors in the appbrowser, see attached screenshot
Do you mean the status text?
-
yes
-
jwm & jwm-snapshot info files updated. flit info updated.
Extension references will be removed from .xsession as noted above.
-
for example:
cat .wmx/OnDemand/alsa
#!/bin/sh
[ -e /opt/.tce_dir ] || exit 1
read TCEDIR < /opt/.tce_dir
[ -e /usr/local/tce.installed/alsa ] || tce-load -i $TCEDIR/optional/alsa.tcz
[ $(which alsa) ] && alsa
last line should terminate with an &
-
We don't run everything backgrounded. When backgrounding is necessary or desired you can enter such when prompted for the binary.
-
why not?
-
I have already answered. But here is another point.
The next iteration of ondemand will use the menu as provided by the extension maker whenever available and will only prompt when none exists. Since the OnDemand items persist and are in your backup you are free to do and run your system as desired. The ondemand script is just a convience to making these shortcuts.
-
6541 tc /bin/sh /home/tc/.wmx/OnDemand/lxappearance
6586 root [loop117]
6603 root [loop118]
6608 tc lxappearance
6610 tc lxappearance demo 31457306 /tmp/gtkrc-2.0-YnCXUk sorry, what's the point of process n° 6541?
-
I think you are confusing backgrounding & with exec.
exec is in the next iteration.of the fully automated ondemand.convience script for flwm users.