Slackware 11 is Coming

ejd3 writes "In the slackware-current changelog Pat has stated that 'Although there's still quite a bit in the TODO queue here I'm making my steps carefully as -current is very stable, and I think it should ship as a stable 11.0 soon so that we can get back to the business of breaking things in -current. :-)' How much longer will the slackers have to wait?"

Comments

Re:Marketshare?

[cloudmaster]

I especially like the BSD style init system, it just makes sense

Yeah, having a bunch of scripts that call each other in an unclear order (unless you read all of the scripts) is a whole lot easier to understand than one directory - named after the current runlevel - full of scripts, all of which are run in the same order that ls shows them to you. "Hmmm, does lpr launch from rc.net1, rc.net2, or something else? When does nfs start relative to ssh?" The only "simple" thing about BSD-style init is that there's no scary case statement in the init scripts to handle the start and stop arguments, and no worrisome symlinks. I'd posit that, if someone doesn't know enough shell scripting to read (and maybe write) a case statement or make a symlink, perhaps they shouldn't be messing with the machine's init scripts. Just edit /etc/rc.local - both SysV and BSD use that one.

Re:No need to wait

[Bert64]

Gentoo, and to a lesser extent debian, are very good at letting you run them for years and keep them up to date as you go along...
The only trick with gentoo, is to update regularly rather than all in one large chunk. You also don't have the typical problems that occur with binary updates being linked to particular versions of libraries and thus needing to install those libraries too.

For instance, anything compiled against glibc 2.4.x will depend on that version of glibc, but the same programs will still compile when using much older versions. A binary distro would require you to upgrade glibc too.