From: Theodore Tso <tytso@mit.edu>
To: Greg KH <greg@kroah.com>
Cc: Bron Gondwana <brong@fastmail.fm>, Matt Mackall <mpm@selenic.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
yi.zhu@intel.com, jketreno@linux.intel.com, akpm@osdl.org
Subject: Re: Recent wireless breakage (ipw2200, iwconfig, NetworkManager)
Date: Mon, 5 Mar 2007 19:56:25 -0500 [thread overview]
Message-ID: <20070306005625.GC19634@thunk.org> (raw)
In-Reply-To: <20070306003715.GA12566@kroah.com>
On Mon, Mar 05, 2007 at 04:37:15PM -0800, Greg KH wrote:
> But I AM TRYING TO MAKE IT COMPATIBLE!!!
>
> That's what that config option is there for. If you happen to be
> running a newer userspace, a different distro than what is in Debian
> right now, or don't use HAL and Networkmanager, then disable that
> option. Then all of sysfs looks just like it used to, no user visble
> changes at all. It doesn't get any more compatible than that.
This is great, but I think the real problem isn't the config option,
but what is changing if the config option isn't enabled. The claim
which some, including Matt and Bron, seem to be making is that if you
turn *off* CONFIG_SYSFS_DEPRECATED, you must be using at least hal
0.5.9-rc1, released ***yesterday***, or suffer breakages for at least
some system configurations.
So the problem with putting a date in Kconfig.txt help file, or in
Documentation/feature-removal-schedule.txt, is that if there are other
incompatible changes which are added to sysfs in say, December 2007 or
January 2008, but which are papered over with CONFIG_SYSFS_DEPRECATED,
and then come June 2008, CONFIG_SYSFS_DEPRECATED is unceremoniously
ripped out, then users will get screwed.
So the question really is are we really done making changes to sysfs,
or maybe what we should do is talk about major version numbers to
sysfs. Call what we have currently not CONFIG_SYSFS_DEPRECATED, but
rather CONFIG_SYSFS_LAYOUT_1. At the moment, CONFIG_SYSFS_LAYOUT_2 is
undergoing changes, but at some point we need to lock down and state
that Layout version 2 is never going to change, and then people who
want changes can go work on CONFIG_SYSFS_LAYOUT_3.
The problem with calling CONFIG_SYSFS_DEPRECATED is that people think
that since it's deprecated, it should be turned off, but if we have
staged major version numbers, with guarantees of absolute stability
once a particular major version number is locked down, then it may
make it a lot easier to talk about what version of hal and udev and
Network Manager is really needed for different versions.
- Ted
next prev parent reply other threads:[~2007-03-06 0:56 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 22:08 Recent wireless breakage (ipw2200, iwconfig, NetworkManager) Matt Mackall
[not found] ` <20070304220857.GH23311-1tnLUEbcrg3YtjvyW6yDsg@public.gmane.org>
2007-03-04 23:39 ` Johannes Berg
2007-03-05 0:25 ` Matt Mackall
[not found] ` <20070305002550.GI23311-1tnLUEbcrg3YtjvyW6yDsg@public.gmane.org>
2007-03-05 0:45 ` Andrew Morton
[not found] ` <20070304164525.349f9589.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2007-03-05 1:05 ` Adrian Bunk
2007-03-05 0:46 ` Ian McDonald
2007-03-05 1:17 ` Greg KH
[not found] ` <20070305011729.GB7681-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2007-03-05 11:20 ` Johannes Berg
2007-03-05 12:59 ` Theodore Tso
2007-03-05 18:58 ` Greg KH
2007-03-05 19:55 ` Matt Mackall
2007-03-05 22:39 ` Greg KH
[not found] ` <20070305223900.GA7676-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2007-03-06 3:07 ` Matthew Garrett
2007-03-05 23:05 ` Jeffrey Hundstad
[not found] ` <20070305185813.GA31465-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2007-03-05 23:40 ` [2.6.21 patch] unconditionally enable SYSFS_DEPRECATED Adrian Bunk
[not found] ` <20070305234052.GR3441-HeJ8Db2Gnd6zQB+pC5nmwQ@public.gmane.org>
2007-03-06 0:07 ` Greg KH
[not found] ` <20070306000722.GA11436-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2007-03-06 0:35 ` Adrian Bunk
[not found] ` <20070306003541.GT3441-HeJ8Db2Gnd6zQB+pC5nmwQ@public.gmane.org>
2007-03-06 0:41 ` Greg KH
2007-03-06 1:30 ` Matt Mackall
[not found] ` <20070306013020.GN23311-1tnLUEbcrg3YtjvyW6yDsg@public.gmane.org>
2007-03-06 1:56 ` Greg KH
2007-03-06 13:20 ` Johannes Berg
2007-03-06 15:55 ` Dan Williams
2007-03-06 2:48 ` Greg KH
[not found] ` <20070306024850.GA24477-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2007-03-06 3:04 ` Matt Mackall
2007-03-06 3:39 ` Matt Mackall
[not found] ` <20070306033947.GQ23311-1tnLUEbcrg3YtjvyW6yDsg@public.gmane.org>
2007-03-06 4:03 ` Greg KH
[not found] ` <20070306040350.GA25783-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2007-03-06 6:10 ` Matt Mackall
2007-03-06 19:01 ` Greg KH
[not found] ` <20070306061009.GR23311-1tnLUEbcrg3YtjvyW6yDsg@public.gmane.org>
2007-03-06 20:05 ` Greg KH
2007-03-06 0:35 ` Recent wireless breakage (ipw2200, iwconfig, NetworkManager) Johannes Berg
2007-03-05 1:16 ` Greg KH
2007-03-05 6:42 ` Matt Mackall
2007-03-05 7:02 ` Greg KH
2007-03-05 7:13 ` Matt Mackall
2007-03-05 15:46 ` Tomasz Torcz
2007-03-05 21:14 ` Matt Mackall
2007-03-06 0:24 ` Bron Gondwana
2007-03-06 0:37 ` Greg KH
2007-03-06 0:56 ` Theodore Tso [this message]
2007-03-06 1:08 ` Andrew Morton
2007-03-06 1:17 ` Greg KH
2007-03-06 1:38 ` Andrew Morton
2007-03-06 1:10 ` Greg KH
2007-03-05 21:58 ` Joel Becker
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=20070306005625.GC19634@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@osdl.org \
--cc=brong@fastmail.fm \
--cc=greg@kroah.com \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.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;
as well as URLs for NNTP newsgroup(s).