Tag Info

New answers tagged

1

Better to create a symbolic link than an alias I think. An alias might make substitutions on your command line when you didn't want one; creating a symlink will allow you to run the program as you want: sudo ln -s full_path_to_opt/LightTable/deploy/LightTable /usr/local/bin This will create a shortcut in /usr/local/bin (which should be in your PATH ...


1

I'm not sure why other answerers have not suggested this, but as the OP actually pointed out, prepending to the $PATH variable would have been the way I would have achieved this: echo 'PATH=/opt/LightTable/deploy:$PATH' >> ~/.bash_profile source ~/.bash_profile Then run with: LightTable


3

They are configuration files. One way: Open a terminal window using Ctrl+Alt+T Run the command gedit ~/.profile Add the line export PATH=$PATH:/media/De\ Soft/mongodb/bin to the bottom and save Log out and log in again


3

You can try to copy the executable to /usr/bin if its a simple executable program and doesn't depend on any other file. if it does depend of other files, the best to do is create a shortcut command to the program. Where you create the alias is by yourself (.bashrc, .profile, etc). However I personally let all my enviroment variables in my .bash_aliases file ...


4

This isn't an elementary question, the best way to do this is to make an alias, Ill use netbeans as an example Open Terminal Ctrl+Alt+T nano ~/.bashrc write this at the bottom of the file: alias netbeans='/home/john/netbeans-7.0.1/bin/netbeans' Ctrl + x Y Enter The netbeans word is the command you will use to start the program, you can change it to ...


7

This can be crudely accomplished with an alias. You can create a permanent bash alias by adding a single line to your .bashrc file. In the terminal run nano ~/.bashrc Add the the following line at the bottom: alias LightTable='/full/path/opt/LightTable/deploy/LightTable' notice I added thee full path instead of the . so this will work in any working ...


0

another solution Add path to ~/.bashrc open using vim $ vim ~/.bashrc example: # add extra paths export PATH=$PATH:~/Scripts once path is added run: $ source ~/.bashrc If added correctly there should be no errors.


2

Update your .bashrc instead of .bash_profile that is used only for bash in interactive mode. Here is a useful explanation.


0

You would be able to run them, you will just have to specify the full path. Modifying PATH does not modify the permissions associated.


2

You are correct. Third party packages should therefore only extend the current path, not limit it.


0

Chances are there used to be a redis-cli in /usr/bin/redis-cli which has now been deleted. Bash maintains an internal hash of executables on your path which hasn't been updated. If you encounter this problem again, rehash it and it will work. hash redis-cli


0

From Environment variables, $LOGNAME is same as $USER which gives The name of the currently logged-in user. This variable is set by the system. You probably shouldn't change its value manually. From man logname logname - print user´s login name Expained differently used by following example: pandya@pandya-desktop:~$ sudo su ...


3

@malohree I've tried to break this down a little bit for you, using your own examples/text as well, check it out: dlevey@bangingbeast:~/development/askubuntu/malohree$ cat fred #!/bin/bash fred='Four spaces between these words.' echo "The value of \$fred is $fred" echo "The next line being printed is simply the results of # echo \$fred" echo $fred ...


1

I think you should put: fred='Four spaces between these words' echo "The value of \$fred is \"$fred\"" You can enter this into terminal, by right-clicking and selecting Paste, or Ctrl+Shift+V), or by entering it one line at a time. e.g:                  You can also create a ...


0

Read carefully sudo man page SECURITY NOTES. try -i option that initializes the environment, leaving DISPLAY and TERM unchanged, setting HOME, SHELL, USER, LOGNAME, and PATH, as well as the contents of etc/environment on Linux and AIX systems. sudo -H -u administrator -i /bin/bash --login -c "~administrator/BuildAgent/bin/agent.sh start"



Top 50 recent answers are included