From: Rogerio Brito <rbrito@iname.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Suggestion to the Advanced Routing HOWTO
Date: Sun, 18 Mar 2001 19:40:17 +0000 [thread overview]
Message-ID: <marc-lartc-98494447130096@msgid-missing> (raw)
I'd like to make a suggestion to the Advanced Routing HOWTO. I
have read parts of it some months ago and I had a hard time
following it and I think that I know the reason: the HOWTO
doesn't give the background on the subjects it discusses.
This difficulty was particularly evident when I was reading
the part about Quality of Service/Bandwidth Shaping. I got the
impression of that section of the HOWTO being a handful of
commands, with arguments that I didn't understand completely
(and often asked myself if they were important or why they
were important).
Especially the *why* questions I asked myself are an
indication that I lack the background of the mechanics of
setting a QoS based service (of course, I would not ask myself
why if I were already convinced of the importance of any
command or argument).
So, here is my input: if possible, please, include a bit of
theory behind the concepts, so the readers of the document get
the big picture before going to the technicalities.
If more information about my doubts is needed, please let me
know and I'll gladly answer, if I can help make this document
better for the community.
Thank you very much, Roger...
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rogerio Brito - rbrito@iname.com - http://www.ime.usp.br/~rbrito/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-03-18 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-18 19:40 Rogerio Brito [this message]
2001-03-19 12:59 ` [LARTC] Suggestion to the Advanced Routing HOWTO bert hubert
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-98494447130096@msgid-missing \
--to=rbrito@iname.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.