From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Anti-CBQ Statements in Howto
Date: Thu, 06 Dec 2001 20:30:47 +0000 [thread overview]
Message-ID: <marc-lartc-100767069231496@msgid-missing> (raw)
I find the negative attitude toward CBQ to be distracting and
non-professional in the HOWTO. I've re-read it for the first time in
about a month and comments like "This can be configured in a variety of
ways, which I do not understand. Use HTB" do not encourage me about the
writer.
This is not a personal critique, as I can imagine this being said on a
personal website, but as a generic HOWTO, this is out of place. A
statement like "if you don't understand these options, you may find HTB
to be easier to follow" is professional and possibly more accurate.
I've seen other documents that describe the options the author says he
doesn't understand whose authors like CBQ and/or believe it to be
well-designed. I've had no real problems with it and don't actually
see HTB as being easier to configure or follow if you leave the 'knobs'
on CBQ to their suggested defaults.
Just my $0.02 worth (actually $1 in paid time to type this).
--
Michael T. Babcock
CTO, FibreSpeed Ltd. (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
_______________________________________________
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-12-06 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 20:30 Michael T. Babcock [this message]
2001-12-06 21:01 ` [LARTC] Anti-CBQ Statements in Howto bert hubert
2001-12-06 21:17 ` Michael T. Babcock
2001-12-06 22:58 ` 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-100767069231496@msgid-missing \
--to=mbabcock@fibrespeed.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.