Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: emninger on November 06, 2015, 03:32:22 PM
-
When i change something in ControlPanel > tcwbarconf the changes are instantanely effective but after the next reboot they disappear. How can i make them permanent?
TIA
-
They change a hidden file in your home dir, so do a backup.
-
They change a hidden file in your home dir, so do a backup.
I do on any shutdown/reboot a backup!
The involved hidden file is ".wbar" which in reality is a symlink to /usr/local/tce.icons. Might it be that way that the original file keeps its settings (since not included in the backup scheme) and there after the next restart "overrules" the changes in ".wbar"?
-
The settings are stored in ~/.wbarconf, and applied on reboot to the non-persistent tce.icons file.
-
The settings are stored in ~/.wbarconf, and applied on reboot to the non-persistent tce.icons file.
Turning back to this issue:$HOME/.wbarconf looks like this:
c: wbar --bpress --pos bottom --zoomf 2 --isize 32
Which seems to me the basic configuration (how wbar behaves).
.wbar is a symbolic link to /usr/local/tce.icons which looks like this:
# The Bar && Font && Font size (11)
i: /usr/local/share/wbar/osxbarback.png
t: /usr//share/fonts/luxisr/11
c: wbar --bpress --pos bottom --zoomf 2 --isize 32
i: /usr/local/share/pixmaps/exittc.png
t: Exit
c: exec exittc
i: /usr/local/share/pixmaps/editor.png
t: Editor
c: exec editor
i: /usr/local/share/pixmaps/cpanel.png
t: ControlPanel
c: exec cpanel
i: /usr/local/share/pixmaps/apps.png
t: Apps
c: exec apps
i: /usr/local/share/pixmaps/flrun.png
t: RunProgram
c: exec flrun
i: /usr/local/share/pixmaps/mnttool.png
t: MountTool
c: exec mnttool
i: /usr/local/share/pixmaps/xfe.png
t: Xfe
c: exec xfe
i: /usr/local/share/pixmaps/aterm.png
t: Terminal
c: exec aterm
i: /usr/local/share/pixmaps/ezremaster.png
t: ezremaster
c: exec ezremaster
i: /usr/local/share/pixmaps/firefox.png
t: firefox-ESR
c: exec /usr/local/firefox-ESR/firefox
i: /usr/local/share/pixmaps/firefox.png
t: firefox
c: exec /usr/local/firefox/firefox
i: /usr/local/share/pixmaps/galculator.png
t: galculator
c: exec /usr/local/bin/galculator
i: /usr/local/share/pixmaps/htop.png
t: Htop
c: exec aterm +tr +sb -T "Htop" -e htop
i: /usr/local/share/pixmaps/lxrandr.png
t: MonitorSettings
c: exec lxrandr
i: /usr/local/share/pixmaps/core.png
t: TC_Install
c: exec tc-install
i: /usr/local/share/icons/hicolor/48x48/apps/viewnior.png
t: Viewnior
c: exec viewnior
i: /usr/local/share/pixmaps/wifi.png
t: Wifi
c: exec cliorx sudo wifi.sh
i: /usr/local/share/icons/hicolor/24x24/apps/xarchiver.png
t: Xarchiver
c: exec xarchiver
i: /usr/local/share/icons/hicolor/64x64/apps/flaxpdf.png
t: FlaxPDF
c: exec flaxpdf
This seems to be the file, where the applications and respective icons which are shown in wbar are listed. And here go the changes made by tcwbarconf in the controlpanel. And this changes are NOT permanent. And yes, i do a backup of /home
-
I cannot reproduce on a clean install. The changes correctly persist.
-
Emninger need to start over clean.
The onboot.lst and .filetool.lst previously shown are a mess, causing many of the problems reported and yet to be reported.
-
Emninger need to start over clean.
The onboot.lst and .filetool.lst previously shown are a mess, causing many of the problems reported and yet to be reported.
I did.
But, i do NOT see, how to exclude e.g. /usr/local/etc/fonts from being backuped because otherwise i'd loose all settings i did in fontconfig (and other settings are also done there, or in /etc/ , which as far as i know cannot be transferred to $HOME .
Just a question: The existence of this 2 files:
$HOME/.wbar and $HOME/.wbarconf is correct?
And also, that .wbar is a symbolic link to /usr/local/tce.icons ?
-
Yes, and yes, but changes to wbar are stored in ~/.wbarconf and in wbar.lst in the tce directory.
-
Yes, and yes, but changes to wbar are stored in ~/.wbarconf and in wbar.lst in the tce directory.
So, ~/.wbarconf is a symbolic link pointing to wbar.lst? In which tce directory? /tmp/tce or /mnt/sda1/... ?
-
No. ~/.wbarconf is not a symlink.
look in /etc/sysconfig/tcedir for wbar.lst.
Are you sure /etc/sysconfig/tcedir points to persistent storage?
-
No. ~/.wbarconf is not a symlink.
Same here.
look in /etc/sysconfig/tcedir for wbar.lst.
Are you sure /etc/sysconfig/tcedir points to persistent storage?
1. There is no wbar.lst? Should i create one?
2. /etc/sysconfig/tcedir is a symlink to /mnt/sda1/tce
-
I suspect your tce directory permissions are wrong.
Do the following and post results:
ce
ls -la
-
tc@box:~$ ce
tc@box:/mnt/sdb1/tce$ ls -la
total 392
drwxrwxr-x 5 tc staff 4096 Nov 11 00:40 ./
drwxr-xr-x 6 root root 4096 Nov 11 00:05 ../
drwxrwxr-x 3 tc staff 4096 Nov 10 23:56 boot/
-rw-rw-r-- 1 tc staff 0 Oct 27 15:37 copy2fs.lst
-rw-rw---- 1 tc staff 0 Oct 26 23:22 firstrun
-rw-rw-r-- 1 tc staff 332016 Oct 27 01:45 mydata.tgz
-rw-rw-r-- 1 tc staff 2003 Nov 11 07:07 onboot.lst
drwxrwxr-x 2 tc staff 4096 Nov 11 00:38 ondemand/
drwxrwxr-x 2 tc staff 40960 Nov 11 00:39 optional/
-rw-rw-r-- 1 tc staff 155 Nov 11 15:32 xwbar.lst
-
OK, xwbar.lst
-
OK, xwbar.lst
Sorry, i do not understand ... :-\
-
The file is xwbar.lst, and you have it.
-
The file is xwbar.lst, and you have it.
But, as far as i understand xwbar.lst contains the items that has been excluded from the wbar. Not those included - at least on this machine it works in that way.
Remains, that ~/.wbarconf contains only basic settings: c: wbar --bpress --pos bottom --zoomf 2 --isize 32 but nothing about the apps included to it. Those values are in /usr/local/tce.icons wherefrom controlpanel > tcWbarConf also seems to read (and write) them.
So, one way to make changes permanent would be to include /usr/local/tce.icons into the backup list (?)
Or, when i delete the symbolic link to tce.icons (~/.wbar) and migrate the settings (by hand) to ~.wbarconf tcWbarConf, then, would read from that file?
-
What changes do you want to make permanent?
-
ControlPanel > tcWbarConf (changes of the order of appearance, excluding also some)
-
The config for WBar (/usr/local/tce.icons holds entries for icons) gets rewritten based on installed apps.
Only the basic settings (position, size, etc.) are stored in ~/.wbarconf .
If you want to add custom icons, you can either abuse the OnDemand feature by adding scripts and icons to /etc/sysconfig/tcedir/ondemand or create *.desktop files at /usr/local/share/applications . The latter would need to be added to the backup or contained in an extension.
-
Thanks for your answer. Frankly, i only want to change the order of the apps in wbar (no new icons). With the *.desktop option i'm pretty familar ;)
In this context - i do not want to open a new thread on it:
I'm using TCL with fluxbox (which is fine for me and i'm really familiar with). I reflected about installing menumaker or, even better. xdgmenumaker (which is made by gapan on git) but now, i see, the TCL fluxbox automatically updates the program starter by including /usr/local/tce.fluxbox) and /usr/local/tce.fluxbox . Now, just out of curiousity, i'd like to understand HOW TCL builds that files (because as far as i see, they are continously rebuilt along with changing installed programs either onboot or ondemand).
Thanks!
-
In order to understand how those icons are created, you should study Core's scripts (/usr/bin/ondemand , /usr/bin/tce-* and /usr/local/bin/fluxbox_*).
You could use the boot code noicons to prevent WBar from being automatically populated with new icons and start WBar manually with a different config file.
-
Hi emninger
There are also a bunch of wbar* files:
tc@box:~/guilib/grabber/grabber-1.1$ ls /usr/bin/wbar*
/usr/bin/wbar /usr/bin/wbar_mv_icon /usr/bin/wbar_setup.sh /usr/bin/wbarconf
/usr/bin/wbar.sh /usr/bin/wbar_rm_icon /usr/bin/wbar_update.sh
tc@box:~/guilib/grabber/grabber-1.1$
-
In order to understand how those icons are created, you should study Core's scripts (/usr/bin/ondemand , /usr/bin/tce-* and /usr/local/bin/fluxbox_*).
You could use the boot code noicons to prevent WBar from being automatically populated with new icons and start WBar manually with a different config file.
Thanks for the pointer! I'll study the scripts you mention. In any case, i'm close to a somewhat definitive setup. There is still some tweaking needed as for the backup - it's way too big and slow (but i'm anxious to loose my settings ;) ).