As I have already stated in a past e-mail to the list:

>--
The tutorial should be updated! I'm not telling that Mark should do that,
no, but someone on this list should update it!
If I had the qualification, I would volunteer. Unfortunately, I am not
qualified to the work.

an idea:
1- as ns has several release #s (2.30, 2.31...) Mark's Tutorial should also
has a corresponding number (2.30, 2.31 respectively), indicating its
correspondence to ns. I think the modifications to the Tutorial between ns
versions would not be very hard.
2- as many people use the Tutorial to get introduced to ns, why ns
developers don't assume this job (only if Mark doesn't oppose to the idea)?


kindly regards,

Marcos



>--

2007/8/14, Raphael <[EMAIL PROTECTED]>:
>
>
>
> On Tuesday 14 August 2007 06:01:25 you wrote:
> > Hi Mr.Rapheal,
> >
> > Conform the following steps:
> >
> > 1. Had you run "makedepend" before "make"
> > 2. Had you binded the variable "off_ping_" in the constructor.
> That's the problem I had and the point which is wrong in the tutorial (at
> least for ns-2.31).
> Thx for the tip!
>
> > 3. Had you modified "ns-allinone-2.31/ns-2.31/tcl/lib/ns-packet.tcl". we
> > should include one line for "myProto" in "foreach port {...... myProto,
> > ......} { add-packet-header $prot}" loop. 4. And finally last but not
> > least, you might compiled by having a saperate copy. $ns <filename>.tcl
> > ---- will run by taking default path of ns
> >   $/<directory of modified ns>/ns-allinone-2.31/ns-2.31/ns
> <filename>.tcl
> > ---  will run the code  with modified ns.
> >
> >
> > byeeeeeeeeeeeeeee,
> >   Have A Nice Day,
> > Ajay Kumar Patibandla.
> >
> >
> >
> >
> >       5, 50, 500, 5000 - Store unlimited mails in your inbox. Go to
> > http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html
>
>
>
>


-- 
--------------------------------------------------------
Prof. Dr. Marcos Antônio Cavenaghi < [EMAIL PROTECTED]>
UNESP - Sao Paulo State University
Phone: +55 14 3103 6079 || Fax: +55 14 3103 6034
--------------------------------------------------------

Reply via email to