Re: 2.6.25-rc2: Reported regressions from 2.6.24

["Alexey Dobriyan" <adobriyan@gmail.com>]

On 2/18/08, Jiri Slaby <jirislaby@gmail.com> wrote:
> On 02/18/2008 10:49 AM, Ingo Molnar wrote:
> > * Alexey Dobriyan <adobriyan@gmail.com> wrote:
> >
> >> Why on earth do we have CONFIG_SYSFS_DEPRECATED at all if the only
> >> sane choice for someone who tests new kernels is to always turn it on?
> >
> > seconded ...
> >
> > it's insane how inconvenient certain storage systems are to use, and
> > people get turned away with NOATBUG. ITISABUG every time user-space
> > breaks or the user has to do _anything_ to get the box working as it
> > should.
>
> No, user needn't to do anything. Just turn that default y option really to y

Suprise, surprise, make oldconfig won't tell you anything about defaults
because you already turned it off moons ago.

> (yes, you are right, the help text of this option is misleading...).

Agree, reference to 2006 is particularly pathetic, given that breakage
happened on recent fedora (sorry, box was reinstalled since then,
I can't recall which fedora exactly).

> It's like you turn off old acpi events option and scream that you acpi daemon
> doesn't work  for instance.
> There are many instances of this behaviour in the kernel.

Indeed, but don't mix types of breakage, please.
You can turn off ACPI or CPU_FREQ or SMP and forget.
You can't turn off SYSFS_DEPRECATED and forget.

> And yes, many people don't need that option tuyrned on --

Wish them luck.

/me goes on thinking about cpufreqfs to eventually turn off SYSFS
completely.