Operating Systems > Linux and UNIX

how to install a program?

<< < (6/7) > >>

Copperhead:
Unforgiven1:

You might be having trouble getting the Java VM to run because you haven't edited your $PATH variable in /etc/profile or /etc/bash.bashrc. If you have done this, and you've READ instructions that you've received via Google (or wherever), you might be a little confused with Red Hat's pathmunge() function.

Either way, I have explained what you need to do here:

http://forum.microsuck.com/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=5&t=001924

If you need more help, just ask  

Fett101:
And people say that Linux is harder then Wondows.. the idiots.

xyle_one:
it is not that hard to install software. most of the time. there are always the instances where you have to deal with dependencies and wierd installs like the java virtual machine. i never did get limewire to work on my linux box. so i opted for a different p2p. i do hope they fix this pesky installation nightmare. mac osX did a good job, the software is self contained, and its easy to install & uninstall. i do hope that some code monkeys out there start adopting this method over an rpm or whatever. good luck with the virtual machine  

Copperhead:

quote:Originally posted by Fett101:
And people say that Linux is harder then Wondows.. the idiots.
--- End quote ---


Like ecsyle said, there are a few instances that you have to do some minor tweaking to get things running.  The Java VM happens to be one of these things that you need to fiddle with. Since Linux is a *true* multiuser OS, certain programs, like the VM, need to be specified as for use by the local user, or use by the entire system. That is why you have to edit the PATH variable. On M$ systems, there is only one PATH variable, and it is system-wide.  There are no user defined PATHS, and there is no PATH for a superuser (because on M$ there is no superuser.) Then, you get into permissions, on which there are none on Window$ systems (none that are worth a fuck, anyways.) If he installed the VM into /usr/local/java, and /usr/local/java was not in his normal users' PATH, bash would have no way of interpeting what the command `java -jar runlime.jar` means.  If it was in his normal users' PATH, and they get a "permission denied" error, he most likely installed it to a location that the user does not have execute permissions.  Of course, since Linux is highly customizable, and most people that know what they are doing tweak certain permissions on certain directories, (for security reasons, and depending on what the main purpose of your machine is) there is no adequate way to make an "auto installer" like there is on window$. A "standard" location on one person's machine, using one distro, might be perfect, and will allow the user to execute everything flawlessly, while that same "standard" directory on another computer might have modified permissions, or the distro that he/she is using might have a unique set of permissions for the "standard" directory by default that do not allow a user execute permissions. Hence, the most logical method is to allow root to install the VM to a location that he/she knows is chmod'ed 777, and then set the PATH for all users to included that chmod'ed 777 directory. That is why there isn't a quaint, pretty, little "auto-installer" like there is on Window$. Unlike Window$, you can modify Linux to do whatever you want it to do for you without getting sued, and most Linux users, once they gain a little experience and confidence, do exactly that.

TheQuirk:
Don't lie. Windows has paths. You can modify them, easily. And there's a superuser, too. "Administrator".

Bash Microsoft and Windows as much as you want, but bash them for the right reasons. (Get it? "Bash"? HA HA!)

Navigation

[0] Message Index

[#] Next page

[*] Previous page