WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: tinycore_2.4rc2  (Read 28829 times)

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_2.4rc2
« Reply #15 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? 

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.
10+ Years Contributing to Linux Open Source Projects.

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: tinycore_2.4rc2
« Reply #16 on: September 30, 2009, 10:20:39 AM »
.....Ctrl Alt =         grows the window (unshifted + key)......
doesn't work on my italian keyboard, maybe because in order to type "=" I have to press shift 0
 :(


legalize cannabis, coke, ero

Do the other hotkeys work?

Note: If using the full Xorg server and hotkeys do not work, you may need to add a sleep command just after the waitfoX


Yes they do.
I don't use Xorg
dCore user

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: tinycore_2.4rc2
« Reply #17 on: September 30, 2009, 10:30:57 AM »
..... (Currently supports fltk gtk+ scheme.)
What does it means?
dCore user

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: tinycore_2.4rc2
« Reply #18 on: September 30, 2009, 10:59:01 AM »
I added this lines in .profile:
Code: [Select]
FLWM_TITLEBAR_COLOR=00:00:00
export FLWM_TITLEBAR_COLOR
but nothing changed.
I also tryied rebooting
dCore user

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_2.4rc2
« Reply #19 on: September 30, 2009, 11:20:40 AM »
..... (Currently supports fltk gtk+ scheme.)
What does it means?
It means if you use scheme "plastic" the color titlebar will not work and the title bar text may become unreadable. So, the color title bars currently only support gtk+ scheme for fltk. This is the default and can be found in your .Xdefaults.
10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_2.4rc2
« Reply #20 on: September 30, 2009, 11:29:47 AM »
I added this lines in .profile:
Code: [Select]
FLWM_TITLEBAR_COLOR=00:00:00BACKUP
export FLWM_TITLEBAR_COLOR
but nothing changed.
I also tryied rebooting

I have mine in .profile just below the BACKUP line.
It works fine. Even tried your colors work ok.

Make sure not to use plastci scheme.

You can easily test by Logout - Exit to Prompt, edit your .profile, exit  again to get login prompt, type tc
10+ Years Contributing to Linux Open Source Projects.

Offline jpeters

  • Restricted
  • Hero Member
  • *****
  • Posts: 1017
Re: tinycore_2.4rc2
« Reply #21 on: September 30, 2009, 11:39:52 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?  

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.

.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
« Last Edit: September 30, 2009, 12:12:31 PM by jpeters »

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: tinycore_2.4rc2
« Reply #22 on: September 30, 2009, 11:42:59 AM »
I added this lines in .profile:
Code: [Select]
FLWM_TITLEBAR_COLOR=00:00:00
export FLWM_TITLEBAR_COLOR
but nothing changed.
I also tryied rebooting

I have mine in .profile just below the BACKUP line.
It works fine. Even tried your colors work ok.

Make sure not to use plastci scheme.

You can easily test by Logout - Exit to Prompt, edit your .profile, exit  again to get login prompt, type tc
it doesn't work.
I'll do like before, changing the line in .xsession which lauch the wm
dCore user

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: tinycore_2.4rc2
« Reply #23 on: September 30, 2009, 12:01:45 PM »
I added this in .Xdefaults:
Code: [Select]
fltk*scheme: gtk+    
fltk*background:black
Text.background:black
fltk*foreground:white
fltk*selectBackground:black
and I did not change .xsession
dCore user

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_2.4rc2
« Reply #24 on: September 30, 2009, 01:45:27 PM »
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?  

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.

.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


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.
« Last Edit: September 30, 2009, 01:51:02 PM by roberts »
10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_2.4rc2
« Reply #25 on: September 30, 2009, 01:54:39 PM »
I added this in .Xdefaults:
Code: [Select]
fltk*scheme: gtk+    
fltk*background:black
Text.background:black
fltk*foreground:white
fltk*selectBackground:black
and I did not change .xsession

You only need the scheme in .Xdefaults!

What do you get when in X with an open xterm and type
env | grep TITLEBAR
10+ Years Contributing to Linux Open Source Projects.

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: tinycore_2.4rc2
« Reply #26 on: September 30, 2009, 02:30:15 PM »
........
You only need the scheme in .Xdefaults!

What do you get when in X with an open xterm and type
env | grep TITLEBAR
FLWM_TITLEBAR_COLOR=00:00:00
dCore user

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7183
    • My Community Forum
Re: tinycore_2.4rc2
« Reply #27 on: September 30, 2009, 02:40:48 PM »
Another strange thing. It happened many times that installing application with appbrowser its content is not stored in the RAM, but appbrowser says it was successful. Downloaded extension is stored in /tce and after rebooting they are working as expected.

Please supply specific example(s) so that I may try to duplicate.
Thanks.

Just take a stock 2.4rc2 with /tce on USB (if it matters) and install applications with appbrowser one by one and check them. First few is OK, but very soon their content is missing. Appbrowser displays a success message, extension name is in /usr/local/tce.installed, extension itself is stored in /tce

It is not extension specific. Free RAM is 1.8G.

Restarting the system everything is copied correctly from /tce to RAM.

Haven't seen such before 2.4

I can't give more specific info  :(
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_2.4rc2
« Reply #28 on: September 30, 2009, 02:46:20 PM »
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?  

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.

.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


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.

Please try http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates/microcore/jwm.tcz

10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_2.4rc2
« Reply #29 on: September 30, 2009, 02:48:54 PM »
........
You only need the scheme in .Xdefaults!

What do you get when in X with an open xterm and type
env | grep TITLEBAR
FLWM_TITLEBAR_COLOR=00:00:00


What Xserver are you running?
10+ Years Contributing to Linux Open Source Projects.