Date: Thu, 7 Jun 2007 09:15:25 -0700
From: Greg KH <gregkh@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Jones <pjones@redhat.com>, Kay Sievers <kay.sievers@vrfy.org>,
       Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
       linux-kernel@vger.kernel.org
Subject: Re: 2.6.22-rc4-mm1
Message-ID: <20070607161525.GA18363@suse.de>
References: <1181168095.3612.4.camel@lov.localdomain> <4667C47C.2010207@googlemail.com> <1181206091.3625.9.camel@lov.localdomain> <4667D2DF.30207@googlemail.com> <1181228660.3625.23.camel@lov.localdomain> <46682385.1060802@redhat.com> <20070607154342.GA16911@suse.de> <20070607085200.f8d6e2d3.akpm@linux-foundation.org> <20070607155953.GA17591@suse.de> <20070607090632.cfcf02e6.akpm@linux-foundation.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070607090632.cfcf02e6.akpm@linux-foundation.org>
User-Agent: Mutt/1.5.15 (2007-04-06)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2248
Lines: 58

On Thu, Jun 07, 2007 at 09:06:32AM -0700, Andrew Morton wrote:
> On Thu, 7 Jun 2007 08:59:53 -0700 Greg KH <gregkh@suse.de> wrote:
> 
> > On Thu, Jun 07, 2007 at 08:52:00AM -0700, Andrew Morton wrote:
> > > On Thu, 7 Jun 2007 08:43:42 -0700 Greg KH <gregkh@suse.de> wrote:
> > > 
> > > > >  Fixed in mkinitrd-6.0.9-6 , which I'll build now and push to 
> > > > >  updates-testing.  Thanks for getting my attention here.
> > > > 
> > > > Great, Andrew, can you please reenable the block-device patch that is in
> > > > my tree now that the problem has been solved?
> > > 
> > > I think we're screwed, aren't we?  Everyone needs to upgrade mkinitrd to be
> > > able to boot the kernel?  Not viable :(
> > > 
> > > For example, what about my two-year-old yellowdog machine?
> > 
> > Enable CONFIG_SYSFS_DEPRECATED and it should all work just fine.  That's
> > what Michal said worked for him.
> > 
> 
> Actually, it _was_ enabled.
> 
> Ho hum, I'll have a poke at it this evening.

Yeah, that sounds odd, it should have worked.

> So...  what's the story here?  Should our position be that
> CONFIG_SYSFS_DEPRECATED=n should only be used by distro kernel-builders,
> who are concurrently shipping userspace which can handle it?

Yes.

There are a number of distros out there right now who can support that
option disabled.  I'm pretty sure they are the following right now:
	Gentoo unstable (actually stable works now for me, but I'm not
			 going to guarantee it just yet...)
	Debian unstable (again stable might work, but I have not heard
			 any reports from testers.)
	openSUSE FACTORY (the 10.3 alpha releases)

and now it sounds like Red Hat rawhide will also work properly.

> And that these distros should (probably) set CONFIG_SYSFS_DEPRECATED=y
> in their update kernels for older distributions?

Yes, unless they have tested things and it all works properly (all old
usages of libsysfs need to be removed and 'odd' initrd scripts need to
be updated as in the case of Red Hat.)

thanks,

greg k-h
-
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/