Tiny Core Linux

Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on September 29, 2009, 07:07:45 PM

Title: tinycore_2.4rc2
Post by: roberts on September 29, 2009, 07:07:45 PM
The Second Release Candidate of v2.4 (tinycore_2.4rc2.iso), is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates/

Change log for v2.4 Release Candidate 2
* Updated flwm to v 1.10 - Top side title bar, hotkeys, and color window title bars (See Notes below)
* Updated flpicsee to v1,0 - replaced Alt with Ctrl hotkyes.
* Updated tc-config, startx, and .profile to make desktop environment reentrant & better support of microcore.
* New tce-setup to load all tce applications from a tinycore "base norestore text" boot
* Updated tc-config now calls tce-setup, as tce loading has been factored out.
* Updated tc-restore & filetool.sh to implement 'protect' blowfish encrypted backup.
* Updated tc-restore & filetool.sh for default backup to be located in persistent tce directory.
* Updated setbackground to process compressed logo template, saves much space.
* Updated tce-load to fix bug regarding partial downloads of dependencies
* Updated .xsession so watcher, now at +0-0, does not overlay flit
* Updated /opt/.tcrc to tcz repository..
* Dropped 'checkfs' boot option. Use options 'base norestore' to check and fix filesystems and then start up complete system.

Files likely in your backup that you must update.
.profile
.xsession

Notes:

The desktop environment has been moved from tc-config into startx. This allows a microcore boot with base norestore, then manually (tce-load -i) the core elements together with your choice of window manager, wbar, flit, and/or watcher. Upon completion, still at the $ prompt, typing startx will bring up a working desktop environment. You can still exit to prompt, and run startx.

And with the new tce-setup, you can load all your PPR with a single command.
Just boot tinycore 'base norestore text   Then when ready.

$ sudo tce-setup
$ startx

Same with microcore, except, of course,  the text boot option is not needed


Notes: Hotkeys for Color Title Bars for flwm v1.10. ( Thanks to Mike L. for the many improvements to flwm! )

changed Alt+Enter to Alt+F1 to iconize a window

Ctrl Alt arrows moves the window
Ctrl Alt =         grows the window (unshifted + key)
Ctrl Alt -          shrinks the window
Ctrl Alt PgUp   grows the window veritcally
Ctrl Alt PgDn   shrinks the window vertically
Ctrl Alt ,           grows the window hortizontally (unshifted < key)
Ctrl Alt .           grows the window hortizontally (unshifted > key)
Ctrl Alt t           taller (sames as PgUp)
Ctrl Alt s          shorter (same as PgDn)

flwm now optionally supports environment variable FLWM_TITLEBAR_COLOR to set color for window title bars.
To set use hex rgb, e.g, 20:5F:20 (Currently supports fltk gtk+ scheme.)


   
Title: Re: tinycore_2.4rc2
Post by: jpeters on September 29, 2009, 09:48:06 PM
Boots jwm without tray or hotkeys; haven't tried much, other than copy over new .profile, .xsession; tried
startx from prompt, jwm_restart, etc..
Title: Re: tinycore_2.4rc2
Post by: jpeters on September 29, 2009, 11:03:29 PM
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?  

Title: Re: tinycore_2.4rc2
Post by: meo on September 30, 2009, 12:19:39 AM
Hi team tinycore!

Just tested the new tinycore 2.4 rc 2 and it works excellent. Very good work! Thanks to all of you.

Have fun developing tinycore further,
meo
Title: Re: tinycore_2.4rc2
Post by: bmarkus on September 30, 2009, 12:51:52 AM
Default backup location offered by cpanel is sdb1/tce booting and using a single FAT partition. I think it is not a proper location. To have a good default is great and much better than leave it blank. I would prefere the root of the boot partition if a single partition is used or the root of the other Linux partition used for /tce if exists.
Title: Re: tinycore_2.4rc2
Post by: Guy on September 30, 2009, 02:14:23 AM
I respect that we all think differently and can genuinely have different opinions.

I like the backup in the tce directory. It keeps the root directory cleaner.

I think it is good to have a default. It makes it easier for new users. There is one less thing for them to get caught up on.
Title: Re: tinycore_2.4rc2
Post by: bmarkus on September 30, 2009, 02:36:45 AM
I respect that we all think differently and can genuinely have different opinions.

I like the backup in the tce directory. It keeps the root directory cleaner.

I think it is good to have a default. It makes it easier for new users. There is one less thing for them to get up on.

Agree, good to have a default.

However mixing up directories is a bad idea. If you like to have a clean root dir why do you like a tce with backup which has nothing to do with extensions?
Title: Re: tinycore_2.4rc2
Post by: Guy on September 30, 2009, 02:56:15 AM
I save certain things in /mnt/sda1 (I actually have several partitions - the partition I am using). By minimizing what is in /home/tc, backup is quick. Having less directories there to begin with is cleaner.
Title: Re: tinycore_2.4rc2
Post by: jls on September 30, 2009, 04:09:19 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
Title: Re: tinycore_2.4rc2
Post by: bmarkus on September 30, 2009, 04:27:41 AM
File/Install File/Mount or File/Download in appbrowser gives an error pop up window with no any description of the error.

System is booted with base nolocal norestore waitusb=5 option. In /etc/sysconfig there are no tce location description file. In previous versions in such case it was tce.mount pointing to /tmp/tce

Just wanted to check new extension dependency on a clean system but can't load modules from the repository due to lack of /etc/sysconfig.tce.mount and tce dir.
Title: Re: tinycore_2.4rc2
Post by: bmarkus on September 30, 2009, 05:43:33 AM
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.
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 06:36:17 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

Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 06:47:01 AM
File/Install File/Mount or File/Download in appbrowser gives an error pop up window with no any description of the error.

System is booted with base nolocal norestore waitusb=5 option. In /etc/sysconfig there are no tce location description file. In previous versions in such case it was tce.mount pointing to /tmp/tce

Just wanted to check new extension dependency on a clean system but can't load modules from the repository due to lack of /etc/sysconfig.tce.mount and tce dir.


Yes, a bug indeed, but an easy fix. The work around for now
echo "/tmp/tce" > /opt/.tce_dir
mkdir /tmp/tce
Title: Re: tinycore_2.4rc2
Post by: tclfan on September 30, 2009, 06:51:16 AM
Default backup location offered by cpanel is sdb1/tce booting and using a single FAT partition. I think it is not a proper location. To have a good default is great and much better than leave it blank. I would prefere the root of the boot partition if a single partition is used or the root of the other Linux partition used for /tce if exists.
If I can add my two cents, I agree with Bela. Folder /tce is to store static content of extensions only, while mybackup file is dynamic content and should live separate not mixed with static content.
E.g. with usb install in Zip emulation, the actual OS is in small first partition sdb1, while /tce folder is created in the second and larger partition sdb2. The backup file (mybackup) should be side-by side with /tce folder, therefore in the root directory. It is not being mixed with the OS files, since the OS is self-contained on the first partition (sdb1) and nothing else is stored there...
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 06:54:27 AM
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.
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 07: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.
Title: Re: tinycore_2.4rc2
Post by: jls on September 30, 2009, 07: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
Title: Re: tinycore_2.4rc2
Post by: jls on September 30, 2009, 07:30:57 AM
..... (Currently supports fltk gtk+ scheme.)
What does it means?
Title: Re: tinycore_2.4rc2
Post by: jls on September 30, 2009, 07: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
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 08: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.
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 08: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
Title: Re: tinycore_2.4rc2
Post by: jpeters on September 30, 2009, 08: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
Title: Re: tinycore_2.4rc2
Post by: jls on September 30, 2009, 08: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
Title: Re: tinycore_2.4rc2
Post by: jls on September 30, 2009, 09:01:45 AM
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
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 10:45:27 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


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.
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 10:54:39 AM
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
Title: Re: tinycore_2.4rc2
Post by: jls on September 30, 2009, 11:30:15 AM
........
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
Title: Re: tinycore_2.4rc2
Post by: bmarkus on September 30, 2009, 11:40:48 AM
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  :(
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 11:46: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.

.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

Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 11:48:54 AM
........
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?
Title: Re: tinycore_2.4rc2
Post by: jls on September 30, 2009, 11:56:27 AM
...What Xserver are you running?
Xvesa
Title: Re: tinycore_2.4rc2
Post by: bmarkus on September 30, 2009, 12:00:13 PM
Maybe I missed something earlier. But what is xlist in the tce directory?
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 12:06:52 PM
It is temporary and will be gone in next cut, for sure before final.
It is used during load process to ensure that existing files and directories are not over written.
Title: Re: tinycore_2.4rc2
Post by: bmarkus on September 30, 2009, 12:12:08 PM
It is temporary and will be gone in next cut, for sure before final.
It is used during load process to ensure that existing files and directories are not over written.

Well, as I see there /usr/local/bin now I understand why /usr/local/bin/xz for example is not loaded  ;D
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 12:15:17 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  :(

I just loaded up 40 apps, some of the largest, all via appbrowser and all "install" to ram. Each app runs fine. I cannot reproduce without more information.

Are you talking about 100s of apps? Do you see the failure after loading a specific app?
Title: Re: tinycore_2.4rc2
Post by: bmarkus on September 30, 2009, 02:00:50 PM
I'm trying to reproduce it but now it works. Anyhow, will make few more tries to reproduce recording the extension load order. For sure it happened not only once before, so the daemon is out there  ???
Title: Re: tinycore_2.4rc2
Post by: jpeters on September 30, 2009, 06:37:58 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


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: [Select]
# !/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
Title: Re: tinycore_2.4rc2
Post by: bigpcman on September 30, 2009, 07:41:30 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


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.
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 07:53:37 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


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: [Select]
# !/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
Yes and that worked just fine until the code was refactored to be reentrant.
Please the the new jwm.tcz as posted earlier.
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 07:59:08 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


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.

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.
Title: Re: tinycore_2.4rc2
Post by: bigpcman on September 30, 2009, 08:01:19 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


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.

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.

As you have said many times, that's what "rc's" are for.
Title: Re: tinycore_2.4rc2
Post by: roberts on September 30, 2009, 08:05:15 PM
There is nothing like public testing to shake things out.
I am glad I have a community willing to do such.
Thanks.
Title: Re: tinycore_2.4rc2
Post by: jpeters on September 30, 2009, 10:47:59 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


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: [Select]
# !/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
Yes and that worked just fine until the code was refactored to be reentrant.
Please the the new jwm.tcz as posted earlier.

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: [Select]
for F in `ls -1 /etc/skel/.jwm*`; do
  [ -f /home/"$USER"/"${F##/*/}" ] || cp /etc/skel/.jwm* /home/"$USER"
  done

Title: Re: tinycore_2.4rc2
Post by: bmarkus on September 30, 2009, 11:03:53 PM
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


In /tmp/backup_status:

Quote

... file changed as we read it


Messages doesn't fit together and first message is misleading.
Title: Re: tinycore_2.4rc2
Post by: bmarkus on September 30, 2009, 11:41:31 PM
usbinstall error messages can't be read when script started in the right click menu as script terminates immediately.
Title: Re: tinycore_2.4rc2
Post by: jpeters on October 01, 2009, 01:10:20 AM
trivial (and not so trivial) issues:

The opt//sed permission errors have returned again (eg, while backing up).  
New: While booting, getting lots of complaints from extensions attempting cat /etc/sysconfig/icons.    
Maybe my imagination, but boot seems to be taking longer (haven't actually timed differences).  

edit: booting is taking about 1.5x  that of ver_2.3  (58 sec vs 38 sec).  
Fast booting was my favorite feature.
Title: Re: tinycore_2.4rc2
Post by: roberts on October 01, 2009, 05:59:55 AM
trivial (and not so trivial) issues:

The opt//sed permission errors have returned again (eg, while backing up).  
New: While booting, getting lots of complaints from extensions attempting cat /etc/sysconfig/icons.    
Maybe my imagination, but boot seems to be taking longer (haven't actually timed differences).  

edit: booting is taking about 1.5x  that of ver_2.3  (58 sec vs 38 sec).  
Fast booting was my favorite feature.

Not sure why extensions need to care about /etc/sysconfig/icons. Extensions should only care about  /usr/local/tce.icons.  /etc/sysconfig/icons is a temporary holder for the environment variable to be read and set and should not be a concern of extensions.

Don't fret over speed, it is still be worked on. Release Candidates are a testing ground.
Title: Re: tinycore_2.4rc2
Post by: Juanito on October 01, 2009, 06:04:11 AM
I see one error of the form:

cat /etc/sysconfig/icons file not found

..when booting with *core*, wbar, flwm, flit, gtk1, glib1, emelfm, gtkfind, beaver in /tce

gtk1, glib1, emelfm, gtkfind and beaver don't attempt to do anything with /etc/sysconfig/icons
Title: Re: tinycore_2.4rc2
Post by: jpeters on October 01, 2009, 07:02:36 AM
I see one error of the form:

cat /etc/sysconfig/icons file not found

..when booting with *core*, wbar, flwm, flit, gtk1, glib1, emelfm, gtkfind, beaver in /tce

gtk1, glib1, emelfm, gtkfind and beaver don't attempt to do anything with /etc/sysconfig/icons

I get the error for:
jwm, links, rdesktop, samba3, shadow-utils, skype, squashfs-tools-4.0, tcl-tk, wireless-2.6.29.1-tinycore_mod, xmms-1.2.11, xonclock; also for script tcz-uninstall

I'm booting "noicon"
Title: Re: tinycore_2.4rc2
Post by: roberts on October 01, 2009, 08:58:34 AM
I see the issue with /etc/sysconfig/icons and will fix it.
Also will be testing an improved load to ram procedure.
Should make things much better.
Title: Re: tinycore_2.4rc2
Post by: jpeters on October 01, 2009, 09:49:06 AM
I see the issue with /etc/sysconfig/icons and will fix it.
Also will be testing an improved load to ram procedure.
Should make things much better.

..must be comforting to know users are booting the rc's with stop watches  :D
Title: Re: tinycore_2.4rc2
Post by: roberts on October 01, 2009, 10:41:33 AM
It is actually great that the community adds extra eyeballs on early testing releases.
It will surely make 2.4 a solid release when it is final. I have made many internal changes in response to community and team requests. 2.4 is more modular and a better fit with microcore. Although, this is, one of the more challenging release cycles. I now have an alpha of rc3 for team QA.
Title: Re: tinycore_2.4rc2
Post by: jls on October 01, 2009, 12:31:52 PM
some extensions doesn't go 2 ram even they're listed in tcz2ram.lst, for example:
graphic-libs-1, libxml2, fontconfig, gtk2, pango, pixman, nss-nspr.
Title: Re: tinycore_2.4rc2
Post by: philip on October 01, 2009, 10:44:35 PM
... this is one of the more challenging release cycles. I now have an alpha of rc3 for team QA.
Dang, you guys are good. RC's just keep pouring out with big improvements, and every day the forums show little bugs getting squashed and newbie users being set right with astonishing speed. Thank you!
Title: Re: tinycore_2.4rc2
Post by: roberts on October 02, 2009, 12:42:37 PM
usbinstall error messages can't be read when script started in the right click menu as script terminates immediately.
I have updated usbinstall for rc3.