public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] Performance leaks with passive network interface cards
Date: Tue, 14 Feb 2012 20:09:27 +0100	[thread overview]
Message-ID: <1329246567.2003.11.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <4F3AA3A6.80506@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]

Hi,

I would like to see the "we recommend" message changed. It is much
better to write "which hardware is worth a recommendation" because there
is no "we".

An also not so good point is the table at the bottom of the page. It
would be much better to add this information to the table over here
(http://wiki.ipfire.org/en/hardware/networking). It is not very easy to
maintain redundant information and it is also not very easy for the user
to join all this information together. You know what I mean...

Another side node would also be interesting. You should consider adding
this: Vendors of hardware with controller chips provide their own
drivers in the kernel (Intel, etc.). Most of the cheaper ones do not and
so the quality is not as good as the first ones.

Michael

On Tue, 2012-02-14 at 19:10 +0100, WhyTea wrote:
> Hi again!
> 
> I've imported the german and the english version into the wiki.
> 
> http://wiki.ipfire.org/de/hardware/passivenics
> http://wiki.ipfire.org/en/hardware/passivenics
> 
> Please take a look.
> 
> - Daniel
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation


  reply	other threads:[~2012-02-14 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 18:10 WhyTea
2012-02-14 19:09 ` Michael Tremer [this message]
2012-02-15  7:30   ` Daniel Weismüller
2012-02-15 10:59     ` Michael Tremer

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=1329246567.2003.11.camel@rice-oxley.tremer.info \
    --to=michael.tremer@ipfire.org \
    --cc=documentation@lists.ipfire.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