slackware 11

[carlosponti]

i saw this recently;
http://store.slackware.com/cgi-bin/s...FKFzy:mv_pc=26

i wondered if anyone had heard when they were planning the 11.0 release of slackware? I hadnt seen any news. though slowly i am growing tired of slackware because of its init scripts and slow kernel adoption.


update: first of all i never heard the news that patrick and his wife had a baby girl. secondly 2.4.x kernel again and 2.6.16 kernel in the testing folder on the second disk. i heard a rumor it was to be a july 15th release but i think that is just a rumor.

[Vergil83]

In the last two releases (10.2 and 10.1), he announced releases of betas about 2-4 weeks before the final release. I would say continue to check the current changelog
10.2 Changelog
10.1 Changelog

[Romxero]

I havent even heard of this before

[Krendoshazin]

Slackware 11 will be released soon, the current tree is very stable and almost ready to go, as Patrick said: "the current tree is very stable right now and is looking good, the sooner we release 11 the sooner we can get back to breaking current".

[Krendoshazin]

though slowly i am growing tired of slackware because of its init scripts and slow kernel adoption.

There is nothing wrong with bsd style init scripts, they're simple, efficient, and follow the KISS philosophy well. Slackware is one of the few distros that still follows the unix design philosophy, "5. Rule of Simplicity: Design for simplicity; add complexity only where you must.".

People should read this and familiarize themselves with it; http://www.faqs.org/docs/artu/ch01s06.html

[carlosponti]

the problem i have with the init scripts is that most tutorials are for the system V init scripts that most distros use. its just annoying to need to modify them and no one has anything on them. they are just different enough to annoy me. I dont have a problem with the scripts themselves on principle but that they are different from everyone else and it makes it hard to work on them. the init script i am most discouraged with are the wireless card scripts.

the things i do like are that the installer is fine for me. the graphical installers always confuse me. i like using cfdisk to partition my drives. for one thing the graphical installers always have a confusing partition application unless you let them decide for you what you want your partition scheme to be.

[techieMoe]

There is nothing wrong with bsd style init scripts, they're simple, efficient, and follow the KISS philosophy well.

There's also nothing wrong with choosing a different distrtibution that doesn't use the init scripts. The lack of automation and myopic development path turned me off to Slackware around version 9, but if it works for you, use it.

[Krendoshazin]

the problem i have with the init scripts is that most tutorials are for the system V init scripts that most distros use. its just annoying to need to modify them and no one has anything on them. they are just different enough to annoy me. I dont have a problem with the scripts themselves on principle but that they are different from everyone else and it makes it hard to work on them. the init script i am most discouraged with are the wireless card scripts.

That sounds fair enough to me, a good explanation. In the Gnu/Linux world, the BSD style init scripts are specific to Slackware, no other distro I know use them, all the rest have favoured the use of system v init scripts and I see your dilema.
The thing about Slackware being the only one to use BSD init scripts, apart from the fact it's closer to what UNIX is, is that it shows that it's not willing to play catch-up with all the other distros just to try and appeal to people that wouldn't have considered using it previously.

I guess you either love it or hate it.

[Krendoshazin]

There's also nothing wrong with choosing a different distrtibution that doesn't use the init scripts. The lack of automation and myopic development path turned me off to Slackware around version 9, but if it works for you, use it.

I agree, but what I'm saying is there's nothing wrong with it's choice to use those particular scripts, I'm not saying they should be the de facto standard. If you want automatic package management, straight off the bat it probably isn't for you, there's always something someone wants a particular way and that's how we've ended up with so many distros.

For me I moved on because I wanted control of every little detail, right from the ground up, and there was only one way I could achieve that, but like you said, if it works for you, use it, if it doesn't, I'm sure there's something else around that will suit your tastes.

[Fallen Angel]

It was a bit of a disappointment for me when I heard that Slackware 11 will use 2.4.32 kernel. I think the kernel should've been switched to 2.6 in this release. Then again, I guess that it's a lot of work changing it. But it will have to be done once.