does this^^ assume
/bin/bash.bashrc ?
What is the correct command for this?
http://pastebin.com/f36c6c7fa
l@EV007:~/sarse$ echo -e '\nPATH=$PATH:~/sarse-1.37/bin' >> .bashrc
l@EV007:~/sarse$ source .bashrc
bash: version: No such file or directory
bash: 1.37: No such file or directory
searching the file brower shows that i have a file at
/ect/bash.bash.rc
l@EV007:~/sarse$ echo -e '\nPATH=$PATH:~/sarse-1.37/ect' >> .bashrc
l@EV007:~/sarse$ source .bashrc
bash: version: No such file or directory
bash: 1.37: No such file or directory
No. Your .bashrc file is in your home (~) directory.
> l@EV007:~/sarse$ echo -e '\nPATH=$PATH:~/sarse-1.37/bin' >> .bashrc
This echoes the content of that string in to ~/sarse/.bashrc
> l@EV007:~/sarse$ source .bashrc
> bash: version: No such file or directory
> bash: 1.37: No such file or directory
Probably because you have some weird content in ~/sarse/.bashrc
Anyway, you'll probably never use ~/sarse/.bashrc again, you should
just use your ~/.bashrc file.
>> On linuxNo. Your .bashrc file is in your home (~) directory.
>> echo -e '\nPATH=$PATH:~/sarse-<version>/bin' >> .bashrc
>> source .bashrc
>>
>> .bashrc system files located in the users home
>> directory.
>
> does this^^ assume
> /bin/bash.bashrc ?
This echoes the content of that string in to ~/sarse/.bashrc
> l@EV007:~/sarse$ echo -e '\nPATH=$PATH:~/sarse-1.37/bin' >> .bashrc
Probably because you have some weird content in ~/sarse/.bashrc
> l@EV007:~/sarse$ source .bashrc
> bash: version: No such file or directory
> bash: 1.37: No such file or directory
Anyway, you'll probably never use ~/sarse/.bashrc again, you should
just use your ~/.bashrc file.
ls doesn't show hidden files by default.
ls -a
>> > l@EV007:~/sarse$ echo -e '\nPATH=$PATH:~/sarse-1.37/bin' >> .bashrc
>>
>> This echoes the content of that string in to ~/sarse/.bashrc
>>
>> > l@EV007:~/sarse$ source .bashrc
>> > bash: version: No such file or directory
>> > bash: 1.37: No such file or directory
>>
>> Probably because you have some weird content in ~/sarse/.bashrc
>
> l@EV007:~$ ~/sarse/.bashrc
> bash: /home/l/sarse/.bashrc: Permission denied
.bashrc is not an executable file anyway. I don't know why you're
trying to execute it.
> /home/l/sarse.bashrc
What?
>> Anyway, you'll probably never use ~/sarse/.bashrc again, you should
>> just use your ~/.bashrc file.
>
> What is the command for that?
It's a file, not a command.
http://www.youtube.com/watch?v=cbBTcYir-4g
>> >> On linux
>> >> echo -e '\nPATH=$PATH:~/sarse-<version>/bin' >> .bashrc
>> >> source .bashrc
>> >>
>> >> .bashrc system files located in the users home
>> >> directory.
>> >
>> > does this^^ assume
>> > /bin/bash.bashrc ?
>>
>> No. Your .bashrc file is in your home (~) directory.
>> > l@EV007:~/sarse$ echo -e '\nPATH=$PATH:~/sarse-1.37/bin' >> .bashrc
>> > l@EV007:~/sarse$ source .bashrc
>> > bash: version: No such file or directory
>> > bash: 1.37: No such file or directory
>> just use your ~/.bashrc file.
>
> What is the command for that?
It's a file, not a command.
------------------------
The example here asume you have root priviledges, and wan't to install sarse in /usr/local:
cd /usr/local
tar xpzf <download-directory>/sarse-<version>.tar.gz
The installation directory is called SARSE-HOME, in the rest of the document.
Then you add sarse to an existing bin directory in the standard path, /usr/local/bin
This way all users wil be able to start sarse easily from anywhere
cd /usr/local/bin
ln -s /usr/local/sarse-<version>/bin/SARSE
Starting the program
----------------------
To run the program simply write 'SARSE' anywhere
Sounds like you messed up your .bashrc file.. I'd open it up and take
a look, see if you can find where it says "version", "1.37" and so on.
Sounds like you messed up your .bashrc file.. I'd open it up and take
a look, see if you can find where it says "version", "1.37" and so on.
Yes, but your .bashrc file is still messed up. You should fix it.