FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I installed ns2.29 on Fedora 12. Unfortunately, NAM doesn't work.
I got same error. moreover, when I tried to download patch file, it doesn't work.
Could you please help me and send me a patch file and steps to implement it as well.
Thank you in advance and your help is appreciated.
sir,
thankyou sir
i patch the tk-8.4-lastevent.patch file from /ns-allinone/tk8.4.18/
nam is also worked well.
now i executed one tcl program.i can view the result in nam sucessfully.
then,when i execute it with ns program_name.tcl from command prompt the part of my program is executed and i can see the calculated through put and delay etc...in terminal window.
i couldn't get it in graph.
error :ns: proc_name: couldn't execute "xgraph": no such file or directory
what are the steps should be followed and what are the possibilities to get these?
i check well in path setting for xgraph also.
please help me to execute my program successfully.
thankyou.
vahitha
command for patching please
---------- Post added 01-10-14 at 12:43 PM ----------
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511
Rep:
#22, @reemlus.
Quote:
couldn't execute "xgraph": no such file or directory
.
command for patching please
I guess you mean "How to achieve a working 'xgraph' ?
The answer is : $ sudo apt-get install xgraph
... If your OS isn't Debian / Ubuntu / Mint, please specify your OS :
a) $ uname -m
b) $ cat /etc/*release*
Quote:
how to open binary nam
How to unpack a <package>.tar.gz : $ tar xvf <name>.tar.gz
... Or use your default 'Archive Manager'.
Hi,
after the installation ns2.31 on fedora12, i had this same problem of nam (in the last line bind Li), to correct it i used the method of the patch. i downloaded the tk-8.4-lastevent.patch and i put it on tk-8.4.14 folder.
then i did this:
cd ns-allinone-2.33/tk-8.4.14/
patch -p0 < tk-8.4-lastevent.patch
and i ran ./install again.
after this i called the nam by nam command in the terminal, and i had this error:
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511
Rep:
Re #24.
First : Check if you created a usable nam : cd nam-1.14/ && ./nam
If nam is working : # make install
( 'make install' will copy 'nam' to /usr/local/bin/
... just like # cd ns-2.33/ && make install will copy 'ns' to /usr/local/bin/.
Therefore : No *PATH settings are required. No adding no *PATH to .bashrc ).
Else : Install a nam package. Much easier than a build. Is what most people do :
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511
Rep:
Re #26.
Quote:
it asked me to add path in .bashrc file, so i did it.
No. You are not asked to add any *PATH text to .bashrc .
It's just a ~15 year old text from those days when students used a University Computer.
The executable 'ns' or "ns-<any-name>" is hard coded to know the location of it`s libraries:
ns-allinone-2.3x/{ lib/*/*, bin/tcsh8* }. And 'nam' is partly statically compiled.
You can actually run 'nam' OK on a computer with no ns2 and no {tcl8*, tk8*}.
".bashrc" is a text file : Easy to edit.
Just select : View > Show Hidden Files in Nautilus / Konqueror.
The original .bashrc :
Code:
# .bashrc
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
# User specific aliases and functions
when i say it asked me to add path i mean this message tha appears at the end of ./install
Quote:
Please put /home/marwa/ns-allinone-2.31/bin:/home/marwa/ns-allinone-2.31/tcl8.4.14/unix:/home/marwa/ns-allinone-2.31/tk8.4.14/unix
into your PATH environment; so that you'll be able to run itm/tclsh/wish/xgraph.
IMPORTANT NOTICES:
(1) You MUST put /home/marwa/ns-allinone-2.31/otcl-1.13, /home/marwa/ns-allinone-2.31/lib,
into your LD_LIBRARY_PATH environment variable.
If it complains about X libraries, add path to your X libraries
into LD_LIBRARY_PATH.
If you are using csh, you can set it like:
setenv LD_LIBRARY_PATH <paths>
If you are using sh, you can set it like:
export LD_LIBRARY_PATH=<paths>
(2) You MUST put /home/marwa/ns-allinone-2.31/tcl8.4.14/library into your TCL_LIBRARY environmental
variable. Otherwise ns/nam will complain during startup.
After these steps, you can now run the ns validation suite with
cd ns-2.31; ./validate
sorry for asking again, but what i need now is only to remove the path from the .bashcr file? then i run this command again or not
"source .bashrc" ?
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511
Rep:
Re #28 , the last century text, ~1999 ...
Please put .... ,, IMPORTANT NOTICES: You MUST put ..
.. was meant only for a "University Computer" :
.. i.e. when you had no write permissions to /usr/local/ : No # make install .
NS-2 is old. A lot of files still have leftover from the ninetieth.
So don't believe everything you read in the files or on the Internet.
$ source .bashrc
... is for adding stuff. Editing :
$ gedit .bashrc
.... ( Or whatever editor you prefer.)
I thought that the commande source is necessary after any modification in the .bashrc file ( i mean for the changes to take effect) .
So it is sufficient to do gedit .bashrc and save the file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.