From: Philip Prindeville <philipp@redfish-solutions.com>
To: "Niccolò Belli" <darkbasic@linuxsystems.it>
Cc: lartc@vger.kernel.org,
"netfilter@vger.kernel.org" <netfilter@vger.kernel.org>,
Linux Networking Developer Mailing List <netdev@vger.kernel.org>
Subject: Re: [Announce] LARTC wiki available
Date: Sun, 03 Jun 2012 14:05:20 -0600 [thread overview]
Message-ID: <4FCBC380.8050704@redfish-solutions.com> (raw)
In-Reply-To: <4EFB3B2B.7060200@linuxsystems.it>
On 12/28/11 8:52 AM, Niccolò Belli wrote:
> Hi,
> I still didn't find a viable solution for the LARTC wiki, so I decided
> to start hosting it on my own server. Later we can easily switch
> somewhere else if we keep using the same wiki engine (and maybe even
> with another wiki engine).
> I decided to use wikimedia because it's the only one I know of, so if
> someone knows a better alternative please let me know, we are still in
> time for a change.
> Since I never used a wiki seriously I will probably need someone else
> who can help me maintaining it, please let me know if you are
> experienced and willing to help.
>
> Here is the wiki: http://lartc.linuxsystems.it/
> And here is the new mailing list for those who still don't know:
> http://vger.kernel.org/vger-lists.html#lartc
>
> I just copy-pasted the Linux Advanced Routing & Traffic Control HOWTO
> atm, it still needs to be wikified and we still need to choose how to
> organize the contents.
>
> Cheers,
> Niccolò
Between command-line stuff for users/administrators and the kernel hacking bits on linux-net, etc. I'd like to see a middle ground: i.e. better documentation about the C API to userspace from the kernel routing mechanisms.
Better documentation about rtnetlink would be appreciated, and maybe the low-level libraries that run atop that as well, such as libmnl.
-Philip
prev parent reply other threads:[~2012-06-03 20:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 15:52 [Announce] LARTC wiki available Niccolò Belli
2011-12-29 0:27 ` Hagen Paul Pfeifer
2011-12-29 9:37 ` Niccolò Belli
2011-12-29 16:19 ` Hagen Paul Pfeifer
2011-12-29 17:13 ` Niccolò Belli
2011-12-29 19:04 ` John A. Sullivan III
2012-01-02 12:48 ` Ed W
2012-01-02 13:07 ` Niccolò Belli
2012-06-01 16:42 ` Niccolò Belli
2012-06-01 19:12 ` Julien Vehent
2012-06-02 14:37 ` Andy Furniss
2012-06-02 14:43 ` Andy Furniss
2012-06-02 15:50 ` Eric Dumazet
2012-06-02 16:58 ` Andy Furniss
2012-06-03 2:36 ` Jesper Dangaard Brouer
2012-06-03 20:05 ` Philip Prindeville [this message]
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=4FCBC380.8050704@redfish-solutions.com \
--to=philipp@redfish-solutions.com \
--cc=darkbasic@linuxsystems.it \
--cc=lartc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).