From: "Chris K Ellsworth" <cke@highlandshighspeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] newbie to shapin'
Date: Thu, 30 May 2002 18:25:51 +0000 [thread overview]
Message-ID: <marc-lartc-102278319313181@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102273784005041@msgid-missing>
first thing to remember is to limit on the outgoing network card and 2nd
look into either HTB or CBQ under TC.
also check out
www.docum.org
----- Original Message -----
From: "mdew" <mdew@orcon.net.nz>
To: "lartc" <lartc@mailman.ds9a.nl>
Sent: Wednesday, May 29, 2002 10:47 PM
Subject: [LARTC] newbie to shapin'
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-05-30 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 5:47 [LARTC] newbie to shapin' mdew
2002-05-30 18:25 ` Chris K Ellsworth [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=marc-lartc-102278319313181@msgid-missing \
--to=cke@highlandshighspeed.net \
--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.