LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-21-2018, 02:14 PM   #31
ArchArael
Member
 
Registered: Mar 2005
Posts: 109

Original Poster
Rep: Reputation: Disabled

Quote:
Originally Posted by upnort View Post
Interesting thread. I do not see the post as trolling or click-bait, especially in light of recent threads where so many people offered Pat suggestions about improving Slackware. I hope this thread can be used as a continuation of that process.
I assure you it is was posted with good intentions. I am trying to understand other peoples motivations to understand better mines.

Quote:
Originally Posted by upnort View Post
I have streamlined the "bloat" removal process as well as streamlined the desktop configuration.
Your post was very insightful. Would you mind sharing more about this process? Maybe I can learn something new and apply to mine setting.

Last edited by ArchArael; 08-21-2018 at 02:17 PM.
 
Old 08-21-2018, 02:22 PM   #32
ArchArael
Member
 
Registered: Mar 2005
Posts: 109

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by animeresistance View Post
I haven't stopped using Slackware it is my heavy duty workhorse, my spearhead, etc., but I do have 2 more distros (Debian and Ubuntu) and FreeBSD in my PC.
Given that you have tried a more complete repository and the convenience of the debian package manager what is still motivating you to use Slackware?
 
Old 08-21-2018, 02:27 PM   #33
hitest
Guru
 
Registered: Mar 2004
Location: Canada
Distribution: Void, Slackware
Posts: 7,341

Rep: Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744
Thumbs up

Quote:
Originally Posted by ArchArael View Post
I assure you it is was posted with good intentions.
Wonderful! This thread is turning out to be informative and very interesting. Thank you.
 
3 members found this post helpful.
Old 08-21-2018, 02:33 PM   #34
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Ubuntu, Debian, Slackware
Posts: 2,178
Blog Entries: 6

Rep: Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470
Quote:
Originally Posted by hitest View Post
Wonderful! This thread is turning out to be informative and very interesting. Thank you.
Indeed, the knee-jerk low star ratings were premature. I still voted - 'good' - it's not quite excellent - but certainly interesting. People should think twice before voting [I hope they do that in all cases... or maybe not.. explains a lot].
 
Old 08-21-2018, 02:45 PM   #35
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,200

Rep: Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307
rg3 wrote a blog entry on why he stopped using it:

https://rg3.name/201502151103.html
 
3 members found this post helpful.
Old 08-21-2018, 02:50 PM   #36
ChuangTzu
Senior Member
 
Registered: May 2015
Location: Where ever needed
Distribution: Slackware/Salix while testing others
Posts: 1,718

Rep: Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857
This is an interesting thread, and at the same time it does have a hint of trolling. Why, because the assumption behind the question is that there is something wrong with Slackware. This has been rehashed many times over the years, and also is not unique to Slackware, you see similar threads on other fora. Why did you stop using Ubuntu? Why did you stop using Debian? etc....

A more productive question would be (and has been asked before), why do you use Slackware instead of other Linux distros or BSD etc...?

1) Why did you stop using Slackware?

I haven't.

2) Are you going to switch back again and why?

Still using it. I do test other distros in VM's and sometimes other partitions, and I am quickly reminded why I use Slackware. So I guess that counts as "going/coming back". Windows is rightly confined to a VM like the little bastard child that it is.

3) Which distribution did you switch to and why?

As long as Slackware is supported/offered, I don't think I would switch. If I did, it would probably be one of the BSD's (perhaps FreeBSD).

PS: Things like this has the philosophy of Slackware reign supreme: In Debian and its legion of derivatives the package maintainers make really silly decisions. Try to install Xfe and it pulls in among other things Audacious as a recommended dependency. Ref: https://packages.debian.org/stretch/xfe

Compare to Slackware and Slackbuilds.org: https://slackbuilds.org/repository/14.2/system/xfe/

So yes, dependency hell is still around and if you throw in systemd, dependency hell is ever growing. Also, I trust smaller repos because it is easier to ensure they are secure, the larger the repo the greater the risk of insecure, unmaintained, poorly packaged or outright fubar you can encounter. Again Debian SSL fiasco rings a bell. Also ponder the thought that if you have 50,000 packages and 1,000 packagers, that means on average they maintain 50 packages each. Oh and then there is the entire split every package as if it is an atom. https://www.sciencedaily.com/release...0605102807.htm
 
4 members found this post helpful.
Old 08-21-2018, 03:17 PM   #37
peumo
LQ Newbie
 
Registered: Apr 2018
Location: Quintero, Chile
Distribution: Slackware
Posts: 17

Rep: Reputation: Disabled
Quote:
Originally Posted by ChuangTzu View Post
In Debian and its legion of derivatives the package maintainers make really silly decisions
The way they prepare packages is very annoying. Preparing more of your system by yourself might be time-consuming; but undoing preprations made by others is just absurd.
It also happens in Slackware with the stock packages and scripts; but it doesn't compare in magnitude and multitude to other distros.
The single annoying package preparation in Slackware, for me, was the one for sudo; Pat just threw every single insult set into it for some reason, haha.
Anyway, I still think that there are sensible reasons to use other distros; I am aware that Slackware has its limitations in terms of serving some use-cases. It just fits well with mine.

Last edited by peumo; 08-21-2018 at 03:22 PM.
 
1 members found this post helpful.
Old 08-21-2018, 03:43 PM   #38
upnort
Senior Member
 
Registered: Oct 2014
Distribution: Slackware
Posts: 1,893

Rep: Reputation: 1161Reputation: 1161Reputation: 1161Reputation: 1161Reputation: 1161Reputation: 1161Reputation: 1161Reputation: 1161Reputation: 1161
Quote:
Your post was very insightful. Would you mind sharing more about this process? Maybe I can learn something new and apply to mine setting.
Yes, I could share Ubuntu streamlining, but this is the Slackware forum.

Big picture -- and this strategy applies to Slackware too, I have used a shell script that tweaks certain things, such as displaying logs in text format, not using the silly so-called predictive network card names, removing and installing specific packages. I don't use the script much these days because after I pruned the bloat and disagreeable design decisions I created partition images. Now when I want to create a new system I manually partition the disk and copy the images.

At one time I had a similar script for my Slackware installs. As the years progressed I had my Slackware installation so fine-tuned that I seldom perform fresh installs and with my backups, never fear losing my tweaks.

With respect to "learn something new," I have opined previously, somewhere, that all operating systems suck. My opinion only. The reason is computers are incredibly complex tools. Just find the operating system that best satisfies your needs and work flow and sucks the least. Then learn to work around the warts and blemishes.

At home Slackware works best for me because Pat does not presume how I use my computer and at the moment, is not designing an operating system for the bell curve masses. I get to massage Slackware into the operating system I want. I think this is a point many first time users and click-bait reviewers do not understand about Slackware. Slackware is a foundation or building block distro. This approach works for me -- and I presume most Slackers, but does not work for many users. Thus upstream distros designed for the bell curve masses include everything including the kitchen sink. For many users this is a sane design choice and includes Windows.

Since I started using desktop computers in the early 1980s I have disliked upstream default design choices. I tend to be rebellious and non conformist. That's my "problem" and not everybody else's. That is, I am the one who has to adjust to avoid trouble. Thus I accept that such a design succeeds for many if not most people. I don't mind that I am a square peg among round holes. Some distros do support "minimal install" ISO images and that might be a good starting point for users like me. With Ubuntu MATE (and other distros I use at work) I kind of did the reverse and started full and pared the bloat. Now that I use partition images the point is somewhat moot.

I don't know if that helps.

Quote:
Things like this has the philosophy of Slackware reign supreme: In Debian and its legion of derivatives the package maintainers make really silly decisions.
From my usage I think much of the time the packagers do just fine. That does not mean I occasionally do not roll my eyes with dependency decisions. Once in a while though I get really riled at the packager. Once again, all operating systems suck, just find the one that sucks the least for you.
 
1 members found this post helpful.
Old 08-21-2018, 04:41 PM   #39
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Quote:
Originally Posted by ChuangTzu View Post
PS: Things like this has the philosophy of Slackware reign supreme: In Debian and its legion of derivatives the package maintainers make really silly decisions. Try to install Xfe and it pulls in among other things Audacious as a recommended dependency. Ref: https://packages.debian.org/stretch/xfe

Compare to Slackware and Slackbuilds.org: https://slackbuilds.org/repository/14.2/system/xfe/
In fairness (at least to this one specific program), audacious is already a part of Slackware. So, if xfe requires it (or if it is an optional dependency that the maintainer made required), that dependency is already satisfied with a full install of Slackware.

Granted, there are definitely examples out there where maintainers add optional dependencies that some may feel aren't required, but that happens everywhere, including on SBo.

As for the OP, I've never felt a need to stray from Slackware. I only use it in my home and, unfortunately, don't use Linux in my professional life (government work where I'm stuck using Windows).

I started with Redhat 7 in college (not RHEL 7, the original Redhat 7 back in the early 2000s). When I tried to install it on my old laptop at the time (Intel Celeron 400MHz with 160MB of RAM -- 32MB onboard and 2x64MB sodimm expandable), I installed everything and then found the cd drive didn't work. I had no troubleshooting knowledge of it and decided to just go back to Windows 2000. I had helped my buddy with Linux a few years later and he was working with Slackware. I decided to take the plunge again, either with 10.1 or 10.2. I had to recompile my kernel like 10 times that first week to get my wireless working on my slightly more modern laptop (Dell 700m with the lovely IPW2200 that wasn't included with the kernel at the time). I was sucked in and have been with Slackware ever since.

I've used other distros on occasion, usually when helping someone with a problem, but I've never felt a desire to find something else. Slackware has fit my needs and has pushed my desire to continually learn more. While topics can sometimes be quite divisive on here, I feel the technical knowledge is quite high and we can help a lot of people.
 
2 members found this post helpful.
Old 08-21-2018, 05:03 PM   #40
ChuangTzu
Senior Member
 
Registered: May 2015
Location: Where ever needed
Distribution: Slackware/Salix while testing others
Posts: 1,718

Rep: Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857Reputation: 1857
Quote:
Originally Posted by bassmadrigal View Post
In fairness (at least to this one specific program), audacious is already a part of Slackware. So, if xfe requires it (or if it is an optional dependency that the maintainer made required), that dependency is already satisfied with a full install of Slackware.

Granted, there are definitely examples out there where maintainers add optional dependencies that some may feel aren't required, but that happens everywhere, including on SBo.
According to Salix package search, these are the dependencies for xfe https://packages.salixos.org/#! :
bzip2 expat fontconfig fox-toolkit freetype gcc gcc-g++ glib2 glu harfbuzz libX11 libXau libXcursor libXdamage libXdmcp libXext libXfixes libXft libXi libXrandr libXrender libXxf86vm libdrm libjpeg-turbo libpng libtiff libxcb libxshmfence mesa xz zlib

Arch: https://aur.archlinux.org/packages/xfe

Again, package maintainer silliness. Oh, I forgot to mention other distros patching packages willy nilly, and thinking they know a program better then the developer.
 
Old 08-21-2018, 05:46 PM   #41
peumo
LQ Newbie
 
Registered: Apr 2018
Location: Quintero, Chile
Distribution: Slackware
Posts: 17

Rep: Reputation: Disabled
Quote:
Originally Posted by bassmadrigal View Post
In fairness (at least to this one specific program), audacious is already a part of Slackware
The devil is in the details. The issue is not the presence of audacious in a system; but the fact that a music player is marked as a dependency for a file manager.
 
2 members found this post helpful.
Old 08-21-2018, 06:01 PM   #42
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Quote:
Originally Posted by peumo View Post
The devil is in the details. The issue is not the presence of audacious in a system; but the fact that a music player is marked as a dependency for a file manager.
That might provide the ability to preview an audio file within the filemanager the same way that mplayerthumbs was used for KDE video thumbnails a while ago. This is the first I've ever heard of xfe, so it's just an observation from an outsider.

I'm not saying it's right, but the maintainer may have had a valid reason to include the dependency... or they may have not. As I said, the same things happen on SBo. Some complain because too many dependencies are required while others complain that some optional dependencies should be required.

You can't please everyone.
 
2 members found this post helpful.
Old 08-21-2018, 06:29 PM   #43
Gerard Lally
Senior Member
 
Registered: Sep 2009
Location: Leinster, IE
Distribution: Slackware, NetBSD
Posts: 2,176

Rep: Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761
Quote:
Originally Posted by bassmadrigal View Post
That might provide the ability to preview an audio file within the filemanager the same way that mplayerthumbs was used for KDE video thumbnails a while ago. This is the first I've ever heard of xfe, so it's just an observation from an outsider.
It's an Orthodox File Manager. Together with Krusader, the only one that is bearable to use on Linux.

Quote:
I'm not saying it's right, but the maintainer may have had a valid reason to include the dependency... or they may have not.
The answer to that might be in the developer's own words:
Quote:
Why yet another file browser?

Yes, it's a good question. Why another file manager when many excellent choices exist already? Why not use a full-blown, animated, bells-and-whistles file manager like Konqueror, Nautilus or Rox?

The answer is quite simple: Although all these file managers are feature rich and cleverly designed, let's face it, they are huge! If you're a console addict, light desktop user or have an older system, resource hogging file managers just aren't the way to go. Especially since most file managers are Desktop dependent (KDE, Gnome, Xfce, etc.), requiring you to load all kinds of unwanted bloat onto your system.
So, to a certain extent, to mandate other libraries is to show contempt for the developer's intention.
 
1 members found this post helpful.
Old 08-21-2018, 08:10 PM   #44
bobalooie
LQ Newbie
 
Registered: Nov 2006
Location: Cincinnati, Ohio
Distribution: Slackware64 15
Posts: 9

Rep: Reputation: 2
1. I started using Slackware back at V4 as a hobby, stuck with it for a while but moved away because I perceived that I didn't have enough time for the care and feeding that Slackware needed. That perception was probably more due to my own ignorance than anything else. When I decided to switch from Slackware 9, I went to Debian.

2. I switched back because I really liked the simplicity of Slackware compared to the behemoth that is Debian and its derivatives. Granted, the Debian system is very well done and fills the needs of a zillion users, but I honestly missed working from the command line (a heritage of my 8 bit days.) I found that Slackware really took less care and feeding than I originally understood. I also discovered Slackbuilds, which is a huge advantage in time saving. My needs are pretty simple compared to many (most?) folks here: writing programs for fun and using some applications for operating ham radio. I use C and also FreeBASIC (which works for me on Windows and Linux with no changes to the code) for programming.

3. As I mentioned, Debian and then Linux Mint. I think I started with Debian slink. A big repository, easy package handling and software installation. Later, I switched to Linux Mint when I ran into a problem with one of my radio applications being too out of date in the (at the time) stable Debian distro. Mint has some nice extensions over Debian and Ubuntu (the update manager is pretty handy.) But eventually I decided to go back to Slackware, running Slackware 64 14.2 and very satisfied.

As an aside, I use Linux only as a hobby; I am an electrical engineer and the software packages I need for my work only run on Windows. So I also have a Win10 64 laptop.
 
Old 08-21-2018, 09:24 PM   #45
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,272
Blog Entries: 28

Rep: Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124
I hazard that the Slackware forum is not the best place to ask why persons have stopped using Slackware. It is probably not where such a question would find the audience it seeks.

I've used many distros, some on bare metal and some in VMs.

I can say that Debian and Mageia have long been my second choices after Slackware, but I have always had at least one Slackware box in my house, because no other distro matches the elegant simplicity of Slackware.

I started with Slackware and Slackware taught me to understand Linux. Once you grok Slackware, no other distro will ever intimidate you.
 
2 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
ipv6 stop in slackware 14.0 hyperborea Linux - Networking 5 11-09-2013 04:51 PM
[SOLVED] start-stop-daemon in Slackware? qlands Slackware 6 06-24-2011 04:03 PM
Start/stop apache - slackware konzo Linux - Newbie 4 08-27-2010 07:03 AM
Slackware stop responding... /bin/false Slackware 6 03-12-2004 05:01 PM
Slackware 9: Perminatly stop services? m3kgt Slackware 1 10-23-2003 03:56 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:38 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration