[added CCs from the other thread on this topic] Alasdair G Kergon schrieb:
On Sat, Feb 16, 2008 at 11:37:37PM +0100, Jiri Slaby wrote:# CONFIG_SYSFS_DEPRECATED is not setIMHO That should be *set* by default until everyone has had time to update their userspace software to cope with the changed sysfs layout.
It *is* set by default. The root cause of the trouble is that its semantics are changing. At one point in time (sorry, don't remember which kernel release exactly) I tested whether the openSUSE 10.3 userspace supported a CONFIG_SYSFS_DEPRECATED=n kernel and found that it did. From then on, "make oldconfig" would carry that setting over to every new kernel I built, which was fine while the meaning of this setting - ie. the difference in sysfs layout it controlled - stayed the same. With commit edfaa7c36574f1bf09c65ad602412db9da5f96bf however, the sysfs layout changed again, so the same CONFIG_SYSFS_DEPRECATED setting now controls a different difference (argh) in sysfs layout. That kind of situation is not handled very well by "make oldconfig", which basically starts from the assumption that a setting that was ok for the previous kernel version is still ok for the new one. I see two ways of avoiding that problem: either create a new backward compatibility config setting for that new sysfs change, or create a way of telling "make oldconfig" that the semantics of CONFIG_SYSFS_DEPRECATED have changed and it should ask the user for that again even if there is a previous setting. HTH T. -- Tilman Schmidt E-Mail: [EMAIL PROTECTED] Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
signature.asc
Description: OpenPGP digital signature
