From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysctl: Deprecate sys_sysctl in a user space visible fashion.
Date: Wed, 29 Aug 2007 11:46:04 +0100 [thread overview]
Message-ID: <20070829114604.242b976c@the-village.bc.nu> (raw)
In-Reply-To: <m1d4x7aysz.fsf@ebiederm.dsl.xmission.com>
> >> adequate job of warning our users. A printk when we run a program
> >> that uses the binary interface and an long enough interval the warning
> >> makes it to the Enterprise kernels before we remove the interface
> >> should be sufficient.
The enterprise products will probably just remove the printk. Even if
they didn't you are looking at ten years before things finish changing
based on current experiences, probably longer as things stabilize.
The whole "whine a bit" process simply doesn't work when you are trying
to persuade people to move in a non-hobbyist context. They don't want to
move, the message is simply an annoyance, their upstream huge package
vendor won't change just to deal with it and they'll class it as a
regression from previous releases, an incompatibility and file bugs until
it goes away.
Its user ABI and as Linus said - we don't break it. Trimming down all the
crap that never worked via sysctl is one thing, not putting sysctl in new
platforms likewise. Trying to undo it isn't going to work
Alan
next prev parent reply other threads:[~2007-08-29 10:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 22:40 Eric W. Biederman
2007-08-28 23:04 ` Christoph Hellwig
2007-08-28 23:53 ` Eric W. Biederman
2007-08-29 1:31 ` H. Peter Anvin
2007-08-29 1:56 ` Eric W. Biederman
2007-08-29 10:46 ` Alan Cox [this message]
2007-08-29 17:16 ` Eric W. Biederman
2007-08-29 17:28 ` H. Peter Anvin
2007-08-29 19:00 ` Eric W. Biederman
2007-08-30 12:13 ` Theodore Tso
2007-08-30 13:20 ` David Newall
2007-08-30 17:40 ` Eric W. Biederman
2007-08-29 22:51 ` Andrew Morton
2007-08-30 19:32 ` Rob Landley
2007-08-30 18:34 ` Christoph Hellwig
2007-08-30 18:57 ` Eric W. Biederman
2007-08-30 23:22 ` Rob Landley
2007-09-01 22:16 ` Andi Kleen
2007-09-02 8:44 ` Rob Landley
2007-09-02 8:54 ` H. Peter Anvin
2007-09-02 11:05 ` Rob Landley
2007-09-02 19:56 ` Eric W. Biederman
2007-09-02 20:00 ` Al Viro
2007-09-02 21:51 ` Eric W. Biederman
2007-09-03 8:37 ` Andi Kleen
2007-09-03 9:16 ` Al Viro
2007-08-29 4:49 ` Andrew Morton
2007-08-30 18:56 ` Jan Engelhardt
2007-08-29 4:49 ` Andrew Morton
2007-08-29 5:24 ` Eric W. Biederman
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=20070829114604.242b976c@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®