Personal computing discussed
Moderators: renee, SecretSquirrel, notfred
just brew it! wrote:No distro is problem free, and no one distro is right for all Linux users.
anotherengineer wrote:I can't really say since I am a windows user........but my moms old pc had XP, and between her and all the grandkids on it, things were getting messed up, plus no longer supported.
Put Linux Mint on it and seems to be good so far (from a guy with 0 Linux and 0 CLi experience), not sure if it was Mate or Cinnamon, looks like a Mac gui. Was a bit of a learning curve with the gui and how things were named, but managed to get through it, and even got the HP printer installed lol. (no webcam though)
I know how the pro Linux people love the power of the CLi, but until Linux gets to the point where there is a truly dumbed down desktop version where everything is just a double click, I can't really see it gaining "real" market share. And that's too bad, cause then it would get more support, be more compatible and then there would be a "real" alternative to windows for the layman windows user.
w76 wrote:Ubuntu, Mint, and a couple others all just gave me grief. Don't know if the blame was with them or some element of the unRAID OS that was playing host to them, but didn't really matter. Manjaro just worked.
Flatland_Spider wrote:Fedora, RHEL/CentOS, Scientific Linux. Red Hat has a really good release engineering teams, and their work is solid.
anotherengineer wrote:I know how the pro Linux people love the power of the CLi, but until Linux gets to the point where there is a truly dumbed down desktop version where everything is just a double click, I can't really see it gaining "real" market share. And that's too bad, cause then it would get more support, be more compatible and then there would be a "real" alternative to windows for the layman windows user.
boing wrote:Manjaro. Least issues and those I've had were fixable.
With Mint, Ubuntu, Debian I suffered a far worse dll-hell equaivalent with ppa's and repositories than Windows ever gave me.
boing wrote:With Mint, Ubuntu, Debian I suffered a far worse dll-hell equaivalent with ppa's and repositories than Windows ever gave me.
just brew it! wrote:RHEL (and downstream derivatives) are certainly solid, but Fedora often feels half-baked and the short support cycles for each release are inconvenient. Fedora == too much churn for my tastes.
anotherengineer wrote:I know how the pro Linux people love the power of the CLi, but until Linux gets to the point where there is a truly dumbed down desktop version where everything is just a double click, I can't really see it gaining "real" market share. And that's too bad, cause then it would get more support, be more compatible and then there would be a "real" alternative to windows for the layman windows user.
morphine wrote:(Don't get me started on Debian - though not for stability reasons)
DrDominodog51 wrote:morphine wrote:(Don't get me started on Debian - though not for stability reasons)
Do you not like Debian for the toxic dev community or is it something else?
morphine wrote:DrDominodog51 wrote:morphine wrote:(Don't get me started on Debian - though not for stability reasons)
Do you not like Debian for the toxic dev community or is it something else?
Debian: security through obsolescence.
The software versions are often so absurdly old that they stop being useful. Yes, and the community is particularly penis-shaped.
whm1974 wrote:morphine wrote:Debian: security through obsolescence.
The software versions are often so absurdly old that they stop being useful. Yes, and the community is particularly penis-shaped.
That is why I only used it for a short time before dumping it.
--Debian security FAQ (https://www.debian.org/security/faq)Q: Why are you fiddling with an old version of that package?
The most important guideline when making a new package that fixes a security problem is to make as few changes as possible. Our users and developers are relying on the exact behaviour of a release once it is made, so any change we make can possibly break someone's system. This is especially true in case of libraries: make sure you never change the Application Program Interface (API) or Application Binary Interface (ABI), no matter how small the change is.
This means that moving to a new upstream version is not a good solution, instead the relevant changes should be backported. Generally upstream maintainers are willing to help if needed, if not the Debian security team might be able to help.
In some cases it is not possible to backport a security fix, for example when large amounts of source code need to be modified or rewritten. If that happens it might be necessary to move to a new upstream version, but this has to be coordinated with the security team beforehand.