WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: tinycore_v3.8rc3  (Read 5865 times)

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7344
  • Founder Emeritus
Re: tinycore_v3.8rc3
« Reply #30 on: August 04, 2011, 11:27:14 AM »
To answer my own question:
Quote
Not being am emelfm user please provide specifics.
There is a run command input area at lower right bottom of emelfm2.
Typing echo $PATH displays the PATH issue that Lee is experiencing and can be reproduced.
10+ Years Contributing to Linux Open Source Projects.

Offline Lee

  • Hero Member
  • *****
  • Posts: 565
    • My Core wiki user page
Re: tinycore_v3.8rc3
« Reply #31 on: August 04, 2011, 11:44:55 AM »
Hi Curaga,

In either 3.8rc2 or 3.8rc3, at a shell prompt, I get the expected PATH:

/home/tc/.local/bin
/usr/local/bin
/usr/local/sbin
/usr/sbin
/usr/bin
/sbin
/bin

Its only in emelfm2 that I see the difference.  I don't see any config files getting created at extension load time, but shouldn't they be the same anyhow?

--- a little time passes, during which I do some testing and roberts does also ---

I'm not a rox-filer user but I was able to verify that this issue affects rox-filer as well.  I also determined that if I close down X completely (exit to prompt)  and restart it, the symptoms disappear.



32 bit core4.7.7, Xprogs, Xorg-7.6, wbar, jwm
PPR, data persistence through filetool.sh
USB Flash drive, one partition, ext2, grub4dos

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7344
  • Founder Emeritus
Re: tinycore_v3.8rc3
« Reply #32 on: August 04, 2011, 12:20:24 PM »
I have a fix. I was attempting a temporary PATH for the coreutils and util-linux-ng issues. I will use an alternate method. Now that I know how to use emelfm2 to test. I can verify all three cases for the next cut.
« Last Edit: August 04, 2011, 03:09:41 PM by roberts »
10+ Years Contributing to Linux Open Source Projects.