SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
But I have to ask, did anyone suggest/give feedback about using 2.6.32.x while 13.1 was still in the oven?
2.6.33 first appeared as part of the massive March 1st update which came out of the blue after a complete month of inactivity on the changelog. It came as a complete surprise to me as .33 was still very new at that point and I certainly wasn't expecting it to hit current: Slackware has traditionally tended to favor proven component versions and I really expected 13.1 to go-live with the most recent of the .32 kernel branch.
In addition to the new kernel version, that March 1st bulk update included rebuilds/updates of libc (presumably against the .33 headers) and a whole heap of other libraries and application packages which would have had to be thrown away and rebuilt again against .32 in order to revert. Pat wouldn't have abandoned all that work without a very strong argument for doing so, and at that point, other than the general wisdom of not living on the bleeding edge I don't think anyone had enough experience of the .33 branch to make the argument.