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.
I never found slackware to as be difficult as people say. Maybe because its similar to the old 'pc' world. When I first installed MSDOS on my pieced together 286 I typed fdisk and made partitions then typed setup and went from there, then I tried out slackware later and typed fdisk and made partitions and typed setup and installed it, seemed about the same to me.
1 members found this post helpful.
Click here to see the post LQ members have rated as the most helpful post in this thread.
I would say Slackware and Debian are two of the best distros around also...in my early days of running Linux, they were the only two that installed with less issues then the so-called easy distros for me at the time.
I believe that Slack's upgrade process is one of the best - following the UPGRADE.txt and CHANGES_AND_HINTS.txt results always with working system and certainty, that it remains this way due high level of control over the upgrade process.
Although this makes the installer a thing you see just once. After the system is up, you never need to reinstall the slack, as upgrade just works!
Arch and Debian are my 2 favorites, but it seems...surprising, at the least, that they found Debian faster than Arch.
I can use Slack, but just never been happy with it. Too much manual intervention required, nowadays I just want to punch a key and be up to date. I don't want to have to DO anything myself.
... nowadays I just want to punch a key and be up to date. I don't want to have to DO anything myself.
Fair enough. This is probably the main reason I love Slack as much as I do: I don't punch any keys and remain not up to date, while the OS is just as secure and stable as it was one second after the installation.
Hehe, remaining not up to date would kill me. Main reason I can't use something like Ubuntu more than 2 months after it's released, it gets too outdated for me. I have this incessant need to keep up to date, so found Debian Testing/SID (with lots of experimental anytime a release approaches) and Arch are pretty much the only OS's I can stick with for any amount of time without getting frustrated.
Fair enough. This is probably the main reason I love Slack as much as I do: I don't punch any keys and remain not up to date, while the OS is just as secure and stable as it was one second after the installation.
That is true, it is as secure as right after the installation. In fact, that is true for any distro. But only because you miss the security updates Slackware (or any other distro) offers. It would be more secure than right after the installation if you install them.
Hehe, remaining not up to date would kill me. Main reason I can't use something like Ubuntu more than 2 months after it's released, it gets too outdated for me. I have this incessant need to keep up to date,
Hi, my name is Timothy and I'm an update addict. LOL
Every time I try to cheat on slackware with another distro I wind up running slackware.
I agree that it is easy and quick to get up a functional system, but there is a large gap between 'need' and 'want'. IMHO slackware is the most stable OS I have ever used, but its also the hardest to tweak. I actually enjoy that aspect of it.
This ironically ties in with the "if you learn slack you learn linux". I totally agree, however, my last slackware install was so nice it lasted longer than the hard drive, and so I wind up re-learning the install process.
I believe that Slack's upgrade process is one of the best - following the UPGRADE.txt and CHANGES_AND_HINTS.txt results always with working system and certainty, that it remains this way due high level of control over the upgrade process.
Although this makes the installer a thing you see just once. After the system is up, you never need to reinstall the slack, as upgrade just works!
Is there any advantage to using that upgrade method instead of using Slackpkg?
Quote:
Originally Posted by Timothy Miller
I have this incessant need to keep up to date
I know that feel. I realize that it's not necessary and not always a good idea, but I do enjoy doing it. One thing that was very hard to get used to after installing Slackware was the lack of updates. I'm starting to get used to it though. Using Arch and Debian Testing helped show me that a nice stable system can be nice. Well, I used Debian Testing for a year and only ran into problems a couple of months ago, really.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.