-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stan Goodman wrote:
** Reply to message from G T Smith
on Fri, 07 Sep 2007 22:16:55 +0100 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Stan Goodman wrote:
** Reply to message from G T Smith
on Fri, 07 Sep 2007 20:27:20 +0100 2) The jdk was installed (foolishly, without thinking) in my home directory,
<snip>
No. The "foolishly, without thinking" was that I did NOT install with YaST; if I had, the answer to (2) would have been the same as for (1), and no problem would exist. What is a safe way to remove the jdk, given that YaST is of no help?
Therefore I assume that you installed with rpm without running the SuSEconfig script ... uninstalling with rpm should remove the package without any problems... not knowing what you options you used to install I would refer to the rpm manpage for the appropriate options to uninstall... <snip>
Here you are talking about modifying the bash profiles... Where you make the changes depends on whether you want the path to change globally or for a particular user, or on login.
I would like to understand both the global and user-only cases. For each of these, I am most interested in producing a permanent change that will survive reboot, so what you have called "on logon".
/etc/profile for system wide configuration
This is the system wide profile... there are other scripts in profile.d that are used, it is called before...
~/.bash_profile ~/.bash_login or ~/.profile) for user login
(Actually, these are not aliases so much as alternates, the shell searches for these files in that order... a login shell is the initial login prompt shell)...Different distros do vary a bit on this.. or
~/.bashrc for non login shells
which is used for further instances of the shell. These are related to settings in /etc/sysconfig.. in most cases user modifications should placed in <profile>.local (read docs for more detail than really be given in an email). I will repeat it is not a good idea to make changes to these unless you have a good knowledge of bash/sh, if you do wish to experiment use a local settings in a test account. If your unfamiliar with Bash a good book is 'Learning the Bash Shell' by Newham and Rosenblatt. There is also a bash guide somewhere in the user documentation (cant for the life of me remember where should be at the moment)...
for a starter
these are effectively scripts and some knowledge of BASH scripting is a good idea before attempting to modify these, (and read the BASH documentation). Getting this wrong could make life rather interesting :-)
For Java use editing the PATH variable is NOT required...
As I have said, I am currently operating successfully with an incorrect PATH variable. But that means that I have to specify the full pathname for the
Once you have loaded the java instance it does not care.. If you have a close look at the bin directories you will come across links to things in other directories... The standard path finds the link and then executes the program.. simple... The SuSE rpm sets up this link ... There is Randalls interesting suggestion which I had not heard any references to before (which is something new to explore :-) ). If you really are worried about having the path include the location of the java directory then invoke java with a script that sets appropriate path changes then calls java ...
- -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG4eK4asN0sSnLmgIRAsdzAJ90rbsZWxs0ZWK1qYzjutYlmxaVTQCg2jRd ZKWueZ/1xmiNy16l8jBof70= =Ufya -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org