From: Willy Tarreau <w@1wt.eu>
To: Joe Pranevich <jpranevich@gmail.com>
Cc: Mike Frysinger <vapier.adi@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 3.0 change listings - Wonderful World of Linux 3.0
Date: Tue, 31 May 2011 22:13:48 +0200 [thread overview]
Message-ID: <20110531201348.GA8723@1wt.eu> (raw)
In-Reply-To: <BANLkTim7XZKLCRp=ZtRJWhi7k4BzwYpRpg@mail.gmail.com>
On Tue, May 31, 2011 at 01:22:49AM -0400, Joe Pranevich wrote:
> Mike,
>
> Thank you. I appreciate the comments and the corrections. It was a
> marathon weekend and yes, I missed some obvious typos. Thanks.
>
> As far as what is supported and when, my rule has been that if it is
> labeled as "experimental", then it isn't released. So, that accounts
> for why I didn't list NFSd v4 in this doc, even though there is a
> module for it. (I should make this more clear though.) Similarly, I
> *do* list IPv6 as new. It was listed as experimental in v2.6.0, so
> that qualifies it for inclusion here.
Many things have been marked experimental for years and remained like
this just because nobody cared to change the comment in the Kconfig
or config.in. But Mike is right :
willy@fw:willy$ ip -6 a s dev eth0
3: eth0: <BROADCAST,MULTICAST,UP> qlen 1000
inet6 2001:7a8:363c::1/64 scope global
inet6 fe80::280:c8ff:feca:d2b9/64 scope link
willy@fw:willy$ uname -a
Linux fw 2.4.37-wt3-fw #1 Sun Jan 31 00:55:16 CET 2010 i686 unknown unknown GNU/Linux
willy@fw:willy$
And this machine was installed with something like 2.4.22 ten years ago.
It's quite awkward to announce as "new" something that has been running
in production at many places for ten years. It will sensibly discredit
your article.
I'd say that in general, almost all of the features you're announcing as
"new" will make unaware people think that older versions did not have
those features, which is quite misleading. Linus took great care to say
that 3.0-rc1 had very few changes, it can be a bit confusing to see a
post pretending it to be a revolutionary new kernel.
Probably that you should more clearly say that all those features were
progressively added in all 2.6 releases, otherwise I'm already expecting
to see a lot of idiocies posted in journals.
Regards,
Willy
next prev parent reply other threads:[~2011-05-31 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 19:59 Linux 3.0 change listings - Wonderful World of Linux 3.0 Joe Pranevich
2011-05-31 3:16 ` Mike Frysinger
2011-05-31 5:22 ` Joe Pranevich
2011-05-31 5:48 ` david
2011-05-31 20:13 ` Willy Tarreau [this message]
2011-06-01 17:47 ` Calvin Walton
2011-06-02 0:03 ` Joe Pranevich
2011-05-31 15:23 ` Konrad Rzeszutek Wilk
2011-06-03 7:01 ` Jiri Slaby
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=20110531201348.GA8723@1wt.eu \
--to=w@1wt.eu \
--cc=jpranevich@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@gmail.com \
/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