WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

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

Offline jls

  • Hero Member
  • *****
  • Posts: 2133
Re: tinycore_2.4rc2
« Reply #30 on: September 30, 2009, 11:56:27 AM »
...What Xserver are you running?
Xvesa
dCore user

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7023
    • My Community Forum
Re: tinycore_2.4rc2
« Reply #31 on: September 30, 2009, 12:00:13 PM »
Maybe I missed something earlier. But what is xlist in the tce directory?
Béla
Ham Radio callsign: HA5DI

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

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_2.4rc2
« Reply #32 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.
10+ Years Contributing to Linux Open Source Projects.

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7023
    • My Community Forum
Re: tinycore_2.4rc2
« Reply #33 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
Béla
Ham Radio callsign: HA5DI

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

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_2.4rc2
« Reply #34 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?
« Last Edit: September 30, 2009, 02:22:28 PM by roberts »
10+ Years Contributing to Linux Open Source Projects.

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7023
    • My Community Forum
Re: tinycore_2.4rc2
« Reply #35 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  ???
Béla
Ham Radio callsign: HA5DI

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

Offline jpeters

  • Restricted
  • Hero Member
  • *****
  • Posts: 1017
Re: tinycore_2.4rc2
« Reply #36 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
« Last Edit: September 30, 2009, 06:41:05 PM by jpeters »

Offline bigpcman

  • Hero Member
  • *****
  • Posts: 719
Re: tinycore_2.4rc2
« Reply #37 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.
big pc man

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_2.4rc2
« Reply #38 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.
10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_2.4rc2
« Reply #39 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.
10+ Years Contributing to Linux Open Source Projects.

Offline bigpcman

  • Hero Member
  • *****
  • Posts: 719
Re: tinycore_2.4rc2
« Reply #40 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.
big pc man

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_2.4rc2
« Reply #41 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.
10+ Years Contributing to Linux Open Source Projects.

Offline jpeters

  • Restricted
  • Hero Member
  • *****
  • Posts: 1017
Re: tinycore_2.4rc2
« Reply #42 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

« Last Edit: September 30, 2009, 10:56:47 PM by jpeters »

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7023
    • My Community Forum
Re: tinycore_2.4rc2
« Reply #43 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.
« Last Edit: September 30, 2009, 11:07:21 PM by bmarkus »
Béla
Ham Radio callsign: HA5DI

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

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7023
    • My Community Forum
Re: tinycore_2.4rc2
« Reply #44 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.
Béla
Ham Radio callsign: HA5DI

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