Slashdot Mirror


Slackware 11.0 Almost Done

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."

190 comments

  1. 2.4 kernel? WTF by LordKazan · · Score: 2, Interesting

    Seriously.....

    --
    If you cannot keep politics out of your moderation remove yourself from the Mod Lottery.. NOW!
    1. Re:2.4 kernel? WTF by Anonymous Coward · · Score: 5, Funny

      1999 called, they want their kernel back...

    2. Re:2.4 kernel? WTF by FreonTrip · · Score: 5, Informative

      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.

    3. Re:2.4 kernel? WTF by NosTROLLdamus · · Score: 0, Offtopic

      Why?

    4. Re:2.4 kernel? WTF by Bob+of+Dole · · Score: 1

      Like people who need to use non-tiny hard drives.

      (Being able to access less than half of my new 300gb drive is FUN!)

    5. Re:2.4 kernel? WTF by Anonymous Coward · · Score: 2, Informative

      Come on its Slackware you should know better ;-p. besides you have a choice of installing either 2.4 or 2.6 its not like you have to use 2.4. I have 10.2 and am using the 2.6 kernel that came with it and its fine. THe kernel really is the only thing thats old but even then its a recent version thats stable.

    6. Re:2.4 kernel? WTF by owlman17 · · Score: 4, Informative

      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

      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.

    7. Re:2.4 kernel? WTF by farrellj · · Score: 5, Insightful

      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

      --
      CAN-CON 2019 - Ottawa's only book oriented Science Fiction Convention! October 18-20, Sheraton Hotel, Ottawa, Canada h
    8. Re:2.4 kernel? WTF by Espectr0 · · Score: 1

      Slackware's always been designed with maximum stability and reliability in mind.

      Slackware used to include older versions of software like debian stable because it was designed with stability in mind. But since around 7.0, haven't you noticed it includes up-to-date software?

      I think i read somewhere that 11.0 (hence the bump in the major version number) would include 2.6 by default

    9. Re:2.4 kernel? WTF by nuzak · · Score: 1

      > Even DSL uses 2.4

      And so does Redhat EL (or perhaps 4 switched to 2.6, I don't know since I'm still on 3). Until Linus decides to stop making 2.6 his personal playground for unstable features, any stable distribution is going to stay "2.4 + vendor patches" for a long time to come.

      --
      Done with slashdot, done with nerds, getting a life.
    10. Re:2.4 kernel? WTF by tylernt · · Score: 2, Insightful
      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?
      --
      DRM 'manages access' in the same way that a prison 'manages freedom'
    11. Re:2.4 kernel? WTF by wed128 · · Score: 1, Offtopic

      I'm using 2.6 and my 300 gigger works just fine.

    12. Re:2.4 kernel? WTF by eln · · Score: 1

      RHEL 4 did indeed switch to 2.6. It also changed all the redhat-* commands to system-* commands for some reason.

    13. Re:2.4 kernel? WTF by oudzeeman · · Score: 1

      that was his point. it doesn't work wih 2.4 so he needs to use a 2.6 kernel

    14. Re:2.4 kernel? WTF by jb.hl.com · · Score: 1

      Offtopic? Hah, this post is funny as hell :)

      --
      By summer it was all gone...now shesmovedon. --
    15. Re:2.4 kernel? WTF by Anonymous Coward · · Score: 3, Informative

      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.

      What are you talking about? Slackware is the only high-profile distro that uses Linus' tree. It's all the other distros that patch the kernel. Slackware doesn't.

    16. Re:2.4 kernel? WTF by eosp · · Score: 1

      I think he figures that anyone capable of using Slackware can install (and compile) their own 2.6. By the way I think it still uses LILO too.

    17. Re:2.4 kernel? WTF by tscheez · · Score: 4, Funny

      and their boot loader

      --
      Supplies!
    18. Re:2.4 kernel? WTF by tux_fairy · · Score: 0

      2.6 will be stable in the same release that will ship KDE4.

    19. Re:2.4 kernel? WTF by partenon · · Score: 1

      I'm sorry, but there are not that much distro's built by "one person", so, not its not a big deal to be the "the most installed distro built by one person (and his wife??)" . I mean, its like "the most installed distro built by a now microsoft employee", or "the most installed distro build in south africa".

      Also, reading your comment, it seems to me that using a distro "built by just one person" is something good, but thinking for less than a minute, I realized that its probably not that good :-) What if he get hit by a bus (or get sick by a misterious disease) ?

      And please, don't get me wrong, I still like Slackware (just like 90% of ./ers, I used slackware some time ago), but I must admit I've never seen a "serious" slack server (yeah, it probably exists, but who've ever seen one?).

      And come on... *Every* distro (and serious OSes), if well configured, "just works, works, works" :-) The difference is: using ubuntu you'll get into this stage after 15 minutes, 1h if using debian, 1 day if using slackware and 1 week if using gentoo :-) (ok ok, I don't trust an ubuntu configured in 15 minutes too)

      --
      ilex paraguariensis for all
    20. Re:2.4 kernel? WTF by proxima · · Score: 1
      RHEL 4 did indeed switch to 2.6. It also changed all the redhat-* commands to system-* commands for some reason.

      I noticed this too. I figured it was part of a harmonization with Fedora. Reduce the number of RH references in Fedora, and since RHEL is based in part on Fedora, certain things would carry through. Or perhaps it just makes more sense to have them be system-* rather than redhat-*. Perhaps they hope that other distros will pick up on the naming scheme, making for a more unified configuration structure (at least from the command line). No big deal, really.

      --
      "The universe seems neither benign nor hostile, merely indifferent." --Carl Sagan
    21. Re:2.4 kernel? WTF by legojenn · · Score: 4, Insightful

      Don't you mean 2001? Anyhow, what difference does it make what kernel they ship with (within reason)? If the hardware and software does not require a newer kernel, wouldn't it be more prudent in an environment where reliability is important to have the most reliable kernel out there?

      --
      I make a reasonable middle-class wage by going to work and not spamming blogs with scams.
    22. Re:2.4 kernel? WTF by MBGMorden · · Score: 1, Flamebait

      I don't see what the fuss is about a distro using LILO instead of GRUB. It's a frickin bootloader for goodness sake. I've got systems that use both (I'll take GRUB over LILO if it's an auto-install - if I have to configure by hand I'll go with LILO as a know it better).

      Ideally though, you will only see the program on a reboot (which is likely not often unless you dual boot). Even then all it's gonna do is throw up a menu where you choose which OS you want.

      --
      "People who think they know everything are very annoying to those of us who do."-Mark Twain
    23. Re:2.4 kernel? WTF by aichpvee · · Score: 1

      Who runs Slackware as a server? Everyone I know uses it where it belongs, on the desktop.

      --
      The Farewell Tour II
    24. Re:2.4 kernel? WTF by Anonymous Coward · · Score: 0

      Dude, are you serious? 2.6 is DEFINATELY not ready for production use, which is what Slackware is used for. Everyone from Pat to Spender knows this.

    25. Re:2.4 kernel? WTF by LordKazan · · Score: 1

      horseshit, we're using it in prod every freaking day no problems - just test your freaking updates before you roll them to prod

      (oh BTW - our prod COULDN'T FUNCTION without 2.6 nor would we have even tried to use 2.6 even if it could have)

      --
      If you cannot keep politics out of your moderation remove yourself from the Mod Lottery.. NOW!
    26. Re:2.4 kernel? WTF by Anonymous Coward · · Score: 0

      Wow, you're an idiot. IT-IS-AN-INSECURE-KERNEL. It's not for use in a production environment because it's not as thuroughly tested and is constantly being added to. How fucking ignorant are you, seriously?

      From grsecurity.net:
      "The 2.6 patch has changed the way it adds -grsec to the kernel's extraversion, so it should apply cleanly to most 2.6.17.x kernel releases. We however continue to discourage the 2.6 series of kernels for production use for reasons that should by now be obvious to everyone."

      From Slackware -CURRENT Changelog:
      "However, I'm
          probably going to leave the bare.i 2.4.32 kernel as the default kernel (or
          perhaps sata.i?) as it has very good performance and probably better security
          due to the simpler and longer-tested design."

      Now shut the fuck up with your "horseshit" comment asshole.

    27. Re:2.4 kernel? WTF by maop · · Score: 1

      Slackware users know how to compile the kernel.

    28. Re:2.4 kernel? WTF by Anonymous Coward · · Score: 0

      Well, 2.4 has a working mmap, and as soon as 2.6 has one, I'll be upgrading too.

    29. Re:2.4 kernel? WTF by evilneko · · Score: 0

      Come now, my debian box was ready in a mere 20 minutes! :)

      --
      Slashdot - where to disagree, is to be a troll
    30. Re:2.4 kernel? WTF by notamisfit · · Score: 1

      2.6 was under consideration, from what I understand. Probably something to do with the eleventy billion 'stable' releases every couple of days. Slack 11 includes a 2.6.16.27 kernel in extras (ie, on the install disk), and a 2.6.17.8 kernel in /testing, so I really don't think it's a big deal.

      --
      Jesus is coming -- look busy!
    31. Re:2.4 kernel? WTF by Kingrames · · Score: 2, Funny

      latest, flashiest distro?

      There's nothing flashy about linux kernels. You sir, need to go outside and light a sparkler. It will blow your mind.

      --
      If you can read this, I forgot to post anonymously.
    32. Re:2.4 kernel? WTF by Anonymous Coward · · Score: 0

      This is really funny.

    33. Re:2.4 kernel? WTF by geminidomino · · Score: 1

      I'm actually in the process of rebuilding my server to migrate from FreeBSD 4-Stable to Slackware.

      And yes, it is on my desktop, too. ;)

  2. Screenshot tour by Anonymous Coward · · Score: 0

    What a waste of bandwith. Like we need to see EVERY screen during the install.

    1. Re:Screenshot tour by FudRucker · · Score: 0, Flamebait

      RE:["Like we need to see EVERY screen during the install."]

      i guess you can install slackware with your eyes closed... get a life troll, some people rather use slackware than any other distro...

      --
      Politics is Treachery, Religion is Brainwashing
    2. Re:Screenshot tour by Anonymous Coward · · Score: 0

      How else are you gonna scare away all those newbie Linux users without even having them download the system? It's like the opposite of a livecd.

    3. Re:Screenshot tour by Alan · · Score: 1

      I think what he means is that a screenshot tour of slackware is about the same as one for mandrake, gentoo, etc, past the install. Who wants to see a bunch of kde screenshots, seriously.

    4. Re:Screenshot tour by Phlux · · Score: 1

      Funny that you should mention this, because Slackware is probably one of the few Linux distros you actually *can* install with your eyes closed (not talking about scripted). I've installed Slackware on PCs without monitors before ;)

    5. Re:Screenshot tour by failure-man · · Score: 1

      With the force of light I will show thee a better way to the mythical headless install, for behold! The holy cable of the null-modi! It has traveled here from the eBay for its $4.99 in order that it may be connected between that system which is blind and thoughtless and that which has already reached enlightenment. Amen.

      (Does slackware support serial install? Very yes, and on the default media . . . . . . as long as you remember to edit /etc/securetty when you're done . . . . . . . )

  3. Stone Age by Jacek+Poplawski · · Score: 4, Insightful

    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.

    1. Re: Stone Age by slummy · · Score: 2, Informative

      Gnome was dumped in 10.2. You can still find a nice release of Gnome from Freerock Gnome built specifically for Slackware.

    2. Re:Stone Age by Derf_X · · Score: 1

      There is no Gnome in Slackware because it was removed a short while ago. It was too hard to maintain. The reason why it is still X.org 6.9 is probably for stability, like the 2.4 kernel and lots of other stuff. Even if it is for desktop use, some want stability. Stability is not just for servers, it is for workstations also.

    3. Re:Stone Age by MamiyaOtaru · · Score: 1

      If they don't want to put in new desktop software? Like KDE 3.5.4, the very latest release? Sounds like another one of the "if there's no Gnome, there should be no KDE either, it's only fair" crowd. Sheesh, the DEs aren't children, they don't need to be babied. They won't be offended if one gets left out. The users on the other hand..

    4. Re:Stone Age by narfbot · · Score: 5, Informative

      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.

    5. Re:Stone Age by Anonymous Coward · · Score: 0

      A transition to modular X.org 7.1 is a _huge_ undertaking that Patrick (rightly) believes should wait until the next development version. And really, what's the rush? Ubuntu still uses the 6.9 codebase (7.0 == 6.9). You people need to stop being so damn reactionary -- cut the "omg it's a version behind lol pathetic!" This isn't gentoo. Stability is important to some people.

    6. Re:Stone Age by pwrtool+45 · · Score: 2, Informative

      I wish I had mod points. Your comments about X.org are spot on. The resultant binaries are the same. X.org 7.0 is just the modularized source for X.org 6.9. I mean, geez. It's the second item on their web page!

    7. Re:Stone Age by Bastian · · Score: 1

      But guys... what's the point to use so old software?

      The point is to keep guys like me who don't always feel the need to mess with the "latest and greatest" happy. I like Slackware because Slackware is solid, and Slackware is solid because it moves with caution.

    8. Re:Stone Age by Anonymous Coward · · Score: 0

      7.0 is modular, puts things in /usr, and will break many apps.

      Like what? Seriously, if your app expects a binary that it didn't install to be in a specific place, then you should be anally violated with exec?p(). If your app breaks because you used a non-API version specific feature, then you have as much right to whine about this as all the Windows developers whining about how Vista enforces API access, or the people going from glibc1 to 2 whose apps used lngjmp ____some_function_not_even_considered_an_undocumen ted_api+0x003F or some shit like that, and were surprised when the function changed. If your app breaks the X protocol, then you were doing it wrong in the first place.

    9. Re:Stone Age by narfbot · · Score: 1

      No. The point wasn't whether they could not be made to work. The point is the impact. Pat does not want to spend the time to test every app, especially seeing that he doesn't package alot of apps. He is waiting for things to stabilize by letting the people that actually maintain the apps to update. He doesn't want to make hundreds of little build patches just to make you happy and provide no functional difference. Also, the change was big enough for the Xorg people to recognize; that's why they made the 6.9/7.0 dual release for transitioning. You can't expect a distro to know exactly how things are working everywhere to keep bleeding edge working especially with a poor reason of 7.0 providing no additional value. This is why slack is considered very stable and all these "user" distros are hacked up to death.

    10. Re:Stone Age by Sketch · · Score: 1

      Download any X app which does not use autoconfig, recompile, watch it fail when the hard-coded path to /usr/X11R6 in the makefile doesn't exist. (or the RPM spec file, or the slackbuild script...)

      Sure, the binaries aren't broken (though I managed to find a few source files with includes with hard coded /usr/X11R6/include paths in them), but it's still a pain.

      --
      -- OpenVerse Visual Chat: http://openverse.com
    11. Re:Stone Age by Anonymous Coward · · Score: 0

      That is my story too. Like Slackware, Arch Linux has clean scripts and good package control, but Arch stays on the bleeding edge. I love Arch for that, but would still go back to Slackware for a rock-solid server install.

    12. Re:Stone Age by kosmosik · · Score: 1

      > Xorg 6.9 and Xorg 7.0 are functionally the same.

      Despite of few rather nice things and few critical (for few people like laptop users) new drivers.

    13. Re: Stone Age by mrjackson2000 · · Score: 1

      there is also Dropline Gnome

    14. Re:Stone Age by narfbot · · Score: 1

      No, your distro or X packages, since it is modular, got updated versions. Read http://x.org/ The press release even states they are released the same except for the changed the build system.

    15. Re:Stone Age by Anonymous Coward · · Score: 0

      Modular X.org can easily be put into /usr/X11R6. I finally got around to installing the modular X.org, and the biggest pain was getting the dependency ordering right. Now that it's installed, though, I've had zero problems.

    16. Re:Stone Age by kosmosik · · Score: 1

      I've meant the 7.1 release. Why I would use 6.9 that works *worst* with my hardware than 7.1? No mind the Xgl/compiz stuff and so on. :) I know - it is now THE-UNIX-WAY to use decent software that does its work. You *NEED* to use old stuff because if you won't THINGS-WILL-BREAK. Not to mention you haven't specified what is wrong with new versions so you need to use old ones.

    17. Re: Stone Age by kosmosik · · Score: 1

      Yeah. Bassicaly - I'am THE MAINTAINER. Screw you guys using GNOME - I don't like GNOME so I'll drop it. It is too hard to maintain - go maintain it yourself. Now that is what I expect of STABLE distro. :) Like *I* don't like whatever you use - go screw yourself.

      Phheeeh. :))) It was also a nice point about Slackware.

      Disclaimer: I don't use GNOME directly, I use various parts of it. And I also use KDE - you know, on Linux/X11 you can use both of them - only the apps you like. But not on Slackware.

    18. Re:Stone Age by Anonymous Coward · · Score: 0

      IIRC that was the reason why there is no full GNOME in Slackware.

      Actually, GNOME was dropped in Slackware because it was taking up so much of Patrick's time that the system as a whole was suffering -- it had nothing to do with X.org 6.9, which by the way didn't even exist at the time. In addition, there were already two whole communities of developers (perhaps three? gware, dropline, and freerock) putting time and effort into making their own GNOME distributions specifically for Slackware. But don't take my word for it...read all about his decision from http://lwn.net/Articles/129282/:

      New Entry: gnome/*: Removed from -current, and turned over to community support and
      New Entry: distribution. I'm not going to rehash all the reasons behind this, but it's
      New Entry: been under consideration for more than four years. There are already good
      New Entry: projects in place to provide Slackware GNOME for those who want it, and
      New Entry: these are more complete than what Slackware has shipped in the past. So, if
      New Entry: you're looking for GNOME for Slackware -current, I would recommend looking at
      New Entry: these two projects for well-built packages that follow a policy of minimal
      New Entry: interference with the base Slackware system:
      New Entry:
      New Entry: http://gsb.sf.net/
      New Entry: http://gware.sf.net/
      New Entry:
      New Entry: There is also Dropline, of course, which is quite popular. However, due to
      New Entry: their policy of adding PAM and replacing large system packages (like the
      New Entry: entire X11 system) with their own versions, I can't give quite the same sort
      New Entry: of nod to Dropline. Nevertheless, it remains another choice, and it's _your_
      New Entry: system, so I will also mention their project:
      New Entry:
      New Entry: http://www.dropline.net/gnome/
      New Entry:
      New Entry: Please do not incorrectly interpret any of this as a slight against GNOME
      New Entry: itself, which (although it does usually need to be fixed and polished beyond
      New Entry: the way it ships from upstream more so than, say, KDE or XFce) is a decent
      New Entry: desktop choice. So are a lot of others, but Slackware does not need to ship
      New Entry: every choice. GNOME is and always has been a moving target (even the
      New Entry: "stable" releases usually aren't quite ready yet) that really does demand a
      New Entry: team to keep up on all the changes (many of which are not always well
      New Entry: documented). I fully expect that this move will improve the quality of both
      New Entry: Slackware itself, and the quality (and quantity) of the GNOME options
      New Entry: available for it.
      New Entry:
      New Entry: Folks, this is how open source is supposed to work. Enjoy. :-)

    19. Re:Stone Age by narfbot · · Score: 1

      You're not making much sense. I didn't say it was wrong to use 7.x. I'm saying the 6.9/7.0 release was made to allow for migration. Slackware hasn't migrated yet. Pat wants to release a stable 11.0 which has been in the works far long before the release of Xorg 6.9/7.0. I expect X.org 7.1 to be in slackware-current for the future 11.1 in a few weeks. Or if you are that desperate for XGL, just download the build off X.org's site. It doesn't make sense to argue it when we are only four months difference in version numbers from 6.9/7.0 to 7.1. Most people just want their system to work.

    20. Re:Stone Age by narfbot · · Score: 1

      I just looked at the XGL/compiz stuff and found it works with Xorg 6.9. Of course you should have your driver updates still. It's not hard to compile the new drivers for 6.9. I've compiled the Xorg 2D drivers from the HEAD before too to use for my older versions. 7.1 isn't really any different than 6.9 than a few updates. It would be analogous to 6.10 if they made such a release.

      In short, complaining that slackware is old when 6.9 is essentially the same as 7.x is stupid. Besides, I do believe that Pat has actually patched the drivers if you look at the changelog.

    21. Re: Stone Age by geminidomino · · Score: 1

      I don't use GNOME directly, I use various parts of it. And I also use KDE - you know, on Linux/X11 you can use both of them - only the apps you like. But not on Slackware.

      *looks at parent post*

      *Looks at desktop running amaroK and gaim*

      *looks at parent post*

      *looks at /etc/slackware-version*

      *shakes head and shrugs*

  4. Slackware Screen Shots by neonprimetime · · Score: 4, Funny

    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!

    1. Re:Slackware Screen Shots by Anonymous Coward · · Score: 0

      The screenshots had another, less obvious meaning. They showed the entire process for a complete install. One thing I love about Slackware is I can have a new install up and running in 10 minutes. Also, this screenshot tour would be useful to someone who never installed Slackware before. Slackware, extremely fast and stable, great server. Package management with dependencies... that's why I switched to Debian.

    2. Re:Slackware Screen Shots by hritcu · · Score: 1

      Package management with dependencies... that's why I switched to Debian.

      That's also the reason most of it's users love Slackware, me included.

      --
      If you don't fail at least 90 percent of the time, you're not aiming high enough. (Alan Kay)
  5. Re:Screenshots? by Anonymous Coward · · Score: 0

    I didn't realise GNOME had renamed itself KDE recently...

  6. Sweet Shots by grayson_DEV · · Score: 0, Troll
    "... OSDir has some sweet shots of Slackware 11.0 RC1 in the Slackware 11.0 RC1 Screenshot Tour."
    sweet shots? I hope you're joking - those are some seriously generic, dull, unappealing screenshots.

    Yes, there's a lot more to a system than looks - but for a desktop OS, looks count a lot. And those screenshots don't give anyone a reason to give Slackware a second glance.
    1. Re:Sweet Shots by Handover+Phist · · Score: 1

      One of Slackware's big pluses is flexibility, at least that's one of the big one's that has kept me using it for quite a few years on both my desktops and servers. My desktop box is quite pretty too (http://www.websterscafe.com/Screenshot.png) running Gnome from http://www.gware.org/. It's also quite simple to fiddle with the guts of the system without screwing things up. For example I prefer to use Postfix instead of Sendmail, so I just pop it in. For those who want a desktop system that's pretty out of the box Slack has never been the distro of choice, and if it becomes one, I'll probably stop using it.

    2. Re:Sweet Shots by Anonymous Coward · · Score: 0

      When it comes to human interaction, generic and dull is good. It's easier to use than "exciting" interfaces where you have to figure out how to use them.

      Have you ever tried to use any of the "good looking" themes? They are practically unusable - low contrast, tiny text, distracting background, etc. Plain and straightforward is usable.

    3. Re:Sweet Shots by hattmoward · · Score: 1

      Unless you really like the type of system Slackware gives you, it's not a desktop OS. People who want to be dazzled with screenshots are unlikely to enjoy the Slackware experience. I've been using Slackware for a long, long time and it's just what I like to have on my desktop, but I'm not going to recommend it for anyone's mom.

    4. Re:Sweet Shots by MikeDawg · · Score: 5, Funny

      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.

      --

      YOU'RE WINNER !
      Another lame blog

    5. Re:Sweet Shots by Anonymous Coward · · Score: 0

      If you want to see sweet shots of Slackware, check out dropline. Its pretty much everything you could want from a desktop on slackware. Original themes, original art, recent kernel, recent X (in testing anyway), and the most recent GNOME. Gware and Freerock never did release 2.14.

  7. Re:Screenshots? by Lispy · · Score: 4, Funny

    Am I missing something here?

    Well, besides that its KDE, I dont think so.

  8. Will the Slackware 11 2.4 kernel include CIFS? by Anonymous Coward · · Score: 1, Interesting

    Will Slack 11 include the CIFS patch in the 2.4 kernel? I need CIFS at work to talk to the Windoze boxes at work :-(

    1. Re:Will the Slackware 11 2.4 kernel include CIFS? by Derf_X · · Score: 1

      I don't think there will be as Slackware is known to use a plain kernel with no patches.

    2. Re:Will the Slackware 11 2.4 kernel include CIFS? by DamnStupidElf · · Score: 1

      Will Slack 11 include the CIFS patch in the 2.4 kernel? I need CIFS at work to talk to the Windoze boxes at work :-(

      You use Slack and don't compile your own kernel? My God man!

      - happy Slack user

  9. 99% ready == *not* ready by jetxee · · Score: 1

    Hey, everybody knows what does it mean when a piece of software is almost done :)

    1. Re:99% ready == *not* ready by neonprimetime · · Score: 2, Funny

      It's kinda like in Windows when you copy or download a file. Where 99% doesn't really mean 99%

    2. Re:99% ready == *not* ready by farrellj · · Score: 1

      Do you mean in a Microsoft world, or a Linux world?

      In a Microsoft world 99% done means only another 20 or so releases until it is officially done...then another 5 years before it is finally finished after it's officially done.

      In a Linux world, 99% done means is probably more functional than a Microsoft product 5 years after release!

      ttyl
                Farrell

      --
      CAN-CON 2019 - Ottawa's only book oriented Science Fiction Convention! October 18-20, Sheraton Hotel, Ottawa, Canada h
    3. Re:99% ready == *not* ready by bmac83 · · Score: 1

      Well, in Slackware's case it means that it is almost done. There is usually a new version of Slackware every summer, so for those of us familiar with the distro it's no surprise that things are where they are right now.

      It goes without saying that Slackware is a completely different beast than Ubuntu, etc. A stable, server-oriented OS has the luxury to grab the best and most stable of what's around at a given time and ship it, without worrying if it has OMG translucent icon bars. I appreciate the diligence with which Pat provides us a new, improved system at predictable times.

    4. Re:99% ready == *not* ready by Anonymous Coward · · Score: 0

      You think you have problems? Every time I try to copy a file in Windows, it gets, ahem, contaminated with something.

      See for yourself.

    5. Re:99% ready == *not* ready by Bill+Kilgore · · Score: 1

      You know, Slackware has never had preannounced or fixed release dates. They work on it until they're done. Somehow, this results in [more or less] regular, stable releases.

      The contrast with Windows is telling.

      Slackware may be "old" software, but it's a lot newer than XP, ain't it?

      --
      Rediculous: A word indicating the writer is ridiculously ignorant.
  10. Cool... by IHSW · · Score: 1
    1. Re:Cool... by Anonymous Coward · · Score: 0

      Where can we go and get the A and N floppy images? I already have Rawrite.

    2. Re:Cool... by geminidomino · · Score: 1

      If you're gonna wave your "I did a net install from 2 floppies" e-peen around, you should at least login so you can get your proper neck-beard cred. ;)

  11. All hail... by Ransak · · Score: 4, Insightful
    --
    "Powers. I have them."
  12. wonderful screen shots... by pedantic+bore · · Score: 1
    ... looks remarkably similar to Linux!

    Please remind me why this is exciting... Slackware is cool to run. It's not particularly interesting to look at. (the OSX folks have that wrapped up) Just tell me when it's ready to download.

    --
    Am I part of the core demographic for Swedish Fish?
    1. Re:wonderful screen shots... by Ransak · · Score: 2, Funny
      (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.

      --
      "Powers. I have them."
    2. Re:wonderful screen shots... by farrellj · · Score: 1

      Or, download Slacke17, the newest Enlightenment, packages for Slackware as a slackpack. It even makes a 700 Mhz PIII look cool and fast!

      http://slacke17.sourceforge.net/

      ttyl
                Farrell

      --
      CAN-CON 2019 - Ottawa's only book oriented Science Fiction Convention! October 18-20, Sheraton Hotel, Ottawa, Canada h
    3. Re:wonderful screen shots... by Shadowlion · · Score: 1

      Does Xgl have very specific video card requirements, i.e. nothing higher than a Radeon 9500-level card?

    4. Re:wonderful screen shots... by wed128 · · Score: 1

      I use slacke17 and i must say, it is easily the most beautiful desktop i've ever seen, even with very little tweaking.

    5. Re:wonderful screen shots... by Anonymous Coward · · Score: 0

      Adventure... excitement... a Jedi craves not these things!

    6. Re:wonderful screen shots... by Ransak · · Score: 2, Informative

      Yes, since it's makes heavy use of your video card. I run SuSE 10.1, the list is in a package called xgl-hardware-list which installs a file to /etc/X11/xgl-hardware-list. I'm not sure of other distros, but Google should have the answers you seek.

      --
      "Powers. I have them."
    7. Re:wonderful screen shots... by niteice · · Score: 1

      It runs fine on my GeForce 2 (that is to say, all the bouncyness gives me a headache :D).

      --
      ROMANES EUNT DOMUS
    8. Re:wonderful screen shots... by stavrosg · · Score: 1

      Does Xgl have very specific video card requirements, i.e. nothing higher than a Radeon 9500-level card? You'll probably need any video card that comes with 256MB of RAM or more, and its drivers support OpenGL. I tried Xgl on my FX5200 w/128MB RAM and while most effects run fine, the system is brought on its knees with any video playback. (Celeron D 2.66Mhz, 1024MB RAM) Regards,

    9. Re:wonderful screen shots... by kosmosik · · Score: 1

      > 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.

      A bit off-topic.

      I have mixed feelings about Xgl (compiz-quinn exactly - Xgl is not something you directly see).

      Recently I've been playing with it and it is great - I do not at all mean eye candy - I mean *functionalities* that I get. I see live pictures of windows as I switch them. I can swith windows seeing all of them miniaturized with live previews. I can peek into desktop to the right/left - really nice. And it is not only eyecandy - screw bouncing menus and windows - it really does not give you anything but more bloat to the eye.

      But on the other had when I use plain X11 with WindowMaker it is a lot more snappier and it just get its work done. My point is that now Xgl/compiz is fine but it uses rather poor window manager. On my laptop when I use Xgl I can't watch movies and use OpenGL (i915 chip).

      On my media-center system in living room I have quite powerfull nvidia card and it copes with Xgl perfectly (movies do work, same OpenGL).

    10. Re:wonderful screen shots... by a.d.trick · · Score: 1

      Many of the effects in compiz and compiz-quinn have been really exagerated (particularly wobbly). I guess this is to make the eye-candy obvious, but it has the effect of getting in the way. Changing setting in gconf-editor really helps.

  13. Seamonkey vs. Mozilla? by pedantic+bore · · Score: 1
    Isn't Seamonkey just Mozilla 1.8?

    Or is there some deeper hidden difference here?

    --
    Am I part of the core demographic for Swedish Fish?
    1. Re:Seamonkey vs. Mozilla? by IHSW · · Score: 4, Insightful

      SeaMonkey, the code name to the Mozilla Application Suite, an internet suite maintained by the Seamonkey Council. It is no longer maintained by the Mozilla Foundation.

      source: http://en.wikipedia.org/wiki/Seamonkey

    2. Re:Seamonkey vs. Mozilla? by Anonymous Coward · · Score: 1, Informative

      Code-wise, Seamonkey is pretty much the code that could have become Mozilla Suite 1.8.

      The Mozilla Corporation/Foundation are not supporting Seamonkey in the same way as they did the Suite - Seamonkey is now a community-driven project, and while it's still mostly hosted by the Mozilla Foundation, the coding is now done by volunteers rather than anyone employed by Mozilla (except for the back-end which is code shared by Firefox, Thunderbird, Camino, Sunbird, etc)

      http://www.mozilla.org/projects/seamonkey/news.htm l#2005-07-02

    3. Re:Seamonkey vs. Mozilla? by noldrin · · Score: 1

      Seamonkey is the continued developement of Mozilla.

  14. Re:Screenshots? by neonprimetime · · Score: 1

    Exactly what I was thinking. It's almost pointless to show screen shots of any linux distro unless you're showing an interesting / new installation process or configuration manager. The rest of KDE / GNOME same ol' same ol', and there really is no point.

  15. yawn by Anonymous Coward · · Score: 0

    Using cfdisk, so I can presume it doesn't do ntfsresize. Still uses LILO. Console font configuration is kind of nice. The installation of KDE is absolutely 100% vanilla.

    I can get a debian system pared down pretty well too, so I still can't see anything compelling about slackware.

  16. Re:Screenshots? by Masa · · Score: 5, Funny
    Why do I need screenshots? It's Gnome.
    and still you failed to see that it's not a Gnome, it's KDE. Maybe few more screenshots would help?
  17. Re:Another Important Announcement by FreonTrip · · Score: 1

    Oh, don't be a penis. If it doesn't interest you, move on. No need to troll up the thread.

  18. Many Kudos! by farrellj · · Score: 5, Insightful

    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

    --
    CAN-CON 2019 - Ottawa's only book oriented Science Fiction Convention! October 18-20, Sheraton Hotel, Ottawa, Canada h
    1. Re:Many Kudos! by Kazymyr · · Score: 1

      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

      Ditto, ditto and ditto...

      Seriously, many kudos from this long-time user as well. I can't wait for Slackware 59.0!

      --
      I hadn't known there were so many idiots in the world until I started using the Internet -Stanislaw Lem
    2. Re:Many Kudos! by JoeF · · Score: 2, Interesting

      Cool. Somebody else who remembers SLS ;-)
      When SLS vanished I too moved to Slackware, since the first Slackware distro was derived from SLS.
      I have been using Slack since then on my main Linux box, currently running Slack 10.2 with a 2.6.17 kernel. I play with other distros on a spare machine, but none has come close to Slack in stability and ease of maintenance.

    3. Re:Many Kudos! by gjh · · Score: 1

      SLS!! "A soft landing from a DOS bail-out!"

      I never was so comfortable with the new fangled Slackware after SLS.

    4. Re:Many Kudos! by spaceyhackerlady · · Score: 4, Interesting

      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

    5. Re:Many Kudos! by JonJ · · Score: 1

      I fail to see have "TGZ hell" is any better than "RPM hell". People piss and moan about rpm even though it's had package managers for some time, Slackwares binary packages also have deps, and so have source packages. Please stop the mindless idiotic bashing of package systems.

      --
      -- Linux user #369862
    6. Re:Many Kudos! by farrellj · · Score: 1

      There is no TGZ hell...unless, of course, you can't understand TAR and ZIP. There is no braindead dependancy checking, something that Debian does much, much better. But Slackware is about knowing your system, being able to work "under the hood", and using your Goddess given intellengece to RTFM and find out what the dependancies of the program you are installing are.

      RPM is so braindead...many times I have had to manually install or "force" software on RH based systems because the "needed" dependancy is already installed, but is a newer, or slight revision off the "needed" one. Debian's package management system is great, if you just want something to work "automatically", and is far superior to RPM. But I do things like compile my own customer kernels, and install software from source.

      ttyl
                Farrell

      --
      CAN-CON 2019 - Ottawa's only book oriented Science Fiction Convention! October 18-20, Sheraton Hotel, Ottawa, Canada h
    7. Re:Many Kudos! by kosmosik · · Score: 0

      > Slackware is still my distro of choice. It's utterly stable, and it just works.

      Good for you.

      > I actually like the text-based install: it's the right technology for what it
      > does. What more do you need?

      I am not bashing Slackware or whatever. I'll just try to answer your question - what do I need from an installer? Well:

      - Remote instalation (when you can controll install process remotely via network), be it VNC, sshd with text mode - whatever. just not to need to sit in front of the box (which is sometimes impossible). Fedora/RedHat installer (Anaconda) has nice feature that is instalation via VNC screen over the network. Great to install Linux remotly at friends machine - I just give them boot image and I install it remotely.

      - Automated/unattended installs. Now to be honest - I know shit about Slackware installer. Does it offer unattended install mode (possibly single shell script that just does everything)? Anaconda has *great* features regarding this. You can do virtually anything you whish - automated partitioning? network setup? system presetup? package selection? Yep - all is here just to use.

      > Besides, it really will run on anything.

      But what kind of point is that? For me it is worthless. On decent workstation I would use decent system. On older one I will use specialized one. Slackware cant fit all. Maybe you mean that it will work on large range of various PCs - OK, but it is not all the stuff Linux can run. And I (only my opinion) find it pointless to run Linux on old PCs. Really - I just throw them out and get decent one that lets me work comfortably. I've used to have old-PC-router, but it sucked - now I have full fledged wireless-adsl-modem-router switch and it does the work better. I've used to have old-PC-server - it died. Now I have normal PC with large disks and decent memory and it finally works as expected.

      Linux giving new life to old-PCs is a myth. It is in fact a lot slower at common tasks than f.e. Windows 98 with Office 97 - so why bother?

    8. Re:Many Kudos! by Anonymous Coward · · Score: 0

      - Remote instalation (when you can controll install process remotely via network), be it VNC, sshd with text mode - whatever. just not to need to sit in front of the box (which is sometimes impossible). Fedora/RedHat installer (Anaconda) has nice feature that is instalation via VNC screen over the network. Great to install Linux remotly at friends machine - I just give them boot image and I install it remotely.

      *Yourgh* (The sound of me puking).

      VNC installations of redhat is quite simply horrible. Having done some of them at work, I can say nothing good about them. If you want to do remote installation, get something that gives you the serial output. A 'screen emulator' or what to call it just sucks. The mouse never positions right, you click to menus and so forth. Ugh.

      No, to do remote installations I prefer a jumpstart image that just lets the box fetch what it needs from the network. No CD, just a simple dhcp server that tells the pxeboot where to look for the boot-image via tftp, then fetch whatever more it needs.

      anaconda supports it.

      If I had to choose between sitting at a remote location with a CD to install something, or sitting at home at VNC, I would rather "cut down, not across" than use VNC. VNC is horrible.

    9. Re:Many Kudos! by spauldo · · Score: 2, Interesting

      Linux giving new life to old-PCs is a myth. It is in fact a lot slower at common tasks than f.e. Windows 98 with Office 97 - so why bother?

      I've got four pentium 1 class machines running right now, all running linux. One's a laptop, and I just can't afford a new laptop to replace it right now, and it does suck for office stuff, although it's fine for coding. Java's kind of slow on it, but it does the job.

      The other three machines are all headless and are in my cabinet. One runs my DHCP, DNS, and IRC. Another was originally set up for VOIP, although I don't really use it for anything right now. The third is my firewall, which runs nothing but the iptables scripts and raccoon. It does things most cheapo routers won't, since it has the full flexibility of iptables, and it does come in handy.

      Why would I want to pay good money for fast machines for stuff that doesn't require them? I'm not worried about reliability - backing up drives smaller than a gig isn't a problem, and I've got about fifty more of those exact machines in storage - and I've got a nice athlon xp mobile box acting as a server for my database server and webserver. I'm a hobbyist nowdays, along with some small-time contract work, so I don't need anything more.

      If you don't have a use for old PCs, that's fine. There's plenty of us who do.

      --
      Those who can't do, teach. Those who can't teach either, do tech support.
    10. Re:Many Kudos! by geminidomino · · Score: 1

      I actually like the text-based install: it's the right technology for what it does.

      Amen. If you have to touch a mouse during the installation of what will become a headless server, you've already failed.

    11. Re:Many Kudos! by kosmosik · · Score: 1

      > I've got four pentium 1 class machines running right now, all running linux.
      > One's a laptop, and I just can't afford a new laptop to replace it right
      > now, and it does suck for office stuff, although it's fine for coding.
      > Java's kind of slow on it, but it does the job.

      OK - you cannot afford new laptop, but if you could the first thing you've done is replace the old one and use the new. If you do Java for living you wouldn't want your workstation to be slow? It is kind of investment.

      > The other three machines are all headless and are in my cabinet.
      > One runs my DHCP, DNS, and IRC. Another was originally set up for
      > VOIP, although I don't really use it for anything right now.
      > The third is my firewall, which runs nothing but the iptables
      > scripts and raccoon. It does things most cheapo routers won't,

      And also the three machines consume power - so if you replace the three with one slick server machine it would return the investment in like a year (since it consumes less power). Also you probably don't mind the fan noise from three old PCs - I do.

      > since it has the full flexibility of iptables, and it does come in handy.

      Heh, same as my router. It has iptables (2.4-linux-uclibc based), telnet interface and all that stuff.

    12. Re:Many Kudos! by spauldo · · Score: 1

      I don't do java for a living. I code as a hobby, and I actually use java for running a few java apps that I didn't write a lot more than I use it for writing my own stuff. If I did code professionally, then it'd be a priority.

      As far as the power issue goes, my power bill isn't huge, so I'm not worried about it. These machines are pretty decent power-wise - I don't remember the power supply rating, but I'd guess it around 150W - they're ancient HP Vecra workstations. I'd imagine my main server and my workstation pull more power than those old machines.

      All my servers are in an old telco cabinet in the spare bedroom, so I don't hear them, but I used to run four or five machines in my dorm in the air force and you'll find you quickly get used to the fan noise. Disk noise is a bit more annoying, and I remember waking up instantly one night when a head crashed... not a fun thing to wake up to at three in the morning. It was nice being able to tell by the sound if someone logged in remotely though.

      A bonus is that the old pentium boxes are very resistant to heat. My air conditioning doesn't extend to that room very well. This summer I've had my athlon server go down a couple of times due to overheating, but I haven't had a blip out of those machines, even though they're the type that have a passive heat sink with the power supply fan blowing on them instead of a dedicated processor fan. And again, if the heat damages them, I can just chuck 'em and put another in its place.

      Cool about your router. I wouldn't mind playing with something like that someday myself, although automated scripts and web interfaces tend to take all the fun out of it if you can't override them.

      I've got about fifty of these machines left in storage, and it's nice being able to actually use them for something. I don't do sysadmin work professionally anymore, but it's fun to putz around with, and these things are perfect for someone who lives in a money trap style house like I do.

      --
      Those who can't do, teach. Those who can't teach either, do tech support.
  19. Are you sure this is Slackware? by DiscWolf · · Score: 3, Funny

    XOrg 6.9, 2.4 Kernel ... are you sure this isn't Debian?

    1. Re:Are you sure this is Slackware? by Anonymous Coward · · Score: 0

      Great troll. :-)

      ii xorg 7.0.23 X.Org X Window System
      ii linux-image-2.6.17 2.6.17-5 Linux kernel 2.6.17 image on PPro/Celeron/PII/PIII/P

      See you using Debian GNU/Linux Etch in December 06'. :-P

    2. Re:Are you sure this is Slackware? by Anonymous Coward · · Score: 0

      Nah. If it was Debian it would be kernel 2.2 and XFree86 3.2.

  20. Gotta love Slackware... by ClickOnThis · · Score: 4, Informative

    ... 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/) that offer lots of additional packages and goodies.

    --
    If it weren't for deadlines, nothing would be late.
    1. Re:Gotta love Slackware... by Jack+Action · · Score: 2, Interesting

      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.

      That's the essence of Slackware.

      I use Slackware on my home network. Its runs the gateway on an old 486, my desktop/file-server on a 3.4 Ghz Intel, and on the 32MB Ram Pentium laptop I use to read mail on the couch.

      Like the name says, its the distro for the good kind of lazy. All hail J.R. Dobbs.

  21. Patrick, maybe the time's come by buffoverflow · · Score: 5, Interesting

    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.

    1. Re:Patrick, maybe the time's come by KillerBob · · Score: 4, Interesting

      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.

      --
      If you believe everything you read, you'd better not read. - Japanese proverb
    2. Re:Patrick, maybe the time's come by freshman_a · · Score: 4, Insightful

      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

    3. Re:Patrick, maybe the time's come by Pop69 · · Score: 1

      You miss the whole point of Slackware.

      It's the OS that Pat compiles to use himself, he just happens to release it to others as well.

      Oh, Praise Bob !

    4. Re:Patrick, maybe the time's come by DamnStupidElf · · Score: 1

      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.

      With a properly configured *nix system, you don't *need* virtualization.

    5. Re:Patrick, maybe the time's come by bersl2 · · Score: 1

      I've always thought that while Pat should continue to maintain Slackware stable and current, several people should maintain a full or mostly-full Slackware testing distro, so that making new packages and newer versions of existing packages ready for inclusion into mainline Slackware can be expedited. There's no reason why the Slackware philosophy cannot be extended to newer packages.

  22. Re:Screenshots? by Reverend528 · · Score: 1
    Anybody can install Gnome.

    Yeah, but it takes balls to install gnome when it's shipped as a tar of binary files.

  23. slackware 11.0 is great news by Anonymous Coward · · Score: 0

    I have been using slackware now for almost a year. before then I have no linux experience. Just that it has been maintained by one person for so long, is in itself the thing that makes slackware so powerful. Congrats to Pat (whom I've never met) for being such an example of what it means to truely keep to what you love.

  24. Re:2000 called, they what their kernel back by GotenXiao · · Score: 1

    Slackware's primary design concern is stability. 2.6 is relatively new, especially by Pat's standards. To be quite frank, it doesn't make a difference; there's a 2.6 kernel option available. Even if there wasn't, there's nothing stopping you from making your own (and given Slackware's target audience, the geek, this is somewhat expected).

    Note: proud Slackware user here.

    --
    Goten Xiao
  25. Ah Slackware. by jellomizer · · Score: 1

    I remember using Slackware 2.0 in 1994. Ahh the memories, Looking at it now it hasn't changed much. I am not sure if it is a good thing or not.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  26. I remember Slackware 1.0 by geekoid · · Score: 1

    you bastard!

    It was Pain.

    But I got it to work AND dual boot.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  27. We are Slackers... by Nichole_knc · · Score: 2, Interesting

    IF you have not used Slack then you should not be a bashing it.... Slackware 10.# + is the rule at this house. Six boxes total (2 are daily "drivers", 2 are servers with 2 backups). This box here (mine) is a custom built box on a Soyo Dragon mobo that came out of a dumpster. You heard me... a Dumpster.... It started as a Slackware 10.1 stock with a 2.6.10 kernel, not very stable... Went back to the 2.4.28 kernel and had no problems... I have tons of custom apps buolt on this box. It has also been updated beyond Slackware Current and I have been running KDE 3.5 since early last year (self built). Slack is solid and if you prefer a more stable platform not loaded with a bunch of "eye candy" than it is what you want... Oh and Slack is very fast..... on any box....

  28. Re:2000 called, they what their kernel back by Anonymous Coward · · Score: 0

    Um... Kernel 2.4.33 was just released on August 11th 2006
    check kernel.org

  29. But what I really want to know is by suitepotato · · Score: 3, Funny

    when is the next Yggdrasil release? Oh, right, I was thrown back six or seven years by seeing the name Slackware and the list of specs. Never mind.

    --
    If my grammar and spelling are off, I am [distracted/tired/careless] (take your pick)
    1. Re:But what I really want to know is by evilviper · · Score: 2, Insightful
      Oh, right, I was thrown back six or seven years by seeing the name Slackware and the list of specs.

      Right. Sure does suck, doesn't it, that there is a Linux distro out there that is extremely stable, and doesn't just jump to the latest version of everything without testing?

      All Linux distros should just be random collections of the latest packages, leaving the users to figure out why nothing works...

      The people that are saying "It's only one guy" are completely off the mark. Slackware is the most stable distro I've come across, no matter how many maintainers are involved.

      Not to mention it's the only distro I've seen that includes full headers with every single package (no extra configuration, no hunting -dev packages down, no need to compile from source programs you've already installed binary packages from, etc). It has a fully working and effectively bug-free development environment, which you probably can't say of any other distros.

      I know the attration to shinny new distros, and all their hype. But use them for a few months, and think of all the hassles and work-arounds you put into it, and ask yourself which of those features is worth an OS environment you continually have to tweak to get basic stuff working.

      But what do I know, I've only had Slackware up and running on my DVR machine for about 3 years now, with not one problem to speak of, even across several changes of TV tuners, sound cards, video cards, etc. I've never even needed to recompile the kernel.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  30. Subscription by tjw · · Score: 1

    For regular Slack users there is also the Subscription.

    --

    XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UB E-TEST-EMAIL*C.34X
  31. Re:2000 called, they what their kernel back by KillerBob · · Score: 1

    Not even mentionning that pretty much all of the 2.6 goodies get ported back to 2.4 :-) 2.4.33 was released on August 11, 2006....

    --
    If you believe everything you read, you'd better not read. - Japanese proverb
  32. Re:2.4 kernel: despair by mobby_6kl · · Score: 1

    I'm surprised no one has yet posted this: Slackware Linux Poster

  33. why? by Gerzel · · Score: 1

    Why does slackware even bother making a screenshot tour?
    From my understanding it is a stability oriented platform with a focus on the terminal interface. Thus the actual screen shots, if they do a good job, should be the same thing over and over again.
    >>: "some command"
    : Command done successfully. Whee!
    *lather rince repeat*

  34. Re:Another Important Announcement by jonathansizz · · Score: 1

    It was a joke - interesting response though, in light of those other posts claiming that Slackware lacks the fanatical userbase of other OS's.

    Other comments get insightful mods for laughing at Slackware sticking with stable version numbers instead of going with cutting edge stuff; I get modded flamebait for joking that a beta release of a relatively minor Linux distro isn't exactly gripping stuff..

  35. Re:2000 called, they what their kernel back by tjw · · Score: 3, Informative
    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.

    --

    XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UB E-TEST-EMAIL*C.34X
  36. Linux Is Dying by jonathansizz · · Score: 2, Funny

    It is official; Netcraft confirms: Linux is dying

    One more crippling bombshell hit the already beleaguered Linux community when IDC confirmed that Linux market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that Linux has lost more market share, this news serves to reinforce what we've known all along. Linux is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin to predict Linux's future. The hand writing is on the wall: Linux faces a bleak future. In fact there won't be any future at all for Linux because Linux is dying. Things are looking very bad for Linux. As many of us are already aware, Linux continues to lose market share. Red ink flows like a river of blood.

    Ubuntu is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time Ubuntu developers only serve to underscore the point more clearly. There can no longer be any doubt: Ubuntu is dying.

    Let's keep to the facts and look at the numbers.

    Debian leader Murdock states that there are 7000 users of Debian. How many users of Ubuntu are there? Let's see. The number of Debian versus Ubuntu posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 Ubuntu users. Kubuntu posts on Usenet are about half of the volume of Ubuntu posts. Therefore there are about 700 users of Kubuntu. A recent article put SUSE at about 80 percent of the Linux market. Therefore there are (7000+1400+700)*4 = 36400 SUSE users. This is consistent with the number of SUSE Usenet posts.

    Due to the troubles of SUSE, abysmal sales and so on, SUSE went out of business and was taken over by Novell who sell another troubled OS. Now Ubuntu is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that Linux has steadily declined in market share. Linux is very sick and its long term survival prospects are very dim. If Linux is to survive at all it will be among OS dilettante dabblers. Linux continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Linux is dead.

    Fact: Linux is dying

    1. Re:Linux Is Dying by subxero37 · · Score: 1

      What the hell are you talking about?

    2. Re:Linux Is Dying by jesuscyborg · · Score: 1

      You haven't been around here very long, have you?

    3. Re:Linux Is Dying by tux_fairy · · Score: 0

      Is this moron on crack or something? Dude, go have sex on a dirty window with billie or go lick that bald head you seem to be dreaming about..

    4. Re:Linux Is Dying by Anonymous Coward · · Score: 0
      Red ink flows like a river of blood.
      It's true - Ubuntu is losing millions, because they have to literally give their product away. And what for? Linux has a 0.36% market share after all these years of concerted development & evangelism. It obviously isn't going to take off. Ever. How much longer can this go on before Shuttleworth pulls the plug?
  37. What's the proper way to upgrade Slack distros? by Anonymous Coward · · Score: 0

    Posting anon since this might be off-topic. But what's the "proper" way to upgrade from one Slackware distro to a newer one? The last time I just plain installed one version over my last version, a lot of things stopped working, especially X. A professor I had said he always just formats his entire Linux partition and installs fresh... buuut... he was always a kind of reckless fellow, and I cannot afford to format over my entire partition. Is there a sensible "middle-ground" way to upgrade to a newer Slackware distribution without breaking anything (and this probably applies to upgrading any version of any distro).

    1. Re:What's the proper way to upgrade Slack distros? by ledow · · Score: 2, Informative

      I've done upgrades over at least three version of Slackware that I can remember (and a lot more clean installs) but all went smoothly.

      - Follow UPGRADE.TXT to the letter (in the root of the CD for the new version) not forgetting to move any .new files over to their proper names but with your configuration details entered (use the .new because sometimes the format changes a lot)
      - Boot in single user mode and upgrade to latest kernel version (kernels go out of date too fast to rely on the default one being worthwhile for more than a few weeks or so). Don't forget lilo/grub etc.
      - Make sure that any graphics drivers/kernel modules/etc. that you compiled in are recompiled with a version suitable for your new kernel
      - Reboot and X should work just fine, then you may need to recompile or upgrade some of your software (e.g. if it's compiled against an earlier glibc or kernel).

      It's a pain in the bum, especially if you have a lot of software or driver modules that are fussy about what they compile against, but it's usually a damn sight easier than trying to transfer all your software, config, etc. over to a new clean install.

    2. Re:What's the proper way to upgrade Slack distros? by Edzor · · Score: 1

      yeah i have always read the UPDATE.TXT, looked at it for a while then thought i would always mess something up. it would be fubared mess of the last version and the next :(

  38. funny by goarilla · · Score: 1

    very funny to see this story submitted at the exact same day
    i was rsyncing current slackware ...
    after 3 months of not feeling the need to stay up to date :D

    1. Re:funny by Anonymous Coward · · Score: 0

      i just finished setting up a 10.2 box a replacement for my trusty 9.1 machine... doh. again, again!

  39. This Slashdot Story Almost News! by Blakey+Rat · · Score: 1

    "Almost" doing something isn't newsworthy, damnit. Yes I am grumpy.

  40. Slackware 11.0 Almost Done by trailerparkcassanova · · Score: 1

    The headline reads like a story from the Onion.

  41. How about Zenwalk? by Bonzodog01 · · Score: 1

    Guys, there is derived distro's from Slackware you know. Try Zenwalk Linux. Kernel 2.6.17, Xfce 4.3.9Beta1, it's own repo/package management system. It is to slackware what Ubuntu is to Debian.

    1. Re:How about Zenwalk? by tiocsti · · Score: 1

      Full of proprietary drivers?

  42. Re:2000 called, they what their kernel back by Anonymous Coward · · Score: 0

    If you have not used Slackware then.

    Shut the hell up!

    If all you do is distro dance.

    Than shut the hell up!

    If all your after is pretty screen shots.

    Then shut the hell up!

    You are not qualified to talk on the subject!!!!

  43. Re:2000 called, they what their kernel back by jones_supa · · Score: 1

    Yes, but it's still based on old technology.

  44. IPv5 by Doc+Ruby · · Score: 1

    "There are still a few changes yet to happen, but let's call this Slackware 11.0 release candidate 1."

    Why not just call it "Slackware 20.0 RC1", and make everyone think it's really advanced? It's not a release candidate when you know it is certain not to be released. It's a beta, tested by people who didn't design or implement it.

    --

    --
    make install -not war

  45. *Clicks Screenshot Link* by HuckleCom · · Score: 1, Insightful

    Because you KNOW the screenshot gallery is a direct representation of what a linux distribution stands for...

  46. Stone knives and bear skins by amightywind · · Score: 1
    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.

    Slackware is very confused about what it is. It used to be the hacker's GNU/Linux. That title now belongs to Gentoo or Ubuntu. It is not an operations oriented distro like Debian. It is not commercially accepted like Red Hat or SuSE. Who are they protecting with all of the caution?

    --
    an ill wind that blows no good
    1. Re:Stone knives and bear skins by pwrtool+45 · · Score: 1
      It used to be the hacker's GNU/Linux. That title now belongs to Gentoo or Ubuntu.
      I do not think that word means what you think it means.
  47. Re:Another Important Announcement by FreonTrip · · Score: 1

    I didn't mod you, and even if I had the points I wouldn't have downgraded your post. It simply didn't have any readily verifiable characteristics I'd normally associate with a joke, so I assumed it was serious and tried to call you on it. No hard feelings.

  48. Needless screenshots.... by Anonymous Coward · · Score: 0

    Every posting about every damn 0.0.1 revision of any Linux distro comes with a completely superflously screenshot tour!
    These screenshots show always just the damn latest version of KDE / Gnome and often Gimp and Evolution (and the advertising text on the distros webpage will always try to sell these programs as their very own achievement...) which has really nothing to do with the distro itself.

  49. Re:2000 called, they what their kernel back by Bill+Kilgore · · Score: 1

    Don't you people get tired of the same old complaint? If you don't want to run 2.4 then don't. No one's forcing you to. But just FYI, your opinion, interests, and needs do not encompass the universe of Linux.

    There are reasons why 2.4 kernel development continues. Also, I don't see how non-programmers are going to see or care about much difference between 2.4 and 2.6.

    --
    Rediculous: A word indicating the writer is ridiculously ignorant.
  50. Why Slack these days? by jfz · · Score: 1

    I've enjoyed using slack purely because it doesn't try to get in the way of an experienced linux user with a mess of configuration utilities and package management. At the same time it provides enough basic, simple, and direct facilities to avoid the desire to roll my own distro.

  51. Bullshit by Anonymous Coward · · Score: 0

    Xorg 6.9 and 7.0 are not the same code; 7.0 supports my video card whereas 6.9 does not. Thus, my distro being stuck back on 6.9 for all friggin eternity makes it so I have to patch and recompile my Xorg to get decent video.

  52. Takes me back, but not much has changed? by GC · · Score: 1

    Well, slackware was my first distribution.

    Back in 1991, I installed Slackware 2.3 (from a set of 20 or so floppy disks).

    So when I saw this article, I thought hmm, got to see that distribution screenshot thingy...

    Well lo and behold, the first handful of screens have hardly changed at all! The same UI the same screens! First deviation was cfdisk, which I think we had to exit to shell and run fdisk in 2.3, but otherwise - EXACTLY the same.

    The KDE screenshots, well, they look like KDE on any distribution, so discount those as meaningful in any sense.

    Slackware was always stable for me, but I stopped using it at around version 9, and after hopping around for a better alternative I've now settled with Gentoo, which provides me with what I need and I still use the odd trick I've learnt from Slackware to break the rules with Gentoo when I find it doesn't do what I want.

    Still, an interesting article.

  53. Re:2.4 kernel: despair by Anonymous Coward · · Score: 0

    Clearly, the person that created this poster/jpg and the person that linked to it knows nothing about Linux or Slackware. The configuration window in the so called Slackware poster jpg is from Trumpet Winsock that ran on Windows 3.1 which never had anything to do with Linux or Slackware.

  54. Scientific Notation Required by Anonymous Coward · · Score: 0
    I wonder what share of the

    0.36% of computers that linux runs on Slackware has?

  55. Slack is the way to go by kolme · · Score: 2, Informative
    I've run Slackware on my computer for 4 or 5 years, then switched to Ubuntu. Each one has its own advantages and disadvantages, but if you know your way around, Slack is way better.
    • Slackware is significantly faster. And much faster with a custom kernel. All the system scripts are written in plain old bash, and the init system, based on BSD's, it's simpler and more elegant. It's just more Unix-ish.
    • The package system is simple, so simple it'll never break. You won't have dependency problems, because there aren't any dependencies. All the headers come with the packages, so you don't have to install any *-dev packages to compile some app.
    • All the software bundled with Slack is unmodified. It's a plain Kernel from kernel.org, with plain GNU stuff and a plain KDE. No especial artwork, nor funny shit you'll never use. Come on, everybody changes the wallpaper and theme after installing a distro.
    • Never crashes, unless you've messed up the config files. I've sometimes seen Fedora and Ubuntu behaving sluggish or buggy. In Slack this NEVER happens (or never happens to me).
    Ubuntu is still installed on my computer, and although it's a nice distro, I'll be back slackin' in no time.
    --
    $ whoami
    1. Re:Slack is the way to go by c0d3m4n · · Score: 0

      Perhaps you should look at Arch Linux. It's fast, clean, and you won't have dependency problems. It's not because there aren't any, however, because that would be silly, as deps often help when installing a suite of applications, which can be troublesome on Slackware. Arch's Pacman will just grab the dependencies you need in a simple manner, and everything is up to date, without being patched gratuitously or named funny, as is the case in Ubuntu and other .deb sorts.

    2. Re:Slack is the way to go by geminidomino · · Score: 1

      Never crashes, unless you've messed up the config files. I've sometimes seen Fedora and Ubuntu behaving sluggish or buggy. In Slack this NEVER happens (or never happens to me).

      That may not be exactly true. I've had my system wedge up on me a few times. Of course, it may not be slack-related at all when I think about it, since it seems to happen when I dare to run ActiveState's Komodo and xmms at the same time...

  56. I think I know what it really means by amightywind · · Score: 1

    I use the word in this context. Got it?

    --
    an ill wind that blows no good
    1. Re:I think I know what it really means by geminidomino · · Score: 1

      Chopsticks and Ubuntu?

      Interesting combination of concepts there.

      Gentoo's not a hacker distro, it's a ricer distro.

    2. Re:I think I know what it really means by amightywind · · Score: 1
      Gentoo's not a hacker distro, it's a ricer distro.

      What the heck are you talking about?

      --
      an ill wind that blows no good
    3. Re:I think I know what it really means by geminidomino · · Score: 1

      Never seen it huh?

      A humorous site (if you're not a gentoo user, I suppose).

    4. Re:I think I know what it really means by amightywind · · Score: 1

      I am a Gentoo user, but I'm probably a little too old to relate. I don't use the forums much anymore, where those hilarious quotes come from. Thanks for the link.

      --
      an ill wind that blows no good
  57. What's the advantage of a single maintainer? by Anonymous Coward · · Score: 0

    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

    OK ... so? You say this like it's a good thing -- a feature of a distribution that's significant enough to outweigh more practical considerations.

    Why do you consider it a feature?

    I don't really care in principle if my distro is maintained by 1 guy or 1000. But in practice, by using a distro maintained by 1000 (give or take), every package I've ever wanted, I've found. That's a big advantage. What's the advantage to one maintainer?

    I'm reminded of jwz's easter egg comment: "Convenient though it would be if it were true, Mozilla is not big because it's full of useless crap. Mozilla is big because your needs are big. Your needs are big because the Internet is big. There are lots of small, lean web browsers out there that, incidentally, do almost nothing useful."

    A distro maintained by one person sounds like a recipe for a small distro, i.e., a distro that doesn't do as much as I need.

  58. Almost doesn't count by iminplaya · · Score: 1

    except in horseshoes, hand grenades, and atom bombs...

    --
    What?
  59. Thank you, Pat by CrkHead · · Score: 1
    When I was distro shopping in the late 90's, trying everything out there and throwing it against a couple boxes, Slack just stuck.

    I have tried several distros over the year, but any 'stable' machine has been Slackware since I started to move to Linux.

    Oh, BTW, for those that complain about newest hardware support, talk to the manufacturer of the hardware. If they are doing their job, you just need to learn ./configure && make && sudo make install.

  60. the swiss army knife of distros by Anonymous Coward · · Score: 2, Informative

    Its a shame that people see slackware as dated. Slackware's stability, and flexibility, makes most other distroes look like another windows. Slackware is a stable base on top of wich you can put whatever you want. Slackware isn't an enterprise solution, but you can easily build an enterprise solution on top of it. Its basically ready to go as a simple webserver though. Slackware is like a blank canvas, just gnu, linux, and a few basic utilities. Gentoo is probably the closest linux to it, but gentoo's portage and weird init scripts are very particular to gentoo. And rebuilding my OS when I want to upgrade isn't very appealing. Slackware's package management, and configuration scripts, are so basic and unobtrusive that they never break or get broken by any modifications you may need to make. I can see why this is annoying to some. Most people would rather spend time using their OS than adding to it or maintaining it. I can see why ubuntu and fedora tend to be the OS of choice for desktop users, but I fail to see their advantage to power-users and server admins. If you're a control freak, and don't have enough time to do LFS, slackware is a great starting point. For what its worth, here is a shot of my laptop running slackware: http://home.comcast.net/~diabolix/shot.png

  61. I am a 42 year old ricer by amightywind · · Score: 1

    I read the link through. It is true! I am a 42 year old ricer! My machine is tricked out with LED's. It is very reminiscent of the street rod pictures on the site. I have made the same hyperbolic Gentoo claims, even on this forum. I still believe them! 10 years ago I was a staid SunOS user who wrinkled his nose at PCs. That all changed with my first Abit Mobo, AMD CPU, and LED fan.

    --
    an ill wind that blows no good
  62. Thank you Patrick. by CeePhour · · Score: 1

    Seriously, thank you.
    I've not used another distribution that I could tolerate for more than a few hours, Slackware being the exception. It's consistently excellent and for the past few years that I've been using Slackware you've proven your mastery over the rest of the crowd. Your vision of this distribution is exactly what a lot of people look for. I think a lot of the others are too afraid to do what Slackware does (probably because it does it the best, no contest), and aim for flash and glitz.

    Ignore the trolls and nay-sayers. I know it's hard, but there is a legion of Slackware users that appreciate the work you do for us.

    On a side note, not everyone wants crappy custom GUI tools to configure their machines and a slow and annoying "magic installer thingy" (I'm looking at you YaST) to download and install their software. Some of us like having control.

    Press the discs, my money is ready to be sent :)
    Once again, thank you.

    --
    Just because you diffused the bomb doesn't mean you're not holding a half pound of C4.