[Xorp-users] Xorp documentation

[Ray Soucy]

For what its worth, I still have a pretty large XORP 1.6 deployment
and wanted a place to throw everything 1.6-related until I can migrate
to XORP.CT or we see XORP proper actively developed again.

I've included instructions for building on Ubuntu Server LTS 10.4
which should be easily adapted to your Linux of choice, along with
patches necessary to compile XORP in a post-GCC 4.4 world (along with
the Heiko patch)   I've also thrown up configuration examples
previously posted here.

http://www.soucy.org/xorp/

On a side note one of the things that's kept me from moving to CT has
been the configuration file syntax has changed, so it's now a manual
process to move over for 100+ devices.

I haven't had time to look through the archive.  But if anyone knows
of any "must have" patches I should include let me know and I'll add
them provided they're bug fixes and not functionality changes.

On Sat, Feb 26, 2011 at 4:20 PM, Ben Greear <greearb at candelatech.com> wrote:
> On 02/26/2011 05:15 AM, Pierre Lepropre wrote:
>>
>> Ben,
>>
>> As I was telling Ray, the wiki we're using is kind of an internal thing
>> and vastly incomplete (and maybe inaccurate for some stuff but I hope
>> not...).
>
> Looks good!  Your presentation slides are particularly nice.  Only problem
> I noticed is that they have SNMP listed in them, and it's been gone
> from Xorp for some time (and unlikely to ever return).
>
>> I guess the best subset of people would be the most experienced ones
>> with XORP (namely you, Ben ;-) ) if they wanna come in. I don't know,
>> it's kinda up to you guys. At the end of my master thesis, I personally
>> guarantee you that I will make everything in my power to transfer you
>> the whole content to upload it somewhere else.
>>
>> Here is the URL in case anybody is interested:
>> http://queen.run.montefiore.ulg.ac.be/~willemaers/doku-xorp/doku.php
>>
>> Please, Ben, do NOT put that URL on the xorp website, at least not yet.
>> I'd like to see how the community responds to that initiative and talk
>> about it with my direct supervisor.
>>
>> Regarding the documentation itself, I think most of it should be written
>> back from square one. Fixing things that have been fixed and then
>> refixed for so much time doesn't lead to an accurate and readable
>> documentation. Don't get wrong heh, I'm not blaming anyone on this, the
>> 1.6 documentation was already outdated at the time they released the
>> version.
>
> It always seems easier (and more fun) to do things from scratch, but often
> taking
> the time to do incremental improvements produces more long-term
> gain.  (You can get a re-write 90% done, at large effort, and
> run out of time/interest, and the end result is still less
> useful than the original funky documentation.)
>
> I'm personally not so interested in poking content into a wiki that I'm
> not 100% certain can be freely copied (ie, what if your project leaders
> decide to suddenly restrict access, or just turn off the servers).
> I would like to add your slide-show to the xorp.ct tree and web site
> if/when you give permission.  And I'll be happy to link to your page
> when you are ready.
>
> For the existing documentation, it's .tex files and found in
> xorp.ct/docs/*  I don't particularly know latex or ever tried to learn
> it, but it is not difficult to make changes to the existing text.
> You can build the postscript & pdf files with scons from the docs dir.
>
> The web docs are at:
> xorp.ct/www/html_src
>
> You 'compile' the web pages by typing 'make'
> in xorp.ct/www
> There is a script in xorp.ct/www/scripts/ that generates
> the html from the source pages.
>
> If anyone makes changes they'd like incorporated upstream, post
> the diffs to the mailing list and/or send them to me directly.
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>



-- 
Ray Soucy

Epic Communications Specialist

Phone: +1 (207) 561-3526

Networkmaine, a Unit of the University of Maine System
http://www.networkmaine.net/