[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1162280182.6416.16.camel@Homer.simpson.net>
Date: Tue, 31 Oct 2006 08:36:22 +0100
From: Mike Galbraith <efault@....de>
To: Greg KH <gregkh@...e.de>
Cc: "Martin J. Bligh" <mbligh@...gle.com>,
Cornelia Huck <cornelia.huck@...ibm.com>,
Andy Whitcroft <apw@...dowen.org>,
Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
Steve Fox <drfickle@...ibm.com>
Subject: Re: 2.6.19-rc3-mm1 -- missing network adaptors
On Mon, 2006-10-30 at 22:59 -0800, Greg KH wrote:
> On Mon, Oct 30, 2006 at 10:37:47PM -0800, Martin J. Bligh wrote:
> > Mike Galbraith wrote:
> > >On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
> > >
> > >>Maybe the initscripts have problems coping with the new layout
> > >>(symlinks instead of real devices)?
> > >
> > >SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
> > >follow symlinks (bounces off symlink and does nutty stuff instead). If
> > >any of the boxen you're having troubles with use libsysfs in their init
> > >stuff, that's likely the problem.
> >
> > If that is what's happening, then the problem is breaking previously
> > working boxes by changing a userspace API. I don't know exactly which
> > patch broke it, but reverting all Greg's patches (except USB) from
> > -mm fixes the issue.
>
> Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> all work just fine. Doesn't anyone read the Kconfig help entries for
> new kernel options?
There's another thread concerning that kaboom, and I think the culprit
is known?
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists