From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: [LARTC] ANNOUNCE: guide to linux IP; basics through iproute2/LARTC topics
Date: Fri, 20 Sep 2002 23:36:36 +0000 [thread overview]
Message-ID: <marc-lartc-103256505727905@msgid-missing> (raw)
Hello all,
I have been working on a guide to IP networking with linux for some time
now, and have been putting off announcing this project for no good reason.
A colleague has suggested that I might benefit from following the open
source credo, (release early, release often). In this spirit, let me
state that the document is still only draft quality, and I would welcome
contributions, suggestions and feedback.
I am announcing my:
Guide to IP Layer Network Administration with Linux
http://plorf.net/linux-ip/
This is intended to be a companion guide and HOWTO for simple host
networking configuration to complex multi-link routers. I have spent my
recent efforts providing examples and English descriptions of many of the
iproute2 tools and other common command line utilities used in IP
networking. This is meant to be an adjunct and companion to the existing
documentation such as ip-cref.ps and man pages for the other command line
tools.
Currently the majority of the content is in the appendices covering the
most common types of operations performed with command line tools and
utilities.
I look forward to any criticism, feedback or suggestions from anybody.
Thanks in advance for any time you may spend looking at this work.
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-09-20 23:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-103256505727905@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.