Slack10.1

Originally posted by win32sux did pat say if it was gonna be like 2-3 weeks? a month? two months?? give us the scoop!! and how'd you get that email from him?? =)

Because I sent him one first :) I was wondering about the ETA of slackware 11, and this was his email back:


Usually it's "when it's done", but I'll tell you want I know. There are
just a few more things I'd like to get squared away in Slackware -current,
and then I'd like to release it as Slackware 10.1. This could be
relatively soon. The reason I'm considering this is that a lot of good
updates have taken place since 10.0 and it's in a pretty stable state
right now. It would be good to get it out before fully adopting the 2.6
kernel and starting to look at glibc with NPTL and other things that will
likely have a destabilizing effect. If I try to make those moves first it
would delay the next release for many more months.

Best regards,

Pat

It would be good to get it out before fully adopting the 2.6 kernel and starting to look at glibc with NPTL and other things that will likely have a destabilizing effect. If I try to make those moves first it would delay the next release for many more months.

Looks like it might be a good idea to move away from -current for a while as my main system and run -current as a separate test system. I was considering that anyway while I frig with the 2.6 kernel (still running 2.4.27).

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [slackware-security] libtiff (SSA:2004-305-02) New libtiff packages are available for Slackware 8.1, 9.0, 9.1, 10.1, and -current to fix security issues that could lead to application crashes, or possibly execution of arbitrary code. More details about this issue may be found in the Common Vulnerabilities and Exposures (CVE) database:

Note the red text above. At first I thought that was a mistake. Maybe it was, but still it shows the state of mind. Cheers to Slackware!