A slightly cleaner way which I use is to make a symbolic link in /usr/java to the current jre (or j2sdk) that you are using. e.g. for your example: cd /usr/java ln -s /usr/java/j2re1.4.2_05 j2re That way you can set the path to include /usr/java/j2re/bin and when you get the next version of java, just redefine the link to point to the new version and you don't have to worry about changing the path setting. I do this on all my Linux boxes that I administer, and it makes life much simpler. Rob --- "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx> wrote: > On Fri, 13 Aug 2004, Jack Howarth wrote: > > > ... Is there a correct approach to making these > > directories available at a system level other than just > adding > > > > set path=($path '/usr/java/j2re1.4.2_05/bin') > > > > to your .cshrc? I am surprised that the rpm didn't come with > > /etc/profile.d/j2re.[c]sh template scripts. > > that's all i've ever done -- manually added a java.sh file to > that > directory. if there's a cleaner way, i'm interested. > > actually, technically, to have my changes survive across > re-installs, > i generally symlink any new files in there to somewhere in my > home > directory (it's pretty much a single user machine). so /etc > can be > completely trashed and re-installed, but my home dir is > preserved > across re-installs. > > rday > > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: > http://www.redhat.com/mailman/listinfo/fedora-list > ___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
