At many places, I happen to see researchers and students wanted to use Windows for NS2 rather than Linux. The reason may be,
- Linux is tough
- It occupies more space and more memory in my Computer
- Linux uses lot of commands and i am not aware of it
- Tough to handle dual boot OS (windows and Linux)
- always wanted to be in the cakewalk. (never try a new thing)
- etc
ns2 installation in Linux |
But here are some basic tips for using NS2 under a Linux Machine.
- It is enough to know some basic Linux commands to work with NS2 (hardly not more than 20 commands)
- One should have a basic knowledge of how tree structure in Linux/Unix look like
- Finally, where to set the PATH information in Linux
With all the above three, one can confidentially work on Linux. As for as windows is concerned, upto NS2.27 version is tested under windows and recent versions there is no hope (however it will work fine, but “Use at your Own Risk”)
Now we will see some basic Linux commands that are needed for NS2.
Now we will see some basic Linux commands that are needed for NS2.
- ls => listing the file contents
- ls -l => listing the file in long format, it tells you about the ownership and permissions
- chmod => Changing the mode of the file (syntax is chmod 755 <filename>
- echo => it echo the value to the screen
- Example: echo name
- echo $SHELL (it will print the name of the shell)
- echo $USER (it will print the name of the user)
- echo $PATH (it display the values contained in the PATH variable)
- echo $HOME (it displays the home folder of the user) (Now you can understood that the variable names are denoted using a $ symbol)
- pwd => it is just present working directory
- make => (it executes the instructions given in the Makefile which is available under that directory)
- gcc filename.cxx => A command to run the gcc compiler (This is not necessarily needed for NS2, but as a developer, you should know)
- ./install => (See a dot in the beginning, it is just executing the install file which is available under a folder, any executable can be executed with the help of this ./)
- passwd => changing the password of the current user
- cd => change the directory
- mkdir => make a directory
- gedit => it is similar like a notepad editor in windows(syntax is gedit filename)
- vi => it is vi editor
Path setting
The path can be set in a file which is available for each user of the Linux OS. For example, a user called “pradeep” will have the home folder as /home/pradeep and another user “kumar” has home folder as /home/kumar
Each user “pradeep” and “kumar” will have a file called .bash_profile (in case of redhat and fedora) and .bashrc (Ubuntu, etc) in their home folder. This file is a hidden file which can be opened using a vi or gedit editor
The command being
vi /home/pradeep/.bash_profile
vi /home/pradeep/.bashrc
or
gedit /home/pradeep/.bash_profile
gedit /home/pradeep/.bashrc
Similarly the same for user “kumar” (if you set the path for “pradeep” and running under “kumar”, it will not work, for that to work, there is a separate customisation is available), for beginners, these steps are enough.
T S Pradeep Kumar The path can be set in a file which is available for each user of the Linux OS. For example, a user called “pradeep” will have the home folder as /home/pradeep and another user “kumar” has home folder as /home/kumar
Each user “pradeep” and “kumar” will have a file called .bash_profile (in case of redhat and fedora) and .bashrc (Ubuntu, etc) in their home folder. This file is a hidden file which can be opened using a vi or gedit editor
The command being
vi /home/pradeep/.bash_profile
vi /home/pradeep/.bashrc
or
gedit /home/pradeep/.bash_profile
gedit /home/pradeep/.bashrc
Similarly the same for user “kumar” (if you set the path for “pradeep” and running under “kumar”, it will not work, for that to work, there is a separate customisation is available), for beginners, these steps are enough.
Comments
Post a Comment