Live data from Hacker News

Slackware 14.1 is released

slackware.com

31–40 of 68 posts

Re: Slackware 14.1 is released

#31
post #30

Usually people are skeptical about Slackware package manager (slackpkg). I thought I'd just throw in some links to alternatives. If you want to try another package manager you can install it and start using it in under one minute. Package manager is a package just like any other :) One is slapt-get [0], supports third party repos, resolves dependencies if you use it with repos that have dependency metadata, if you re…

There's also slackpkg+[0], an extension for the regular slackpkg program that enables third-party repos (e.g. Alien Bob's multilib repo.[1])

[0] http://slakfinder.org/slackpkg+.html

[1] http://connie.slackware.com/~alien/multilib/

Re: Slackware 14.1 is released

#32
Time to try Slackware again. It was my first dip into Linux many years ago. I moved to apt-get supportive distros but the idea of keeping a smaller set of applications around and knowing exactly what's on there is appealing.

Re: Slackware 14.1 is released

#34
post #19

Slackware is irrelevant and outdated. No package manager. No net install. Give me one reason to use it instead of Arch or Debian.

Slackware's strength is it's simplicity. Makes it easy to understand what's going on.

This also makes it a great learning tool.

There used to be a saying: Install Redhat, you learn Redhat. Install Debian, you learn Debian. Install Slackware, you learn Linux.

Re: Slackware 14.1 is released

#35
post #29

Earlier quoted context omitted.

Amen. I can't believe what people do for free, and that OSS has taken off at all. While there's room in this world for all kinds, my soul dies a little when someone comments, "wow, kids these days are so smart with computers!" While they watch them install iPhoto off the App Store. It's not true, but there will always be awesome people with awesome ideas and be willing to share them with the community. It's like http…

For example, if you would like your system to be mostly stable and unchanging, like Debian or a Red Hat Enterprise Linux clone, but would like access to cutting-edge packages from Arch, Bedrock Linux can provide this simultaneously and transparently. Does... not... compute. If you want your system to be stable and unchanging, why would you care about the most cutting-edge packages? Those are the buggy ones, the reaso…

It would compute If you explored a little further than the front page, or even carefully considered the meaning of "bedrock".

http://bedrocklinux.org/introduction.html#what_bedrock_does

Re: Slackware 14.1 is released

#36
post #19

Slackware is irrelevant and outdated. No package manager. No net install. Give me one reason to use it instead of Arch or Debian.

In case you are not trolling: 1. Everything is as close to the upstream package as possible. Debian maintainers sometimes heavily modify their packages and that makes finding help difficult. Slackware rarely changes their packages or only does if necessary. 2. Package manager does not do dependency checking. This makes installing packages from source easier because I don't have to worry about breaking the system when…

This thread made me think. Perhaps Slackware is due for a slight comeback due to the ZFS style snapshot / containerization type trends going on right now, since Slackware's quirk of "not having" package management becomes irrelevant.

Re: Slackware 14.1 is released

#37
I ran Slackware many moons ago. It was very bare bones and it took a lot of work, but I was young and it was an immersive experience. As another commenter wrote, people on IRC played up how 1337 they were for running Slack. I disagree slightly with that statement. I spent a lot of time building my Slack system on a PII 266, and I was 12, so it took me a long time with a lot of false starts. I don't think anyone was trying to be "1337", they were just proud of what they'd accomplished. I know I was.

In any event, it's cool to see Slack is still around. I installed ArchLinux on my MBP a couple weeks back. After installing Mavericks, the modified EFI partition I created no longer lets me boot Arch, so I think I'll give Slack a try. It's the challenge that makes it worth it.

Also, I have to strongly suggest to anyone who is not all that into Linux but is interested in learning: Skip the window environment. Force yourself to just sit there on the command line. It's surprising the kind of focus you have when you can't be distracted by all manner of visual eye candy. I know that sounds ridiculous, but it was a real pleasure to use only the CLI. It's sort of like the difference between writing with sidewalk chalk and a fine fountain pen. You find yourself writing /differently/. It's a subtle change with lots of unintended consequences that cause you to think about your work from a different perspective. As Alan Kay put it: Perspective is worth 80 IQ points.

Re: Slackware 14.1 is released

#38
post #6

I know that this is no way of judging a distribution - which never had a decent package manager as far as I know - but all the assholes, hacker-wannabes from my early IRC era (1999-2004) were pompously bragging about how elite they were using slackware. I know many of you find that behavior childish but I'm 100% others encountered the same behavior as I did. I never knew if it was the founders/dev's (I think was only…

I started as a hacker-wannabe and felt in love with the simplicity, minimalistic approach, stability and control it gave to me.

Never went back.

Re: Slackware 14.1 is released

#39
post #37

I ran Slackware many moons ago. It was very bare bones and it took a lot of work, but I was young and it was an immersive experience. As another commenter wrote, people on IRC played up how 1337 they were for running Slack. I disagree slightly with that statement. I spent a lot of time building my Slack system on a PII 266, and I was 12, so it took me a long time with a lot of false starts. I don't think anyone was t…

Also, since package managers seem to be the common gripe. I never used one, and I'm glad I didn't. I learned a lot by not having a proper package manager as a crutch. The creature comforts were never the point for me, inventing creature comforts that fit me was an enlightening experience and one that I think ought to be recognized for what it was: It wasn't "efficient" or "awesome" -- it was the basics. It was nuts and bolts, and so few things are these days. Sometimes it's not about nostalgia, it's about first principles.

Re: Slackware 14.1 is released

#40
post #34
post #19

Slackware is irrelevant and outdated. No package manager. No net install. Give me one reason to use it instead of Arch or Debian.

Slackware's strength is it's simplicity. Makes it easy to understand what's going on. This also makes it a great learning tool. There used to be a saying: Install Redhat, you learn Redhat. Install Debian, you learn Debian. Install Slackware, you learn Linux.

> Install Slackware, you learn Linux.

Which is becoming less true since Linux as a full OS is moving to PulseAudio and systemd and has long since moved to PAM (among other things). By default, Slackware doesn't have, and probably will never have, any of those.

Slackware experience is becoming less and less transferable.

Post reply on HN