Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Slackware 11.0 Almost Done

Posted by Zonk on Tue Aug 15, 2006 12:03 PM
from the is-it-worth-the-wait dept.
linuxbeta writes "DistroWatch reports that the development process for Slackware Linux 11.0 is almost over. OSDir has some sweet shots of Slackware 11.0 RC1 in the Slackware 11.0 RC1 Screenshot Tour." From the article: "'There are still a few changes yet to happen, but let's call this Slackware 11.0 release candidate 1.' Other recent changes include upgrade to stable kernel 2.4.33; upgrade to udev 097, and rebuild of glibc 2.3.6 for both 2.4.33 and 2.6.16.27 kernels. The new release will ship with X.Org 6.9.0 and KDE 3.5.4, and will provide SeaMonkey instead of Mozilla."
+ -
story

Related Stories

[+] Technology: Slackware 11 is Coming 115 comments
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?"
[+] Slackware 11 Has Been Released 220 comments
CCFreak2K writes "Slackware 11 has been officially released, just over a year after Slackware 10.2 became available. Software available with Slackware 11 includes KDE 3.5, Mozilla Seamonkey 1.0.5 and X11R6 6.9. As usual, ISOs are available through BitTorrent and FTPs, packages can be synced through FTPs, and you can always buy a copy."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Stone Age (Score:5, Insightful)

    by Jacek Poplawski (223457) on Tuesday August 15 2006, @12:12PM (#15910768) Homepage
    I was using Slackware for few years before I switched to Arch Linux.

    I don't understand why it still uses xorg 6.9. Maybe the reason is that nobody has the time to make so many packages for xorg7? IIRC that was the reason why there is no full GNOME in Slackware.

    Kernel 2.4 - OK, as long as it is 2.6 ready (and it is).

    But guys... what's the point to use so old software? If you don't want to put new desktop stuff, then just remove all desktop packages from distro.
    • Re:Stone Age (Score:5, Informative)

      by narfbot (515956) on Tuesday August 15 2006, @12:53PM (#15911103)
      Argh... don't make assumptions.

      Xorg 6.9 and Xorg 7.0 are functionally the same. The only difference is installation methods in that 7.0 is modular, puts things in /usr, and will break many apps. The distros that adopted 7.0 so fast were foolish and likely caused problems for their end users. So when you call Xorg 6.9 so old, you are so wrong. Xorg 6.9 and Xorg 7.0 are essentially the same code and released the same time.

      I'm not going to detail the other things people have done, but I will also state, that slackware has supported 2.6 for a long time now. Not only that, I've been running it with 2.5/2.6 since about 2003.
  • by neonprimetime (528653) on Tuesday August 15 2006, @12:12PM (#15910775)
    Granted, I don't use Slackware. But when I saw a link stating "Slackware Screen Shot Tour", I fully expected to see a bunch of shell prompts :-P I wasn't entirely wrong!
  • All hail... (Score:5, Insightful)

    by Ransak (548582) on Tuesday August 15 2006, @12:16PM (#15910804) Homepage Journal
    ... the Church Of the SubGenius! [wikipedia.org]
  • Many Kudos! (Score:5, Insightful)

    by farrellj (563) on Tuesday August 15 2006, @12:41PM (#15911031) Homepage Journal
    To Patrick Volkerding, his wife and Volkerding 2.0!

    This is the oldest existing Linux Distro! Possibly one of the most stable as well. It retains the Unix philosophy that it does a few things really, really well, and gives you the tools to add on to it. It's tanj simple to maintain and update, no "RPM Hell". And it's one person's vision, which gives it a consistancy that is lacking in other "art by committee" Distros.

    And I am biased...I moved to Slackware from Soft Landing Systems (SLS) Linux, and although I have tried many different Distros over the years, I keep on comming back to Slackware...and not just for religious reasons, either!

    Thanx you Patrick and Co for keeping the vision!

    ttyl
              Farrell
    • Re:Many Kudos! (Score:5, Interesting)

      by spaceyhackerlady (462530) on Tuesday August 15 2006, @02:31PM (#15911903)

      Hear! Hear!

      Slackware is still my distro of choice. It's utterly stable, and it just works. I actually like the text-based install: it's the right technology for what it does. What more do you need? Besides, it really will run on anything.

      Slackware is one of the few distros that realizes that it's OK for a Linux box to look and feel like Unix. And, yes, I have used real Unix, back in my VAX days. I still have a Solaris box in my cubicle, and I do real work with it.

      Keep up the good work, Patrick. Thank you.

      ...laura, typing this on a Slackware 10.2 box

  • by DiscWolf (976849) on Tuesday August 15 2006, @12:41PM (#15911032)
    XOrg 6.9, 2.4 Kernel ... are you sure this isn't Debian?
  • by ClickOnThis (137803) on Tuesday August 15 2006, @12:49PM (#15911078) Journal
    ... for its venerability as well as its stability. It was my first, and still favourite distribution. It's not on the bleeding edge, but it has other virtues. One is that it can be scaled easily to install as much or as little of it as you need, and run on machines with very different CPU and memory resources and amounts of disk space. Great for turning a bunch of old mismatched PCs into a Beowulf Cluster.

    Semi-automatic package management has taken awhile to evolve, but for some time now it has been very good indeed. There are several good PM clients; I think slapt-get has the edge right now. And if you can't find what you need in the distro, there are several sites (such as http://www.linuxpackages.net/ [linuxpackages.net]) that offer lots of additional packages and goodies.
  • by buffoverflow (623685) on Tuesday August 15 2006, @12:55PM (#15911119)
    Being a dedicated Slack user for the better part of a decade, I've rarely questioned any of Patrick's decisions in the maintenance of HIS distro. (Most people who piss & moan about Slackware being dated don't realize that it's one of the few distros that is still maintained, for the most part, by a single individual).
    However, with great trepidation, I must say that perhaps some changes are in order.
    Slackware has had a dedicated following for a long time because the distribution filled an industry need. The need for a truly rock solid stable distro that was a fairly easy transition for those coming from a pure Unix world. It seems now that those days are, for the most part, gone. The majority of the engineers out there now days have been brought up on other Linux distros, and many have never touched an actual Unix system. (No need to start any "What is Unix really?" flame wars).
    While I do still prefer the structure and stability of Slackware, I do think it's time to make certain changes. I'm not saying it's time to jump on the "Latest and Greatest Everything" bandwagon. I think it's time for the distro to be re-focused. Possibly into a pure Server OS, with a strong focus on commercial grade clustering & virtualization. All of the other distros that have done this (i.e. RedHat, SUSE, etc.), did not have the right base for it. They were based on bleeding edge, sometimes alpha code, and everything had to be stabilized (which hasn't seemed to work out very well). Slackware does have the right, truly stable base for a dedicated server OS. If Patrick were to shift things to this direction, build in the right set of truly enterprise-class server features, I think he may very well see a new found following.
    The other area that I believe a re-focused version of slack could be very successful is the embedded systems market. Slack is known for is lean, fast, optimized code. I think it would fit well into this segment.

    I think either of these markets are perfect for Slack. Neither is looking for the latest, most newfangled, gui-based, anything. They want lean, fast, stable code, & steady release cycles. Just my $.02.
    • by KillerBob (217953) on Tuesday August 15 2006, @01:18PM (#15911291)
      I disagree. Slackware is what it is: stable. It's also one of the fastest distros I've ever used. There's a reason it's running on all of my servers. There's *tons* of other distros out there that specialise in bleeding edge. Let them do it.

      If you want bleeding edge out of a Slack-based distro, btw, you should check out Zenwalk (http://www.zenwalk.org/). Slack packages are compatible, though they have their own package manager and custom-compiled packages that support dependency checking )while still maintaining compatibility with pkgtool and install/removepkg). The real advantage is when Zen doesn't have a package for what you're looking for... then you can just pop over to slackware.com and grab Pat's version, or over to linuxpackages.net and grab one of theirs.
    • by freshman_a (136603) on Tuesday August 15 2006, @01:23PM (#15911327) Homepage Journal
      No.

      I'm a long-time Slack user. One of the reasons I love Slack and use it everywhere I can is because of it's versitility. I can have a super stable server and a super stable desktop with the same version of the same OS. As it stands, Slack is quick to install, lean, stable, and it just works. Patrick's whole philosophy is Keep It Simple Stupid. Moving in the direction of enterprise-class servers would not be KISS. Also, the people behind Slack consist of Patrick and... well, pretty much just Patrick. How would one person maintain a distro aimed at the enterprise market? I like the fact that one person is behind the distro. Patrick makes the decisions, and that's it. There's no need to fear a split with the maintainers or delays in releases due to arguments about what should or shouldn't be included. I fully agree that Slackware makes a great server OS, but I would be really sad if Patrick re-focused Slack's direction and made it a pure server OS aimed at the enterprise market.

      That's my $0.02
    • by Anonymous Coward on Tuesday August 15 2006, @12:06PM (#15910723)
      1999 called, they want their kernel back...
    • Re:2.4 kernel? WTF (Score:5, Informative)

      by FreonTrip (694097) <freontrip AT gmail DOT com> on Tuesday August 15 2006, @12:07PM (#15910732)
      Slackware's always been designed with maximum stability and reliability in mind. Patrick thinks that 2.4 is still the safer bet, so he's gone with it as a default. The option to install with a new 2.6 kernel is also available, for those who'd prefer something a touch more modern.
    • Re:2.4 kernel? WTF (Score:5, Informative)

      by owlman17 (871857) on Tuesday August 15 2006, @12:16PM (#15910803)
      2.4 is old but by no means 'dated'. 2.4 is significantly leaner than 2.6, runs on old hardware and has a lot of backports from 2.6 http://kernel.org/pub/linux/kernel/v2.4/ChangeLog- 2.4.33 [kernel.org]

      Even DSL uses 2.4. I still use 2.4 on my old PIIs and newer hardware myself.

      Slack aims to run on as many types of hardware as possible. Besides, you can always compile your own 2.6 kernel into your slack system.
    • Re:2.4 kernel? WTF (Score:5, Insightful)

      by farrellj (563) on Tuesday August 15 2006, @12:18PM (#15910814) Homepage Journal
      Because it's considered more stable, and supports things that haven't been up-ported to the 2.6 kernels.

      Patrick aims at the most stable distro...not the latest, flashiest distro. That is why it is used on a large variety of servers...in fact, it has the probably more server installs than any other Distro still built by one person, and his wife. Debian is probably closest, but it is now a large team that works on it.

      Slackware just works...and works...and works...it's sort of the Energizer Bunny of Distros!

      ttyl
                Farrell
      • I have 10.2 and am using the 2.6 kernel
        I tried using the bundled 2.6 once, and I encountered some problems. I ended up getting the vanilla source from kernel.org and it actually worked better.

        I love Slackware, it runs all of my servers, but man... I wish 2.6 was the default. 2.6 has some things that 2.4 doesn't, so sometimes I have to upgrade, which is a PITA. What does 2.4 have that 2.6 doesn't?
    • (the OSX folks have that wrapped up)

      Turn on Xgl. Seriously. I run it on every one of my workstations now, and I've gotten so use to the enhanced interface I feel like I'll get eye cancer if I use a 'non Xgl'd' system for more than five minutes.

    • by MikeDawg (721537) on Tuesday August 15 2006, @01:06PM (#15911201) Homepage Journal
      I choose my linux distro (read: flavor of the month) based upon screenshots, and the pure number of fanboys. That is why I am Ubuntu until I die (or until the lemmings march themselves into the water), and I have to choose a new distro, 'til I die.
    • by tjw (27390) on Tuesday August 15 2006, @01:45PM (#15911490) Homepage
      Kernel 2.4.33? Is that serious? What is wrong with 2.6.x?

      Nothing is wrong with 2.6, but for some of us having the 2.4 option is essential. For example, certain applications built for 2.4 LinuxThreads will tend to be very unstable running on the new POSIX threads in 2.6.

      People are looking at this the wrong way. It's not that Slackware doen't included the 2.6 kernel (it does), it offers the versatility to run either 2.4 or 2.6 which is a major advantage over other distros. Especially for us poor bastards who have to run expensive closed-source proprietary software at work.