From: David KOENIG <karhudever@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Albert Cahalan <acahalan@gmail.com>
Subject: Re: sysctl
Date: Wed, 18 Oct 2006 11:27:29 -0700 [thread overview]
Message-ID: <45367211.7060802@gmail.com> (raw)
In-Reply-To: <787b0d920610181123q1848693ajccf7a91567e54227@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Albert Cahalan wrote:
> In the wireless-extensions thread, Linus writes:
>
>> In general, the answer to "when can we break user space" is very simple.
>>
>> Never.
>>
>> It's just not acceptable. We maintain old interfaces for years (and in
>> some cases, well over a decade by now), simply because the pain from not
>> doing so is horrendous, and it makes debugging impossible. You get into
>> situations where users need to upgrade to tools that don't work with
>> older
>> kernels, and can thus not downgrade, etc etc.
>
> I guess the sysctl question has been answered then,
> especially since random normal apps use sysctl.
>
> If it needs a maintainer, put me down.
>
> I think the main problem was fixed long ago,
> by assigning fixed numbers to the enum values.
> Practically no other kernel code uses an enum
> for an ABI, and I think we can see why.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
How about rewriting sysctl so that it refers to the real way (with /proc)?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFNnIQmhCgVPlWJY8RAiTCAKDUtO4L7XqWo7+vC2vlhltdcb/L3ACfXSeM
Ii48VQu3334MkrGc23StPSA=
=pcCo
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-10-18 18:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 18:23 sysctl Albert Cahalan
2006-10-18 18:27 ` David KOENIG [this message]
2006-10-18 18:31 ` sysctl Linus Torvalds
2006-10-18 18:52 ` sysctl Cal Peake
2006-10-18 19:12 ` sysctl Olaf Hering
2006-10-18 19:44 ` sysctl Andrew Morton
2006-10-18 21:06 ` sysctl Cal Peake
2006-10-19 4:41 ` [RFC] [PATCH] Improve the remove sysctl warnings Eric W. Biederman
2006-10-19 16:25 ` Cal Peake
2006-10-19 19:50 ` Alexey Dobriyan
2006-10-19 19:55 ` Cal Peake
2006-10-20 7:05 ` [CFT] Grep to find users of sys_sysctl Eric W. Biederman
2006-10-20 7:35 ` Andrew Morton
2006-10-20 12:54 ` Eric W. Biederman
2006-10-20 16:39 ` Andrew Morton
2006-10-21 10:23 ` Eric W. Biederman
2006-10-20 7:52 ` Russell King
2006-10-20 14:38 ` Eric W. Biederman
2006-10-20 15:18 ` Albert Cahalan
2006-10-21 10:53 ` Eric W. Biederman
2006-10-20 15:46 ` Bill Nottingham
2006-10-20 8:02 ` Jakub Jelinek
2006-10-20 13:41 ` Eric W. Biederman
2006-10-20 17:54 ` Marco Roeland
-- strict thread matches above, loose matches on Subject: below --
2001-04-01 10:48 sysctl Subba Rao
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=45367211.7060802@gmail.com \
--to=karhudever@gmail.com \
--cc=acahalan@gmail.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 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.