Slashdot Mirror


Slackware 10.0 Officially Released

BRTB writes "Slackware 10.0 is out! X.org 6.7.0, kernel 2.4.26 (2.6.7 optional), KDE 3.2.3, GNOME 2.6.1, GCC 3.3.4... it's all new, and just as stable as you'd expect from Slackware, if RC2 was any indication. There's an official announcement, as well as some ISO BitTorrent links, and a mirror list. Of course, the non-cheapskates among us should go buy the CD-set to support the project. Have fun, everybody..."

521 comments

  1. Wasn't expecting this so fast. by Wig · · Score: 0, Offtopic

    Although, I'm sure Slack is the greatest it ever was, and won't let me down. If I had DSL, I would get it right away, but...56K doesn't believe in fast downloads. Yes, I'm still in the stone age.

    1. Re:Wasn't expecting this so fast. by Anonymous Coward · · Score: 0

      > Yes, I'm still in the stone age.

      If you're creaming yourself over a Slackware release, and feeling depressed because your USRobotics/56 can't download all the packages in a timely manner, then YES, I'd say you're still in the stone age (for either of those two reasons).

    2. Re:Wasn't expecting this so fast. by Anonymous Coward · · Score: 0

      There was a time when people had to spend all night downloading disk sets of slack, on much slower connections. Or, God forbid, order a copy.

  2. about time by jedi_rhnio · · Score: 1

    finally, I love Slack I cant wait to give this a spin.

    1. Re:about time by zoloto · · Score: 1

      Finally? Wow, this was a quick release since 9.1 came out. I was expecting it to take longer? Perhaps some of the other developers or donations came through so he could work on his baby.

      This was my first distro ever when I got off Windows. Once a slacker, always a slacker.

    2. Re:about time by ThatComputerGuy · · Score: 1

      Wha? Slack isn't a part-time effort, Pat works on it full time.

      --
      XML is like violence. If it doesn't solve the problem, use more.
  3. xorg + radeon by Coneasfast · · Score: 2, Interesting

    anyone tested x.org 6.7.0 . i want to know if it supports proper 2D drivers for later radeons (9600 and later) out-of-box? i know xfree86 4.4.0 does.

    --
    Marge, get me your address book, 4 beers, and my conversation hat.
    1. Re:xorg + radeon by failedlogic · · Score: 1

      I've been using the VESA drivers since the Radeon driver doesn't work with my 9600 XT (or at least the one included with x.org 6.70 as packaged with Slackware).

      Is there anyway to add the file to the X.org driver list or something? What speed differences are there between the GPL'd driver and the ATI one for just general X use and no OPEN-GL stuff?

    2. Re:xorg + radeon by Tyler+Eaves · · Score: 0, Offtopic

      Huge difference.

      --
      TODO: Something witty here...
    3. Re:xorg + radeon by sp0rk173 · · Score: 3, Informative

      I'm running it right now with a 9700 pro. No problems. Runs beautifully.

  4. Yay! by thenextpresident · · Score: 5, Funny

    Damn, and I am going home now too. Wait, I know...

    Me: Hey, can you go grab slackware 10 for me?
    My GF: Sure.
    Me: They have bittorrents...
    My GF: I know. Already downloading...

    Oh yeah. Tech girlfriends...the only way to download distro's. =)

    --
    Jason Lotito
    1. Re:Yay! by Anonymous Coward · · Score: 3, Funny

      Of course, no one actually believes you have a geek girlfriend.

    2. Re:Yay! by Anonymous Coward · · Score: 0, Funny

      Oh yeah. Tech girlfriends...the only way to download distro's. =)

      they are useful for fucking too!

    3. Re:Yay! by rkef · · Score: 0

      Hmm. His nick is "thenextpresident"; I'm guessing fantasy post ;)

      Go Slackware! I'll always reserve a place for you, on every hard drive I come across.

    4. Re:Yay! by Anonymous Coward · · Score: 1, Funny

      You just sent 99% of the readers on this site into shock by mentioning sex with an actual woman.

    5. Re:Yay! by Dorothy+86 · · Score: 1

      yeah. I decided to try out this linux bandwagon about a 2 weeks ago; so i downloaid slackware... JUST IN TIME FOR A NEW RELEASE. damn :-(

    6. Re:Yay! by Anonymous Coward · · Score: 2, Funny

      for those who become depresesd as they know that they shall never have the joys of carnal knowldege of a woman... i suggest: the the Fleshlight :)

    7. Re:Yay! by Anonymous Coward · · Score: 0

      Hmm. His nick is "thenextpresident"; I'm guessing fantasy post ;)

      Wow Ralph Nader is a Slackware Linux user...

      Vote Nader 2004!!

    8. Re:Yay! by Anonymous Coward · · Score: 0

      I think I may have a geek girlfriend.

      She still uses Windows 2000, and sometimes has trouble remembering her hotmail address, but she has ascended Nethack characters on nethack.alt.org about eight times, which is surely a nerd feat.

    9. Re:Yay! by Pieroxy · · Score: 1, Redundant

      Unless you're really willing to get your hands dirty up front, and if you really are a n00b with Linux I wouldn't recomment Slackware as your first distro....

      Try some more user-friendly distros such as RH, SuSE, Mandrake or other...

    10. Re:Yay! by ianr44 · · Score: 1

      Don't worry. With Slackware you can only run into that issue every year or more.

    11. Re:Yay! by Dorothy+86 · · Score: 1

      exactly what I want to do. I do have a few friends handy who can help out; AND the slackware book is really helpful. I've had fairly good luck so far.. the hardest thing *yet* was gifuing out vi so I could edit menus for fluxbox. Lilo was easy, even config for X was easy. Next step is sound card (which should work with a new kenel) and getting my external drive accessible. But, I didn't really want to go with mandrake, or RH which IMHO do too much for you at installation. Granted, slack does a lot... but it seems a good balance.

    12. Re: Yay! by theparanoidcynic · · Score: 1

      I'll believe it because it's just too adorable to attack.
      Also, if it's true it means that the only class of women capable of ever loving me is real . . . . .

      --
      Only in a Slashdot fantasy can a Slackware install turn into several hours of sex . . . . .
    13. Re:Yay! by Anonymous Coward · · Score: 1, Informative

      Considering that Pat has been doing two releases each year for several years now, your post doesn't make much sense. Slackware 9.1 only came out like - 9 months ago. There was only 6 months between 9 and 9.1.

    14. Re:Yay! by jazman_777 · · Score: 2, Funny
      Unless you're really willing to get your hands dirty up front, and if you really are a n00b with Linux I wouldn't recomment Slackware as your first distro....

      Yeah, Fedora Core 2 for the dual-booter n00bs, eh? Joke's on them.

      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
    15. Re:Yay! by ianr44 · · Score: 1

      Yeah, I completely misspoke there. Got the 9 release confused with 9.1... Oh well.

    16. Re:Yay! by Anonymous Coward · · Score: 3, Funny

      More like:

      Me: Hey, can you go grab slackware 10 for me?

      My GF: Are you kidding? I used slack in HIGH SCHOOL. Stick with gentoo, big guy.

      Me: Well, I wanted to try it out. Maybe it's gotten better!

      My GF: Tell you what, I'll start giving you a blow job and I won't stop until the distro finishes installing. Now which distro do you want to try?

      Me: HOLY SHIT! Gentoo, please!!!!!!!!!!!!!! And remember I use both KDE and Gnome!!

      Oh yeah. Made-up fantasy girlfriends are the BEST. =)

    17. Re:Yay! by ShadowRage · · Score: 1

      yes, techie girlfriends rock like all hell.

    18. Re:Yay! by Bandman · · Score: 1

      I bow in respect. Some day I hope to find the nirvana that you have reached.

      My last techie girlfriend owned a Wallstreet model Powerbook *shudder*

    19. Re:Yay! by Rodrin · · Score: 1

      Damn straight, thats why I use Gentoo...ahem..If I had a geekgirl..too bad I'm stuck with the average woman.

    20. Re:Yay! by zoloto · · Score: 5, Insightful

      Now if the slashdot effect would take effect on the following torrets, we'd be in business much quicker:

      Slackware 10.0 Installation ISO disc 1
      Slackware 10.0 Installation ISO disc 2 (GNOME/KDE/KDEI, /testing, live rescue disc)
      Slackware 10.0 ISO disc 3 (Sources part 1, /extra , Slackware book)
      Slackware 10.0 ISO disc 4 (Sources part 2, ZipSlack, /pasture)

      Please download and keep your torrents open to at least a 1:1 ratio! I do it, so can you! LEave it on ALL NIGHT BABY!

      Offtopic: I for one welcome our slashdotting overlords.

    21. Re:Yay! by Anonymous Coward · · Score: 0

      Everyone knows that slackware is a multi-disc install... Disc two won't be inserted if the installer is "occupied" so the install will never finish...

    22. Re:Yay! by MuParadigm · · Score: 2, Funny


      So glad I don't live in your world.

    23. Re:Yay! by Anonymous Coward · · Score: 0

      Alright who modded the parent "Funny?" It should be informative...

    24. Re: Yay! by MuParadigm · · Score: 1


      I'm 39 years old. Trust me. They're real.

    25. Re:Yay! by Anonymous Coward · · Score: 0
      Screw vi. Slack has pico, which is much easier for quick editing.

      On configuring sound, here's a link.

      There is a post about half way down on how to set up sound. It's for Slack 8, so you might have to play with it a little, but it has worked for me up to this point.

    26. Re:Yay! by Anonymous Coward · · Score: 0

      Marry that girl.

    27. Re:Yay! by bigberk · · Score: 1

      Torrent ratio? You can configure that? Anyway the torrents are working, I'm getting up to 60 KBytes/sec and will leave mine running all night.

    28. Re:Yay! by bigbadwlf · · Score: 0

      I wouldn't recomment Slackware as your first distro

      Slackware (3.6) was my first distro. I was quite happy with it, although I've run Debian ever since I discovered apt-get.

    29. Re:Yay! by Anonymous Coward · · Score: 0

      I'm getting 100 KBytes/sec down. I'm curious what others are getting on the ISO CDs?

    30. Re:Yay! by zoloto · · Score: 1

      i think so, however i was referring to those who use torrents to download their iso's really fast, and then shut them down when their upload rate hasn't reached a one-to-one (1/1) ratio yet.

      not that it's evil, but goes against the bittorrent principle of sharing bandwidth for very popular files etc.

      not that it's hard to share bandwidth considering most users have unlimited per month (or so mine says) on fast connections. Leavning it up overnight wouldn't hurt many people. I know I'll leave mine online for at least a week before burning the ISO's and installing it along side SuSE 9.1 that I just installed :) (boo yah!)

      --zoloto

    31. Re:Yay! by The+Analog+Kid · · Score: 0, Troll

      Last I check that was only if you picked KDE if you didn't it's only a one CD install.

    32. Re:Yay! by Anonymous Coward · · Score: 0

      In Slackware 9.1, KDE (plus KDE internationalisation packages) and GNOME were both on CD 2.

    33. Re:Yay! by pherthyl · · Score: 2, Interesting

      Hey cool, same here. First installed slackware 3.6 on my 386. Downloaded all the floppy sets over a 14.4 dial-up connection and installed it. It was great, I remember emailing a KDE guy asking if I could run KDE 1.0 with 4MB of ram. Turns out they recommended about 8MB...

      Oh the nostalgia.. I miss the excitement of the discovery in those days.

      Now I run Debian, which kicks ass, but it lacks the same kind of excitement and hobby feel as I had back then.

    34. Re:Yay! by TiMac · · Score: 2, Funny

      My last techie girlfriend owned a Wallstreet model Powerbook *shudder*

      Which should be perfectly fine, since one can assume that probably WAS around 1998...I know that some /.ers can go a decade without 2 girlfriends.

      Unless you've got something against the PowerBook...

      --

    35. Re:Yay! by Anonymous Coward · · Score: 0

      some /.ers?

    36. Re:Yay! by Anonymous Coward · · Score: 0

      for the most part i try to stay at a 2:1 (share twice as much as ye recieve) when i'm off at school (they don't monitor crap on the lines, so i do alot of things, trust me i work in there!) but at home with a measly 5kb max upload (i fucking hate charter) i can't really reach a 1:1 if at any point it downloads >50kbs (electric bill)

    37. Re:Yay! by Anonymous Coward · · Score: 0

      I am getting 100 who-the-fuck-cares per second.

    38. Re:Yay! by jusdisgi · · Score: 0

      Dude....shut the fuck up.

      --
      Given a choice between free speech and free beer, most people will take the beer.
    39. Re:Yay! by Anonymous Coward · · Score: 0

      Gentoo sucks dick, it's a toy.

    40. Re:Yay! by Anonymous Coward · · Score: 1, Insightful

      Bzzzzzzt! Wrong, using one of those click and point distros will help you learn linux like running XP will, the issue with using one of the handicapped distros you mention is that it hides SO much of the internals, new people will start using the GUIs and never learning whats going on in the end, then when they move to slack, they are lost, and immediatly run back to something that can hold their hand, a BETTER idea is to START with slackware, then you'll learn the internals, so when that cool webadmin crap ruins a config file you can actually FIND the file and fix it, then later if you want, move to somehthing like half-a-mandrake or redshit, or that joke, gentoo, you'll have the knowledge to fix what those wannabe distros' gui tools break. I'll wager you use SuSe with KDE, why not just run windows XP if you're gonna use that garbage.

    41. Re:Yay! by Pieroxy · · Score: 1

      Bzzzzzzt! Wrong,

      I do use Slackware. And to be honest, I would point two things:
      1. If you want an OS to get things done, install SuSE, RH, etc...
      2. If you want an OS to learn how Linux works, run Slackware.

      Note that option 2 will occupy these evenings that you were wondering how to fill.

    42. Re:Yay! by finkployd · · Score: 4, Insightful

      If I had a geekgirl..too bad I'm stuck with the average woman.

      I suspect that if she ever stumbles upon this comment you will not have her much longer :)

      Finkployd

    43. Re:Yay! by jefe7777 · · Score: 1

      >>the hardest thing *yet* was figuring out vi so I
      >>could edit menus for fluxbox

      by all means keep practicing with vi, but you do know that fluxconf is your friend?

      it comes with fluxmenu. it's separate from fluxbox, so you need to download and compile it.

      http://devaux.fabien.free.fr/flux/

    44. Re:Yay! by Errtu76 · · Score: 1

      i strongly disagree. I'd said you _should_ go for slack and learn the hard (best) way. Anyone can install a package by rpm, but the real kick is when you got an entire system up and running, and you ./configured && compiled everything yourself. You know where what has been installed and what it does. Something i find lacking when dealing with rpm's. It's easier, yeah. But is it better?

    45. Re:Yay! by Anonymous Coward · · Score: 0

      The trouble with that is, afterwards, you might find that women don't feel as good, AND they are a helluva lot more annoying. And more expensive.

    46. Re:Yay! by Pieroxy · · Score: 3, Insightful

      It depends if you want an OS for getting things done or to play around.

    47. Re:Yay! by Feztaa · · Score: 1

      Torrent ratio? You can configure that?

      Yeah, it's called "closing the torrent when you're satisfied with what the ratio is".

      Please leave your torrent open until it's uploaded just slightly more than it's downloaded.

    48. Re:Yay! by Anonymous Coward · · Score: 0

      Except when they have more facial hair than you do...

    49. Re:Yay! by sarragorn · · Score: 0, Flamebait

      Bzzzzzzzt !, Like, what, you learned lunix "back in the good ol' dayz" with all us 1337 r00ts but now you're working for a big corporation and install redhat and suse ?! fuck off u lam3r.

    50. Re:Yay! by doshell · · Score: 1

      Is it possible to make BitTorrent download only from a specified IP range? I have a nasty 1GB international traffic monthly limit vs. 20GB national traffic (I'm in Portugal and my ISP is Netcabo). I've never heard of such possibility, but perhaps some of you know better than I do.

      --
      Score: i, Imaginary
    51. Re:Yay! by cloudmaster · · Score: 1

      Slackware was my first Linux experience, back in the early 90's. Prior, I had only used DOS and Windows, though I had recently started college and had an account on the HPUX 'n Solaris (SunOS? I forget) machines. I've still got the monsterous pile of floppy disks that I had to download to get it installed... Anyway, it forced me to learn how things worked in order to get *anything* done. Later, I built an early beta of KDE, which allowed me to move full-time to Linux (away from Win NT) until I learned the rest of how to do things.

      Slack's a great starter platform if you're serious, though not so good if you wanna go straight to a[nother] system that you don't need to know anything about... I still run Slack on my routers and several boxes, but I uses SuSE on most everything else just because that makes it easier to keep up-to-date on just about everything I'd want/need to run. :)

    52. Re:Yay! by Bandman · · Score: 2, Funny

      actually, it was around december :-/ and the Wallstreet had more wrong with it than our relationship (Ba-ZING)

    53. Re:Yay! by Anonymous Coward · · Score: 0

      2. If you want an OS to learn how Linux works, run Slackware.

      Note that option 2 will occupy these evenings that you were wondering how to fill.


      Or, get Gentoo as option #2 and you'll have time in the evenings to go out to a dinner and a movie while you wait for it to install.

      Best of both worlds!

    54. Re:Yay! by Alexis+de+Torquemada · · Score: 1

      Oh sure... your girlfriend's a geek. Had you said an astronaut, a supermodel, or a submarine commander - I would've believed you. But a geek? No way.

    55. Re:Yay! by Anonymous Coward · · Score: 0

      heh. not all of us live in our parents basements and actually DO need to get work done.

      you must be one of those arrogant little school kiddies.

      fucking lam3r. hah.

    56. Re:Yay! by wizrd_nml · · Score: 1
      Is there something wrong with the tracker? I successfully downloaded the first CD but now that I'm trying the second I seem to be having trouble connecting to the tracker.

      Anyone else experience this problem?

    57. Re:Yay! by Anonymous Coward · · Score: 0

      you could look up the countries allocated ip space and only allow those to the torrent ports. depending on your firewall. if your running linux or bsd (probably mac as well), this is easy. i dont know with any other OS...

    58. Re:Yay! by Anonymous Coward · · Score: 0

      170 Kbps

    59. Re:Yay! by kwoff · · Score: 1

      How many non geekgirls read News For Nerds?

    60. Re:Yay! by xilmaril · · Score: 1

      I think I speak for 90% of home computer users when I say I play around. Realy, how often do you productively use your home computer? if it's more than 5% of the time, I think you're beating the average. 2%, if you have kids/are one.

    61. Re:Yay! by Pieroxy · · Score: 1

      I think I speak for 90% of home computer users

      What would make you think so?

      I have kids, and that is the reason I don't play around anymore, because of my shortage of free time. I'd say that I must spend 75% of my time getting things done (Which include browsing, email reading, encoding my home videos, working on my website, etc...), and 25% playing around (trying to figure out config, preferences, skins, etc...)

      Although config went dramatically up in the last couple of days since I installed WinXP on one of my machines...

      The OS has at last become a commodity. It is something that I set up straight once and I don't want to get back to it once I'm done. It is the platform that allow me to get things done. If I spend time on it (read: more than 25%) it becomes an annoyance and gets in the way of everything else I want to do. Or because I want to, but then it becomes one of the things I want done.

      The problem with Slack/Gentoo, is if you're not a Linux guru, those config thing get in the way. With a SuSE (for example) you get the thing installed straight, it works, you can start working. If you want to play around afterwards, it's your choice. Not the other way around.

      Although I am a Slack user.

    62. Re:Yay! by bccomm · · Score: 1

      I'd have to disagree. Those distros don't ``hide'' shit. I learned how to use Linux well enough on Lycoris (yes, Lycoris) to make the switch to NetBSD only a few months later---with no help but manpages. You seem to falsely associate a nicely setup desktop environment with non-hacker types. What you fail to recognize is the fact that we appreciate style too...not that you would know.

    63. Re:Yay! by whiteranger99x · · Score: 1

      OH and I don't believe in compiling on different machines, so we'll let the installer run on my 486 ;)

      --
      Join the TWIT army now!
    64. Re:Yay! by wiremind · · Score: 1

      Probably none.
      But if the girlfriend ever does a vanity search on google for his username these slashdot comments will no doubt come up.

      My girlfriend discovered all sorts of stuff i said on K5 a long time ago. aqward silence followed for about a week.

    65. Re:Yay! by jefe7777 · · Score: 1

      >>aqward silence followed for about a week.

      now that's funny!

      where are the mods when you need em.

      rotflmao

    66. Re:Yay! by Anonymous Coward · · Score: 0

      Actually if you ask your ISP they might just go buy you the CD, it'll be cheaper for them than you using BT all night.

  5. Slack and X.org by dancingmad · · Score: 2, Interesting

    Perhaps its not completely germane, since it was announced a while ago, but again, kudos to Slack for moving to X.org so quickly. The faster everyone gets away from X the better we all are.

    --
    "There is no time, sir, at which ties do not matter," Jeeves, (Jeeves and the Impending Doom)
    1. Re:Slack and X.org by pairo · · Score: 2, Funny

      kudos to Slack for moving to X.org so quickly. The faster everyone gets away from X the better we all are. Aren't you contradicting yourself a bit there?

    2. Re:Slack and X.org by rmohr02 · · Score: 4, Funny
      The faster everyone gets away from X the better we all are.
      Away from XFree86 anyway. Personally, I prefer distros that still support X in some manner ;).
    3. Re:Slack and X.org by Anonymous Coward · · Score: 1, Interesting

      kudos to Slack for moving to X.org so quickly. The faster everyone gets away from X the better we all are.

      Yeah. Thanks for sharing that interesting insight. Can you tell us why you feel that way? What does X.org do better? Or is this just something you overheard on slashdot?

    4. Re:Slack and X.org by kfg · · Score: 3, Funny

      Personally, I prefer distros that still support X in some manner ;).

      E actly. It would seem a rather pointless and e treme measure to fail to support in some manner, at least lower case.

      The Window System is also nice to have around, but if you at least have support you can always still work at the console, although that might suck on an Window System oriented distro like andros.

      KFG

    5. Re:Slack and X.org by Anonymous Coward · · Score: 0

      I believe you mean "away from XFree86" - X.org /is/ X, just as XFree86 is X. They are just two sepperate implementations of X, and X.org is a fork of XFree86, and the difference between them is not huge yet.

  6. This is so cool! by mw5299 · · Score: 0
    This is so cool!!! i cant wait to try it out!!!!

    ------
    go here

  7. I was wondering why my connection was slow... by Nyder · · Score: 2, Funny

    Well, I guess that explains why my connection is so slow today.

    --
    Be seeing you...
  8. Re:Yet Another Distro by GoofyBoy · · Score: 3, Insightful

    You do realize that Linux itself is a "garage basement project"?

    --
    The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
  9. Ha! you think you have it bad... by twoslice · · Score: 0

    33600 USR external with a flaky power supply connector that I have to hold in or the fricken thing will fall out. But I am the best one-handed typist that you will ever see...

    --

    From excellent karma to terible karma with a single +5 funny post...
    1. Re:Ha! you think you have it bad... by Wig · · Score: 1

      Why not just flip the computer the way it lies?

    2. Re:Ha! you think you have it bad... by Drooling+Iguana · · Score: 1

      That, my friend, is why they invented electrical tape.

      --
      ... I'm addicted to placebos
    3. Re:Ha! you think you have it bad... by Anonymous Coward · · Score: 1, Funny

      But I am the best one-handed typist that you will ever see...

      Me too, but for, uh, different reasons......

    4. Re:Ha! you think you have it bad... by stor · · Score: 1

      Oh man,

      Here's a penny kid, go buy yourself a real modem =)

      Cheers
      Stor

      --
      "Yeah well there's a lot of stuff that should be, but isn't"
  10. I'm definately going to have to get this by ChairmanMeow · · Score: 3, Funny

    Slackware 9.1 gave me a great few days setting it up. I'm definately going to have to try Slack 10.

    ok... so I'm a total nerd... so what?

    --
    1. Re:I'm definately going to have to get this by SphericalCrusher · · Score: 1

      Yeah. If you're going to start with Slackware, it's always best to start on the latest version. That applies to anything though. I remember when I wanted to use SuSE before I became updated with news... I installed version 4 around when version 7 was out and when I noticed that all of my new drivers I downloaded asked me to update... I was like "Whao. There's two newer versions out? Damn." so yeah... Slackware is a lot of fun though... and VERY powerful later on once you begin to learn how to use it better.

      --
      "Instant gratification takes too long." - Carrie Fisher
    2. Re:I'm definately going to have to get this by akaiONE · · Score: 1
      I am there with you all the way. Setting up slackware for the first time back in the early winter of 1995/1996 was very fun. Back then I remember how everyone looked at me with weird eyes; "what is it you're doing with those computers?" Now, years later, Slackware 10.0 is out and I still feel the same joy and giggling feeling I had back then when I think about installig it.

      For me, average installtime is just about 1 hour for a working X setup with Gnome 2.6.1, and thanks to the wonders of Dropline Gnome I have been able to play around with what's now Slackware 10's Gnome for quite a while. I am confident that the Dropline Crew will move on onto Slackware 10.x as they did with 9.x., thus allowing Slackware-users to deploy updated Gnome-packages and other system utilities along the development of the next Slackware version.

      Perhaps, if I may add some disapointment at the bottom; I had hoped that 10.0 would be the first time Slackware got on the 2.6 series, but I do somehow understand the desire to stick with 2.4 as I myself do so also on my workstation and servers. 2.6 is great tho, and I would very much like to see it on the 10.1-release. Keep up the good work Patrick!

      --

      "-Who said sit down?!"
      -- S. Ballmer @ MSDC 2003.

    3. Re:I'm definately going to have to get this by Anonymous Coward · · Score: 0

      2.6 - It's there. Check /testing

  11. Not Slackware X? by PornMaster · · Score: 5, Funny

    Bah. Not Slackware X, not Slackware XP.

    C'mon! Where's the marketing, folks? ;)

    -PM

    1. Re:Not Slackware X? by Anonymous Coward · · Score: 1, Funny

      They got fired after they convinced Patrick to go from 3.x to 7.0 ;)

    2. Re:Not Slackware X? by kfg · · Score: 3, Funny

      Bah. Not Slackware X, not Slackware XP.

      I'm waiting for Slackware XPalidocious myself.

      Out here on the east coast we won't get the special edition slated for distribution in California, but I hear that one's not so stable anyway.

      KFG

    3. Re:Not Slackware X? by Anonymous Coward · · Score: 0

      What happened to 4?

    4. Re:Not Slackware X? by Anonymous Coward · · Score: 0
      C'mon! Where's the marketing, folks?

      On some other CD somewhere. Slackware is concentrated productivity and there is no room for such crap on a Slackware CD.

      I forgive your foolish comments. Please drive through.

    5. Re:Not Slackware X? by Anonymous Coward · · Score: 0

      Bah. Not Slackware X, not Slackware XP. ... and being sued? What about SlaXware? ;)

    6. Re:Not Slackware X? by dukeisgod · · Score: 1

      That's because the fault line's aren't very stable there. Move to more solid ground, and you'll get a more stable version of slack.

    7. Re:Not Slackware X? by kfg · · Score: 1

      Move to more solid ground, and you'll get a more stable version of slack.

      True, but you won't get as much slack. The more slack, the less stability.

      Those of us who like stability, but still like a bit of slack, move to Vermont.

      KFG

    8. Re:Not Slackware X? by Wild+Wizard · · Score: 1

      That would be funnier if you got it right

      it was 4.0 to 7.0

    9. Re:Not Slackware X? by sould · · Score: 1

      Bah. Not Slackware X, not Slackware XP.

      C'mon! Where's the marketing, folks? ;)

      Moderation +4
      50% Interesting
      30% Underrated
      20% Funny


      50% Interesting?

      Weird...how could anyone find that interesting?

    10. Re:Not Slackware X? by Tinik · · Score: 1

      Marketing? Ok how about SlackwarE X! After all, it sells, and it's probably about as close as I'm going to get for a while *sigh*.

  12. Re:Yet Another Distro by Yi+Ding · · Score: 5, Insightful

    Just what Linux needs... Yet Another Distro

    Please, keep these garage basement projects out of the news... we already have enough distros. Thanks.

    Yep, that's right, the distrobution that was out before kernel 1.0 is now considered Yet Another Distro. Oh how the times have changed.

  13. Cool by N4DMX · · Score: 1

    Slackware rocks! I have been meaning to try X-org, so I guess this is as good a time as any.

    --
    42
    1. Re:Cool by tarballedtux · · Score: 2, Interesting

      The transition to X.Org from XFree coulnd't have been easier. 1)I backed up my XF86Config file. 2) Removed ALL the XF86 packages. 3) Used swaret to DL and install X.Org 4) Renamed xf86config to xorg.conf and bam it worked right away. --tarballedtux

  14. Migrating from SUSE 9.1 by sjwaste · · Score: 1, Troll

    Any recommendations out there on how to move from SUSE 9.1 to Slack 10.0? I recently started using Linux again. The previous was Slack 4.0 or something like that. Really old, 5 years ago. I always liked Slackware back then and would like to go back to it, really just for the sake of doing it. Rather than blowing out my linux partition and restarting, is there a way I could migrate?

    1. Re:Migrating from SUSE 9.1 by jefe7777 · · Score: 3, Funny

      fdisk

    2. Re:Migrating from SUSE 9.1 by jefe7777 · · Score: 1

      i kid i kid.

      what exactly are you trying to preserve?

      home directories?

      config files?

    3. Re:Migrating from SUSE 9.1 by sjwaste · · Score: 1

      I wanted to hold onto KDE and some installed apps. Slackware is still as bare as it was back in the day, while SUSE had a ton of software I installed (firefox, thunderbird, etc). I was looking at both, though, and I don't think I want to go through the trouble of preserving all the apps. In the end, I might save some time if I archive the config files and just reinstall everything.

    4. Re:Migrating from SUSE 9.1 by jefe7777 · · Score: 3, Informative

      >>In the end, I might save some time if I archive the config files and just reinstall everything.

      you'll save a lot of time doing that.

      don't forget to visit

      http://www.linuxpackages.net/

      for your precompiled slack addons.

      good luck...i'm off to download.

    5. Re:Migrating from SUSE 9.1 by PONA-Boy · · Score: 1

      Cobble some spare parts together and give DROPLINE a try. I think you will be surprised just _how_ feature- and app-rich the X(Free|.org) has become oer the years.

      -PONA-

      --
      +that's funny...I don't FEEL tardy.+
    6. Re:Migrating from SUSE 9.1 by Billly+Gates · · Score: 1

      But like BSD doesn't Slackware have alot of stuff with its default packages online?

      I am a BSD junkie and I love how minimal it is by default and how you can use the ports or packages to add things like firefox and thunderbird.

      I was told slackware had a simple source based package manager similair to Solaris.

    7. Re:Migrating from SUSE 9.1 by irokitt · · Score: 1

      Slack uses a very simple package system based off of *.tgz files. There is no ports system like BSD has, but there are tools like Swaret and slapt-get out there which come close.

      That said, most of the configuration (i.e. daemons and such) is done in the old-style BSD way, with rc.* files.

      Don't worry about the sparcity of features on a basic install. You can either choose to download discs 3 and 4, which have a plethora of other software packages (including a newer version of gcc and a 2.6 kernel) or you can download piecemeal from the mirrors.

      --
      If my answers frighten you, stop asking scary questions.
    8. Re:Migrating from SUSE 9.1 by Anonymous Coward · · Score: 0

      Slackware is definately not bare. It actually uses two CDs now, if that tells you anything. The choices of included software, however, are pretty practical. There is no GUI installer and very few fancy configurators (just you and your favorite text editor and init scripts), but pretty much all of the software you'll need comes with it, and it's quite up to date.

    9. Re:Migrating from SUSE 9.1 by nazsco · · Score: 1

      Slack 4 is not THAT old considering that slacks don't age so kickly :)
      Now, if you use red hat, then a day or two without the automatic update, you can't even boot the machine
      Besides, they've jumped a lot of version numbers.

      well. If you fell confortably with Yast, then i sugest you keep that SuSe. If you fell that Yast was a pain in the ass, then the best way to migrate is:
      1. copy your /home
      2. install slack in "new install" mode.
      3. restore /home
      4. no 4, you'r already done

    10. Re:Migrating from SUSE 9.1 by normal_guy · · Score: 1

      What benefits would Slackware have over SUSE other than X.org? SUSE has the 2.6 kernel.

      --

      Linux: Free if your time is worthless.
    11. Re:Migrating from SUSE 9.1 by Kesha · · Score: 0, Troll

      You know, I've recently felt nostalgic about the good old days when Linux was harder then necessary, I tried to install RedHat 5.2 on a 486 with 16MB RAM - it worked, but it cost me a day and made me appreciate all the improvements that Linux has gained in the last 6-7 years.

      What exactly do you hope to gain by switching to Slackware besides the reduced usability? Doing it just for nostalgia's sake may not be the best reason (unless you really do have time to waste).

      Paul.

    12. Re:Migrating from SUSE 9.1 by Anonymous Coward · · Score: 0

      Reduced usability? I can't figure anything else out half the time. Slackware there is one way to do it, and thats what the documentation for the software package says on the developers site. The Slackware Book is about the best "learn linux basics" guide out there I think, though it could use a little bit of updating...

      I tried to use a RedHat system, wanted to setup a virtualhost my way, found one of the bajillion httpd.conf files and edited it up. Went and touched the X based config utility, it didn't know about some of the directives i used and just wiped them out.

      My slackware box (my linux box period, only one i have, other two are Windows XP...yeah yeah) sits down in the basement plugged into the wall for power with a network cable plug in on the other wall. It just sits there nicely in the corner for months at a doing its job... file serving, web, ftp, ssh, cvs, and other stuff like that. It doesn't need X (heck it doesn't have a monitor!) If I need to change something, fire up putty, log in, and vi or vim whatever i want to change then /etc/rc.d/rc.httpd restart (for apache) and press enter. I don't see how this is difficult to do...

      I can usually get a slackware box up and running in about as much time as it takes for it to copy it from my DVD (i keep a -current and -10.0 (now) tree rsynced up, and a nice shell script to build a DVD iso (nothing excluded) which i then open in windows over samba and directly burn, hey it works without a hitch).

    13. Re:Migrating from SUSE 9.1 by geminidomino · · Score: 1

      Slack has it in /testing along with nice install instructions for using 2.6 instead of 2.4.

    14. Re:Migrating from SUSE 9.1 by Anonymous Coward · · Score: 0

      After using such diverse distros over the years as Caldera 1.something (yeah, I know), Red Hat 5.3 and 6.3 and SuSE 7.3, I have finally found in Slackware a distribution that I can truly love.

      SuSE, to me, was so opaque it was almost as bad from an administraton standpoint as Windows. Plus, it loads up all sorts of crap by default that I could just never get rid of.

      Slack is much nicer in this regard. Easy to install (but VERY insecure in its default configuration - get a firewall script BEFORE you even think about getting on the net) and administer. You can learn more about Linux from Slack in a day than you can from SuSE in a year.

    15. Re:Migrating from SUSE 9.1 by reallocate · · Score: 1

      Slackware's single biggest advantage is, perhaps, the fact that it doesn't gum up the works with a proprietary packaging and cnfiguration schemes. That means you don't need to wait for someone else, or the business who sells your distribution, to package a program in a form that works. In Slackware, odds are you can just download the program and install it.

      E.g., if you want Fireforx and Thunderbird, go to the Mozilla site and grab them.

      Slackware isn't minimal. It does a full install of the current versions of KDE and Gnome. Mozilla 1.7 made it into this distribution, as did the latest release of Epiphany. OpenOffice isn't there, but, again, you just need to go to their site and get it.

      --
      -- Slashdot: When Public Access TV Says "No"
    16. Re:Migrating from SUSE 9.1 by sjwaste · · Score: 1

      I don't know why these posts are getting modded to troll. Oh well. To answer your question, I don't think it'll reduce the usability. I just really dont like yast. With SUSE it seems like if i dont install it from one of their packages, it's a lot of work to get something to run properly. Slackware doesn't seem to suffer that problem.

    17. Re:Migrating from SUSE 9.1 by Anonymous Coward · · Score: 0

      You're not really comparing 1995 Redhat 5.2 with 2004 Slackware 10, are you?

      Why don't you try it out first before making assumptions? It's exactly the same kind of "Eww, ancient!" kind of face that Windows users always make when confronted with a *gasp* black-and-white *gasp* console screen. They have no idea just how powerful it is, yet assume the contrary. Slackware is a modern distribution like any other. While the overall approach differs than, let's say, Suse Linux it's still contemporary Linux in all it's beauty (and ugliness). Use what you feel is best for you, but don't judge other ways especially if you haven't walked them.

    18. Re:Migrating from SUSE 9.1 by Anonymous Coward · · Score: 0

      don't worry. i metamoderated the dumbass who modded you a troll.

  15. So, honest question. by Anonymous Coward · · Score: 2, Interesting

    Does Slackware have an apt/"windows update"-style auto-update tool yet?

    1. Re:So, honest question. by Anonymous Coward · · Score: 1, Funny

      *pets the troll*

    2. Re:So, honest question. by ianr44 · · Score: 1

      No. If it did, it wouldn't rock. Simple as that.

    3. Re:So, honest question. by Silvertre · · Score: 5, Informative

      You mean something like Swaret? http://www.swaret.org/

    4. Re:So, honest question. by Anonymous Coward · · Score: 0

      Ah, so rocking requires the use of a more cumbersome update tool. Good to know!

    5. Re:So, honest question. by ianr44 · · Score: 1

      Not exactly. The lack of a tightly integrated update tool is a big part of what makes slackware so nice IMHO. Installing stuff 'by hand' gives a bit more control of what's going on, but it's definitely not for everyone.

    6. Re:So, honest question. by Anonymous Coward · · Score: 0

      Right!

      Where "a bit more control" means "your box gets haxored by a Romanian script kiddie because your beleaguered system administrator can't be bothered to recompile every single minor service on the box every time that a security patch is released, which means your WuFTPd happens to be five months old".

      This is certainly a better situation than, say, Debian, on which it is not even possible to compile software.

    7. Re:So, honest question. by germanbird · · Score: 4, Informative

      Does Slackware have an apt/"windows update"-style auto-update tool yet?

      Check out slapt-get. It can be found on freshmeat at http://freshmeat.net/projects/slaptget/. I used it to keep my Slack 9.1 install up to date and was pleased with its performance.

    8. Re:So, honest question. by Anonymous Coward · · Score: 0

      Bwahahaha! Behold my evil plan! I will troll Slashdot by asking legitimate questions about the feature set of products being discussed!

      For my next troll, I will cause a horrible flamewar in a thread about a Mac OS X security update by asking whether the Launch Services .dmg vulnerability has been fixed yet! Or maybe I'll ask about the Halo 2 release date in a thread about the XBox! THAT'LL get everyone up in hackles!

    9. Re:So, honest question. by ianr44 · · Score: 1

      Like I said, it's definitely not for everyone (which includes lazy/incompetent/overworked admins.) It's really not that hard to think of a situation where (semi)automatic update systems aren't the best idea.

    10. Re:So, honest question. by atomic-penguin · · Score: 1

      Personally, I like slackupdate (bash script).

      Originating at VA Tech, I believe.

      Downloads new packages to /tmp/slackupdate. Then you just run upgradepkg /tmp/slackupdate/*.tgz.

      So simple you could put it in your daily cron. If you must have a silly little icon associated with it, just make a shortcut to run the script and upgradepkg.

      Here is a link to the update script.

      --
      /^([Ss]ame [Bb]at (time, |channel.)){2}$/
    11. Re:So, honest question. by SomeOtherGuy · · Score: 1

      Just point swaret.conf to CURRENT

      and then

      swaret --update;swaret --upgrade

      Works great. Slakware IS Linux .

      --
      (+1 Funny) only if I laugh out loud.
    12. Re:So, honest question. by tweek · · Score: 1

      In all fairness, it took me a bit of searching to find this out when I installed 9.1 a few months ago (or was it weeks ago? it all runs by).

      I did my first linux install on floppies Slack floppies. I still have a book that Patrick did the intro for that included a Slack cd in the back.

      Even so, I wondered this same thing myself and since swaret isn't linked from the Slack homepage, it took a while to find it.

      So it COULD be an honest question but in all fairness I think you're right in petting the troll.

      --
      "Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
    13. Re:So, honest question. by alexdm · · Score: 0

      Of all the respositories that I've tried with slapt-get, linuxpackages.org seems to be the only one with updates available. However linuxpackages also contains a bunch of broken packages that messes your system up.

    14. Re:So, honest question. by JooBYE · · Score: 0
      yes, it's called SlackwareTool. Front end GUI for it as well...

      Enjoy!

    15. Re:So, honest question. by light101 · · Score: 2, Informative

      yes they do, you can check out slapt-get and also swarret. Im a fan of slapt-get, you chan check it out here. Easily put into cron if you want it to be updated daily/weekly/montly whichever you prefer with something like

      slapt-get --update
      slapt-get --upgrade --no-prompt

      Check also the possibility of somechangedscript.new for upgraded ways of doing things.

    16. Re:So, honest question. by Anonymous Coward · · Score: 0

      unless you coun't third party tools the answer is no. And thank goodness.
      Good old upgradepkg just /works/ - I for one don't want some automatic tool to take control of my box and break it in strange ways. I prefer to be in control and know what packages get installed and be able to inspect them before I install them... Besides, it's not like it's hard to just use wget to grab patches/packages/* from an ftp site when updates are released and then run upgradepkg *.tgz if you just want to install without inspecting the stuff first... two commands, just two commands, how much more easy do you want it...?

    17. Re:So, honest question. by mattyrobinson69 · · Score: 2, Interesting

      and slapt-get (which i prefer) (also slapt-gui to go with it)

      you can find that yourself on freshmeat

    18. Re:So, honest question. by CybrGuyRSB · · Score: 1

      Yes, it does, sort of.

      Look around on one of the mirrors for a package called slackpkg. I think it's in the testing dir. It's not entirely automatic, you kind of have to do a search for at least a piece of the name of the package you wanna download and upgrade. For example to upgrade X i can type
      slackpkg upgrade x
      It'll give a list of the packages that will be upgraded and ask if you want to do it, then it'll download them all and install.

      you can also check the status of your packages by typing something like:
      slackpkg search x

      it'll give you a list of every package with x in the name and whether they're installed and if theres a newer version available.

  16. distribution based on slackware still using xfre86 by cyfer2000 · · Score: 2, Informative

    available from this link Buffalo Linux.
    JoLinux
    Plamo Linux
    Slax Live Linux

    --
    There is a spark in every single flame bait point.
  17. Twin kernels by Neo-Rio-101 · · Score: 2, Interesting

    This looks exciting. I can't wait to try this one out. Especially as it has 2.6.7 in it.

    Why are some linux releases still hanging onto the 2.4.26 kernel, or relasing two kernels (Knoppix comes to mind) ?
    Th2 2.4 kernel tree still has that floating point kernel bug in it, doesn't it?

    --
    READY.
    PRINT ""+-0
    1. Re:Twin kernels by Googo · · Score: 3, Informative

      "If you actually cared to read the release note"(that's slashdot for you), you would realize that it is a released with two kernels compiled with different configurations. This was the same during the previous kernel change and was probably the same before that. Slackware 10 comes with 2.4.26 default with 2.6.7 selectable during install I believe.

    2. Re:Twin kernels by nihilogos · · Score: 1

      Why are some linux releases still hanging onto the 2.4.26 kernel

      I am not sure what is going on, but a samba 3.0 server I maintain has been quite slow at processing domain logons with 2.6.x. Switching back to the debian provided 2.4.18 kernel speeded them up quite a bit.

      Admittedly it might be because I compiled the 2.6.x one myself, but things like this make me uneasy about using newer kernels that haven't been so rigorously tested.

      --
      :wq
    3. Re:Twin kernels by dangerz · · Score: 3, Insightful

      Why are some linux releases still hanging onto the 2.4.26 kernel

      The 2.4 kernel has had 26 revisions in it fixing bugs.

      The 2.6 kernel has had 7.

      That's why :)

      --
      The greatest experience we can have is the mysterious.
      - Albert Einstein
    4. Re:Twin kernels by Anonymous Coward · · Score: 0

      Actually, 2.6 is indeed quite less mature than 2.4. The number of revisions is irrelevant.

      Many things are still changing with 2.6, and there are still many bugs that need to be ironed out.

    5. Re:Twin kernels by bender647 · · Score: 2, Interesting

      For what its worth, I've been dual-booting Slackware-current (now known as 10.0) with the latest 2.4 and 2.6 kernels and it's been rock solid. He's done his homework and the distribution seems well set-up for either kernel. Of late, most everything I want is now supported in 2.6, so its probably time to cut 2.4 free (although the CAD tools I use are not yet certified for a 2.6 kernel).

    6. Re:Twin kernels by Anonymous Coward · · Score: 0

      Well,ALJHFDforALJHFDoneALJHFthingALJHFDmyALJHFDfuc kingALJHFDspaceALJHFDkeyjhfdw doesn'tALJHFDworkALJHFDanymore.ALJHFDALJHFDIsALJHF Ditjhfdw 2.6,ALJHForALJHFDisjhfdw myALJHFDlaptopALJHFDdying?

    7. Re:Twin kernels by MicroBerto · · Score: 2, Interesting
      I disagree, this is very un-exciting. The 2.6 series is VERY stable for only being the 7th release. I definitely think that it should be the default install by now.

      If you take two identical PCs, load Mandrake 10 on one, and Slackware 10 on the other, have the same window manager and everything else, you'll definitely see a difference in that Mandrake 10 has a MUCH faster feel.

      Granted, Mandrake shipped it perhaps a bit early with 2.6.3, but the 2.6.x is that much better, as testified by basically everyone out there.

      I think making 2.4 default is a mistake now. 2.6 has proven its weight in gold. I've avoided upgrading my computer even longer because this kernel solved so many of my speed issues.

      --
      Berto
    8. Re:Twin kernels by FuegoFuerte · · Score: 1

      If you take two identical PCs, load Mandrake 10 on one, and Slackware 10 on the other, have the same window manager and everything else, you'll definitely see a difference in that Mandrake 10 has a MUCH faster feel.

      This probably has quite a lot to do with the Mandrake builds being optimized for i686 while the slack builds are optimized for i486. This may make slack a bit more sluggish in some situations, but it also means I can grab an old 486 dx25 laptop, throw a very basic install of slack on it, and use it for network stuffs with no problems at all. This is definately something not doable with Mandrake.

    9. Re:Twin kernels by evilviper · · Score: 1
      Why are some linux releases still hanging onto the 2.4.26 kernel

      Maybe because there is tons and tons of drivers, modules, and software that just won't work with 2.6 just yet, and not everyone feels like being on the bleeding edge and having to fix everything themselves...

      Good enough answer for you?
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    10. Re:Twin kernels by Anonymous Coward · · Score: 0

      Wel, samba performance with the 2.6 kernel branche still sucks. Even NFS is slow as hell compared to the 2.4 branche.

      I can that i use the 2.4 for servers and the 2.6 for clients (it has a faster desktop experience yes).

      My input here, hope it help's.

    11. Re:Twin kernels by dinivin · · Score: 1

      Why are some linux releases still hanging onto the 2.4.26 kernel, or relasing two kernels (Knoppix comes to mind) ?

      Maybe because 2.6 is still relatively new. There are very definite regressions in certain drivers between 2.4 and 2.6. For example, my firewire drive works great in 2.4, but doesn't work at all in 2.6.

      Dinivin

    12. Re:Twin kernels by dinivin · · Score: 1

      2.6 has proven its weight in gold.

      All 2.6 has proven to me is that it won't work with my firewire drive.

      Dinivin

    13. Re:Twin kernels by Lew+Pitcher · · Score: 1

      Pat Volkerding doesn't usually move to the 'latest and greatest' kernel until it has proven that it is stable and usable. Think back to the troubles with the (then newly released) Linux kernels 2.4.1 through 2.4.15 (aka the "kernel of pain")

      Need I say more?

      --

      "values of beta will give rise to dom!"

  18. Grammar-fix by BRTB · · Score: 1

    Hrm, seems my writeup was rearranged a bit... I _do_ know how to write, I promise! =] Slightly corrected one below.

    BRTB writes "Slackware 10.0 is out! X.org 6.7.0, kernel 2.4.26 (2.6.7 optional), KDE 3.2.3, GNOME 2.6.1, GCC 3.3.4... it's all new, and just as stable as you'd expect from Slackware, if RC2 was any indication. There's an official announcement and some ISO BitTorrent links, as well as a mirror list. Of course, the non-cheapskates among us should go buy the CD-set to support the project. Have fun, everybody..."

  19. for ppc? by wooby · · Score: 2, Interesting

    I ran Slackware on my PC for years, but have recently switched to a Powerbook. I'd like to run Linux, and I've investigated dual-booting with either Debian or Gentoo.

    I'm having trouble finding good resources, though these people seem to have made some progress... last November.

    I've had a difficult time finding a current PPC port of Slackware. Has anyone experimented with building a Slackware base system on a G4 from some other distro, or had any luck with some other approach?

    1. Re:for ppc? by jefe7777 · · Score: 1

      check out crux linux for ppc.

      it has the same mentality as slack.

      the new version should be out soon.

    2. Re:for ppc? by Anonymous Coward · · Score: 0

      Dunno 'bout you but my powerbook came with a BSD-like operating system...

    3. Re:for ppc? by commodoresloat · · Score: 1
  20. Re:Yet Another Distro by sjwaste · · Score: 1

    No kidding. Slack has been around for a WHILE. I'm moving back to it just for the nostalgia value :) Seriously.

  21. Re:Yet Another Distro by riffenator · · Score: 1

    You moron.

    slack is one of the first distros!

  22. X.org 6.7? by pherthyl · · Score: 1

    Where did the 6.7 come from? I guess I can see the 6 from X11R6 but when was 6.1 - 6.5 released?

    Does anyone know the historical reasons why X.org's first release it called 6.7?

    1. Re:X.org 6.7? by Michael+Hunt · · Score: 4, Informative

      If memory serves (may be a bit rusty on the dates)

      X11R6.2 - XFree86 3.2 (c 1996)
      X11R6.3 - XFree86 3.3 (late 96-early 97)

      The xc changed the license for R6.4 so XFree86 stayed based on 6.3 for a while, until they backpedal sometime in 1998-1999.

      X11R6.4 - XFree86 4.0
      dunno about 6.5
      6.6 was merged into XFree86 4.2 or 4.3 if memory serves.
      X11R6.7 IS X.Org 6.7 as X.O is the xc's reference X distribution now.

    2. Re:X.org 6.7? by erikharrison · · Score: 2, Informative

      It's 1988 and the X Consortium is the maintainer of the X protocol and it's reference implementation. The reference implementation goes through 6 major releases. Release 6 goes through (i think) 3 minor revisions with the X Consortium. X11R6.3.0

      X consortium dissolves, and maintainance passes to the Open Group.

      The Open Group establishes X.org an independent group to maintain the standard, after TOG make a serious licencing blunder with X11R6.4.0 which pisses off XFree86. XF86 basically threatens to perform a complete fork rather than a parrallel implementation if the licence changes, TOG backs out and X.org gets formed.

      X.org makes a few releases - keep in mind that they maintain a reference implementation, whereas XFree86 seems to be focused on drivers and features, based on the X.org code. This starts with (again, I think) R6.5.1.

      Fast forward, David Dawes of XF86 pisses off everybody whose an important developer in his project (notably Keith Packard), and then threatens to change the licence. X.org has been thinking of making their position in their relationship with XF86 more dominant anyway and the whole thing culminates in a full fledged fork of XF86 prior to the licence change. This code is worked on, some random bug fixes are included, and many of the GPL incompatible licence cahnges are released by the original developers under the X.org licence, bada boom bada bing, X11R6.7.0.

    3. Re:X.org 6.7? by Anonymous Coward · · Score: 0

      when was 6.1 - 6.5 released?

      A while back. X11R6was first released something like 10 years ago. The current revision is X11R6.7, hence the X.org version.

    4. Re:X.org 6.7? by Anonymous Coward · · Score: 0

      Maybe for the same reason there was never a Slackware 5 or 6.

  23. Re:Yet Another Distro by Anonymous Coward · · Score: 0

    Oh, bah. It's not like there weren't Linux distributions before this or anything...

  24. You people by krazykit · · Score: 0

    You people, with your "money" and "broadband connections." And me stuck on AOL :( Oh well, it looks good.

    1. Re:You people by Anonymous Coward · · Score: 0

      Sorry to hear that. Let me check my recently purchased AOL E-mail address list. Ah, there you are. I'll download it and e-mail it to you, k?

  25. Re:Yet Another Distro by bach37 · · Score: 1

    Just what Slashdot needs.... Yet Another Troll

    Please, keep these garage basement posts out of the news... we already have enough trolls. Thanks.

  26. grass is always greener by bcrowell · · Score: 4, Insightful
    I guess the grass is always greener on the other side of the fence. I keep getting disgusted with FreeBSD and wanting to switch to a different unix...until I actually try a different unix and get just as annoyed with it :-)

    What do slackware users perceive as its strengths? My perception is that slackware is the distro where you install everything from tarballs, with no automatic system for satisfying dependencies (as you'd have in Debian, Gentoo, or FreeBSD, for instance).

    Actually I'm starting to feel that automatic systems for installing software and satisfying dependencies are more trouble than they're worth. In FreeBSD, I often feel like a prisoner of the ports system. If I want to run application A, it forces me to upgrade library B. But then the new version of B breaks application C. Oops! Try recompiling C. No, that doesn't work. Oh, it's because C depends on library D, which then depends on B, so you really need to recompile D. Note how the whole story started because this automated system felt it was so important for me to upgrade library B, when in fact I would have probably been fine not upgrading it.

    The real issues are (a) software needs careful testing, and (b) open-source hackers are sloppy about making changes that break stuff. If slackware is really thoroughly tested, that could be great...

    1. Re:grass is always greener by mw5299 · · Score: 0

      Slackware seems to be thoroughly tested...

    2. Re:grass is always greener by A.T.+Hun · · Score: 3, Interesting

      The biggest strength of Slackware, for me, is its rock solid stability. It just doesn't crash or do anything weird. It definitely isn't "bleeding edge" (although it does contain the most recent KDE, for example), but that's just fine by me.

      I've also grown to appreciate Slack's lack of dependency checking. Basically, Slack just gets out of your way. The KISS principle applies everywhere. I've used Red Hat and Mandrake, but now that I know what I'm doing, I think I'm a Slackware lifer.

    3. Re:grass is always greener by Space_Soldier · · Score: 1, Flamebait

      This is where .NET comes in. There is no more DLL hell. There are 2 ways to fix this in Linux. One way is to not use dynamic libaries, and use inline. The binaries will be big, but that is not a problem anymore since hard drives are big and cheap. The second way to fix this is to do what .NET did, make assemblies (exe, dlls) strong named. They cantain a version like 1.1.3434.13243, a digital signature, and are stored in a global assembly cache. This means that foobar.dll v1.0 and foobar.dll v1.1 can exist on disk at the same location (to the requesting program). On disk they are actually stored as foobar.dll, but the program does not see that. This way DLL hell is fixed. .NET takes care of this problem. A similar service can be created for UNIX. I'm not talking about .NET, just about the service that gives the right version of the libary to the requesting program. Since almost every distro has a different file system hierarchy, and no distro capitulates to a standard, I don't think that this will ever happen.

    4. Re:grass is always greener by ag0ny · · Score: 5, Insightful
      Back when I wass still using Linux (Slackware had been always my distro of choice), I used to download, compile and install everything myself instead of using the precompiled packages.

      Perhaps that's because I'm a do-it-yourself guy.

      Around 3-4 years ago I started using FreeBSD. In the beginning I was using the ports system for everything, and often got into the same dependency hell that you're talking about.

      Now I'm using a "hybrid" approach:

      - Things that don't change often, I install from ports and forget about them.
      - Programs that I think will need to update from time to time, I download, compile and install under /usr/local/software/packagename-version/

      I feel quite comfortable doing this because each package is sitting on its own directory. It's also easier to handle dependencies:

      Say FooProgram-1.0 requires libFooBar-1.0 and BarProgram-1.0 requires libFooBar-2.0. I would have this:
      /usr/local/software/FooProgram-1.0/
      /usr/local/software/BarProgram-1.0/
      /usr/local/software/libFooBar-1.0/
      /usr/local/software/libFooBar-2.0/

      Of course, the compilation phase sometimes gets a bit messy and requires some tweaking, but IMHO it is worth the extra effort. There should be no dependency problems. Also, removing an old version of a program is as easy as removing the directory where it has been installed.

      I know this approach will not be suitable for everyone, but it works for me. I hope this helps you.
    5. Re:grass is always greener by goon · · Score: 1
      What do slackware users perceive as its strengths?

      you can install it on old machines and get better access to latest file systems and linux kernel and openSSH. Thought I've got it to install on a 16M machine I've yet to start installation on a 8M machine.

      --
      peterrenshaw ~ Another Scrappy Startup
    6. Re:grass is always greener by Anonymous Coward · · Score: 1, Funny

      Forget all that and just use java. There is nothing wrong with garbage collection, my uncle has been doing it for 34 years.

    7. Re:grass is always greener by gr3g · · Score: 1

      I've always felt that Slackware danced that fine line between an easy set-up and the ability to tinker. I've tried other distros that either set themselves up for you and there is no way you are modifiying them, or you have to set everything up by hand. And so far it's the only distro that consistently works with my Inspiron 5000.

      --
      "It has always been this way and it won't change, god bless the fucked up USA" The Briefs
    8. Re:grass is always greener by blindbat · · Score: 1

      I came to Slack from FreeBSD because I couldn't run FreeBSD on my new laptop. I never had much luck installing Mandrake or RedHat but Slack felt like being back on FreeBSD.

      I like being able to adjust things in the start scripts, etc. Compiling a kernel is more involved in selecting options in Linux than FreeBSD but is not too difficult.

      I doubt if I'll ever return to FreeBSD.

      Slack's packages are very easy to install and upgrade as were things in FreeBSD.

    9. Re:grass is always greener by Anonymous Coward · · Score: 0

      I like Slackware for my desktop system, mainly because I build everything from source and hack a lot of programs. I use Slackware as the base for my system.

      However, that being said, I won't use anything but FreeBSD for all my other systems, such as servers. To ease your ports woes, you might want to check out portupgrade. It takes care of most of the "dependency hell" that using straight ports gives you. portupgrade makes port management a breeze.

    10. Re:grass is always greener by Anonymous Coward · · Score: 0

      You have never used a unix, have you?

    11. Re:grass is always greener by 13Echo · · Score: 1

      The important thing with Slackware is to make sure that you compile your programs properly. Generally, this means using "./configure --prefix-/usr" (maybe even sysconfdir as well) to make sure that you don't have crap going everywhere.

      Otherwise, dependancies have never been an issue for me. Slack has most of the important stuff. There are a few obscure libraries, like those used in games (Battle of Wesnoth comes to mind), but the majority of programs will install on a Slackware machine with minimal need for additional libraries or files.

      On my Slackware machine, everything always works wonderfully and is fast and stable. That's been my experience since I started using it in 2000, and is the reason I've used it ever since.

      I'm going over to the Slackware store this week to order my copy of Slackware 10. I haven't ordered a CD since 8.1 (downloaded the last two releases), and feel its important to show our support to Pat for the awesome work he's done with Slackware.

      Keep em coming Pat. ;)

    12. Re:grass is always greener by pavon · · Score: 3, Interesting

      This means that foobar.dll v1.0 and foobar.dll v1.1 can exist on disk at the same location (to the requesting program).

      This is already possible in Linux and has been for years (it probably inherited the practice from other unices before it was created). The way that linux handles different versions of the same libraries is actually really nice. You can read about it here . Where the problem comes in is that that either the package manger doesn't like to install multiple versions of the libraries, or the user isn't aware that it is possible. I think that the latter is the more common case. The user sees that they need library version Y, and they have X so they naturally upgrade the package rather than installing it beside the existing one.

      This is where .NET comes in. There is no more DLL hell.
      Kind of live WinForms/Avalon :P

    13. Re:grass is always greener by Atmchicago · · Score: 1

      I read all the 9 answers here and felt that there was too much disinformation/lack of the right information. Here goes:

      Slackware has its own packaging system - they end in .tgz. Basically, it unpacks the binaries etc into their proper directories and adds itself to a lsit of installed package. You can use pkgtool, installpkg, upgradepkg, removepkg...

      The good tools to have are: Swaret/slackpkg/slapt-get for downloading packages. I prefer swaret. Swaret has optional dependency checking, where it asks you if you want to download dependencies after installing the package. Packages that aren't in slackware-current (like K3b, bzflag, foobillard, cinelerra...) can be found at http://www.linuxpackages.net.

      Finally, if you decide to compile from source, you can use Checkinstall to make it into a slackware package!! Basically, slackware's package system is simple yet works very nicely.

      --

      You can lead a horse to water, but you can't make it dissolve.

    14. Re:grass is always greener by 13Echo · · Score: 1

      Oops. Typo. That's "./configure --prefix=/usr"

    15. Re:grass is always greener by Anonymous Coward · · Score: 0

      I've been using Slackware since 7.1 about 5 years ago. It was my first dip into a non-Microsoft world, and I haven't gone back since. I've used several distros, but I'm currently running Slackware exclusively, which tells how satisfied I've been with it.

      Slackware has many advantages. It sticks closely to the KISS (keep it simple, stupid) concept, which leads to a functional and complete interface for doing things, without getting bloated like some of our better known distros. Because of the non-bloat, it is exceptionally fast also. It strives to be very close to UNIX, so it gives you a feeling of a powerful UNIX station, while keeping the simplicity and other advantages of Linux. It is relatively secure and stable also.

      Slackware's package managment is pretty cool too. It does install from pre-packaged tarballs (.tgz), but doesn't by default do dependancy tracking. However, there are other unofficial, yet recommended third party apps that _do_ do dependancy checking, and automatic downloading of packages, etc. Google for slapt-get or swaret.

      On the down side, because of some of the above strengths, it may not be the most user-friendly towards beginners. But it's not overly hard.. like I said, it was my first steps away from Windows back before high school, and I had very few problems with it, while learning a ton about Linux.

      All in all, I highly suggest Slackware. It'll make a great desktop, which I'm using right now, and it also makes a great server distro, as I've done several times also. Whatever you wanna do, Slackware will do it.

    16. Re:grass is always greener by mule007 · · Score: 1

      Ahh.. finally someone else who takes the same approach to installations as me. I've been called a crackhead on numerous occaisons for taking this approach to 'package management', but I totally agree with you that it makes it pleasure to upgrade individual components (escpecially when the software being updated is something you havn't touched in over a year and you aren't even sure which files it originally installed).

      Now if only I could get my friends who use RedHat/Mandrake to see things from my point of view..

    17. Re:grass is always greener by Brandybuck · · Score: 1

      What the heck have you been smoking, and how much does it cost per gram?

      --
      Don't blame me, I didn't vote for either of them!
    18. Re:grass is always greener by Bandman · · Score: 1

      and I'm beginning to think that only Slack users understand what we mean when we say it "gets out of our way". I've given people that exact line, and they look at me like I'm retarded. They just wouldn't know.

      Slackware follows the rule of least astonishment. It works the way it should.

    19. Re:grass is always greener by Bandman · · Score: 1

      If you don't want to do anything extravagant (X, games, etc (or even X with FVWM)), then a 486 with 8 megs will do fine. I actually ran it on 4 megs of ram, but that was a LONG time ago (Slack '96)

    20. Re:grass is always greener by Anonymous Coward · · Score: 0
      > Now I'm using a "hybrid" approach:

      I do exactly the same thing you do, with Red Hat. I only use errata RPMs (well, used to), but all else is compiled by hand and stored in:

      /usr/local/software/FooProgram-1.0/

      I've been doing this for years. Some time ago it was suggested I use stow which looks really good but I'm already too set in my ways to change. Nonetheless, I think it's the best way to go, no matter what flavour of Linux/BSD you are using (in fact, I find this approach really makes you a distro agnostic).

    21. Re:grass is always greener by Kevin_Peters · · Score: 2, Interesting

      This is something I've been trying to address to the OSS community. We need to use hard links if the version isn't the same. Install it in the application's directory. That's where it belongs. This would solve all of Linux's dependency problems, IMO.

      --
      The music is all around us. I can hear it. Can you?
    22. Re:grass is always greener by bcrowell · · Score: 1

      This is already possible in Linux and has been for years (it probably inherited the practice from other unices before it was created). The way that linux handles different versions of the same libraries is actually really nice.
      I've had the worst problems with dependencies that aren't just libraries. For instance, the pango library went through some big changes recently, and on my system, it doesn't help if I leave both the old and the new versions of the library installed. The new one and the old one apparently want their data files stored in different formats or in different places.

    23. Re:grass is always greener by Space_Soldier · · Score: 1

      Correction: ... On disk they are actually stored as [HASH]foobar.dll, but the program...

    24. Re:grass is always greener by bcrowell · · Score: 2, Interesting
      One way is to not use dynamic libaries, and use inline. The binaries will be big, but that is not a problem anymore since hard drives are big and cheap.
      Actually the LSB says that binaries should be statically linked, except for a very short list of very stable shared libraries. Too bad nobody actually pays any attention to the LSB.

      The second way to fix this is to do what .NET did, make assemblies (exe, dlls) strong named.
      One problem with this type of scheme is that sometimes you upgrade a library because it had a security hole, or perhaps because it had a bug that caused crashes or sent data to /dev/null. When you actually want the new version of the library, it's really nice to upgrade it and know that the new behavior will apply to all programs. The real problem is that programmers are sloppy about changing their APIs (and also that some dependencies aren't even libraries). C++, unfortunately, really encourages programmers to break binary compatibility, because any change to an exposed class breaks compatibility.

    25. Re:grass is always greener by john_smith_45678 · · Score: 1

      So you have a ton of stuff in the PATH environment var? I assume all the bin/ dirs are in the respective distribution dirs.

    26. Re:grass is always greener by fok · · Score: 1

      You should try GoboLinux [www.gobolinux.org]: each program resides in its own directory, such as /Programs/Xorg/6.7.0/ and /Programs/KDE/3.2.2. It uses a recipes system to compile packages. Very interesting approach.

      --
      \m/
    27. Re:grass is always greener by ag0ny · · Score: 1

      My PATH is quite clean. Many of the programs installed under this directory don't need to be on the PATH at all: mail client, Gimp, etc. I run these programs using launchers on a Gnome panel, so I just need to set up the location on the launcher once.

      For programs that do need to be on the path, I have a directory for this purpose (/usr/local/software/links/ in my case). This directory is on my PATH, and it just contains links to the binaries that I need to have available. Things like libFooBar-config, programs that I use often on the commandline and stuff like that.

    28. Re:grass is always greener by ag0ny · · Score: 1

      Thanks, but I'm quite happy with FreeBSD. :-)

      Anyway, that's a very interesting approach, as you said.

    29. Re:grass is always greener by Anonymous Coward · · Score: 0

      I've used FreeBSD since 4.0 and I've _never_ had a problem with ports, other than certain ports were out of date (before I figured out the cvsup command to update ports). I'm not saying the problems don't exist, I've just never witnessed them. And slackware has a minimalist and purist philopshy.

      Slackware ships with vanilla builds of all the software, ships with full source, and ships with very little automation. I normally install a very minimal system, then install NetBSD pkgsrc and use pkgsrc to get the rest of the system. As you seem to be against ports, I don't know how well you'd like this.

    30. Re:grass is always greener by Moridineas · · Score: 1

      You check out portupgrade for freebsd? Sounds like it does exactly what you are talking about (handling dependencies)

    31. Re:grass is always greener by captaineo · · Score: 3, Interesting

      That sounds eerily familiar... I think most admins that need a stable production system probably end up doing about the same thing!

      I was spoiled starting out as a Windows programmer. I hate to say it, but Windows has the best attitude towards backwards compatibility of any mainstream platform I've seen. System APIs are preseved, bug-for-bug, *forever*. If I ship or buy a Windows package today, I'm virtually guaranteed it will run on any Windows platform years into the future. Whereas Linux binaries age like meat in the summer sun.

      Perhaps one day a Linux or BSD vendor will get their act together and offer a truly stable system (in the sense of minor upgrades not routinely breaking everything). This will probably require a lot of effort to modularize the various component packages and strictly enforce versioning of interfaces. (Debian seems furthest ahead - e.g. they understand that unstable libraries need a unqie API version for each and every release, regardless of whether the original authors care to provide one)

      The LSB seemed like it was intended to move forward in this direction, but instead it just seems to have codified the existing (poor) situation. RedHat provided a pretty good solution (100% compatibility within major releases) but with the discontinuation of support for their low-end distros, Linux software vendors are left with no clear standard target system.

    32. Re:grass is always greener by CAIMLAS · · Score: 1

      As a debian/gentoo user by choice, I have to ask this same question. What are the benefits of slackware over debian/gentoo? I can see the potential advantages of debian, gentoo, redhat/fedora, and mandrake each - but what of slackware? It doesn't seem to have a leg up on any of the other distros on install, ease of use, package management, community, et al.

      Not specifically what, but -how- is slack superior in your mind?

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    33. Re:grass is always greener by evilviper · · Score: 1
      If I want to run application A, it forces me to upgrade library B. But then the new version of B breaks application C. Oops!

      Which is very simply fixed by reviewing and editing the Makefile before you blindly compile a port.

      Personally, I find OpenBSD to be better in the ports department, but not by a lot. I can tell you one thing, if you think FreeBSD is bad, don't ever try to use Gentoo. It has the same dependency problems, but several orders of magnitude worse... The BSD's ports system usually only wants to upgrade the dependencies when there's a new major version of a port (eg. autoconf-2.14 vs autoconf-2.54), where as Gentoo forces you to install the newer version of a ebuild available, even if it's just a sub-sub-sub version upgrade. You really have to go through removing thousands of ebuilds just to prevent it from upgrading every program on your whole system when you want to install the newer version of even the simplest programs.

      Yes, the grass is always greener.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    34. Re:grass is always greener by ChocoboKnight · · Score: 1

      After reading your post I felt that I had to say this, I run Gentoo on my laptop and I am very happy about it, but on my servers, I run FreeBSD (4 & 5). The thing about FreeBSD is that everything is so logical, I can find everything where I *think* it will be, man pages are very well writen, even new things that have just been imported (like ALTQ in PF for FreeBSD-CURRENT). In gentoo, I just don't *feel* that 'being at home' likehood, but still, I love it. Right now I am leaving and I have to train my replacement, when I was thinking about the system I had to leave to my successor, by a reflex I thought about FreeBSD. For me, I feel it is easier to leave to a total newbie than to leave another system. I feel most at home and I feel I can teach someone else better if its something I appreciate and can talk about without having to Goolgle something up (like, about DUMMYNET, I think I can send him to the relevant man pages) but in Linux, I just don't feel I can leave him to work with iptables and just do not screw up. I know this might sound too centric but the point is, because FreeBSD is build userworld + kernel as a whole, it is much more coherent. Much more easier to train someone into.

    35. Re:grass is always greener by Walles · · Score: 1
      If what you say about FreeBSD ports is true (I haven't used it so I can't tell), it means that FreeBSD ports are broken, not that automatic updates are a bad idea.

      I'm personally running Debian Testing which is automatically kept free from conflicts like those you describe. And the automated updates of Debian using apt-get work very well.

      --
      Installed the Bubblemon yet?
    36. Re:grass is always greener by Anonymous Coward · · Score: 0

      "I was spoiled starting out as a Windows programmer. I hate to say it, but Windows has the best attitude towards backwards compatibility of any mainstream platform I've seen. System APIs are preseved, bug-for-bug, *forever*. If I ship or buy a Windows package today, I'm virtually guaranteed it will run on any Windows platform years into the future. Whereas Linux binaries age like meat in the summer sun."

      Ever use Mac OS? I can run 1985 circa Mac binaries on my 64-bit G5 running Mac OS X, despite radical hardware differences - Classic will run pre-OS X apps, and Classic can run 68K (Motorola 68000 - 68040) apps. Nearly twenty years and two hardware platforms later compatibility, can MS top that?

    37. Re:grass is always greener by Anonymous Coward · · Score: 0

      DSO versioning and symbol versioning within a DSO has been possible for a long time now. You can install multiple copies of the same library, all at different versions, with no problems. Imagine you have libfoo.so installed someplace. You can have:

      libfoo.so.1.2.1
      libfoo.so.1.2.2
      libfoo.so.1.3.3
      libfoo.so.2.0.0


      The trick is then to use symlinks:

      libfoo.so.1.2 -> libfoo.so.1.2.2
      libfoo.so.1.3 -> libfoo.so.1.3.3 libfoo.so.1 -> libfoo.so.1.3
      libfoo.so.2 -> libfoo.so.2.0.0
      libfoo.so -> libfoo.so.2


      The last one, libfoo.so, is always a link to the very latest version installed. ld will use this symlink (And any subsequent symlinks) at compile time to find the latest version of the library to link against. At run time however ld.so will use whichever specific version the binary was compiled against, E.g. binary bar was linked against libfoo.so.1.3.3 while baz was linked against libfoo.so.2.0.0.

      The problem comes from poor package maintainance. Developers need to bump the minor/major DSO version appropriatly, and package maintainers need to ensure that new versions install alongside existing versions, instead of replacing them.

    38. Re:grass is always greener by Welsh+Dwarf · · Score: 1

      Well I did that last summer (slack 8.1, 386 4MB), Had loads of fun :-)

      --
      Ask 8 slackers a question, get 10 awnsers (a citation, but I can't remember from who)
    39. Re:grass is always greener by Welsh+Dwarf · · Score: 1

      Ever tried a Mandrake install on a P133? Desktop I mean, not server. That's one of the greatest advantages of Slack.

      Another is speed, gentoo may be optimised, but Slackware is so streamlined it makes up the difference.

      Also, Slackware 'just works', no hassle. All my kit (tv card, sound card, network) worked straight out of the box.

      Add to that the fact that Slackware is notoriously resistant to security flaws (the pam stuff didn't even touch it, since pam wasn't compiled in...) and you have a few reasons why people use Slack.

      Oh, and one last thing, with Slack, you don't get lost in distro specific config files, everything's where you'd expect.

      HTH

      David

      --
      Ask 8 slackers a question, get 10 awnsers (a citation, but I can't remember from who)
    40. Re:grass is always greener by Anonymous Coward · · Score: 0

      I haven't tried any other distro in years so this opinion may be invalidated by now, but the main reason I stuck with it was because it seemed more like UNIX than any of the other distros. Particularly with Redhat, I got the impression that I wasn't honing my UNIX skills but my skills in some specific distro. In other words, Slackware is a more generic GNU system than the other distros and acquired knowledge is therefore transferable.

      The other advantage of Slackware is that it doesn't get in the way, it just bundles some useful apps, installs them and that's that. It doesn't customise anything, it just presents the apps as is and that's what I want. No unwanted kernel modifications or silly, customised desktop icons that exist only to ignite flamewars.

      Yes, Slackware in my opinion is the closest thing we've got to a version of UNIX in the Linux world. The BSDs are the only alternative if you want a free UNIX implementation.

    41. Re:grass is always greener by Vanders · · Score: 1

      Thats actually the solution we use with Syllable. Packages go into their own directories under /usr/ Syllable has an extra step of running a tool which creates symlinks from /atheos/autolnk/ into the various files and folders within the package directory. That way PATH only needs to contain the directories in /atheos/autolnk/ instead of all those package directories, which speeds up searches.

    42. Re:grass is always greener by Bazer · · Score: 1

      I was spoiled starting out as a Windows programmer. [...] If I ship or buy a Windows package today, I'm virtually guaranteed it will run on any Windows platform years into the future.

      That's one of the many reasons why the whole system is crippled - it encourages the developers to be lazy. Now Microsoft tries to do something about it with .NET and it's upcoming successor but that has bad effects taking into account their past policy. Pushing lazy developers to a completely new API makes them angry, pushing them twice can make them leave. Linux is constantly changing but it's a steady pace and if your application doesn't rely on the kernel you could always, include a static library like Opera or Skype.

    43. Re:grass is always greener by goon · · Score: 1


      I might try to get X to work as it's a hack box for the ankle biter (just learning to read) ~ though he is having fun using OpenBSD playing Adventure.


      Of all the distro's looks like slackware really goes to the effort of keeping the hardware requirments light.

      --
      peterrenshaw ~ Another Scrappy Startup
    44. Re:grass is always greener by pacman+on+prozac · · Score: 1
      It's strengths for my uses are:
      • Ten minutes installation process.
      • BIOS->login prompt in about 12 seconds or less (with tuning).
      • All the boot scripts are clearly written shell scripts that are easy to adapt (unlike most distros).

      It's weaknesses are the packaging system, I just couldn't ever go back to any non-source-based packaging again. I still remember having to re-install to get new glibc support, never again.

      I never had the problems you mention with FreeBSD or Linux, mainly because the libs I use seem to be always backwards compatible. Compared to the problems I have had with binary-packages I'll take a little library clashing anyday, at least you know that can be fixed in ten minutes by compiling two of the problem packages from source.
    45. Re:grass is always greener by Bandman · · Score: 1

      definately. Not many of them can still boast that they make a 486 a usable machine*

      * - may have to recompile default kernel :-)

    46. Re:grass is always greener by reallocate · · Score: 1

      I think you'd find Slackware a breath of fresh air coming from BSD.

      Your assessment of automatic dependency resolutions is correct. Sooner or later, something will break. It isn't the fault of the automatic resolvers. They don't use AI. If someone installed the same software manually, they'd have the same problems.

      Some folks seem to install and remove dozens of programs per week. Dunno why, but that seems a recipe for breakage. In my experience, nothing I've installed from the Slackware site has ever caused a problem. If you pay attention (read the readme before installing, etc.) installing from source ought to pose no problem, either. You will know exactly what's on your machine because you out it there.

      If something does break, at least you know that it wasn't because you annoyed the packager or the dependency resolver.

      On the down side, Slackware could use a couple of good online forums, one for veterans and one for newbies. Patrick V. killed his forums a few years ago after they devolved into flames, spam and bitterness. Alt.os.linux slackware can be helpful, but I find that some of the regulars are overly territorial and condescending (too many responses that say "I know, but you should RTFM.) A few Liux sites have Slack-specific forums, but I've found the quality of their postings to be debatable,

      --
      -- Slashdot: When Public Access TV Says "No"
    47. Re:grass is always greener by Space_Soldier · · Score: 1

      That has to do with version numbers Major.Minor.Build.Revision. If the revision number has changed, .net treats the 2 libs as compatible. The newer version has only bug fixes. If the bulid version has changed, .net treats them as possible compatibility between them. If the minor, or major is changed, it treats them as uncompatible.

    48. Re:grass is always greener by KennethSundby · · Score: 1
      Actually I'm starting to feel that automatic systems for installing software and satisfying dependencies are more trouble than they're worth.
      You could always just not use the automatic systems you know.
      --
      -Kenneth Sundby-
    49. Re:grass is always greener by nighty5 · · Score: 1
      I have a similar approach although with one slight twist:

      I install app in:
      /usr/local/software/FooProgram-1.0/

      and create a symlink from:
      /usr/local/software/FooProgram

      which points to:
      /usr/local/software/FooProgram-1.0/

      Whenever you install a new version of app, and then your happy with it, i then just change the symlink without needing to update any other dependancies within scripts etc.

      Your milage may vary for this approach but it works quite well for me.

    50. Re:grass is always greener by pope1 · · Score: 1

      Speaking as a member of the National Center for Biotech. Information, this is how we do things as well.

      It is so much easier to keep fast changing software in release-specific directories.

      Things like Mozilla for instance: /usr/local/mozilla-1.4 /usr/local/mozilla-1.6 /usr/local/mozilla-1.7 /usr/local/mozilla-test /usr/local/mozilla -> /usr/local/mozilla-1.7

      the last entry there is a symlink in case you were wondering.

      we have a script that gets executed during the login procedure to setup personal preferences for the version of each software package we support.

      It sets $LD_LIBRARY_PATH, $PATH, $PKG_CONFIG_PATH and any other environment variables that need tweaking to get stuff loaded (or for development).

      And if we need to remove a version, it's as easy as the parent poster said, just kill the directory.

      For the Base OS we use packages, but we maintain dependancy info. ourselves. Most of what we consider "Base" requires only 1 or 2 dynamic libs. max (mostly just libc and ld-linux).

      It's nice to see this methodology applied elsewhere as well.

      --
      /* * pope1 */
    51. Re:grass is always greener by captaineo · · Score: 1

      A LOT of OSX software broke between the incremental 10.2 and 10.3 releases. This was due to Apple "cleaning up" APIs without preserving backwards compatibility.

    52. Re:grass is always greener by captaineo · · Score: 1

      You should read Joel Spolsky's "Why Microsoft lost the API war" http://joelonsoftware.com/articles/APIWar.html. Microsoft is just fine with encouraging lazy developers, because a lazy Windows developer is still a Windows developer. Microsoft realized that if an OS upgrade breaks an application, the public will see it as Microsoft's fault, even if the breakage was due to poor programming by the application vendor. So they decided to make sure upgrades break as little as possible.

      I don't mind a crufty API that works forwards and backwards for years.

    53. Re:grass is always greener by CrkHead · · Score: 1
      Several years ago I tried out several distos, and have stayed with slack. The learning curve may have been greater than with RH, but slack has always 'just worked' out of the box and I have never felt as though I was being crippled to keep from doing something stupid. When I do something stupid I have always been able to recover, at least well enough to preserve data and rebuild.

      Every once in a while I'll try *BSD or another Linux distro, once I tried Solaris, and I have either felt that I have lost some control of my system or I get bored hunting down config files that are not where I'm used to finding them.

    54. Re:grass is always greener by agraupe · · Score: 0

      Linux binaries don't age well because the programs are meant to be compiled from source, as far as I can tell. That's why I use gentoo :)

  27. Re:Yet Another Distro by Anonymous Coward · · Score: 0

    Yet Another Distro? At version 10? Think before you post man.

  28. Re:Yet Another Distro by tiny69 · · Score: 2, Insightful
    Please, keep these garage basement projects out of the news...
    Apple and a few other large computer companies started out in a garage. Google started in a dorm room. So what's your point?
    --
    Go not unto/. for advice, for you will be told both yea and nay (but have nothing to do with the question)
  29. Re:Yet Another Distro by Aggrazel · · Score: 1

    I wonder how many self proclaimed linux geeks know how to pronounce Yggsdrasil.

  30. Re:Yet Another Distro by kfg · · Score: 0, Offtopic

    So what's your point?

    Humor.

    KFG

  31. Somebody help me out... by rindeee · · Score: 2, Interesting

    ...what is the draw to Slackware? I have used (and loved) both SUSE and Debian for years and use them as my primary systems (along with OS X and Solaris). SUSE has YAST. Debian (and based distros) has the best (in my opinion) package management system. RedHat has....ummmm...well, I'm sure it has something. Anyway, since I've never used Slackware, what are its best qualities? I'm very curious as it seems to garner a lot of respect.

    1. Re:Somebody help me out... by ananke · · Score: 1

      Simplicity and elegance. It's a great starting point for many purposes.

      --
      --- d'oh
    2. Re:Somebody help me out... by poohsuntzu · · Score: 1

      It is one of the oldest distributions of Linux, for starters, and this one of the most loyal fanbases.

      However, I feel a lot of people respect slackware for it's founder and the principles in which it is based off of. The KISS principle, for example (keep it simple stupid) is what draws myself to it. No hidden "WTF is this config file?! it isn't in etc!", and configuration is very straight foward. A binary will be in /usr/bin, not /opt/bin/usr/somewhere/in/egypt. They can take the complicated aspects and provide enough infile documentation for you to learn what you are doing.

      It's really a matter of personal preference. If you want a balance between newer packages and proven stability (think of a cross between gentoo bleeding edge and debian stability), then go slackware. If you want a very straight-foward no-holds-barred OS, go slackware.

      --
      "We're breaking out the ramen noodles. . . "
      "Really? Is it someone's birthday?"
    3. Re:Somebody help me out... by fayd · · Score: 1

      As I've responded before, I use SuSE on my desktop, although I'm starting to reconsider that.

      However, I can't stand any pretty packaged distro on my servers. Too much crap that I have no interest in gets installed even on their "server" installation.

      With Slackware, I install _exactly_ what I want, and nothing else. That's the attraction: almost every option available, and absolute control over what gets installed and how it gets configured. Mind you, you have to think, even learn something occasionally, but you can't beat getting exactly what you want.

    4. Re:Somebody help me out... by guacamole · · Score: 1
      However, I feel a lot of people respect slackware for it's founder and the principles in which it is based off of. The KISS principle, for example (keep it simple stupid) is what draws myself to it. No hidden "WTF is this config file?! it isn't in etc!", and configuration is very straight foward. A binary will be in /usr/bin, not /opt/bin/usr/somewhere/in/egypt. They can take the complicated aspects and provide enough infile documentation for you to learn what you are doing.


      This argument doesn't stand any more IMHO. It seems like you have just described Solaris (specially, pre-Solaris 8 versions) where indeed the OS binaries and config files often used to live in really strange places. However, in these days of LSB, I don't see anything controversial with the file system layout of Fedora, Debian, or other mainstream Linux distributions.

    5. Re:Somebody help me out... by tomhudson · · Score: 1
      However, in these days of LSB, I don't see anything controversial with the file system layout of Fedora, Debian, or other mainstream Linux distributions.
      Oh, come on.

      media/, opt/, srv/, and sys/ as top-level directories on a linux box? (That's what I've got on SuSE 9.1, which is really nice, except for things like that).

      Slackware is simple, and simple is simply good.

      Mind you, so many people must want it, because here's what you see now:

      Warning: mysql_pconnect(): Too many connections in /var/www/slackware/php_includes/database.inc on line 20 could not connect to database
      Yep, a good old-fashioned slash-dotting. Slackware sure is popular, you think? My torrents will be finished downloading within the next 2 hours, but I'm leaving them open for the next couple of days, just to help spread the gospel :-)
    6. Re:Somebody help me out... by johnnyb · · Score: 3, Insightful

      Slack appeals to the "traditional UNIX" group of people. I actually started on Slack 3.(5|6) that came bundled with a book. The book said it came with a complete UNIX system. I didn't really believe it - I was assuming it was some sort of trialware - and learning about people who actually shared code with each other freely really changed my perception of the field of computer science while I was in college.

      Slackware today still has a lot going for it:
      * it doesn't assume much about you, except that you know what you're doing
      * it is built for speed - it attempts to be cruft-less (and from what I've seen it succeeds quite well)
      * it's packages are backwards-compatible w/ .tar.gz formats
      * BSD-style init for those who like it (I'm a SysV guy, myself)
      * a competent community

      It's kind of a do-it-yourself kind of environment, which, for some reason, Linux people often enjoy :)

    7. Re:Somebody help me out... by Katamai · · Score: 1

      Redhat has up2date.

      https://rhn.redhat.com/help/latest-up2date.pxt

    8. Re:Somebody help me out... by Anonymous Coward · · Score: 0

      Slackware has geek status, It's got a cool name and is always requiring you to edit make files, find libraries, generally is a pain in the ass but nobody will call it a newbie distro thus making you cooler than suse, redhat and mandrake users instantly. It doesn't matter that it doesn't innovate like redhat, isn't as pretty as suse, isn't as easy as mandrake, doesn't have good package management like Debian, doesn't have repositories like fedora. The general thing is these other distro's do something to improve linux's usability while all slackware does is tarball free software and fix bugs.

    9. Re:Somebody help me out... by EvanED · · Score: 2, Funny

      A binary will be in /usr/bin, not /opt/bin/usr/somewhere/in/egypt

      Just what do you have aganst Egypt? Are you racist? I have a dream that one day binaries will be judged not by the path in which they reside, but by the nature of their execution.

      (With sincerest apologies to Dr. King)

    10. Re:Somebody help me out... by James4765 · · Score: 2, Insightful
      Because I can strip it to the bones and make it into a custom router, or print server, or whatnot very, very easily. Red Hat, Mandrake, SuSE and the rest try to put their "brand" on just about anything - Slackware hasn't been tinkered with overmuch, hasn't had 2.5 kernel stuff backported to 2.4 (breaking gawd-knows how many libraries, libdnet for one - sorry, no Nessus on your Fedora box!) and generally just behaves itself better.

      OTOH, it is definitely not a beginner's OS. Sort of like how no novice rider could ride a Ducati even close to it's peak, but with experience, a rider can do amazing things with the same bike.

      Plus, Slackware (and Debian) are the only distros left that can install on really old PC's - 486's and 386DX's. 'Bout the only thing they're good for is a poor man's remote terminal server, tho...

    11. Re:Somebody help me out... by evilviper · · Score: 3, Insightful

      I think it's simple. Slackware is the most simple of all distros. It doesn't have SysV scripts, just the basic /etc/rc scripts, which are incredibly simple, easy to configure, etc.

      It has the simpliest package manager of any. It doesn't get in your way, and it's trivial to make a package. In fact, it's trivial to install a slackware package without the package manager.

      All packages come with the dev files (headers, libs) so you don't need to mess around with all the roadblocks other distros put in your way that make it harder to install the dev files for your programs.

      There's plenty more reasons, but I find that to be a good run-down of the biggest reasons to use it.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    12. Re:Somebody help me out... by hopeless+case · · Score: 1

      Allow me extend your points by putting my finger on the mother of all reasons why slackware is simple.

      Let me begin with this question:
      Where exactly does the simplicity of slackware come from?

      It comes from the fact that one man, Patrick Volkerding, maintains/develops the entire distribution. This puts a severe upper limit on how complex a build script he can write for any given package. The build scripts had better all follow the same basic concepts and be easy to read or one man could never maintain a thousand of them.

      I don't know much about the other distribtions, but I'd wager that there is quite a bit of variance and complexity among the build scripts. Would any debian users care to comment on that?

      How many distributions can boast that a single man develops/maintains the entirety of the build scripts?

    13. Re:Somebody help me out... by lanc · · Score: 1
      Oh, come on. media/, opt/, srv/, and sys/ as top-level directories on a linux box? (That's what I've got on SuSE 9.1, which is really nice, except for things like that). Slackware is simple, and simple is simply good.

      /opt - to install stuff with own directories, like /opt/tomcat4. /usr/local should be used like /usr/locale/sbin /usr/local/lib etc.

      /sys - use with the 2.6 kernel sysfs. gonna help you wiht your probs with /proc

      OK /srv I dont like that much, and personally i like /mnt/cdrom /mnt/floppy over /media things, but /opt and /sys are just useful and necessary.

      Too simple is not always productive.
      --
      "First they ignore you, then they laugh at you, then they attack you, then you win." -- Mahatma Gandhi
    14. Re:Somebody help me out... by tomhudson · · Score: 1
      /opt - to install stuff with own directories, like /opt/tomcat4
      ... or stick it in /usr/local, like everyone else (and make /usr/local on a separate partition, like home, so when you upgrade/reinstall/change distros, all *your* programs and data are still there :-)
      /sys - use with the 2.6 kernel sysfs. gonna help you wiht your probs with /proc
      ... so why not just "fix" proc and devfs? Mind you, if Linus wants it, it can't be *all* bad ...
    15. Re:Somebody help me out... by lanc · · Score: 1
      ... or stick it in /usr/local, like everyone else
      as I see I wasn't clear enough. let's try again with some easy-to-understand examples:
      /opt/tomcat
      /opt/java/current
      /opt/oracle
      /opt/veritas/netbackup
      /opt/veritas/volumemanager
      /opt/foreignsoftware

      and:
      /usr/local/bin
      /usr/local/sbin
      /usr/local/lib

      ...etc. get it now? /opt for things yu want to keep away from /usr, or u want to install them in an own dir. in /usr/local are things installed, which belong to the PATH, and where u can manage the permission auf directory level ... and in /opt every dir is an own world. Cannot explain it better, so either you try to understand it hard, or we both give up. hm?
      ... so why not just "fix" proc and devfs? Mind you, if Linus wants it, it can't be *all* bad ...
      let me quote an article: The Wonderful World of Linux 2.6
      "The final, but possibly the most obvious, ramification of the new centralized infrastructure is the creation of a new "system" filesystem (to join 'proc' for processes, 'devfs' for devices, and 'devpts' for UNIX98 pseudo-terminals) called 'sysfs'. This filesystem (intended to be mounted on '/sys') is a visible representation of the device tree as the kernel sees it (with some exceptions). This representation generally includes a number of known attributes of the detected devices, including the name of the device, its IRQ and DMA resources, power status, and that sort of thing. However, one aspect of this change that may be confusing on the short term is that many of the device-specific uses of the "/proc/sys" directory may be moved into this new filesystem. This change has not (yet) been applied consistently, so there may continue to be an adjustment period."
      --
      "First they ignore you, then they laugh at you, then they attack you, then you win." -- Mahatma Gandhi
  32. WMP54G by jeffkjo1 · · Score: 2, Interesting

    If slackware will work, out of the box, with my Linksys WMP54G wireless card, I'll start using it yesterday.

    Anybody know?

    1. Re:WMP54G by Anonymous Coward · · Score: 1, Informative

      If by "out of the box" you mean you don't mind using (building) ndiswrapper, then yes, it works out of the box. ;)

    2. Re:WMP54G by osmin626 · · Score: 2, Interesting

      There's an old saying that been floating around in the hallowed halls of Slack for a long time:

      'Ask ten Slackers a question; get eleven answers.'

      I.e. Slackers tend to know exactly what they are doing.

      They don't have to hide behind any fancy-pants tools to get the job done. With Slack, you get down to the bare metal, and most Slackers like it that way.

    3. Re:WMP54G by EvanED · · Score: 0

      If slackware will work, out of the box, with my Linksys WMP54G wireless card, I'll start using it yesterday.

      What I want to know is how you got it to interface with your time machine; I have one myself and have had incredible difficulties with it. It gets up to 299,792 km/s or so then crashes with "Error: speed out of range." Any ideas?

    4. Re:WMP54G by Anonymous Coward · · Score: 0

      What I want to know is how you got it to interface with your time machine; I have one myself and have had incredible difficulties with it. It gets up to 299,792 km/s or so then crashes with "Error: speed out of range." Any ideas?
      Sounds like your using an old Mark II TARDIS. You'll need to apply a kernel patch or upgrade to a Mark III.

    5. Re:WMP54G by mattyrobinson69 · · Score: 1

      maybe - enable /etc/rc.d/rc.hotplug during setup.

      if that doesn't work then recompile your kernel - its not hard or time consuming

    6. Re:WMP54G by RDW · · Score: 1

      This is actually a legal rather than a physical limitation. Use of transluminal velocities by Linux kernel modules infringes a US patent unless you have an appropriate license for this technology. I believe a license is available for $299,792,458 per device, which allows you to reset LIMIT_C_VELOC to zero and re-compile.

    7. Re:WMP54G by Skater · · Score: 1

      My favorite, from Distrowatch: "If you want to know something about Linux, ask a Slackware user."

      (I'm biased since I use Slackware exclusively. :) )

      --RJ

  33. The question is... by NoData · · Score: 1, Funny

    why are you talking to your right hand?

    1. Re:The question is... by Anonymous Coward · · Score: 0

      Psst, thenextpresident is left handed.

    2. Re:The question is... by NoData · · Score: 1

      Psst, thenextpresident is left handed.
      Yeah, but it's his right hand that's the awkward geek.

    3. Re:The question is... by WhiteDeath · · Score: 5, Funny
      why are you talking to your right hand?

      because the other one left?

    4. Re:The question is... by Anonymous Coward · · Score: 0

      Haven't you ever seen Vampire Hunter D?

    5. Re:The question is... by Anonymous Coward · · Score: 0

      Vampire Hunter D is shit ass crap anime. Real Otaku watch Sailor Moon.

    6. Re:The question is... by Anonymous Coward · · Score: 0

      Earth to you: YOU SUCK LOSER!

    7. Re:The question is... by tylernt · · Score: 1

      Vampire Hunter D... ah, my first anime ever. Hey, I liked it!

      --
      DRM 'manages access' in the same way that a prison 'manages freedom'
  34. I agree.... by strabo · · Score: 2, Funny

    Anything that came after SLS is just Yet Another Distro...

  35. Slackware through the years by ziggyboy · · Score: 3, Interesting

    I have been a Slackware user since 1996. I've seen it grow all through these years, and even though it didn't get as popular as Redhat, Mandrake, SuSE or Debian, I stuck with them. It's been Slackware from the first Internet server I've installed in 1996 to my new personal server this year. I've never been so proud of my distribution of choice! My thanks goes to Patrick Volkerding for all his effort. He actually replied to my emails years back...however minor my concerns were. Thank you for taking care of your Slackware users.

    Slackware has always been releasing the latest software, although this time they sounded 'too Debian' by releasing a 2.4 kernel claiming it was more 'stable' than 2.6. This is a first. They still don't have a packaging tool to match apt. Well, maybe someday... Nonetheless, viva la Slackware!

    1. Re:Slackware through the years by tarballedtux · · Score: 1

      I think swaret is pretty bad ass if ask me. Maybe it's not the greatest but it gets the job done and easily. It has dep check to :) --tarballedtux I know someone is going to bring up the point about the developer being an ass towards the slapt-get project, but I read he has nothing to do with swaret anymore and that doesn't matter to me anyway cause the software works.

  36. Once again, the subtle humor is lost on a geek... by Anonymous Coward · · Score: 0

    Or maybe he just likes being contrary...

  37. RE: Not Another Distro by Anonymous Coward · · Score: 0

    In other news, Nasa scientists were recently overheard complaining about a garage basement spaceship making national news.

  38. Re:Yet Another Distro by Anonymous Coward · · Score: 0

    Yeah, I don't think anyone else got it...

    I mean, come on people... really.

  39. Re:Yet Another Distro by Anonymous Coward · · Score: 0

    Yeah, that's why it's funny.

  40. About mysql_pconnect by nihilogos · · Score: 2, Insightful

    Slightly off-topic, but hey. The site is slashdotted with a "too many connections error"

    <rant>
    This is why just about no-one should use php's mysql_pconnect function. It sounds great, "Oh cool it will keep the connection open so apache doesn't have to reconnect to the server." The connection overhead when mysql is running on the same machine is minimal, and you don't run into this problem where apache spawns 50 child processes, each of with its own persistent connection, and eventually you get the "too many connections error".
    </rant>

    --
    :wq
    1. Re:About mysql_pconnect by ag0ny · · Score: 1

      Any self-respecting sysadmin would have been wise enough as to set the max_connections on the MySQL server to be at least the same as the MaxClients parameter on Apache's config file.

      It isn't nice to blame PHP for the sysadmin's lack of foresight.

    2. Re:About mysql_pconnect by nihilogos · · Score: 1

      True. But typical ISPs don't.

      It isn't nice to blame PHP for the sysadmin's lack of foresight.

      I wan't blaming PHP, I was blaming web scripter's undiscerning use of persistent connections.

      --
      :wq
    3. Re:About mysql_pconnect by Anonymous Coward · · Score: 0

      Persistent connections do not help if you allow more connections to your web server than mysql does.

      Configure apache properly. Set max clients to your database server's limit.

  41. Re:distribution based on slackware still using xfr by Anonymous Coward · · Score: 0

    I CAN'T be the only one frightened by the concept of a Jo linux.

  42. Re:Yet Another Distro by DA-MAN · · Score: 1

    Yggdrasil - (Igg Druh Sill) First Linux distro I ever used. Came with retarded video, with a classroom full of people nodding with a clueless look on their faces . . .

    --
    Can I get an eye poke?
    Dog House Forum
  43. Why slackware? by deviantonline · · Score: 1, Redundant
    Ive always wondered what was so special about slackware. Ive never actually tried it myself (Ive only ever used Mandrake and Redhat, favoring Mandrake over the two), so I dont know what slackware is all about.

    Ive noticed that people seem to hold slackware in a high respect and I just wanted to know what makes it different from the rest.

    1. Re:Why slackware? by Anonymous Coward · · Score: 0

      Sounds like someone got kicked in the balls by Slack one day and has never fogiven it. Slack and Gentoo are nothing alike, and never will be. While going the compile route for Slackware is fine, most users just go with packages. And using Slackware doesn't make you l33t, it makes you smart about Linux. It doesn't matter if you're on RedHat, Slack, or Gentoo, if you've mastered Slack then you can adapt to any of them and manage them. This is really important in the real world where problems come up often in the office and a Slacker can help out. Might give that Slacker a promotion as well. So instead of whining, why not try Slackware out (you obviously haven't) and see how you're wrong.

    2. Re:Why slackware? by nazsco · · Score: 1

      I don't have a buzz-word to spit for you as an answer right now, as someone that uses Mac, Windows, Red hat, would.

      And THAT's why slacks rocks!
      I have a server that's already runed OS2, Free and Open BSD, red hat, suse..damn, even Plan 9 hehe

      and except from plan9, i runned everything for at least 11months. and at least 3 full installs of each. That's more than enough for a benchmark of the ease of use for the sysadm. ...I'm not interested in performance in this server. btw, It's always been a Pentium MMX 100@133 with a good intel mother board and PCI network cards and mere 32Mb of ram. Nothing fancy.

      The fact is that i don't have time to deal with that machine. It simply have to work. Every install was made with less than a day -usualy a rainy sunday- and all the maintenance was done remote while waiting time pass at work. So, now that i've choose slack -since version 4- i'm pretty sure it's the one that bother me less than the rest. The buzz word to convince you... well, i still lack it. Cuz i don't need any buzz word to convince *myself* that's slack is what i should use.

      But, keep in mind that my experience is purely for server stuff... this machine don't even have a screen!
      The only time i used it as a desktop, was to run X+blackbox+Opera

      I've only one friend that uses slackware9.1 at his workstation, but since he already used freeBsd4 i don't think he counts. And if you want a workstation you shouldn't look into linux. Use a bootleg copy of Windows, it runs the newer games while you'r slacware sidekick keeps the worms at bay :)

    3. Re:Why slackware? by nazsco · · Score: 1

      oops, i forgot to tell the real reason:

      fortunes at every logon by *default*

    4. Re:Why slackware? by Anonymous Coward · · Score: 0

      Slackware isn't interested in buzzwords and marketing?

      Oh really.

      So why did Pat jump the version number from 4 to 7 so he could be "one better" than redhat 6?

      Just because no one uses slackware doesn't mean it's not still a for-profit distro. But since it only really has one employee it can't go out of business. Of course if that one employee gets hit by a bus you are seriously fucked but hey no one uses slack for anything important anyways...

    5. Re:Why slackware? by L0stm4n · · Score: 0

      I started using slackware on version 8.0. Slack taught me how to use linux, not how to use redhat, or suse, or [whatever]. Slackware is elegant, simple, straightforward, linux. I can easily walk through the startup files and find out what is going on without bouncing between 30 files. It does not attempt to hold your hand to much. It reminds me of walking through a park with a good friend instead of walking through the park with my mother, which is how many distros seem to treat the newbie now.

      I now use fedora on my desktop, Suse for my webserver and slackware for my firewall. If any one of these machines give me any shit I fall back to my slackware learned roots and fix the problem.

      Slackware gave me the basics, now I can use any distro and beat it into submission when it acts up.

      --
      superman runs linux
    6. Re:Why slackware? by nazsco · · Score: 1

      The fact that he jumped from 4 to 7 to keep pace with other distros was more a JOKE than a marketing approach.

      The prove that he don't give a damn about RH's 1 release per week at the time.

  44. Re: Torrents directory layout a bit weird by tomhudson · · Score: 3, Informative
    The torrents save the first set of files to slackware-10.0-iso/, the rest to subdirectories under it, kind of weird, so you end up with this:
    • slackware-10.0-iso/
      • slackware-10.0-install-d1.iso
      • slackware-10.0-install-d1.iso.asc
      • slackware-10.0-install-d1.iso.md5
      • slackware-10.0-iso/ (subdir with same name as parent dir!)
      • slackware-10.0-install-d2.iso
      • slackware-10.0-install-d2.iso.asc
      • slackware-10.0-install-d2.iso.md5
      • slackware-10.0-source-d3.iso
      • slackware-10.0-source-d3.iso.asc
      • slackware-10.0-source-d3.iso.md5
      • slackware-10.0-source-d4.iso
      • slackware-10.0-source-d4.iso.asc
      • slackware-10.0-source-d4.iso.md5
    Not the prettiest layout for the disks, IMO.

    Nevertheless, I'll leave it running for the next few days (got to use my 1mb upload for something, right :-)

    This may be an artifact of linux, as I've noticed it before with a few pieces of code I wrote where a directory already existed, and it created another with the same name under it ...

  45. Re:Do you want us to use slackware, or have fun? by Anonymous Coward · · Score: 0

    Yes.

  46. Re:Yet Another Distro by sbrown123 · · Score: 1

    hahahaha.....hahaha.....ha....ha?

    Sorry, dont get it. Its either a very poor attempt at humor or a poor attempt to try to make people believe it was humor to cover a bad comment. Ill go with the later.

  47. Donations by Via_Patrino · · Score: 5, Insightful

    "non-cheapskates among us should go buy the CD-set to support the project"

    If you want to support the project you dont need to buy anything, donate directly and all the money you wanted to donate (not just part of it) you reach the end you wanted.

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

      How about donating CD's?

  48. My Love by dangerz · · Score: 5, Informative

    RedHat was the very first distro I ever used, which was several years ago. Eventually, I tried out several other distros once I was comfortable with RedHat and once I came to Slackware, I hated it more than life. It was so hard to configure and was much different than RedHat.

    Eventually, I did get it working and I am so happy that I did. Slackware has been my favorite distribution of Linux ever since, and I continue to use it today on all my linux pc's. Gentoo was ok, but something about Slackware keeps me coming back. I'm currently on my P4 3.2ghz Laptop running Slackware 9.1, while my server upstairs which hosts all my projects and work is running Slackware 9. At my parents' house (I live with my gf in an apartment at college), my mp3 server still runs to this day running some oooold version of Slackware from 1998. It still is just as stable and just as good. It's a 486, so it has no reason to upgrade anything. The system runs stable and fine for all the hardware and all the tasks it needs.

    Eventually, I'd like to have my desktop upstairs running linux. It's hard to part with MS Flight Simulator though and I need Macromedia Flash for development.

    Either way, this is my thank you to Patrick for giving me a beautiful and stable distro.

    --
    The greatest experience we can have is the mysterious.
    - Albert Einstein
    1. Re:My Love by wpc4 · · Score: 1

      As for Flight Sim, I don't think WineX supports that yet. BUT Crossover Office does support Macromedia Flash MX.

    2. Re:My Love by dangerz · · Score: 1

      Ya, I actually purchased a license to CrossOver Office and use it to run Adobe Photoshop 7. The last time I tried Macromedia Flash on CO though, the animations ran very slow and it was hard to actually develop in it.

      I read a while ago that Macromedia was going to try for native support for linux, so I hope that also means their development suite.

      And ya, I wish Flight Sim was supported. Although Flightgear is pretty good, I think MS's product is much better looking (don't tell anyone here that I said that, I'll get beat) and has more support.

      --
      The greatest experience we can have is the mysterious.
      - Albert Einstein
    3. Re:My Love by ahaning · · Score: 2, Funny

      don't tell anyone here that I said that, I'll get beat

      Don't worry. You've just praised a Microsoft product after praising Slackware. All those that would beat you are currently passed out due to a short circuit in their beliefs code.

      --
      Withdrawal before climax is very ineffective and those who try this are usually called "parents."
    4. Re:My Love by john_smith_45678 · · Score: 1

      > It was so hard to configure and was much different than RedHat.

      Can you elaborate? What specifically?

      > my mp3 server

      Which one?

    5. Re:My Love by Anonymous Coward · · Score: 0

      ANOTHER TROLL MODDED 5

  49. Welcome to Unix by Billly+Gates · · Score: 1, Interesting

    One of Windows strengths (only) is that you can have multiple versions of dll's. This started with Windows2k.

    Yes the infamouse GP faults were the cause of conflicts and wrong dll versions but Windows tracks each one and applies the right version of the dll for the right app at runtime.

    Why can't unix do this? ALso instead of having everything in /usr/lib most non system dlls are in seperate directories of where the apps are installed. When you run an .exe setup program it only copies the dlls that are needed or puts its won dlls in their own private folders.

    Korn who worked some unix services for Windows commented that he liked the idea of having seperate libraries in each folder.

    Why can't we do this?

    Also many older apps wont run on Linux or emulated well in FreeBSD. Why? Because of linking to newer versions of libraries and tools that are incompatible.

    It would be great to have the kernel decide which .so and tools for each version of the app. That way we can run old RH4 apps and Linux apps in FreeBSD without a problem.

    1. Re:Welcome to Unix by transiit · · Score: 1
      transiit@darkstar:/bin$ ldd /bin/ls
      librt.so.1 => /lib/librt.so.1 (0x4002d000)
      libc.so.6 => /lib/libc.so.6 (0x40040000)
      libpthread.so.0 => /lib/libpthread.so.0 (0x40176000)
      /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
      See all them numbers?
      This isn't a feature of the future....been around for quite some time.
      For any program that doesn't hang well with latter-day libraries, just make a quick shell script that sets LD_LIBRARY_PATH to point where you've got the older versions stashed away before starting the app. Things dependent on all sorts of hoary old stuff can always be done in a chroot'ed old-school environment, though it'd probably be overkill.
      -transiit
    2. Re:Welcome to Unix by Billly+Gates · · Score: 1

      So I could run an old RH 2.x app?

      What if I did the LD_LIBRARY_PATH to look at libc3? It would break everything.

      Its one library for all the system only. Thats the problem.

      BUt lets be real why should we need a jail or chrooted?

      Face it with 3k apps you are abound to have problems like the original poster says. In Windows you just point and click and it works.

      Its at a crises level and many linux users prefer windows as a desktop for the reason described with conflicts.

    3. Re:Welcome to Unix by transiit · · Score: 1

      An application linked to say, libc5 wouldn't be asking for libc.so.6 (glibc). It'd be asking for libc.so.5, which for a system-wide thing would've ended up in ld.so.conf, not the LD_LIBRARY_PATH. Use the latter only for when you need to do special tricks like user-level compatibility stuff (i.e., root (presumably, not you for this example) doesn't want to install a bunch of old libraries system-wide, so you use LD_LIBRARY_PATH to let the loader know where the extra stuff lives, perhaps /home/billygates/lib)

      It's not one library for the whole system.

      It doesn't just work in Windows. It took them years to get where *nix has been. DLL hell was a phrase coined for them.

      I am a linux user. I prefer linux on the desktop. I can't speak for others, and I won't even try.

      But don't mistake "what you're used to" to "only one capable"

      -transiit

  50. Since it is a fork of Xfree... by poohsuntzu · · Score: 1

    It will work just like Xfree did.

    --
    "We're breaking out the ramen noodles. . . "
    "Really? Is it someone's birthday?"
  51. The KISS principle by poohsuntzu · · Score: 1

    Slackware, I felt, has always kept a solid balance of stability and newer packages. I wouldn't doubt that Pat saw all the errors and problems people have been having with the 2.6 family and decided to hold back, as he would much rather have a kernel he knows is solid, stable, and proven than one that could give his worshipers problems. KISS (keep it simple stupid) applies the most here because of the drastic changes from 2.4 to 2.6 in terms of configuration. From Alsa to OSS, to even SCSI emulation, a lot of things have changed that he may not feel the slackware userbase want's just yet.

    --
    "We're breaking out the ramen noodles. . . "
    "Really? Is it someone's birthday?"
    1. Re:The KISS principle by irokitt · · Score: 1

      Although it should be noted that, even with a 2.4.x kernel, slack 9.1 used ALSA and not OSS. Much to Pat's credit for that particular backport.

      --
      If my answers frighten you, stop asking scary questions.
    2. Re:The KISS principle by poohsuntzu · · Score: 1

      I could be completely wrong here, so by all means correct me :) Didn't ALSA need the OSS as a base enviroment to run in?

      --
      "We're breaking out the ramen noodles. . . "
      "Really? Is it someone's birthday?"
    3. Re:The KISS principle by geminidomino · · Score: 1

      I think You're wrong. :) ALSA has an OSS-compatibilty module for things (QuakeIII) that require OSS, tho.

  52. I Disagree. by sp0rk173 · · Score: 5, Interesting

    When I started out, I cut my teeth on Mandrake. It was easy, but I did nothing for two weeks but say, "Man! Look at all these fractal programs!" A week later I installed slack...that's when I began to love *nix. The curve went from a slope of zero to exponential. The slackware installer even has a good intro for a newbie. It's nothing to be afraid of.

    1. Re:I Disagree. by RyuuzakiTetsuya · · Score: 1

      I disagree too.

      But i Look weird around all of my friends who run RedHat and Debian systems/based systems when they use foreign words like apt-get and RPM around me.

      --
      Non impediti ratione cogitationus.
    2. Re:I Disagree. by Lord+Kano · · Score: 1

      I have been using linux for 6 years. I started out on Red Hat, I switched to Mandrake and have promarily been a Mandrake user ever since Mandrake 6.0.

      I've dabbled with other Distros like Genoo, Slackware, TurboLinux, and Storm but Mandrake is just what I like.

      Right now I'm running Mandrake 9.1 on an AMD x86 box and a PPC. It's so sweet to have the same configuration for two machines with such different architectures.

      LK

      --
      "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
    3. Re:I Disagree. by Anonymous Coward · · Score: 0

      "I cut my teeth on Mandrake".

      Kind of impossible when all Mandrake consists of are chewy pink sweeties.

      fucking kiddie.

    4. Re:I Disagree. by sp0rk173 · · Score: 1

      Dude, I have fragile teeth, lay off.

      That was, however, the point of my post. Mandrake holds your hand.

  53. Re:Yet Another Distro by kfg · · Score: 1

    Sorry, dont get it.

    Watch more Black Adder.

    KFG

  54. Someone mod the parent up by guacamole · · Score: 0, Offtopic

    it couldn't have been said better.

  55. Am I already running Slack 10.0? by Anonymous Coward · · Score: 1, Interesting

    I'm coming from a Mandrake background, but switched to Slack 9.1 last year.

    I upgraded most of my packages via swaret over the past few days, upgraded to KDE 3.2.3, replaced Xfree86 with X.org, upgraded to Mozilla 1.7 etc. And I updated my kernel to 2.6.7 last week.

    So am I pretty much running Slack 10.0 already, aside from a few minor packages here and there that might need to be upgraded using swaret?

    1. Re:Am I already running Slack 10.0? by SomeOtherGuy · · Score: 1

      If swaret.conf is pointed to CURRENT then yes you are running Slack 10. (VERSION=current)

      Cool hu?

      --
      (+1 Funny) only if I laugh out loud.
    2. Re:Am I already running Slack 10.0? by ghostdancer · · Score: 1

      If you read the ChangeLog, you will notice, there is no change since 22nd June. So, if you have upgraded after 22nd, there is no need to update again.

      However, 'swaret --upgrade' only upgrade the packages that you had already installed. You may need to use 'swaret --install' to install new packages. Read more about it via 'man swaret'.

      --
      I rather be free in hell than a slave in heaven.
  56. Slackware by Anonymous Coward · · Score: 0

    Once you you Slack, You'll never go Back.

    Been running it before 94.

  57. crackhead moderators by adolf · · Score: 0, Flamebait

    Eh?

    Surely, you meant to say "XFree86", and not just "X".

    +5, even. Truly amazing.

    1. Re:crackhead moderators by dancingmad · · Score: 0

      Well OBVIOUSLY I meant XFree86.

      --
      "There is no time, sir, at which ties do not matter," Jeeves, (Jeeves and the Impending Doom)
  58. Why ??? by gorim · · Score: 1


    I am genuinely curious. People are raving
    about slackware but not saying what is so
    great about it.

    This is not a troll, I really sincerely want
    to know. I have no opinion about Slackware,
    its been over 10 years since I used it. It
    gets little press these days compared to Redhat.

    So why would one choose it over the more well
    known distributions ? I might want to check it
    out, but I do want to know whats in it for me
    first.

    1. Re:Why ??? by dangerz · · Score: 2, Insightful

      Stability. It has always been extremely stable for me.

      I also never liked things like 'apt-get' and slackware is mainly gzipped tar. Although there is 'pkgtool', I don't really use it that much. I like configuring, compiling, and installing on my own.

      I guess Slackware just gives admins more 'admin' power, rather than putting it all into a bunch of programs. Use RedHat or Gentoo for a while and you'll forget how many different options you have when configuring or compiling something.

      Consider my opinion biased though, as I have only used Gentoo for a month, the last time I used RedHat I was in junior high, and any other distro I don't even remember.

      --
      The greatest experience we can have is the mysterious.
      - Albert Einstein
    2. Re:Why ??? by Anonymous Coward · · Score: 0

      The main advantages I find are:
      -It doesn't install lots of services just to be helpful (like Mandrake and others do).
      -The minimal install is that, minimal
      -Assumes that you know exactly what you are doing, which is a good thing if you do and a bad thing if you don't.
      -Should you ever need to recompile the kernel or want to add new patches, you get the vanilla kernel, no modifications.
      -swaret seems to resolve dependencies based on the files that are needed, so if I install my own version of "libwhatever" it seems to find that I don't need "libwhatever-1.1" (not too sure about this). That means I can mix compiled + binary packages without any problems
      -A helpful community (unlike some of the BSDs I tried).
      -It is up to date without being bleeding edge

    3. Re:Why ??? by DMadCat · · Score: 1

      Do yourself a favor. It takes literally ten minutes to install. Where words will fail, experience will win the day. When you've become a true believer you can come back and answer your own question.

  59. "Awesome!" say 95% of computer users. by copponex · · Score: 2, Funny

    This is meant to be sarcastic. I know it's not always this bad, but I love playing the Devil's (Microsoft's) Advocate.

    "I bet with Slack 10, I can add my friend's windows printer! Oh... It's okay. I bet my wireless card will work now! Well, shit... my laptop isn't even supported. And I can't even get the sound to work. Oh, alright. Read the manual, huh?"

    The next step is to configure /etc/conf.modules. Make sure that none of the following aliases is commented:

    # alias char-major-14 off
    # alias sound on
    # alias midi off

    Then insert (if not already there) the following lines:

    alias char-major-14 ad1848
    options ad1848 io=0x530 irq=10 dma=1 dma2=0
    post-install ad1848 modprobe "-k" opl3; modprobe "-k" v_midi; modprobe "-k" softoss2
    options opl3 io=0x388

    Furthermore, it might be necessary to configure your pcmcia (/etc/pcmcia/config.opts), because there might be an IRQ conflict. Exclude at least the IRQs 7 and 10. Now you should be ready to boot your new kernel. Good luck!


    "Umm, fuck Linux."

    1. Re:"Awesome!" say 95% of computer users. by Anonymous Coward · · Score: 0

      ... looks like you should try mandrake, or perhaps windows?

      although if you want to setup a kickass server very quickly then even you could probobly get through it.

    2. Re:"Awesome!" say 95% of computer users. by Anonymous Coward · · Score: 0

      "I bet with Windows, I can add my friend's music collection to my playlist! Oh... DRM. I bet I can create a wireless network without an access point! Oh... Need Linux for that. I can't even change the MAC address on my ethernet cards. And my sound card skips and crackles, because it's older and not well supported. Same with my old video card, damn. No solution except to downgrade to Windows 98, huh?
      To install a sound card:

      Plug it in
      Hope it works
      Swear if it doesn't

      Then buy a new card, but be sure to buy a brand name card, or the drivers will suck

      I think I'll write some software!

      Oh, Windows doesn't come with a compiler. But there are free ones available!

      Download mingw32....

      Oh, Windows APIs are partially undocumented and their header files add new functions with each "upgrade" to the operating system, and require "magic" API calls to enable certain functionality.


      "Umm, fuck Windows to hell."

    3. Re:"Awesome!" say 95% of computer users. by nsushkin · · Score: 1
      "I bet with Slack 10, I can add my friend's windows printer! Oh... It's okay. I bet my wireless card will work now! Well, shit... my laptop isn't even supported. And I can't even get the sound to work. Oh, alright. Read the manual, huh?"

      BTW, I just upgraded from 9.1 to 10 on my Thinkpad T41 by running swaret --update && swaret --upgrade. Well, my original Slackware installation wasn't quite "out of the box", but I grabbed a good bag of tricks

      Also, you can print to any windows printer, just use RedMon and CUPS.

    4. Re:"Awesome!" say 95% of computer users. by copponex · · Score: 3, Insightful

      "I bet with Windows, I can add my friend's music collection to my playlist! Oh... DRM."
      If you can't afford the songs, then you don't really want them, do you? Borrow an album, sure, but do you think fair use should really include "permanently borrowing" thousands of songs?

      "I bet I can create a wireless network without an access point! Oh... Need Linux for that."
      Linux and roughly twenty pages of howtos. Which wireless cards work with which distros? Oops, I meant which revisions of which wireless cards works with which distros?

      I really wish I could use some sort of "wizard" in XP to "share" my connection. Oh wait, I can.

      "I can't even change the MAC address on my ethernet cards."
      Gosh, I wish there was an item for around $100 or so that allowed me to "route" all of this "internet" traffic. Guess I'll just have to read the howtos and learn how to use all the unix commands.

      "And my sound card skips and crackles, because it's older and not well supported. Same with my old video card, damn. No solution except to downgrade to Windows 98, huh?"
      I would have tried downloading drivers, but you sound like you've got better ideas.

      "To install a sound card: plug it in, hope it works, swear if it doesn't."
      It sure is easier to look for modules, compile them, and then add them to the kernel, isn't it?

      "Then buy a new card, but be sure to buy a brand name card, or the drivers will suck."
      Gosh, you're right. I've never heard of anyone trying to make sure pieces of hardware worked with linux.

      "I think I'll write some software!"
      I do it every day, honest. Oh wait, I'm 95% of computer users. I don't think I write software, do I?

    5. Re:"Awesome!" say 95% of computer users. by Anonymous Coward · · Score: 0

      I do it every day, honest. Oh wait, I'm 95% of computer users. I don't think I write software, do I?

      Yes, you do. I am suprised you do not remember doing so...

    6. Re:"Awesome!" say 95% of computer users. by Kphrak · · Score: 2, Interesting

      Your points are all perfectly valid. That's why I don't recommend Slackware to the casual user. If you want to see what this whole "compooter" thing is about, run SuSE, Fedora, or (zealots, please have mercy) Windows. :) If you want to have a fairly user-friendly system with minimal viruses and spyware, at low cost, run any of the first two. If you want to get your feet wet, try Knoppix; it doesn't require any drastic alterations to your current system since it's a LiveCD, and it's pretty usable.

      If you're knowledgable about Linux, like a hands-on install where you get to manage your system without those pesky wizards and auto-generators getting in the way, don't mind BSD-style FS layouts, and don't expect everything to be handed to you...for God's sake do yourself a favor and run Slackware. You will thank me later.

      I should mention that I define "later" as "after you manually install your drivers by looking up the names and opts in the kernel docs and uncommenting the requisite rc.modules entries in vi, exclude your PCMCIA IRQs 7 and 10 (your machine will lock up), call the Korean manufacturer of your monitor (your system is down, right? So you have no network) to figure out what to put in the XFree86Config, and add your SMB connector (missing by default) to your CUPS connector list...etc."

      --

      There's no sig like this sig anywhere near this sig, so this must be the sig.
    7. Re:"Awesome!" say 95% of computer users. by Anonymous Coward · · Score: 0

      If you can't afford the songs, then you don't really want them, do you? Borrow an album, sure, but do you think fair use should really include "permanently borrowing" thousands of songs?

      Just like I don't want Ferarri's and beach houses? Borrowing an album isn't possible with most DRM (Apple excluded)

      I really wish I could use some sort of "wizard" in XP to "share" my connection. Oh wait, I can

      Yeah, and let it automatically create a nice subnet for you. Not what you wanted? Broke your existing LAN? Oops, no Internet Connection Sharing.

      I would have tried downloading drivers, but you sound like you've got better ideas.

      When was the last time you tried to get Windows XP drivers for five or six year old hardware that WASN'T made by Intel, Creative Labs, ATI, nVidia, et al? Oh, that's right, five year old computers are disposable garbage that should be replaced with a shiny new Dell every two or three years.

      It sure is easier to look for modules, compile them, and then add them to the kernel, isn't it?

      Better than having to buy a new card for no good reason.

      I do it every day, honest. Oh wait, I'm 95% of computer users. I don't think I write software, do I?

      Okay, I want to write a letter, but all I have is this buggy, insecure email client! I'll buy office... Oh, another buggy, insecure email client! For $300! I want to open a document my friend sent me, but I have an older version of Office!

      Frankly, 95% of computer users probably take their computer to the repair shop for anything more than a new mouse or keyboard. The ones who can only set up Internet Connection Sharing under Windows inevitably don't patch their systems and also leave their $100 Wireless Network Routing Solution wide open. Are you really advocating that it's better for the only software people are able to use to be buggy, insecure, restrictive, and expensive? How about we educate people on how to do things, not make them dumber and more dangerous.

    8. Re:"Awesome!" say 95% of computer users. by copponex · · Score: 1

      Just like I don't want Ferarri's and beach houses?

      Sweet. An argument where Ferrari's = $15! Let me clarify. If something is well within your means, and you don't purchase it, then you don't want it. Let me know if you need further clarification.

      Borrowing an album isn't possible with most DRM.

      Using Windows forces you to buy your music online? I need to check the EULA again. I wonder if they can sue me for using Winamp, iTunes, CDex, or any other program that I use to archive my CDs to mp3 without DRM.

      Yeah, and let it automatically create a nice subnet for you. Not what you wanted? Broke your existing LAN? Oops, no Internet Connection Sharing.

      Every home user has more than one subnet. Honest.

      Oh, that's right, five year old computers are disposable garbage that should be replaced with a shiny new Dell every two or three years.

      They are. You can't even donate them. If you want to waste your time and money trying to save the $150 it costs to buy a used PIII-866, with a 2000 or 98 license on the box, then that's up to you. Don't act like your hobby is a good idea because you like it.

      Better than having to buy a new card for no good reason.

      I've got this toaster that's worth $2. Should I spend four or five hours trying to fix it, or buy the same model brand new for $20, or go to a thrift store and buy a working used toaster for $5?

      Okay, I want to write a letter, but all I have is this buggy, insecure email client! I'll buy office... Oh, another buggy, insecure email client! For $300! I want to open a document my friend sent me, but I have an older version of Office!

      If you're trying to imply that Linux software is less buggy that Microsoft Office, you need to check your head. I use Office Every Goddamn Day. It has never not worked. There are display issues with Microsoft Word, but if that becomes a problem, I could always use OpenOffice.org. On Windows. Without recompiling.

      Are you really advocating that it's better for the only software people are able to use to be buggy, insecure, restrictive, and expensive? How about we educate people on how to do things, not make them dumber and more dangerous.

      I understand how you think, but you have to remember, you live in a world of computers. To you, having something not work exactly the right way is a disaster. To 99% of the rest of the world, we plainly don't care. If our computers catch fire and melt, we can still go home and garden, or ride our bike, or, god forbid, even watch TV. (I love the Daily Show). We want to get the maximum amount of work done with the minimum amount of time wasted to get our computers to work.

      Don't fight this. Embrace it. It doesn't make sense to have everyone learn about computers, because too many other areas suffer as a result. Do you know exactly how your car works? How about your air conditioner? How about your plumbing?

      Windows is $90, or roughly two dinners for two people. It's affordable. It's not restrictive. It works.

  60. I'll break it down for you... by Anonymous Coward · · Score: 0

    Just what Linux needs... Yet Another Distro

    Notice his use of a "Yet Another..." acroynm template? Kinda suggests that the guy's familiar with the culture, doesn't it? Also, considering it's release 10, we all realize that it's hardly something new.

    Please, keep these garage basement projects out of the news... we already have enough distros. Thanks.

    Linux' reputation for being a "garage basement project" was shed years ago. Slackware is one of the oldest distros around; this is generally understood knowledge. Notice he refers to "we", as in "the Linux community, of which, I'm a member?".

    God, some of you Johnny-come-lately kids are dense...

  61. Slackware 10 is out, Cant Wait by AcidFnTonic · · Score: 1

    Wow I been waiting quite some time for Slackware 10 to be released... Been with it since kernel 2.2.* Its the only distro where I reboot only to upgrade. There went my ~9 month uptime

    --
    Sometimes the majority just means all the morons are on the same side.
  62. Re:Slackware's time has passed by Anonymous Coward · · Score: 2, Insightful

    So why does it have the most posts at LinuxQuestions? Why was it voted best distro in last years LinuxQuestions awards? Why, after 10 years, has Slack survived when countless other distros have failed? Why is Slackware looked to for being secure, stable, and a great way to learn Linux? Sounds like a lot for a distro that is "no longer wanted". I don't know what Linux community you're part of, but most of us respect and enjoy Slackware.

  63. Re:Slackware's time has passed by atomic-penguin · · Score: 1

    ...their distribution is no longer needed or wanted by the linux community...

    Who made you spokesperson for the linux community? ...debian is perfectly suited for those who want the absolutly most "stable" release...

    When you say absolutely most "stable", you meant to say least innovative right?

    --
    /^([Ss]ame [Bb]at (time, |channel.)){2}$/
  64. Okay by Anonymous Coward · · Score: 0

    But that's an external add-on, it isn't integrated, is it?

    1. Re:Okay by notanatheist · · Score: 1

      Not yet. Swaret does rock though. The only thing needed now is the package selection that Gentoo and/or Debian have to offer and I'd even leave Gentoo behind.

  65. Re:Yet Another Distro by 13Echo · · Score: 1

    You do know that RedHat (and virtually everything else) was based on that "garage basement project", right?

    There are reasons why Slackware is so legendary, and has always been a profitable project for the one-man operation.

  66. Bad binaries support by Via_Patrino · · Score: 3, Interesting

    Slackware is a nice distribution, its easy to understand its package system for example. But it has bad binaries/package support.

    You can live happily with it if all packages you need are in the distro, which include all packages needed for servers and small offices machines, but it can be a nightmare if youre a home user.

    Slackware is a "one man" distribution, the reason for that is its low number of official packages.

    And if you need some other software outside of that its better you compile all yourself or youll be in a jungle of amateur made packages.

    People with different software and hardware configurations generating packages and spreading it around.

    That lead to missing libraries messages (even when you have them), missing new versions of libraries that are on the official distro (but not yet updated), complaints about not finding your remote control (even when you dont have one), binaries compiled with strange options (some missing other unuseful) and so on.

    A slackware zealot may say "compile your own", but sometimes you cant, because of time restrictions, or just dont want to waste a lot of time compiling a "one task application" and its dependencies.

    And in that situations youre SOL in the jungle, and is not a good experience at all.

    1. Re:Bad binaries support by erikharrison · · Score: 2, Informative

      That's what linuxpackages.net is for. It's an independent location for slack packages.

    2. Re:Bad binaries support by Via_Patrino · · Score: 1

      Thata an example of amateur packaging (not compling with the official rules), a search for xmule leads to: xmule-1.8.2-i686-1orb.tgz

      i686 ? What about the rest of us (i586)?

      The author of that package made just 5 packages and joined on April of 2004? Is it an experienced user?

      He didnt packaged any of the xmule dependecies.

      The package is rated 2 of 3.

      I tried and it seens anyone can post a package there without previous checking.

      Thats what I call amateur.

    3. Re:Bad binaries support by Xpilot · · Score: 1

      And if you need some other software outside of that its better you compile all yourself or youll be in a jungle of amateur made packages.

      I learned a lot by compiling my own packages. As for the "jungle of amateur made packages", that goes for Redhat too hmm?

      --
      "Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." -- Linus Torvalds
    4. Re:Bad binaries support by broxys · · Score: 0

      The lack of binaries can be startling, I'll admit. But really it's not so hard to port binaries over (especially from RedHat) usign the rpm2targz scripts. I've ported many packages than I couldn't find as a .tgz from rpms with minimal directory changes. just another opinion .oliver

    5. Re:Bad binaries support by evilviper · · Score: 2, Insightful


      And if you need some other software outside of that its better you compile all yourself or youll be in a jungle of amateur made packages.

      That's what I love most about Slackware... It's about the only Linux distro left where you can mix source and packages. All slackware packages have the devel stuff, not just the binaries, so you don't have to jump through extra hoops to get the -dev packages like with all other distros.

      The Slackware package manager doesn't screw with you on dependencies either. If you want to install a package of XMMS, and you installed libmp3 from source, it won't stop you from installing XMMS just because it didn't detect the libmp3 package as installed.

      It may sound trivial when you are just reading it, but it can be a massive pain in the ass. With RedHat or something else, a certain package doesn't work on your system, so you have to install from source. Then it won't let you install anything depending on that library you compiled. Even if you force it to do so with --nodeps, it might install the first package that depends on the lib, but when you install another package that depends on that package, which in-turn depends on that lib, you're usually just screwed, and no combination of switches to RPM will work.

      complaints about not finding your remote control (even when you dont have one)

      You can't blame slackware (or unprofessional packagers) for this problem. It is an inherent limitation of binary packages. Functionality like LIRC must either be compiled in (in which case you must have the LIRC libs), or it must not be compiled in (in which case you can't get your remote working if you have one).

      The solutions to that problem are all unpleasant.

      Have hundreds of different packages for each program, all with different options compiled-in, and different dependencies.

      Have programs statically linked, so you have all the libs built-in, and the binary is huge and wastes lots of memory.

      Compile with the lowest-common-denominator options, which gives you absolutely bare-minimum functionality, and many people will have to compile their own.

      Compile with the most popular options, in which case some people need to install more libs than they have or want, and others need to compile their own to get more features added in.

      Frankly, with applications that have various dependencies, you're just best off compiling from source. No package manager can fix these problems.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    6. Re:Bad binaries support by Anonymous Coward · · Score: 0

      And on the flip side, if all you know how to use is binary packages, you get a situation that I observed many months ago....

      Sitting at my lab machine at the uni and noticing another user muttering, I asked what was up. The user then complained that since he was running an unsupported version of RedHat, he couldn't find an RPM of the latest version of OpenSSH. No sweat, I said, just grab the source and make your own RPM. The other user then looked at me like I'd sprouted horns then complained about compiling causing issues. I tried for a few more minutes to explain I didn't mean "make install", but instead to create an RPM and then upgrade the RPM. Finding him being completely unresponsive, I left him to his web searching for the fabled RPM and returned to my workstation.

      Then I realized that my OpenSSH version was a bit stale. No biggie, I have a slack build script already set up for that package as I upgrade it often enough. So, downloaded the source, verified the md5sum, plopped the tarball over in the appropriate directory, fired up the slack build script, waited for the compile, used upgradepkg and restarted the SSHD service. Took all of 10-15 minutes.

      Most humorously, after all this, I looked back at the poor RedHat user and he was still fruitlessly searching for an RPM.

    7. Re:Bad binaries support by Cro+Magnon · · Score: 1

      It's true that Slack has fewer packages than other distros, but I haven't had much problem. When I started with Slack 7.0, there were quite a few packages I had to compile from source, but they weren't difficult, and unlike RH, I didn't have to worry about messing up an RPM database. Each new version of Slack added some of the missing software, and right now, the only thing I've compiled from source is the kernel.

      I do have one complaint. I wish Slack had gnucash. That's the only package I'd like to have that I can't compile myself.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  67. a few days... ah yes, the good ol' days by ChipMonk · · Score: 4, Interesting

    Time was, this was real. I had The Linux Bible, which had an old Slackware based on kernel 1.2.13. I took notes for 3 hours before I ever did a thing with the CD. One week later, I was online. No GUI yet, so Lynx was my friend. Another week to get XFree86 up and running (I learned more about video timing than I ever wanted). Two more days, and I had Netscape loaded and running. That's when I knew I had taken the first steps of that fateful journey...

    1. Re:a few days... ah yes, the good ol' days by Bandman · · Score: 5, Funny

      I'm with you. Ya just haven't lived till you've entered modelines by hand, I tell ya.

      Kids today, what with their XVGA setup programs, and their live CDs.

      GET OUT OF MY YARD

    2. Re:a few days... ah yes, the good ol' days by stor · · Score: 1

      Ya just haven't lived till you've entered modelines by hand, I tell ya. ...on a no-name/rebadged fixed-frequency monitor.

      Sometimes you needed to open the monitor to find out who *really* built it.

      And we didn't even have Google back then. We were searching for model numbers in AltaVista.

      The Horror! The Horror!

      Cheers
      Stor

      --
      "Yeah well there's a lot of stuff that should be, but isn't"
    3. Re:a few days... ah yes, the good ol' days by Anonymous Coward · · Score: 0

      Ya just haven't lived till you've entered modelines by hand, I tell ya.

      Pffft, you havn't lived until you've written your own RAMDAC PLL clock calculator for a video driver.

    4. Re:a few days... ah yes, the good ol' days by Anonymous Coward · · Score: 0

      I didn't know anything about Unix when I started with slackware oh so long ago.

      I had to learn vi before I could edit the modelines.
      That took a while. Also made me fall in love with the stupid editor.

      And now you throw a redhat/suse/knoppix.... cd at a computer and it just kinda picks itself up and crawls into the harddrive.

      It's all too easy

  68. Re:distribution based on slackware still using xfr by Via_Patrino · · Score: 1

    Maybe because they couldnt base on something that didnt exist yet (slackware 10) but on the now old slackware 9.1

  69. Re: Torrents directory layout a bit weird by pavon · · Score: 1
    This may be an artifact of linux, as I've noticed it before with a few pieces of code I wrote where a directory already existed, and it created another with the same name under it.

    Hmm, interesting. One gotcha that you need to keep your eye open for is the ending "/". For example, if you say:
    mv dir1 dir2
    it will rename dir1 to dir2, overwriting the contents of dir2 if files of the same name already exist. But if you say:
    mv dir1 dir2/
    it will move dir1 into dir2, as a subdirectory.

    Don't know if that was the case, but thought I'd mention it.
    Cheers!
  70. Re:Yet Another Distro by bender647 · · Score: 1

    Yet Another Distro? At version 10? Think before you post man. Of course many of us remember when Slack jumped from like version 4 to version 7 in one release. I think it was an effort to deal with people who thought that Redhat versions = official Linux version and Slack wasn't keeping up :)

  71. Yes, not for everyone... by Anonymous Coward · · Score: 0

    And I don't just mean n00bs. For example, admins who oversee 100's of servers and workstations...

    I'm sure it's satisfying to manually update your personal machine at home, but in a fast-paced production environment, that just won't fly.

    1. Re:Yes, not for everyone... by Anonymous Coward · · Score: 0

      that's why slack is so admired, it's meant to be a home distro, where everything is meant to be edited by the user

      it's so beautiful...

  72. It's possible to do both! by Anonymous Coward · · Score: 0

    Provided you are a member of the BDSM community.

    1. Re:It's possible to do both! by Anonymous Coward · · Score: 0

      Not if you wish to be safe, sane and consensual.

  73. Re:Yet Another dumbaxx by dokterneo · · Score: 1

    hey Goofy, I don't know how long you've been using linux, but you are way off on the whole another distro bit. Slackware is one first distros created, geez, do your homework. Garage basement project? are you 12 or something?

  74. gentoo! by IshanCaspian · · Score: 1

    I've been using Gentoo for a year now, and I've never had the problem you described...Gentoo's portage always figures out exactly which packages need updating and takes care of it. It's even possible to update a library, such as some of the cryptography ones, and then rebuild everything that statically linked against it.

    --

    But there is another kind of evil that we must fear most... and that is the indifference of good men.
    1. Re:gentoo! by bcrowell · · Score: 1

      It's even possible to update a library, such as some of the cryptography ones, and then rebuild everything that statically linked against it.
      It's also possible under FreeBSD (using portupgrade), but my experience is that it generally results in a completely broken system.

  75. Re: Torrents directory layout a bit weird by treat · · Score: 1
    You are wrong.

    $ mkdir foo bar
    $ touch foo/a
    $ echo hi > foo/a
    $ echo bye > bar/a
    $ mv foo bar
    $ ls bar
    a foo
    $ cat bar/a
    bye
    $ cat bar/foo/a
    hi
  76. Re:Yet Another Distro by johnnyb · · Score: 0, Offtopic

    Slackware is what taught me about open-source and free software. I've been trying to teach others about it ever since. Somehow the concept of sharing has gotten so lost in the Christian community that it's taken a atheist to remind us what it is.

  77. It works alright by tarballedtux · · Score: 5, Informative

    I've using a 9600XT with X.Org 6.7.0 and the ATI binary driver 3.7.6 (3.9.0 was making mplayer crash or at least refuse to do usual operations). I'd say it works well. If only ATI could beef up there Alternative OS drivers it could be alot better.

    --tarballedtux

    1. Re:It works alright by Anonymous Coward · · Score: 0

      That's probably because you're using Xv (mplayer -vo xv). I've been using mplayer -vo xvidix instead. Xine has a xvidix output driver too. (xividix uses the XVIDEO extension)

      I've heard that Xv is b0rked in Xorg and XFree86 4.4.0. Apparantly they b0rked it with a nVidia bugfix. But yeah, it could be an ATI driver bug.

  78. OT: Does It Work With A DVI FLat Panel? by reallocate · · Score: 1

    This is a bit OT, but I've been staying current with Slackware until a few days ago: I bought a flat panel LCD monitor to use with my Matrox G550. Unfortunately, Slack, or, rather, Xorg's X11, can't drive the DVI output. Analog works, but the image is decidedly worse.

    Anyone know if DVI and X11 can be happy together?

    --
    -- Slashdot: When Public Access TV Says "No"
  79. Exactly... by Anonymous Coward · · Score: 0

    That's why I don't even deploy other people's software. I hand code everything from scratch myself. 'gives me more control and a better idea of what's going on. In fact, I don't even use calculators, levers, or wheels. These "tools" are merely hallmark of the lazy/incompetent/overworked.

  80. Re:Yet Another Distro by bigberk · · Score: 5, Insightful
    Yep, that's right, the distrobution that was out before kernel 1.0 is now considered Yet Another Distro.
    Another interesting angle about Slackware is that it has been profitable for some time. Pat does a lot of the work himself, and his small team helps him with CD orders etc. Much of the testing is community volunteer work, of course. RedHat might have 1,000 employees doing what Pat+friends can accomplish. Hey, here's an article on ten years of Slackware

    After trying many different distributions I have settled on Slackware. The BSD-style configuration is, I find, straightforward and powerful (even though I wasn't a BSD user before Linux). Slackware does not impose specific configuration styles, layouts, interfaces or layers on you and I enjoy the resulting flexibility and freedom. I like the "EZ" .tgz packages. You either use the slackware packages, or compile from source (I use a hybrid approach). I have NOT found RPM or FreeBSD ports to be particularly more convenient. Sorry, but it's true.

    Security notices are rapid, accurate, and to the point thanks to Pat himself. Things in the Slackware installation work properly, without embarassing-looking glitches. It is intelligently put together, and tested to perfection.

    Overall the distro is the lean and the easiest to tweak in the least amount of time. I personally found it the easiest to install of all Linux distros. Slackware is a winner.
  81. Really? by nate+nice · · Score: 1

    "Of course, the non-cheapskates among us should go buy the CD-set to support the project."

    Actually, that's why it's called "Free Software".

    OK, that's a troll. Go ahead and send them a few dollars if you enjoy using their distribution. You only help yourself when you do this.

    --
    "If you are a dreamer, a wisher, a liar, A hope-er, a pray-er, a magic bean buyer ..."
  82. Re:Yet Another Distro by Anonymous Coward · · Score: 0

    Yep, cause nobody knows how to share execpt Christians. All other people are shelfish assholes.

  83. Re:Slackware's time has passed by Anonymous Coward · · Score: 1, Informative

    The problem with Debian, is that they wait for to damn long to add updated packages to their distro... Slack incorporates packages at a much faster rate...

    Not only that, but Debians main advantage, apt-get, now has a Slackware equivalent.. swaret

    GO SLACK!

  84. Dude, you're a riot... by Anonymous Coward · · Score: 0

    Seriously, man.... it's a shame you have to go AC as often as you do because so many mods have undergone humor bypass surgery.

    1. Re:Dude, you're a riot... by kfg · · Score: 1

      By wearing my tinfoil hat too tight I missed my chance to have a coveted low ID# and posted AC for quite some time. Perhaps years, I'm not sure. Since loosening my hat and registering I do not recall ever posting as an AC. Maaaaaaaybe I did once when the option was first introduced to see how it worked. I'm not sure about that either.

      Oh, wait. I remember posting as an AC not too long ago as part of a joke about posting as an AC.

      I signed it.

      I stand behind every pointless, brain dead, trollish and offtopic post I write, and with only one or two rare exceptions, so does my karma.

      KFG

    2. Re:Dude, you're a riot... by kfg · · Score: 1

      Oh, wait. I remember posting as an AC not too long ago

      Oh, wait. I now remember that the joke was that I "forgot" to hit the Post Anonymously button, so I didn't actually make the post as an AC after all.

      KFG

    3. Re:Dude, you're a riot... by Anonymous Coward · · Score: 0

      well my uid is so low that even comparing it to any other uid returns null. at least i think that's how it works.

    4. Re:Dude, you're a riot... by Anonymous Coward · · Score: 0

      now that i think of it, with such a low uid, why hasn't my karma improved by now? all my posts always start out at zero. it must be all those racist first posts that someone else with access to my account keeps posting. i wonder how they got access to my account...

  85. Re:Yet Another Distro by Anonymous Coward · · Score: 0

    It is pronounced "BOB"

  86. Re:Yet Another Distro by Anonymous Coward · · Score: 0

    It prefers to go by "ROBERT"

  87. Question About Gnome/KDE Programs by Anonymous Coward · · Score: 0

    From the release announcement...

    GNOME 2.6.1 (including a collection of pre-
    compiled GNOME applications)

    Are they saying they have made some of the GNOME
    apps available as statically linked executables
    so that I don't have install all the GTK/GNOME
    libs? If so, all I can say is ye-ha!! Maybe it's
    just me but I have a heck of a time finding
    people and projects in the GNOME/KDE communities
    that realase dynamic AND static verions of their
    programs. I don't use either KDE or GNOME but
    I occassionaly have use for a "GNOME" app or a
    "KDE" app but I don't want to have to install
    a "desktop" environment just to use the app. I
    hope people in the GNOME and KDE communities
    start releasing static versions of their
    executables. It's would be very useful to some
    of us.

  88. old skool by theCat · · Score: 1, Insightful

    Hey, my first linux distro back in around '98 was Slack, downloaded and copied to a whole box of floppy diskettes over a 28.8 modem! The installer was the same one as recent distros (haven't seen 10 yet) and was a pain to run, and of course you had to feed it all those diskettes, but I got it working on an old AMD boxen I'd built from spare parts.

    I ran across the diskettes recently while cleaning up the garage, but the irony is that none of my current systems seem to have floppy drives any more.

    Sadly, I think I tossed the diskettes out.

    And in the end, have our systems really improved that much over the years? You would think so. But I look back and I'm not so sure. Even back then, there was so much to work with.

    --
    =^..^= all your rodent are belong to us
    1. Re:old skool by Anonymous Coward · · Score: 0

      28.8 modems and floppy installs in '98 ?????

      What the hell are you blathering about?

    2. Re:old skool by evilviper · · Score: 2, Insightful
      my first linux distro back in around '98 was Slack, downloaded and copied to a whole box of floppy diskettes over a 28.8 modem!

      Okay, but why? In '98, I had an inexpensive 4X CD Burner ($200, IIRC), and 56K modems were old news already.

      Sorry, but this is a poor excuse for a euphoric story... I hear almost the same story from people who were doing the same back when floppies weren't what they are now, and 28.8 modems were a distant fantasy, yet slackware was already around...

      And in the end, have our systems really improved that much over the years?

      Oooooo, a whole 6 years. Surely we should have 3-D computer interfaces, and flying cars by now...

      Come now, I could tell you the stories of installing Slackware, XF86, and GNOME on my 486/33 with 4MB of RAM, etc.

      In reality, our computers haven't changed more than a little from way back in the 486 days. In the 386 days, PCI was just comming in to use, and in the 486 days ISA was practically gone. The only thing that's really changed is that an AGP port was added, while PCI ports are still there.

      AT cases were the thing, although current ATX cases have practically no changes vs. AT. Power supplies still have an 80mm fan in them, and mount in the top back of the tower. The motherboard mounts to the inside of the case, the CPU has a heatsink and fan on it. All the cards mount in the bottom back of the case, plug into PCI slots. 5.25 and 3.5 inch drives still mount in the front of the case, and plug-in via good old IDE ribbon cables.

      Almost nothing has changed since the 486, which is a lot longer than 6 years ago.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    3. Re:old skool by Enucite · · Score: 2, Insightful

      Okay, but why? In '98, I had an inexpensive 4X CD Burner ($200, IIRC)

      Well, that 'inexpensive' CD Burner probably cost you at least $400 if you got it even near the end of '98. CDW Dec. 1998 It wasn't until close to 2000 that they got under $200
      I remember I spent over $250 on my first burner, (4x Plextor) in late '99.

      and 56K modems were old news already.
      Believe it or not--for those of us who weren't living in a large city--in '98, 56K was still the fastest we could connect.

      I remember staying after school my senior year (98) in high school to use the "fast" connection to download Linux isos at ~50KBps and burn them on the "fast" 2x burner they just got in the computer lab.

      in the 486 days ISA was practically gone
      As long as by "practically gone" you mean "the standard". Hell, even my Pentium systems had more ISA ports than PCI, most didn't even have a PCI device installed. It wasn't until the P2 that PCI cards started becoming the standard.

    4. Re:old skool by Anonymous Coward · · Score: 0
      working on an old AMD boxen

      Dude, "boxen" is supposed to be plural:

      ox -> oxen
      box -> boxen

      If you're going to use the lingo, try and use it right, otherwise you come off as a poser.

    5. Re:old skool by Anonymous Coward · · Score: 0

      Dude, boxen isn't a word, singular or plural.

      ox --> oxen
      box --> boxes

      If you're going to speak English, do it right, otherwise you come off as an idiot.

    6. Re:old skool by evilviper · · Score: 1
      CDW Dec. 1998 It wasn't until close to 2000 that they got under $200

      Oh no! One single site listed them at higher prices than elsewhere... Shucks.

      Even if they were the site with the lowest prices in the world (that's a laugh), and had all the cheapest brands of CD-Bruners, that still wouldn't count in-store sales, mail-in rebates, etc.

      It also doesn't mention that 2X and 1X CD Burners were much cheaper as well, so quite a lot of people had CD-Recorders already.

      Believe it or not--for those of us who weren't living in a large city--in '98, 56K was still the fastest we could connect.

      56K is just fine... But this guy is saying that he was still connecting at 28.8 for some reason. That may be the case, but only because he didn't want to spend $30 for a faster modem... Hardly a hard luck story.

      in the 486 days ISA was practically gone
      As long as by "practically gone" you mean "the standard". Hell, even my Pentium systems had more ISA ports than PCI,

      Well, either you had several of the most unusual systems on the planet, or your memory is just wrong...

      I've still got several very early Pentium systems around here, and they have 4 PCI, and 2 ISA, and I never used the ISA slots. If you didn't get PCI slots until P2s came out, you had the most freakish Pentium motherboard around. I can't remember ever seeing a Pentium mobo without PCI slots. By P2, the transition was long over, an ISA was nowhere to be found.

      I don't have my old 486 around any more, but I know it had 50% PCI slots, and since I have worked on hundreds of computers around that time, I know that PCI slots were already fairly common.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    7. Re:old skool by Enucite · · Score: 1

      I still stand by my original comment.

  89. Re:grass is always greener - Swaret baby by teslatug · · Score: 1

    Get yourself Swaret and you're set.

  90. Re:OT: Does It Work With A DVI FLat Panel? by Anonymous Coward · · Score: 0

    You might try running "X -scanpci" to see if the video card implements the DVI output as a separate virtual adapter. If so, you will see multiple video adapters, differentiated by their BusID field. If that's the case, you probably just need to try those other values in BusID in your XF86Config until one drives the monitor.

  91. As a recent slack user: by JoeShmoe950 · · Score: 3, Interesting

    I'd tried Debian, Mandrake, and a few minor distro's. I don't know why everyone says that slack is hard to configure. Atleast in the newer versions , it isn't. I installed slack 9.1 I think it was. It went without a hitch, not at all confusing compared to debian, although a graphical install would have been nice for anyone new. It finished the install and then restarted. I typed startx. On most computers, it would have been fine. I looked in the file and it was configured, except for my integrated graphics, which I no longer used (put in a GeForce but never disabled integrated). I changed that one line in the file to NV, and X worked. Network worked, CDRoms worked, etc. I don't get why people say its hard to install. Although nongraphical, the install is still menu driven and straight forwards. The configuration is minimal, and its fast and rock solid. I never looked back after that. Swaret works great, and for things not in a slack package, they will usually compile perfectly. GO SLACK!

  92. Buy the CD folks... by linuxhansl · · Score: 2, Insightful

    support Patrick's effort...

    I was using Slackware from its inception in 1993 (ahhh... I remember downloading a large set of floppy images over night at work from my Ultrix machine, storing the "large" files on my DEC/VMS diskspace).
    After a long digression over FreeBSD, RedHat, I came back to Slackware last year...
    I already ordered the CD, not that I couldn't download the iso's but this a great distribution and if I can help to keep it going I'll do so.

    1. Re:Buy the CD folks... by PrimeNumber · · Score: 1

      Exactly...or buy a cap (like I did a couple of weeks ago) T-shirt, etc from the Slackware store if you absolutely have to download the image today and cant wait.

      Give back to slack. :)

    2. Re:Buy the CD folks... by Cro+Magnon · · Score: 1

      Agreed! I've already used swaret to upgrade to 10.0-RC2, and I'll upgrade to the release when I get home, but I'm also a Slack subscriber, and looking forward to that nice, shiny CD even if I don't really need it.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  93. Yeah by copponex · · Score: 1

    Nothing gets my 6 month old emachines m6805 to work. Gentoo can get everything but the wireless card, which doesn't work on any distro. But who really ever wanted to waste 6 hours of their life installing it?

    Linux is great for server stuff, but still sucks for the average user. All 200 million of them.

  94. The faster everyone gets away from X the better. by Anonymous Coward · · Score: 0

    He knows what he's saying...

  95. Priority!! Ftp Install Please... by Anonymous Coward · · Score: 0

    When is Slackware going to "officially" support
    and FTP install option? I know there are a
    couple of unofficial hacks to do it but it
    would be nice to see it cleanly integrated with
    the rest of the official install options.

  96. Slackware X... by Anonymous+Writer · · Score: 0

    ... you know, like OS X <ducking>

  97. AMD64 ISOs anyone? by Black+Acid · · Score: 1

    Is there an AMD64 architecture ISO of Slackware 10.0 available?

    1. Re:AMD64 ISOs anyone? by mjuarez · · Score: 1

      I'm also waiting for this. If enough of us pester Patrick about it, he just might consider an AMD64 distribution in the future. Maybe at 11.0?

    2. Re:AMD64 ISOs anyone? by crache · · Score: 1

      You forget that this would require him to own an amd64 machine to compile it on. Who's going to buy him one?

    3. Re:AMD64 ISOs anyone? by Freon115 · · Score: 1

      I too wish there was a AMD64 version.
      I've been using slackware a bit, but when I got an AMD64, I couldn't get the 64 bit NVIDIA drivers (not my fault, they know it's bugged ;)).

      So I have to use Mandrake 10 now :(

      I know there won't be an AMD64 version before long, but I'd like a little guide on how to build slackware from the source to get it work fully on a 64 bit CPU.
      Anybody can help me here?

  98. Re:Slackware's time has passed by harikiri · · Score: 1

    Nah, the oldest! (ducks)

    --
    Man watching 6 MSCE's around a sun box, looks alot like the opening scene's of 2001:space odyssey...
  99. MOD PARENT UP by Anonymous Coward · · Score: 0

    and make the grandparent explain himself!!!!!one

  100. Re:CNN Reports death of Bob Bemer by Anonymous Coward · · Score: 0

    Truly an American icon.

  101. Re: Not Another Distro by Anonymous Coward · · Score: 0

    Not another spaceship!

  102. why I love Slack! by JooBYE · · Score: 0

    Simple, stable, and old school...

    Slackware user since 3.4
    Keep up the great work Patrick!

  103. Re:OT: Does It Work With A DVI FLat Panel? by Anonymous Coward · · Score: 0

    ?!?!? In Windows, it just works...

    Why does it take a nuclear scientist just to get DVI output on Linux?!?!?

    Does noone see a problem with this?

  104. Wallstreet's great by green+pizza · · Score: 1

    My last techie girlfriend owned a Wallstreet model Powerbook *shudder*

    I know several people that still use their Wallstreet PowerBook G3s, mostly writers. Those machines came in 9 flavors: 233 MHz, 266 MHz, 300 MHz; 12", 13", 14" LCD. Ability to use two batteries. Thicker and heavier duty than the Lombard and Pismo PowerBook G3s. Awesome keyboard. Dedicated MPEG-2 DVD decoder available on a CardBus card.

    It's a time machine, though, I think Wallstreet/Mainstreet came out in 1998. Most of the folks that I know who still use theirs have stuck with Mac OS 8.6, 9.1, or 9.2.2. They generally use MS Office 1998 or 2001 (or Nisus Writer). For that, it works great.

    OS X 10.3 is awesome, but you really need a Pismo PowerBook G3 to get good performance.... 400 MHz G3 and Rage128 graphics (plus USB and Firewire) makes for a good OS X experience. Actually, I don't think 10.3 will install on a Wallstreet anymore, at least not without using Xpostfacto to help start the install. Which is sad and odd, considering that 10.3 runs much faster than 10.1 or 10.2.... even (or especially) when using an oldschool CRT iMac.

    1. Re:Wallstreet's great by Anonymous Coward · · Score: 0

      "OS X 10.3 is awesome, but you really need a Pismo PowerBook G3 to get good performance.... 400 MHz G3 and Rage128 graphics (plus USB and Firewire) makes for a good OS X experience."

      HA HA. Good one.

      I have a pismo 500Mhz w/ rage128 graphics and OSX 1.3 is aggrivatingly slow, but not unusable. Certainly not something I'd use as my daily machine.

  105. Swaret by Anonymous Coward · · Score: 0

    Let swaret handle all your downloading and updating of your slackware packages - it even has dependency checking (but no forced dependency installs => no dependency hell). I've kept my initial 9.1 install updated to -current for the past six months and it's worked flawlessly, and now I've just upgraded to 10.0 using swaret. Check it out!

  106. In other news... by generationxyu · · Score: 2, Informative
    Slackintosh is dead as of today. Slackintosh was a port of Slackware to the PPC, specifically Macs, by simply recompiling Slack packages from source.

    If anyone is interested in taking this project, I would love to help. I don't have the webspace, but I'm willing to do the porting, and get Slack 10 into PPC form. If you're interested email me: jlongs2@SLACKuic.edu minus distro.

    --
    I mod down pyramid schemes in sigs.
  107. burning the ISO while torrents are open? by notanatheist · · Score: 1

    Is it safe to burn the ISO while people are still pulling them from me?

    1. Re:burning the ISO while torrents are open? by Anonymous Coward · · Score: 0

      Yep. Once at 100% BT closes write access.

    2. Re:burning the ISO while torrents are open? by jeffcm · · Score: 1

      Of course, once BitTorrent finishes the download, it only reads the files, and doesn't write.

  108. I'm a slackware believer by Anonymous Coward · · Score: 0

    I'm a linux newbie. I just had my third go (in 4 years) at entering the linux experience.
    Redhat config was a pain in my ass.
    Fedora 1 installed no prob but fedora 2 locked every time. Did alot of research. Never found out why.
    Then my friend gives me a copy of slackware.
    EZ install and EZ config. Everything is just working. It's bizarre.

  109. CD's? I remember a pile of floppies by dhartman · · Score: 1
    Who started with cd's? I remember downloading my very first installation of slackware (3.0 I believe) on a pile of floppy disks in the college computer lab (Sun IPX's). Two disks to boot, A, AP...each one of those groups used to be divided up by floppy disk sizes (A1, A2, A3...AP1...) I also could have sworn that Mosaic was included in way back then and not Netscrape, but I could be wrong (hell it's been almost 10 years).

    I do have the original book someplace. All I can say is I've tried Redhat a few times but always found myself coming back to what just plain works! Slackers forever!

  110. Quick question... by Anonymous Coward · · Score: 0

    This is something that wasn't answered in the release of 10.0 Community Edition, and I think it's kind of major. Simply put, installing the Community Edition changes things in one's MBR when it tries to install a bootloader in the MBR of /hda (no confirm dialog at all, it just does it). You can make changes to the bootloader options AFTER it changes the MBR, but these changes cause Windows XP to blackscreen, and are a major pain in the ass to fix, if at all. Using sfdisk doesn't work. Using DISKPART doesn't work. Using anything other than a complete format of the NTFS partition will not work. Be sure to back up your data. I really hope the installer fixed this, but you never know.

    This link at LinuxQuestions addresses this problem in more detail.

    1. Re:Quick question... by Anonymous Coward · · Score: 0

      WTF does this have to do with Slackware?

      Slackware doesn't have a "Community Edition".

  111. Re:CD's? I remember a pile of floppies by ChipMonk · · Score: 1

    I lucked out. The only floppies I had to deal with were the boot and root. Getting the images written to the floppies was half the battle for a base install! (Remember, this was in the days of Windows 95.)

  112. Rsync 9.1 Isos on Windows? by black88 · · Score: 0

    Hello, I know there is a Win32 version of rsync, but have forgotten what I need to do. So I need to rip the cds to isos, then what? Anyone care to elaborate and/or help?

  113. But it *is* bleeding edge by Baki · · Score: 1

    Just look at the version numbers and you see that it has the latest official release of almost anything, and usually a newer version than other current distributions.

    There used to be a time, some years ago, that Slackware was stable but conservative w.r.t. package versions. Nowadays, it is stable and still has the latest and greatest.

  114. Only 7 more days to use my June bandwidth... by privaria · · Score: 1

    file: slackware-10.0-iso
    size: 682,819,837 (651.2 MB)
    dest: /usr/download/slackware-10.0-iso
    status: finishing in 2:48:57 (2.4%)
    speed: 85.4 KB/s down - 230.5 KB/s up
    totals: 15.5 MB down - 34.0 MB up

    1. Re:Only 7 more days to use my June bandwidth... by linuxelf · · Score: 1
      My DSL must just suck. This is about all I ever get from a torrent. I get 100k from FTPs and HTTPs fairly regularly, but not from torrents. I wonder if there's some sort of throttle because I'm uploading simultaneously.
      file: slackware-10.0-iso
      size: 682,819,837 (651.2 MB)
      dest: /vol2/BitTorrent/slackware-10.0-iso
      status: finishing in 12:20:30 (2.4%)
      speed: 25.5 KB/s down - 24.9 KB/s up
      totals: 15.8 MB down - 17.9 MB up
      --
      - "That's just the kind of fuzzy-headed liberal thinking that leads to being eaten."
    2. Re:Only 7 more days to use my June bandwidth... by MCZapf · · Score: 1

      If you are behind NAT or a firewall, make sure you open up the correct port to the outside, so that other clients can connect to you. This should improve things a lot. If you're already doing that, maybe you should try throttling your upload a little bit (I think it's a commandline option).

    3. Re:Only 7 more days to use my June bandwidth... by linuxelf · · Score: 1

      Yeah, I'm allowing the ports through... I think you're on the right track about throttling uploads. I believe if my upload rate is too high, it kills my download. Although, looking at it now, I'm getting far better transfer than I've ever gotten via BitTorrent, I'm up to like 75k/sec. I certainly can't complain about that. Don't know why it's been much slower in the past.

      --
      - "That's just the kind of fuzzy-headed liberal thinking that leads to being eaten."
    4. Re:Only 7 more days to use my June bandwidth... by privaria · · Score: 1

      This ain't DSL... :-)

      file: slackware-10.0-iso
      size: 682,819,837 (651.2 MB)
      dest: /usr/download/slackware-10.0-iso
      status:&nb sp; download succeeded!
      speed: 0 B/s down - 414.7 KB/s up
      totals: 652.2 MB down - 17.2 GB up

    5. Re:Only 7 more days to use my June bandwidth... by linuxelf · · Score: 1

      I should think not! And, just as someone who is stuck on a DSL connection, I'd like to personally thank you for the 17.2 GB!

      --
      - "That's just the kind of fuzzy-headed liberal thinking that leads to being eaten."
  115. Gentoo is for ricers. by gluke · · Score: 0, Troll

    And Linux, actually, in general.

    1. Re:Gentoo is for ricers. by phrasebook · · Score: 1

      and ... ?

  116. Who will benefit from Slackware vs other distros? by penginkun · · Score: 1

    I'm curious to know what benefits Slackware offers vs Mandrake, Fedora, etc. I haven't heard much of Slackware since its early days.

    Will this clueless n00b be able to pick it up and use it, or would I be better off with Fedora or (insert other distro here)?

  117. Paging Mr Volkerding..... by slayer99 · · Score: 0, Troll

    The 1980s called, they want their package management system back. ;)

    --
    Martin Brooks / Slayer99 #linux / UIN 2178117
  118. Stop wasting resources!! by SpaghettiPattern · · Score: 2, Insightful
    the non-cheapskates among us should go buy the CD-set to support the project

    By that I'd pay for:
    • The packaging (materials and handling)
    • The delivery
    • Possibly the store which almost certainly will NOT give any support.
    I don't want to cut out the middle man for the sake of it but in small distros (currently all linux distros can be considered small compared to windows) the delivery overhead is out of proportion. Most people involved in the deal will make much more money out of the deal than Slackware themselves.

    I also think the resources in this process are almost completely wasted.

    I recall wanting to buy a copy of Tux Racer. The retail price here in Europe was way above what I wanted to pay for it. The retail price in USA was better but shipping amounted to US$20. So emailed the Tux Racer guys telling them I don't need the box and the manual. I also told them that I'd be happy to pay them full price if I could download the game. That was useless because it didn't change anything at all. They probably thought I was crazy.

    When possible I try paying the people/bodies that make/package/service my software directly. And I do!!
    --

    I hadn't the slightest objection to his spending his time planning massacres for the bourgeoisie... (P.G. Wodehouse)
    1. Re:Stop wasting resources!! by a24061 · · Score: 1

      I agree. I prefer to download software and donate money to worthwhile projects and organizations (e.g. Debian, FSF).

    2. Re:Stop wasting resources!! by Anonymous Coward · · Score: 0

      That's right, because cutting out the middleman is the best way to make sure those middlemen continue to carry the product, ensuring widespread availability, which encourages greater use, a state that can be generally assumed to promote more development interest/activity.

      Middlemen aren't really THAT bad. Saying you want to see linux on the desktop, or at least see it become more popular, then making statements about eschewing the retail distribution system is a lot like saying you want to stop crime then turning around and voting to take funding from your local police department.

  119. disappointed by Anonymous Coward · · Score: 0

    Used to be a big slack fan, but that X6.7.0 was just a big problem for me. Using Estonian keyboard and right alt just does not work. In XFree86 the line options "RightAlt" "modeShift" made a trick, but not in X.org. This leaves me without '@' and '|' characters. After all there are other minor issues with slackware since version 9 already. Sad, but I cannot use the system that does not cooperate with me.

  120. SlackOS X by Anonymous Coward · · Score: 0

    a good name for ;)

  121. Re:FIRST GENTOO POST by Anonymous Coward · · Score: 0

    ha ha ha gentoy is teh greatast cos it compilled from teh source and is teh 0.0001% faster on my athalong microprocessor 3ghz nforce 3!!11!!!1!!one

  122. Wohoo by Anonymous Coward · · Score: 0

    My favorite Linux distribution through the last 10 years gets a new major update... This beats X-Mas :)

  123. Not SuSE. But Slackware? by MikTheUser · · Score: 1

    I started out on Linux with SuSE. Nice beginner's system, easily set up, a lot of stuff works without configuring too much. But it's exactly that which began to bother me - after each installation I would rewrite the kinda messy /etc/fstab, and was already pissed that it had been entwined with links on the KDE Desktop.
    Well, this tendency, I think has, gotten worse. SuSE is all Windows-style, lots of colors and it's hard to configure the real stuff. Even updating a library can result in a disaster, for example when sources and precompiled RPMs get in each others way (a friend tried to update his SuSE 9.1-glib 1.2 to 2.4 and screwed his system).

    So, I'd like to try some other system, and after a lot of surfing (no trying tho, I haven't been at home for a year and am just about to get back) I decided to give Slackware a try.
    I am confident, but sometimes I shudder when I think of getting my TV Card, scanner or CF-reader up running manually. Anyone got experiences, tips, anything?

    1. Re:Not SuSE. But Slackware? by Anonymous Coward · · Score: 1, Interesting

      I have run Slackware since way-back-when, and it has certainly gotten a LOT easier to install/setup than people give it credit for now. Still not the auto-configuration bliss of some distros, but it isn't a painful process anymore either.

      I just did a fresh install of 9.1 a couple of days ago to set up a MythTV box. The BTTV-compliant tuner card was automatically recognized, sound (AC97 chipset on the motherboard) just worked, and grabbing the source for Myth and compiling it was no problem. It was a LOT easier than I expected! And a whole lot faster than waiting on Gentoo, which is what I had been running on that machine.

      I haven't had to do anything fancy to support CF readers (I have USB and PCMCIA), although I do still manually mount/unmount them at the command line. I've considered setting up supermount or something, but never bothered. My USB scanner Just Works too. I think I had to install XSane myself (been a long time since I did it, my laptop is at Slack 9.0) but again, simple compilation.

      I've actually tried just about all the other distributions recently, thinking maybe - just maybe - I might want to switch. But the number one thing that keeps sending me back to Slackware is package management, oddly enough. Everyone keeps saying what a wonderful thing apt or rpm is, and I found that to be true up until I started trying to do something bleeding edge and I had to compile my own stuff. Then it started to get frustrating and irritating. Slackware just trusts you to do the right thing. Or, put another way, gives you just enough rope to hang yourself! Besides that, things just didn't seem to be in the right places. Slackware tends to keep its packages strictly stock. There are a few changes, but they are pretty minor.

    2. Re:Not SuSE. But Slackware? by MikTheUser · · Score: 1

      Thanks a lot for your experiences, it gave me some courage to Not Be Led Into Temptation and install SuSE ;)

  124. Re:Who will benefit from Slackware vs other distro by a24061 · · Score: 1
    I would recommend Mandrake or something similar for the clueless n00b. I started off with it several years ago: it detected hardware well and set itself up (mount points, LILO kernel options, etc.) accordingly.

    After a while, when I felt more confident, I switched to Debian, which I'm now extremely happy with. But it isn't (IMHO) suitable for the new Linux user. I had to figure out how to set a lot of things up manually, but now I know how to change those things myself.

  125. Meh by stud9920 · · Score: 0, Offtopic

    Meh ! Mandrake has been 10.0 for how long ?

  126. WTF? by Arker · · Score: 2, Insightful

    if you really are a n00b with Linux I wouldn't recomment Slackware as your first distro.... Try some more user-friendly distros such as RH, SuSE, Mandrake or other...

    What a bunch of nonsense. Tell me why Slack isn't as good as RH, SuSE, or Mandrake for a beginner? Any serious reason or are you just repeating some prejudice you heard somewhere else? Have you even tried Slack?

    It's not user-friendly? How so? Because the installer runs in text mode? Please.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:WTF? by Cro+Magnon · · Score: 1

      It depends on the beginner. If someone wants something that "just works" without the viruses and spyware found in certain OSs and doesn't want to learn the nut and bolts, they might be better off with the "easy" distros. Of course, if someone really WANTS to learn, and isn't afraid to RTFM when neccesary, Slackware is the best! And it's straight-forward enough to be easy to learn.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    2. Re:WTF? by rsheridan6 · · Score: 1

      I tried Slackware as a newb. I wouldn't recommend it. Installing it wasn't a problem, but getting the peripherals to work was.

      --
      Don't drop the soap, Tommy!
    3. Re:WTF? by Arker · · Score: 1

      Slackware has always 'just worked' for me. And yes, it was my nooby distro. I've tried most all the others, and they often don't just work - they try to do a lot of stuff 'automagically' and guess what - that means it often breaks and there is no easy or obvious fallback solution. Slackwares tools may look 'primitive' at first glance to someone used to Windows or Mac, but they have some great virtues that are just as important, if not moreso, for newbies as for the experienced. They are simple, and utterly reliable. They aren't hard to understand. There is great documentation for them. And they're lightweight - whereas many other distros install a setup by default that isn't really usable without a very new machine, a newbie can do a small amount of reading and then get a usable slackware system up and running on most any old box and get a great experience, encouraging them to continue using it in the future.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
  127. Seriously, I don't get it by Lord+Kano · · Score: 1

    Time and time again. I see posts indicating that /. regulars don't get laid. I think of myself as an average /.er. I do pretty well in that department. I've been in the game for almost 12 years now and in all that time my longest dry spell was 5 months and 7 days.

    Since I was 19 my longest dry spell was less than 3 months.

    Is this supposed to be self-deprecating humor, like when jewish people tell lawyer jokes or when black people make jokes about being ghetto?

    Seriously. I just don't get it.

    LK

    --
    "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
    1. Re:Seriously, I don't get it by Shakrai · · Score: 1

      Time and time again. I see posts indicating that /. regulars don't get laid. I think of myself as an average /.er. I do pretty well in that department. I've been in the game for almost 12 years now and in all that time my longest dry spell was 5 months and 7 days.

      I was torn between modding you up or replying. I'd rather contribute my two cents to this one though rather then a measly +1, interesting.

      I see these posts all the time too and I don't understand them myself. I consider myself a fairly average /. person and I happen to be in a long term relationship with somebody that I love very much.

      My girlfriend herself has said it many times -- geeks are cool nowadays. We tend to make more money, we listen better, we aren't as likely to be violent drunks and (believe it or not) there are just as many female geeks as there are male geeks. In fact my girlfriend would probably be one of them -- being an art teacher/historian. There are many classes of geek -- us techies aren't the only ones.

      I would submit that it comes down to the difference between the average geek (virtually all of the /. readership and a large portion of the real world society) and the average nerd (a large portion of the /. readership and a smaller portion of the real world). The ones making the jokes are probably the nerds that are still in high school and haven't ventured out into the real world yet -- because the real world typically seems to turn most nerds into geeks. There probably is a little bit of self-deprecating humor tossed in there as well.

      If that made any sense to anybody who read it then I tip my hat to you -- it didn't come out nearly as clear as I intended but hopefully it got the point across :)

      --
      I want peace on earth and goodwill toward man.
      We are the United States Government! We don't do that sort of thing.
  128. Network Installation by Genin · · Score: 1

    Am i going to have any headaches installing it via lan? I want to experiment with it on my old thunderbird/gf2mx400 system that i don't use and i can't be bothered to buy an optical drive for it.

    --
    I am forced to conclude you are the master of the obvious. May others take heed of your wisdom.
  129. Kernel question by Viol8 · · Score: 2, Interesting

    Does anyone know how hard it is to upgrade to the 2.6 kernel if you go for the standard 2.4 install with this dist? Do the seperate installs literally just install different kernels or does it install different versions of libraries too which would need to updated on a manual upgrade?

    1. Re:Kernel question by Lispy · · Score: 1

      Its easy. All the tools are ready. You can either simply install the new kernel or compile your own vanilla. I dont think you will be in much trouble. I never had any issues with the 2.6 series. That is actually one of Slacks major strenghts.

  130. watch the Kernels! by SillyCON · · Score: 1

    Im Slackware-current user. Kernel 2.6.6 didnt cope with my VIAs ide controller at all: Unable to boot, neither ACPI disabled. Kernel 2.6.7 has bt848 module broken, video_buf module exactly. ALSA driver modules behaves extrange.
    Kernel 2.4.26 works fine.

    Looking after 2.6.8.

  131. My Xorg experience by SillyCON · · Score: 2, Informative

    Slackware-current. Using NVidia GForce4 MX440 (NV17) with Nvidias last linux driver (build five thousand and something) Xorg works exactly as XF86.
    Only quiks came from applications that dont find /etc/X11/XF84config-4. Soft-link to /etc/X11/xorg.conf and youre done.

  132. Re:Yet Another Distro by Anonymous Coward · · Score: 0

    Actually, Yggdrasil (Igg Drah Sill)

  133. LVM2 by SteelX · · Score: 1

    Any word on Slackware 10's support for LVM2 under kernel 2.6.x? It wasn't working properly in prior versions.

  134. Re:Who will benefit from Slackware vs other distro by Anonymous Coward · · Score: 0

    These days I point gnubies at knoppix. I find it friendlier then mandrake and has all the advantages of debian only easier.

  135. The slackware differential by davi_slashdot · · Score: 2, Informative

    From the announcement:

    "Each Slackware package follows the setup and installation instructions from its author(s) as closely as possible, offering you the most stable and easily expandable setup."

  136. Yay slackware. by chegosaurus · · Score: 1

    If you're a crusty old Unix bod, it's the only way to go. Install the core and build the rest on top yourself. Just the way you want it. No crap. No package dependencies. No depending on the distribution vendor. You know what you're doing. Slack just lets you do it. It also seems to be the lowest profile, least "political" of the established distributions, which I like.

    My old laptop disk gave up the ghost a little while ago. It had the latest and greatest everything installed, but I think the core of it had come from a Slackware 3.2 CD I got with a book back in the day. Every single part of it had been replaced, but deep down, it was still Slack 3.2. In a way. I downloaded ISOs for later versions, but there was no point upgrading. My new laptop disk has OpenBSD on it. I might just jump back to Slackware, for old time's sake.

  137. Re:OT: Does It Work With A DVI FLat Panel? by Nighttime · · Score: 1

    I can certainly confirm that X.org, Matrox G550 and DVI output can be achieved. Currently running a dual LCD set-up under Fedora Core 2 with said card.

    What you need to do is grab a beta driver from Matrox's site. Although it says it is for XFree86 4.1, 4.2 & 4.3 it works under X.org 6.7. Be aware that there is a bug in the driver that causes X to hang for 30 seconds or so when it first starts up.

    Matrox also have a forum to discuss all things Linux and their graphics cards.

    --
    I've got a fever and the only prescription is more COBOL.
  138. The version 10 milestone deserves a name change... by Vandil+X · · Score: 1

    Maybe they should rename it...Slack OS X!

    (mods: this was intended to be funny, not a troll or flamebait)

    --
    Up, Up, Down, Down, Left, Right, Left, Right, B, A, START
  139. Network install by bcmm · · Score: 1

    I hate wasting CDs on ISO installs, (the images are usually over the 650MB limit for CD-RW). Does slack have some kind of boot floppy/minimal ISO ftp install? If so, where?

    --
    # cat /dev/mem | strings | grep -i llama
    Damn, my RAM is full of llamas.
    1. Re:Network install by Anonymous Coward · · Score: 1, Informative

      forget iso's just download the disk sets you want, boot via floppy, setup your nic with the network disk. and use a nfs install. though you do need another box for this...

    2. Re:Network install by Anonymous Coward · · Score: 1, Interesting

      I also dislike burning CD:s. When installing FC2, I followed some advice somewhere; the thing to do was to store all ISO:s on an ext2/ext3-partition, mount the first ISO on loopback, copy the vmlinuz & initrd image to /boot, add it to the lilo/grub-menu, reboot, choosing that entry when booting, running the rest from hard drive. Worked nicely :-). Although FC2 didn't (both my sound cards refused to work, tried unmuting things etc. to no avail), so I went back to Debian. But, it was possible to install entirely from hard drive & an old linux partition. You might try doing something similar... (the reason for using ext2/ext3 was that those were the only filesystems understood by the install-kernel before it had loaded modules for reiserfs etc.)

  140. Re:WRONG. Another washed up slack kiddie? by Anonymous Coward · · Score: 0

    "You'll just look like a fucking moron"
    -I'm not the one cursing and complaining.

    "I've course I've used slackware"
    -The wonderful. At least you're making comments based on experience and not naive opinions.

    "No distros are derived from slack"
    -CollegeLinux, VectorLinux, Amigo, etc.

    "Anyone with half a brain and a little unix experience can see the distro is shit"
    -Don't know how to reply to that. I have half a brain (a little more I think) and some Unix experience, yet I like Slack.

    "bizarro wannabe bsd style inits that all the other non-shit modern distros do not use"
    -See distos listed above. This has more to do with philosophy of init than anything. And your comment will only anger the BSD folks.

    "Oh you don't like slack? Well you obviously aren't leet enough to handle it!"
    -I never said that. I just said it made you learn Linux, another point you disagree with.

    "If you learn redhat or debian you would be much better able to switch distros since more distros are based on and closely related to those"
    -You would know how to manage RedHat and Debian based distros. I just speak from experience about learning Slackware equals learning Linux.

    I guess that's enough. I'm done with you and this arguement.

  141. Virus by gleather · · Score: 1

    Sign of "Win32:Gaobot-331 [Wrm]" has been found in slackware-10.0-install-d2.iso

    --
    Idiot.
    1. Re:Virus by Anonymous Coward · · Score: 0

      Where do you people come up with this stuff?

    2. Re:Virus by Chaxid · · Score: 1

      An ISO cannot be executed anyway, so what does it matter? Besides, this is obviously a false positive.

  142. Re:Slackware's time has passed by satan666 · · Score: 1

    Post with your real name so I can bitch slap you.

  143. SLACK! THE XISTS ARE COMING! by radiophonic · · Score: 1

    10.0: Just in time for the coming of 7X day. DON'T PINK OUT!

    OK, no, really, good to see that Slackware is still going strong. My first distribution...everybody sing! Memmories...do do de do...

    --
    Whenever you read this sig someone's refrigerator light turns on.
  144. Re:Who will benefit from Slackware vs other distro by a24061 · · Score: 1

    I've heard good things about Knoppix but I haven't had a chance to try it out yet.

  145. yeay by techefnet · · Score: 0

    have been waiting for this for months :) tho ive always used the latest current, it worked fine.. :)

  146. I smell trademark infringement by macmastery · · Score: 1

    Cupertino will never stand for "Slack OS X". :-)

  147. Torrents are down by Danathar · · Score: 1

    Hey What gives! The torrent trackers are offline...does anybody know what the problem is?

  148. Re:WRONG. Another washed up slack kiddie? by Anonymous Coward · · Score: 0

    How would slackware equal "learning linux" since it doesn't use Linux style inits or a common linux package manager system like rpm or deb?

    More like you would be learning slack.

    How can you say if you learn Redhat that you have not "learned linux"?

    WTF does "learned linux" mean exactly anyways?

    Face it slack is crap. It has no advantages whatsoever other than a warm fuzzy "i'm hardcore cuz i use slack" feeling it gives newby chumps.

  149. Re:As a recent slack user: by slasher+guy · · Score: 1

    before slackware, I'd tried to install Caldera (before I knew SCO = evil, and it came with a magazine). I didn't have enough RAM for a graphic install, and it didn't have text-based. Slackware works fine.

  150. Re:WRONG. Another washed up slack kiddie? by PitaBred · · Score: 1

    This sounds like a troll, but you sir, are a moron.
    It's because slackware CAN USE rpm (it actually comes with rpm in the install... didn't know that, did ya?). It's because slackware knowledge lets you know what's going on behind the scenes on all other distro's. It gives you the experience to be able to figure things out. I've walked in and adminned Redhat boxes from never working on anything other than slackware, and it was a piece of cake. Not that RPM is anything but another executable, same with .deb, apt-get and all those other fancy things that you all seem to hold so dear, in some kind of esteem not regarded to other programs. It's a philosophy thing. Some people are simply users, others know what the hell is REALLY going on. You sir, are a user.

  151. Slashdotted by slasher+guy · · Score: 1

    "problem connecting to tracker - operation timed out"

  152. Re:Yet Another Distro by Anonymous Coward · · Score: 0

    Goodness, was that a sneeze?

  153. It's supposed to be "Slackware X" by karlandtanya · · Score: 1
    Deja Thread


    Not to be confused with Deja Thoris.

    --
    "Reality is that which, when you stop believing in it, it doesn't go away." - Philip K. Dick
  154. Re:Slackware's time has passed by Cro+Magnon · · Score: 1

    Well, some of want something that's stable (bye, Fedora/Mandrake) AND made in this century (bye, Debian).

    --
    Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  155. WTF is going on? by KrisCowboy · · Score: 1

    Downloaded the 2 CD Slackware 10.0, officially. Been using Redhat 7.2/8/9, FC 1/2 till now, since 3 years. I didn't like Slack at all. Wait, it's not a flamebait and I'm not "just-another-rh-lover". I'll tell you why I didn't like Slackware. First of all, it's a great distro. A complete installation of 3 GB is great compared to FC2's 6.9 GB. All those window managers, greeeeat!!! But, when I log in, my favourite "Sans" font was missing :-( So are "Serif" and "Sans-Serif". I use "konsole" along with my Gnome. With FC2, there were some 20 fonts to chose from for konsole fonts. Slack gives just 3? Guys, don't blast me...let me know how to make my Slack work. I really like it and it's time I decided to move from Fedora.

    1. Re:WTF is going on? by higuita · · Score: 1

      let see... you complain about FC being 6.9Gb and then complain that slackware only have 3 console fonts instead of 20 as FC??

      make up your mind, do you want a small and fast distro or a distro that have all kind of trash you will never use (or do you really use 20 console fonts?!)

      if you like another font, take then from FC and install in slackware, you even have rpm2tgz or plain rpm in slackware!!

      --
      Higuita
    2. Re:WTF is going on? by KrisCowboy · · Score: 1

      let see... you complain about FC being 6.9Gb and then complain that slackware only have 3 console fonts instead of 20 as FC??

      Okay, my mistake. Anyway, I installed Slackware now and loving every moment of it. It's small and no-shit. But man, it sure generates lot of dependencies when I try to install a rpm :-( I think I'll use it for few more days and if everything goes well, bye bye FC2.

    3. Re:WTF is going on? by higuita · · Score: 1

      you can use RPM, but i dont recomend, as it doesnt know what slackware already have installed

      i prefer installing the tgz packages (from slackware or linuxpackages.net) or install from the source

      its simpler and you have more control on what is in the system

      --
      Higuita
  156. Re:Who will benefit from Slackware vs other distro by penginkun · · Score: 1

    I've played with Mandrake a bit, and it seems pretty decent. I'll have to check out knoppix as well.

    Thanks to you both for your suggestions!

  157. I guess I'm in the 10% by TheHonestTruth · · Score: 1
    My Windows machine died, so I installed Mandrake on a Celeron 600. I can IM, email, surf, and run Citrix to work from home. It isn't fast, but it works.

    I don't want to dick with config files or recompile the nightly build. I just want a computer I can work on at home that doesn't have a 12" screen (like my iBook) and Mandrake gave that to me, almost straight out of the gates (a little configuring of my wireless card). *shrug*

    -truth

    --

    I had a steady B+ in my AI class until I failed the Turing test...

  158. Bittorrent Fairness / Leech Prevention Causes That by billstewart · · Score: 1
    Bit Torrent works because everybody who's downloading is also creating bandwidth by uploading to other people. Since the number of bits that get downloaded is obviously equal to the number of bits that get uploaded (less occasional lost bits), both per second rate and long term quantity, so in the long term, BitTorrent only works because the amount of bandwidth people offer for uploading exceeds the amount of bandwidth people actually use for downloading, and it also only works if enough people are generous with allowing uploads after they're finished downloading to make up for the freeloading leeches who disconnect after they've gotten their downloads finished.

    So to enforce this, Bittorrent has a general tit-for-tat policy that your download rate is limited to your upload rate unless you're getting lucky, and a bunch of tuning to try to optimize things so that people with high upload rates get extra lucky on excess downloading bandwidth a lot (so the system can keep their uploads full) and in general.

    Your bandwidth looks like your upload and download rates are pretty balanced, at about 200 kbits/second. Depending on your DSL circuit, that's not too bad - slower ADSL is limited to ~128kbps upstream, faster US ADSL is often 384kbps upstream, and you're in about the middle. Cable modems in the US are usually limited to 128kbps or 256kbps upstream. You can often do better than this downstream - in the last hour, my upload rate has usually been 10-14 kB/sec (mostly filling my ADSL 128kbps upstream, though I use a client that lets my throttle it to about 90% of maximum capacity so my other applications don't starve), and my download rate has sometimes been 6-10 kB/s,
    but is currently cranking at 72 kB/sec, because there are some fast seeds or fast peers available right now that don't have anybody else to feed (with 15 seeds and 6 peers.)

    What I often see is that downloading popular distributions goes slowly for a while after release, but often I get huge bursts of download speed overnight, because people's downloads finish after they've gone to bed and get left on for uploading, while other people aren't starting many new clients to use up the available speed.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  159. Tracker for Disc 2 having trouble. by billstewart · · Score: 1
    I'm running BitTorrent on Disc 1 (and had a nice friendly 110% upload ratio until an hour ago, when a couple of peers dropped out and my download speed zoomed to 70+kbps, making me look like an 80% slacker :-)

    I was running BitTorrent on Disc 2 also, and got about 85% downloaded when the tracker dropped me, and I haven't been able to reconnect. Anybody have a way to check if the tracker's died and kickstart it?

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  160. Re:Bittorrent Fairness / Leech Prevention Causes T by linuxelf · · Score: 1

    Actually, I was getting ~ 20k/sec. Not very fast at all. What I figured out was that my DSL doesn't like when I'm uploading at maximum. I don't know the technical reasons, but there you have it. Since at max I can upload at about 20k/sec, I used the --max_upload_rate switch and capped my uploads to 15K. Doing so, I was able to increase my download rate from 20k/sec to 160k/sec, and still share the files almost as efficiently as before.

    --
    - "That's just the kind of fuzzy-headed liberal thinking that leads to being eaten."
  161. GNU Stow by patrikr · · Score: 1

    Congratulations, you've reinvented the wheel. :)

    --
    All Glory To The Hypnotoad!
  162. Bits vs. Bytes, and overloading uploads by billstewart · · Score: 1
    You were getting 20-25k BYTES per second, which is about 160-200k bits per second.

    But yeah, if you're trying to cram data into the DSL pipe faster than it has room for, it's going to queue a little bit of the excess and drop the rest, and you can get into trouble with retransmissions, as well as trashing your other data. Another problem is that any protocol that depends on ACKs, including TCP, is really much happier if the ACKs don't get delayed or lost, and keeping your Bittorrent transmission rate lower than your upstream speed makes a huge difference in that.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks