Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on January 29, 2011, 11:58:04 AM
-
The First Release Candidate of Tiny Core v3.5 is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates
tinycore_3.5rc1.iso
tinycore_3.5rc1.iso.md5.txt
Change log for Tiny Core v3.5:
* Clean up of tce-audit 'delete' spurious messages.
* New tce-remove support for tce-audit/appsaudit.
* Update wbar_rm_icon to support tce-remove.
* Updated appsaudit to support removing ondemand uninstalled extensions without rebooting.
* Updated appsaudit, added highlight on FAILED md5 checking.
* Moved thinkpad_acpi.ko from base to extension.
* Updated tc-config crond call and removed duplicate crond script.
* Updated wbarconf added many more bar position options.
* Updated services to support nested daemon starting.
* Updated appbrowser moved Mirror Selection to support mirror.tcz extension.
* Updated busybox 1.18.1 plus patches.
* Scripts adjusted to remove extra spaces to reduce size.
* fsck replaced with busybox fsck
* zsync upgraded to 0.6.2.
* updated fluff file manager to 0.8.9
-
when is tce-remove called apart from shutdown?
-
Automatically upon exit from appsaudit.
Or if only using CLI tce-audit then when specified.
Example:
tce-load -wo abiword
tce-audit updatedeps
tce-audit delete abiword
tce-audit remove
-
There is a typo in tinycore-filemgr.desktop
Categories=Utilities;
where Utilities is an invalid category. Correct definition:
Categories=Utility;
I advise to add this entry:
OnlyShowIn=Old;
This would hide fluff in DE's like LXDE or Xfce as they are packed with their own file manager already but would leave native TC environment unchanged.
-
Agreed. Adjustments made. Thanks.
-
tce-remove removes only the non installed apps, but if an app is copied to fs it can be deleted
-
Scatter mode is not on demand. So of course not.
-
In a .desktop file you can define a terminal application which is executed in the default terminal window. For Midnight Commander it looks like
Exec=mc
Terminal=true
Type=Application
It worsk in Xfce, but not honored by TC and while it appears on WBAR not executed in a terminal so doesn't work. On the WBAR it must be executed as
aterm -e mc
However binding it to aterm is not a good solution as user may have changed to another terminal like urxvt due to UTF-8 environment. Proposal is to introduce the system wise terminal which defaults to aterm and can be changed by user or extension, and used on WBAR. It can be a text file for example
/etc/sysconfig/terminal
BTW, Terminal= requires a Boolean argument. Allowed values are 0, 1, true, false (lower case). However detecting it case insensitive would eliminate some further headackes.
-
Proposal is to introduce the system wise terminal which defaults to aterm and can be changed by user or extension, and used on WBAR. It can be a text file for example
/etc/sysconfig/terminal
If such a system wise terminal would be introduced, would such be without any impact in the case of concurrently using aterm(s) and VT(s)?
-
Of course base must be adjusted accordingly, for example terminal in the menu or on WBAR must start the proper terminal. It would work similarly as /etc/sysconfig/Xserver currently.
-
How about just pointing the "xterm" symlink to whatever terminal one uses? It's by default to aterm, but can be overridden by the startup script of any terminal extension.
It's the generic terminal name, and tried by just about any app that calls a terminal.
-
How about just pointing the "xterm" symlink to whatever terminal one uses? It's by default to aterm, but can be overridden by the startup script of any terminal extension.
It's the generic terminal name, and tried by just about any app that calls a terminal.
May work, but I'm not sure. A while ago testing UTF-8 setup I had some issues where application depended on terminal name, and the related environment variable BTW to set up its behavior but do not remember details. This has to be tested.
-
Scatter mode is not on demand. So of course not.
sorry?