SoylentNews is people
SoylentNews
If you have gained some Linux skills after using Ubuntu for some time, you may try switching to these distributions to explore the world of Linux distributions further.
Ubuntu is one of the best Linux distributions for beginners. It's an excellent platform for people new to Linux. It is easy to install, has tons of free resources available along with a massive list of applications available for it. https://itsfoss.com/distribution-after-ubuntu/
This discussion has been archived.
No new comments can be posted.
Discussion: Which Linux Distribution to Use After Ubuntu?
|
Log In/Create an Account
| Top
| 127 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Love is the delusion that one woman differs from another.
-- H. L. Mencken
(Score: 2) by leftover on Saturday March 24 2018, @05:54PM (5 children)
Slack '96 for my first time. It was an effort but I learned a lot. Using KDE neon now and finding it to be ... workable. Getting stretched between too-old this's and too-new thats repairing and rebuilding various CAD/CAM tools for my own use. The biggliest problem, IMHO, is the lack of definitive choice. I do not get to pick one initialization system, I am forced to use them all simultaneously. It seems like everything that has ever been in the history of BSD and Linux is still actively used. My most frequent gripes are too few cross-library APIs and too many individual library APIs that change with every minor version. I would like to choose, for example, how I want BLAS operations to be performed -- SMP or GPU or MPI or whatever -- and have that choice dynamically apply to everything that uses BLAS operations. As things are right now, I need to concurrently track all the various libraries that my applications use and rebuild entire application stacks whenever one library makes a significant change. I have no choice, given the list of applications I need to use.
To tie this issue back to the topic of distributions: this was what I determined to be my underlying motivator for constantly examining different distributions. It isn't a distribution issue at all since it affects all of them nearly equally. Same with boot and initialization, X itself and all the widget libraries (fixing something in Tkinter right now), sound (how many different and conflicting packages do we really need to make a machine with a dozen Xeon cores play music almost as well as an old MP3 clip-on?) ad infinitum
I would venture that a goodly percentage of us looking for the next distribution are actually being driven by this issue. No one distribution can possibly fix it for the general case. A distribution based on a desktop environment would appear to have a chance of success for 'normal' office desktop use. This is why I am trying KDE neon and the jury is still out on whether it can overcome the ubuntu base and the increasing fragmentation within KDE/Plasma. Trying to even define an "engineering workstation environment" seems remote.
Bent, folded, spindled, and mutilated.
(Score: 2) by Azuma Hazuki on Saturday March 24 2018, @06:07PM (4 children)
I'd define that as "minimal and stable." And ideally "without bloody SystemD." Devuan Jessie or Slackware might be good, maybe Void if you don't mind rolling release.
I am "that girl" your mother warned you about...
(Score: 2) by leftover on Saturday March 24 2018, @08:53PM
Agreed, as far as they go. That still leaves all of the application + libraries logjam up to the end user. I am tired of spending more time repairing tools than using them. When I find myself wistfully remembering the productivity of dividers and straightedges I know it is time to take a break.
Bent, folded, spindled, and mutilated.
(Score: 2) by Gaaark on Sunday March 25 2018, @06:45PM (2 children)
Looking at the slackware site, it looks like slack is all but dead? Released 14.2 in 2016?
Too bad.
--- Please remind me if I haven't been civil to you: I'm channeling MDC. ---Gaaark 2.0 ---
(Score: 2) by RS3 on Friday March 30 2018, @01:44AM (1 child)
No no, Slackware doesn't work like that. I don't know how/why they choose version numbers, but you can sort of ignore them.
I don't know the official policy for how far back they go, but older versions are kept updated, found in "root-name"/patches/packages.
I just download them to some directory, "upgradepkg *txz", and it figures out what to do. As with many distros, you have to look for "(whatever).new" files, which are usually /etc startup and config stuff. It can be updated daily. (ftp root)/slackware-current/ChangeLog.txt tells you what's been updated, and it can happen daily, several times a day, or every few days- all depending on package source code releases.
But also, Slackware can be used as a rolling-release. Slackware-current (and Slackware64-current) will have the newest stuff, and simple wget scripts will get the latest, and "upgradepkg" will do the obvious thing.
My favorite running/working install is a 14.1 (updated). I recently did a 14.2 and had some problems, like xorg.conf, which I fixed, but still have some annoying odd problems with xterm (that I haven't spent much time trying to fix).
I've been running Slackware since about 1994.
(Score: 2) by RS3 on Friday March 30 2018, @01:46AM
ftp://ftp.slackware.com/pub/slackware/slackware-current/ChangeLog.txt [slackware.com]