Messages in this thread | | | Date | Mon, 10 May 2004 17:14:13 -0700 | From | Andrew Morton <> | Subject | Re: 2.6.6-mm1 |
| |
Chris Wedgwood <cw@f00f.org> wrote: > > On Mon, May 10, 2004 at 04:51:32PM -0700, Andrew Morton wrote: > > > Maybe that's the price we pay for leaving this problem unsolved for > > a year. > > I didn't know it needed solving until recently. I guess I've been > under a rock or something then.
It has stagnated. I think the mindset has been "oh, we need to ship a hack because upstream is bust" and so nobody did anything.
> > You misunderstand. Nasty workarounds will be shipped to end users > > by vendors. That's a certainty. We cannot change this now. > > Vendors will support this too presumably. > > > What I wish to do is to ensure that all users receive the *same* > > nasty workaround. Call it damage control. > > How urgent is this? Can it wait a few more weeks? It seems people > are new looking at this and a little more discussion won't hurt if > it's been a year already. >
Migrating away from this will require work from vendors, Oracle, PAM developers, /bin/login and /bin/su developers. Until that has happened I think we should arrange for vendor kernels and kernel.org kernels to offer the same interfaces.
And I don't think pulling the feature out of kernel.org kernels will provide any added stimulus, frankly. They'll just ship the hack and go off to do something else.
If someone had done the kernel and userspace work 6-12 months ago then sure, we wouldn't be in this situation.
As to whether it is practical to jam all this work through at this stage: dunno, really. I doubt it. It would be good to try though. - 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/
| |