Is Slackware easier to use now than it was 16 years ago?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yes, it did, in release 8.1, when the current package naming convention came in (7.x and 8.0 still used the 8+3 filename format) and thus enabled real updating.
You are correct, but I was referring to the appearance and interface of the installer.
I would say yes. I started with Slackware 7.0 way back in December 1999. Back then I only had dialup internet access so buying a CD set was essential. My current full installation was in 2009. It's a lot easier to use Slackware from version 13.0 onwards compared to versions 7.0 to 10.0.
Last edited by mats_b_tegner; 08-11-2019 at 08:51 AM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Rep:
The first Slackware CD I purchased was dated March 1995.
Over the years I don't believe the installation procedure has changed, much, but a few things
have been made easier.
By version 13, we finally had automatic mounting of removable media. Long, long, long overdue!
Then xorg became easier, but I still do it the "old fashion way."
There are probably several other things that have "improved" over the years, but the only other item that comes to mind is NetworkManager. Oh, and PulseAudio. Some people like them, some don't. They both "just work." No fuss, no muss.
YMMV.
Last edited by cwizardone; 08-11-2019 at 10:03 AM.
Reason: Typo.
The first Slackware CD I purchased was dated March 1995.
At that time I didn't have a CD-rom drive (486dx2, dual drive floppy (5.25 and 3.5") and 540 MB disk with NO room for expansion and NO USB or so yet for external drives), so up to and including Slackware 4.0 I downloaded the separate floppy contents (at work!).
BTW: that 486 was my "machine at work" at the time, at home I still had "only" a 286.
Several years later I bought my first Pentium (/60) which did have a CD-rom drive (sbpcd interface) and installed Slackware 7.1 on it (image downloaded and burned on another machine at work).
I still got the complete (and updated) 4.0 tree and the 7.x iso images.
When I first started using Linux in 2004 or thereabouts, I was told that Slackware was the only Linux you installed from floppies.
Hello hazel,
Interesting!... though a bit confusing since even OS/2 Warp 3 circa 1994, though still possible to install from some ~30 floppies, was preferred to be installed via 3 floppies that could be easily altered for variables and then it asked for the CD if one chose the CD version boot disks. By 1996 when OS/2 Warp 4 was released, it received considerable flack for not having a CD-only installer with no floppies required. IBM apparently preferred the flexibility of having an easily alterable environment and never officially released a CD-Only install. eComStation took over OS/2 and the first thing they did was go CD-Only in 2001. By 1998 it was really all about Opticals, at least here in the US..
In 2004, Slackware had released v10, a very solid release btw (I kept a 10.2 machine running up until v13 was released), and though floppy images were available, I certainly didn't use them by that late date. Right around that time/version the initial array of needed installer kernels would no longer fit on a single floppy, unless you chose one specifically for a hardware environment. By 2007, when v12 was released the array of specialized kernels was no longer needed when the "huge" kernels were released reflecting that extremely few PC OEMs even offered floppy drives anymore. On my end I still used floppies for deep level stuff but by 1999 I had sold even my Zip drive since it was obvious that Optical drives were going to be the winner for some time, although I did entertain the possibility of Magneto-Opticals for a time.
Just a few weeks ago I tossed out my last machine with a floppy drive in it, finally admitting to myself I hadn't used a single floppy in a decade. Now what do I do with some 1000 3.5 inch disks?
I knew people from other distros consider Slackware .... ummm... "quaint" but it ain't. I didn't know it was considered an antiquity.
In 2004, Slackware had released v10, a very solid release btw (I kept a 10.2 machine running up until v13 was released)
My old (year 2000) Dell Pentium III system still is running Slackware 10.2 (it doesn't have the capabilities, especially RAM, to run newer releases and it's not connected to the internet anyway).
When I first started using Linux in 2004 or thereabouts, I was told that Slackware was the only Linux you installed from floppies.
No, version 10 (released in 2004) wasn't installable (although it WAS bootable from a 3.5" floppy) from pure floppies anymore. Somewhere between 7.1 and 8.0 the change was made to not split every category into separate floppy-sized directories:
I find Slackware to be the easiest distribution there is, because it doesn't get in the way of old school users. I have much more difficulty with so called "easy" distributions because I have to circumvent so much crap :-)
(for example, you wouldn't recognize my Manjaro setup with all the work I've done to it)
I would love to see an example of an old /etc/rc.d/rc.module and xorg.conf file so that I can appreciated that I don't have to edit them. Though that depends on how involved they were, commenting out the odd line doesn't sound too hard.
Unlike most of the more experienced Slackware users here in 2003 I would have still been with Windows (whichever version was out then) with Ubuntu Breezy Badger coming to me in 2005. But it is very interesting to hear the old stories
My old (year 2000) Dell Pentium III system still is running Slackware 10.2 (it doesn't have the capabilities, especially RAM, to run newer releases and it's not connected to the internet anyway).
Just FTR until about 2 years ago I had an ancient Sony Vaio PII 433MHz laptop maxed out at 512MB RAM running Slackware 13.37. It was agonizingly slow to boot but once up it was slow, but not at all painful since the greatest bottleneck then is network bandwidth and graphics settings. If your box isn't involved in internet, then, if configured right, 512MB is not a huge handicap for OpSys version. Only how fast your graphics can paint a page might be, but the most RAM intensive work will be similar on 10.2 compared to most newer releases. The version footprint is very similar, almost identical or can be configured so.
I can't recall how long I've been using Slackware now, but I think it was around the time Slackware-8.0 was released. I had been using OS/2 Warp quite happily, but when support for that was dropped, I decided to try something else. There was a Red Hat release on a magazine disk, so I tried it and got absolutely nowhere with it! Then I found a cover disk with VectorLinux (based on Slackware), and found that very easy to live with compared to Red Hat. After a year or so on Vector, I decided to stop messing round with a clone, and try the real thing. Never had a problem, and never looked back.
Occasionally I will install Mageia for a family member or friend who is not computer literate. It is easy to live with if you are just a simple user, but if you have a problem or want a specific piece of software that isn't in their repository, it can be a pig! And I don't know if its just me, but I have never managed to successfully install any of the 'buntus! Slackware, no problem! 'buntu, fail every time!
So no, I don't think Slackware has become easier to install, because I've never had a problem installing it in the first place!
I find that installation of any opsys is quite routine if one plans and creates partitions ahead of time and labels them. Not every opsys or distro displays partition labels (Slack doesn't unless you run cfdisk) but it helps on some though just knowing exactly what partition to install to and then which will get the bootloader avoids many, many pitfalls. Slackware's installer for me is just the best.
@pchristy - Wow! another OS/2 geek! Hiya!Were you a fan of Clear and Simple? and did you ever do emx runtimes and install Enlightenment on Warp?
There were SlackBuilds those days (that's how Slackware packages are built anyway), there wasn't slackbuilds.org as it is these days.
Hardware is easier to set up and running now.
Other than that there is not much difference. Memory footprint is larger but again, the kernel is larger these days.
So it's neither noticeably easier, nor noticeably harder to use. Maybe harder to maintain in some parts (Firefox for instance with its mania of reinventing the wheel every 3 releases, GTK+3 the same breaking compatibility with theming and changing the API every couple months, things like that. Not really Slackware's fault, but upstream). I think that's why Patrick removed GNOME.
These days I'm mostly using Tor Browser for everyday browsing, not because it's inherently more "secure", but because it's more stable (read, the UI tends to look the same without wild redesigns), than Firefox.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.