Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slackware 14.2 release candidate 1

slackware.com

Post reply on HN
Print view View original

41–50 of 99 posts

Re: Slackware 14.2 release candidate 1

#41

Post by digi_owl »

bitwize wrote: post #27
Tomte wrote: post #4

Earlier quoted context omitted.

Patrick Volkerding is hesitant about systemd, but not openly hostile, so he has decided to stay away from it for now, but hasn't ruled it out for the future. People who are set against systemd should probably better look elsewhere (although their options are pretty limited).

Alternatives include CRUX (whose maintainer's systemd stance is "over my dead body :)"), Void Linux (the only distro I know of to adopt systemd by default and then migrate away from it; currently it uses runit with systemd as an option), and Alpine. I'm sticking with Slack for the time being, but I've got my eye out for alternatives should the worst happen.

> to adopt systemd by default and then migrate away from it

Now that could be a interesting read, if documented somewhere.

Re: Slackware 14.2 release candidate 1

#42

Post by adrusi »

creshal wrote: post #40
baldfat wrote: post #39

Earlier quoted context omitted.

So you post a German blog post about something you have never done. I now have gone full on salt. Once again their is nothing wrong with RPM and this anti-RPM stuff needs to just die. Linus uses Fedora and if anyone would flip out if something was bad technology Linus would, but instead people who just heard a cool RPM Dependency Hell still continue this 10+ year old issue over and over again without knowing anything…

> So you post a German blog post I'm sorry, I didn't know Germans weren't allowed to have opinions.

But if your goal is to provide veracity to your claim, then posting a German article on an English forum isn't very useful.

Re: Slackware 14.2 release candidate 1

#43

Post by IgorPartola »

baldfat wrote: post #28
warrenmar wrote: post #3

For those of you that don't know about Slackware. Slackware is the oldest distro and it is still plenty alive today. When to setup linux on my computer in the early days with other distros (red hat/suse/etc), this would eventually crap up (rpm hell) and give me something unusable. Using Slackware forces you understand how everything works in a linux distro. This lets you fix your own problems.

I know you didn't mean to bring this up as a point against rpm but my ALL TIME MOST HATED PHASE is rpm hell. I still hear people say that they won't use RPM based systems because of RPM Hell which makes me inside want to jump through the screen and shake them and say "Have you ever built a single package?! Because if you ever have you would know this is 100% crap for over 10 YEARS!" Sure there was a time frame when t…

Sorry, but I am still stuck in my own version of RPM hell, and yes I have packaged RPM's.

The problem: production servers for a client use RHEL 6.3 and are very slow to upgrade. Moreover, they don't have the subscription to RH's commercial repos, and instead host their own, which means that some packages are straight up missing.

For development I use CentOS of a matching version. All works well until I go to deploy something to production and find out that a package I need is not available. The solution has been to (a) install packages from the CentOS repos (yup, old school download them off their site and then `rpm -i` them locally) or ask the client's IT to temporarily enable certain repos of later RHEL versions they have, so that I can install packages with lots of missing dependencies. The most recent fiasco with this involved ImageMagick and ImageMagick-dev not being there and depending on a crapton of libraries that were also missing.

Now, I am not RPM-distro professional, I stick to Debian derivatives for the most part, but I have worked with them enough to know that unless you do things by RH's book, you are going to be in trouble, and even people whose full time jobs it is to maintain these production servers seem to have a really hard time figuring out how to get this right.

P.S.: One solution I attempted was to create my own RPM repo that I could these missing packages from. This worked for some, until it landed me in a world of hurt where yum really wanted to install i386 versions of the packages instead of x64, even though (a) the server was x64 and (b) both versions of the package were available. This resulted in yum refusing to do anything because it saw conflicts. I have never had these types of problems with Debian based distros and a day of Googling for answers did not solve it.

Re: Slackware 14.2 release candidate 1

#45

Post by sbarker »

adrusi wrote: post #42
creshal wrote: post #40

Earlier quoted context omitted.

> So you post a German blog post I'm sorry, I didn't know Germans weren't allowed to have opinions.

But if your goal is to provide veracity to your claim, then posting a German article on an English forum isn't very useful.

Google translate... We have the technology, just not the sense to use it :-(

Re: Slackware 14.2 release candidate 1

#46

Post by jqm »

unixhero wrote: post #34

I really want the best for Slackware. I used to be a slacker 1996-2006 and grinded my Linux teeth on it. It escapes me why they don't want to innovate at all with a proper modern package manager. Also they need to remake their website and with that create a decent forum and a decent wiki just like Arch has perfectly done. Nowadays I don't care at all about knowing every corner of my system. I have applications to man…

I still run Slackware on my home/work machines. I find that setting it up once every couple of years and moving my home directory is about all I need.

On the rare occasion software needs to be installed yes, it has to be built from source and it takes a few extra minutes. But you know what? Ubuntu package managers have failed me more than a couple of times. Slackbuilds.org has never once failed to produce a working package for me.

I know people don't want to have to know about every corner of their system. But you don't necessarily need to. Set it up and it works. But if you ever need to you can with Slackware. All the way down without a lot of cruft on top. And that's worth a lot when it's needed.

I guess the point is... I don't spend a lot of time screwing around with my Slackware systems. They are stable, simple and they work. Not dissimilar to the Slackware web site. Lacking over-engineered cruft.

Re: Slackware 14.2 release candidate 1

#47

Post by [deleted] »

IgorPartola wrote: post #43
baldfat wrote: post #28

Earlier quoted context omitted.

I know you didn't mean to bring this up as a point against rpm but my ALL TIME MOST HATED PHASE is rpm hell. I still hear people say that they won't use RPM based systems because of RPM Hell which makes me inside want to jump through the screen and shake them and say "Have you ever built a single package?! Because if you ever have you would know this is 100% crap for over 10 YEARS!" Sure there was a time frame when t…

Sorry, but I am still stuck in my own version of RPM hell, and yes I have packaged RPM's. The problem: production servers for a client use RHEL 6.3 and are very slow to upgrade. Moreover, they don't have the subscription to RH's commercial repos, and instead host their own, which means that some packages are straight up missing. For development I use CentOS of a matching version. All works well until I go to deploy s…

[deleted]

Re: Slackware 14.2 release candidate 1

#48

Post by crncosta »

unixhero wrote: post #34

I really want the best for Slackware. I used to be a slacker 1996-2006 and grinded my Linux teeth on it. It escapes me why they don't want to innovate at all with a proper modern package manager. Also they need to remake their website and with that create a decent forum and a decent wiki just like Arch has perfectly done. Nowadays I don't care at all about knowing every corner of my system. I have applications to man…

Here is the wiki you are looking for: http://docs.slackware.com/

Re: Slackware 14.2 release candidate 1

#49

Post by megous »

unixhero wrote: post #34

I really want the best for Slackware. I used to be a slacker 1996-2006 and grinded my Linux teeth on it. It escapes me why they don't want to innovate at all with a proper modern package manager. Also they need to remake their website and with that create a decent forum and a decent wiki just like Arch has perfectly done. Nowadays I don't care at all about knowing every corner of my system. I have applications to man…

Yeah, I don't know either. I went as far as to write spkg (spkg.megous.com) in 2006, just to replace the funcionality of pkgtools bash scripts without adding new features. (imporving robustness and speed) I never got any response from the Slackware team. I guess they're just very very conservative.

I loved my Slackware times for the learning experience. But it was hell of a lot of work to use it.

Re: Slackware 14.2 release candidate 1

#50

Post by ktRolster »

pjmlp wrote: post #36
warrenmar wrote: post #3

For those of you that don't know about Slackware. Slackware is the oldest distro and it is still plenty alive today. When to setup linux on my computer in the early days with other distros (red hat/suse/etc), this would eventually crap up (rpm hell) and give me something unusable. Using Slackware forces you understand how everything works in a linux distro. This lets you fix your own problems.

It was my very first one, Slackware 2 with kernel 1.0.9. I still remember the main feature being announced was the early support for elf format. Nowadays after a decade of jumping between OSes, I just settled on Windows, for better or worse, it does better what I need for my work (please don't start a flame war on this). However I do owe a lot to Slackware, as before it my only access to UNIX were expensive Xenix, Ai…

(please don't start a flame war on this).

tbh I think you already flamed yourself, charred to a crisp, worse than any of us here could do. Windows User.

Post reply on HN