From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] LARTC Wiki
Date: Wed, 24 Jan 2007 03:34:31 +0000 [thread overview]
Message-ID: <45B6D3C7.A08E3232@iswest.com> (raw)
In-Reply-To: <92ed523b0701230746x242726b1w123782b4ff9ea53d@mail.gmail.com>
Mark Krenz wrote:
>
> I also think that this would be a good idea. Having examples rulesets
> and related firewall and QOS stuff.
>
> On Tue, Jan 23, 2007 at 03:53:23PM GMT, Andrew Beverley [andy@andybev.com] said the following:
> > I'm not aware of one, and I think it's an excellent idea.
> >
> > There's some great software available for LARTC, and some of the
> > documentation is very good, but unfortunately it's all a bit disparate.
> > A wiki would be a great start.
> >
> > I'd be happy to host one and transfer stuff into it unless someone else
> > has a better idea/offer?
> >
> > Andy Beverley
> >
> >
> > On Tue, 2007-01-23 at 12:46 -0300, Marco Aurelio wrote:
> > > Hi all,
> > >
> > > Since the mail list receives a lot of repeated subjects (for example:
> > > "i have two adsl lines..."), maybe these specific issues should be
> > > treated on the LARTC Guide, or maybe if we had an wiki?
> > >
> > > Is there a LARTC Wiki?
> > >
> > > If not, what do you think about creating one?
> > >
> > > Thanks
> > >
> > > --
> > > Marco
The existing wiki is at http://linux-net.osdl.org
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-01-24 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 15:46 [LARTC] LARTC Wiki Marco Aurelio
2007-01-23 15:49 ` Jordi Segues
2007-01-23 15:53 ` Andrew Beverley
2007-01-23 15:54 ` Mark Krenz
2007-01-23 20:13 ` Alex Samad
2007-01-23 22:09 ` Tiago Bruno Espírito Santo Silva
2007-01-24 3:34 ` gypsy [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=45B6D3C7.A08E3232@iswest.com \
--to=gypsy@iswest.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.