> >> adequate job of warning our users. A printk when we run a program > >> that uses the binary interface and an long enough interval the warning > >> makes it to the Enterprise kernels before we remove the interface > >> should be sufficient.
The enterprise products will probably just remove the printk. Even if they didn't you are looking at ten years before things finish changing based on current experiences, probably longer as things stabilize. The whole "whine a bit" process simply doesn't work when you are trying to persuade people to move in a non-hobbyist context. They don't want to move, the message is simply an annoyance, their upstream huge package vendor won't change just to deal with it and they'll class it as a regression from previous releases, an incompatibility and file bugs until it goes away. Its user ABI and as Linus said - we don't break it. Trimming down all the crap that never worked via sysctl is one thing, not putting sysctl in new platforms likewise. Trying to undo it isn't going to work Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
