[ale] Mandrake PATH headache

[Charles Shapiro]

Aha. Interesting.  My preliminary googling indicates that there's a
"startkde" thing, and I'm guessing it's a script. If that's the case, that's
probably got ${PATH} settings in it. Or you could add it to
${HOME}/.xsession if you wanted to change ${PATH} for a specific login.  I
tend to segregate tasks by login, so that's probably the way I'd go. Alas,
I'm at work in Windoze World and can't directly check this.  Bummer.

Anyways for me I'd want to keep all that java hideousity segregated into the
scripts that needed it. But that's mostly a Religious Issue.

-- CHS



On 8/16/06, PairOfTwins <PairOfTwins at mindspring.com> wrote:
>
> Charles:
>
> Thanks for the Java tips.  I'm trying to run the Linux NetZero client,
> which is horribly outdated but works under the best of conditions, and
> calls java.  I'm using konsole only to check the path, as all my
> "profile" and "rc.*" changes had NO effect on the path there.
>
> NetZero runs if I append the java path to the existing path, then export
> PATH within the netzero script itself.
>
> The frustration was (and is) with getting the PATH changed at the KDE
> desktop.
>
> Thanks,
> Tom
> ===============================================================
>
> Charles Shapiro wrote:
> > Umm. If you just run a command it has its own environment. If you set
> > ${PATH} there it's set in that environment, not the parent.  Don't you
> > actually want to run ". ~/profile"?  That runs the commands in the
> > current environment as if you'd typed them in.
> >
> > If you're using bash(1), it runs "~/.bash_profile" as if at the dot
> > automagically on login. Most consoles have some kind of switch or
> > argument line where you can tell the shell to start as if you've
> > logged in rather than as a sub-shell of your current shell. In that
> > case it will source in ~/.bash_profile every time. Or you can set the
> > "env" variable to point to a file which will get sourced in on every
> > sub-invocation.
> >
> > Also usually I've usually organized java stuff in the
> > ${JAVA_HOME}/javaconfig.sh script, which I source in (".
> > ${JAVA_HOME}/javaconfig.sh") as needed. That way I can run different
> > jvm s for different programs by resetting JAVA_HOME -- handy in the
> > 'maze of twisty little passages' java versioning world. And I can
> > manipulate ${CLASSPATH} and other java hideousities globally without
> > having to wrangle every start script when something new happens.
> >
> > -- CHS
> >
> > On 8/16/06, *PairOfTwins* <PairOfTwins at mindspring.com
> > <mailto:PairOfTwins at mindspring.com>> wrote:
> >
> >     Anyone:
> >
> >     After installing Mandrake/PCLinuxOS, I'm unable to change the
> >     PATH.  At
> >     least what PATH applies at the konsole.
> >
> >     Tried:
> >
> >     /etc/profile
> >     ~/.profile
> >     /etc/rc.d/rc.local
> >     /etc/rc.d/rc.sysinit
> >
> >     and NONE of them adds the jre path that I need!
> >
> >     HOWEVER if I run "source profile" I get the desired PATH update.
> >
> >     Does KDE set that PATH (searching Help didn't Help).
> >
> >     Thanks,
> >     Tom
> >
> >     _______________________________________________
> >     Ale mailing list
> >     Ale at ale.org <mailto:Ale at ale.org>
> >     http://www.ale.org/mailman/listinfo/ale
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://www.ale.org/mailman/listinfo/ale
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>
-------------- next part --------------
An HTML attachment was scrubbed...