Tiny Core Base > Release Candidate Testing
tinycore_2.4rc2
bigpcman:
--- Quote from: roberts on September 30, 2009, 10:59:08 PM ---
--- Quote from: bigpcman on September 30, 2009, 10:41:30 PM ---
--- Quote from: jls_legalize on September 30, 2009, 02:30:15 PM ---
--- Quote from: roberts on September 30, 2009, 01:54:39 PM ---........
You only need the scheme in .Xdefaults!
What do you get when in X with an open xterm and type
env | grep TITLEBAR
--- End quote ---
FLWM_TITLEBAR_COLOR=00:00:00
--- End quote ---
I'm running 2.4rc2 in qemu and see the same results. I tried FLWM_TITLEBAR_COLOR=32:32:32. There was no change.
env | grep TITLEBAR returns:
FLWM_TITLEBAR_COLOR=32:32:32
Using xvesa.
--- End quote ---
Yes. Appears to be my bad. The classic build got the latest cut. This is the version that I prefer. The topside build did not. You can try the classic build or wait until next cut for the topside to be updated.
--- End quote ---
As you have said many times, that's what "rc's" are for.
roberts:
There is nothing like public testing to shake things out.
I am glad I have a community willing to do such.
Thanks.
jpeters:
--- Quote from: roberts on September 30, 2009, 10:53:37 PM ---
--- Quote from: jpeters on September 30, 2009, 09:37:58 PM ---
--- Quote from: roberts on September 30, 2009, 02:46:20 PM ---
--- Quote from: roberts on September 30, 2009, 01:45:27 PM ---
--- Quote from: jpeters on September 30, 2009, 11:39:52 AM ---
--- Quote from: roberts on September 30, 2009, 10:00:20 AM ---jpeters wrote:
--- Quote ---Boots jwm without tray or hotkeys; haven't tried much, other than copy over new .profile, .xsession; tried
startx from prompt, jwm_restart, etc..
Looks like the new RC overwrote the .jwmrc files in $HOME. I had some backups, so restored.
edit: and continues to overwrite them; shouldn't they be only in /skel?
--- End quote ---
jwm is not in the base system. jwm is an extension and the extension has not changed.
However I will look into booting the jwm extension.
--- End quote ---
.jwmrc files are in /etc/skel. The issue is that they're somehow being written to $HOME, overwriting the files from backup. Workaround is to recopy them after the boot. They're even overwritten if returing to a prompt and issuing the startx command.
edit: strange....I don't see any .jwmrc files after unpacking tinycore.gz (in /etc/skel or ~home)...not sure where they're coming from. I'll try the snapshot extension. edit: same issue
--- End quote ---
I see the issue. It came about as part of the refactoring of code. I will correct it. I believe it can be handled in the extensions itself. Thanks for reporting.
--- End quote ---
Please try http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates/microcore/jwm.tcz
--- End quote ---
Just took a brief break from work, I didn't get a chance to check out the link. THANKS!
I just noted line 7 in jwm_initmenu. I see the .jwmrc files are put in /etc/skel by the extension, then
copied to $HOME.
--- Code: ---# !/bin/sh
3 # (c) Robert Shingledecker 2009
4 # Called from tc-config to setup jwm tce menu
5 USER="$(cat /etc/sysconfig/tcuser)"
6 TCEMENU="/usr/local/tce.menu/menu"
+7 cp /etc/skel/.jwm* /home/"$USER"
8 cp /usr/share/jwm/tce/menu_template "$TCEMENU"
9 chown "$USER".staff "$TCEMENU"
10 chmod g+w "$TCEMENU
--- End code ---
--- End quote ---
Yes and that worked just fine until the code was refactored to be reentrant.
Please the the new jwm.tcz as posted earlier.
--- End quote ---
I don't exactly know what refactored to be reentrant means, but the linked jwm extension includes a test before copying, which works nicely: (but it DID work before :))
--- Code: ---for F in `ls -1 /etc/skel/.jwm*`; do
[ -f /home/"$USER"/"${F##/*/}" ] || cp /etc/skel/.jwm* /home/"$USER"
done
--- End code ---
bmarkus:
Backup displays the following error message:
--- Quote ---
Make sure you are using a valid backup/restore device. Some errors are logged in /tmp/backup_status
--- End quote ---
In /tmp/backup_status:
--- Quote ---
... file changed as we read it
--- End quote ---
Messages doesn't fit together and first message is misleading.
bmarkus:
usbinstall error messages can't be read when script started in the right click menu as script terminates immediately.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version