Because distros from the Debian family are more popular, any random help article aimed at beginners is likely to assume one of those distros. (If you know how to map from apt to rpm, you’re probably not a beginner.) Plus, I don’t trust Red Hat, who have a strong influence on Fedora.
(Note that I don’t generally recommend my own distro—Gentoo—to newcomers either, unless they have specific needs best served by it.)
Even better: “#1 in the count y” with a damaged area right before the y. Missing letter or just bad kerning? No one will be able to tell until after they taste the pizza! 😜
That would gum up the belt on the sander, which surely is not responsible for the thumbnails.
If it were an Itanium, the OP would know it. They’re not common (and I doubt Puppy would have booted on such a system—it isn’t compatible with x86).
Also, support for that arch is being dropped from the Linux kernel as of 6.7.0, so looking for a supporting distro would be a fool’s quest (Gentoo still technically offers Itanium packages, but they’re on the way out.)
I agree that Gentoo will probably work, as it still has functional i486 support. Be aware that you may be spending a lot of time compiling if you go that route and don’t have a second, faster machine to use for distcc or the like.
As for the nvidia card, the proprietary driver won’t work for something of that age. Check the supported cards in Nouveau (and maybe even the really old drivers for prehistoric cards). In a pinch, the vesa driver should work. Good luck.
Gnome and other desktops need to start working on integrating FOSS
In addition to everything everyone else has already said, why does this have anything to do with desktop environments at all? Remember, most open-source software comes from one or two individual programmers scratching a personal itch—not all of it is part of your DE, nor should it be. If someone writes an open-source LLM-driven program that does something useful to a significant segment of the Linux community, it will get packaged by at least some distros, accrete various front-ends in different toolkits, and so on.
However, I don’t think that day is coming soon. Most of the things “Apple Intelligence” seems to be intended to fuel are either useless or downright offputting to me, and I doubt I’m the only one—for instance, I don’t talk to my computer unless I’m cussing it out, and I’d rather it not understand that. My guess is that the first desktop-directed offering we see in Linux is going to be an image generator frontend, which I don’t need but can see use cases for even if usage of the generated images is restricted (see below).
Anyway, if this is your particular itch, you can scratch it—by paying someone to write the code for you (or starting a crowdfunding campaign for same), if you don’t know how to do it yourself. If this isn’t worth money or time to you, why should it be to anyone else? Linux isn’t in competition with the proprietary OSs in the way you seem to think.
As for why LLMs are so heavily disliked in the open-source community? There are three reasons:
Item 1 can theoretically be solved by bigger and better AI models, but 2 and 3 can’t be. They have to be decided by the courts, and at an international level, too. We might even be talking treaty negotiations. I’d be surprised if that takes less than ten years. In the meanwhile, for instance, it’s very, very dangerous for any open-source project to accept a code patch written with the aid of an LLM—depending on the conclusion the courts come to, it might have to be torn out down the line, along with everything built on top of it. The inability to use LLM output for open source or commercial purposes without taking a big legal risk kneecaps the value of the applications. Unlike Apple or Microsoft, the Linux community can’t bribe enough judges to make the problems disappear.
Ships with Gentoo by default, since you actually need a nongraphical editor there and nano is easier to learn than vi or emacs.
They’re unlikely to do worse than my laptop from 2008, and it’s perfectly usable under Linux (bit of a lag when starting up large programs, that’s all). As has already been said, go for a lighter desktop environment (XFCE, LXQT, Mate, TDE) unless these machines were high-spec’d for their era. For the oldest machines, you might want to consider installing Puppy Linux rather than one of the more mainstream distributions, since Puppy specializes in old x86-family hardware.
Some of them throw up their hands and reinstall at the first sign of a problem. The rest get someone else to do the “hard” part for them, in my experience. They hand it over to the Unofficial Repair Person Paid in Beer and Pizza, who does the command-line stuff, registry editing, etc. Or they get an official repair person. Less than 10% of the Windows-using population does their own fixes.
One thing no one seems to have touched on yet: distros have philosophies—guiding principles that affect what packages they have and how they’re presented.
For instance, Debian is strongly open-source-centric. Closed-source software is not normally found in their main repository (even when it would be useful to put it there, like some drivers).
Gentoo, on the other hand, is all about user choice. You’re expected to choose for yourself whether you want to use systemd or OpenRC, X or Wayland, which DE (if any) you want to use, and which features you do or don’t want compiled into your software. However, Gentoo is quite happy to include closed-source software in the main package repository, because using it is also a choice that some people prefer to make.
Red Hat, Arch, and Slackware (to name the remaining major foundational distros) also have their own philosophies. Some descendant distros retain their parents’ principles, while others discard them and develop a philosophy of their own (Ubuntu doesn’t have Debian’s Open Source Uber Alles tendencies, for instance).
I prefer mplayer—novel-length man page and all—for video, but there’s nothing innately wrong with VLC. I did try it, a very long time ago, but it felt too GUI-oriented for my taste back then.
(I can think of exactly two times mplayer has failled to play a file I presented it with, and in both cases it was my own fault for not compiling in support for that codec. However, the man page is justifiably frightening.)
I have a laptop of that era (2008 HP Pavilion, Athlon64x2, 2GB RAM, 100GB HDD). It runs the Trinity Desktop Environment, which works just as well now as it did when that laptop was a flagship machine. (Updating a Gentoo system running on a machine that old is a bit time-consuming, mind you, but that isn’t the DE’s fault.)
I’ve tried several of the other lighter-weight DEs—XFCE, LXDE, Lumina, Gnome2 before it became MATE—but TDE does what I need it to do, and (just as importantly) the development team prefers to work on features and compatibility rather than tearing out things that still work or forcing new paradigms that don’t really make sense for my use case onto me. It’s there, it’s solid, and I’ve already learned its quirks, so I can save my brain cells for learning useful features in other programs rather than having to figure out where the control for some bit of the GUI ran off to this time. Why would I use anything else? The thing I want most from my DE is for it to stay out of the way and not keep me from using other software.
(Plus, Konqueror may no longer be useful as a web browser, but it’s still a better file manager than, say, Thunar, which I found to be a pain in the arse when I tried XFCE.)
Rolling-release Linux distros such as Arch, Gentoo, and OpenSUSE Tumbleweed constantly release the latest updates, but they’re not used in businesses.
So some businesses decided that monolithic releases were more important than being able to get the latest upstream vanilla kernel version, and somehow that’s the fault of “all Linux kernel vendors” (including rolling-release distros, since there was no attempt to qualify “all”) and not the businesses’ decisions about tradeoffs?
Delete all the code. Then you’ll have no bugs.
should still already choose their sexuality
Sexuality is not a choice, any more than your skin colour is a choice.
To echo others here, you really need to kill the driver. There are a couple of different kernel modules that might be involved, depending on exactly how your touch panel is connected to the rest of the system. Software that has no specific touch support will likely treat your renegade hardware as a mouse, rather than ignoring it.
You may be able to unbind the driver from the device, see this discussion on stackexchange.
Dude. I actually have sources for most of my installed packages lying around, because Gentoo. Do you know how much space that source code takes up?
Just under 70GB. And pretty much everything but maybe the 10GB of direct git pulls is compressed, one way or another.
That means that even if your distro is big and has 100 people on development, they would each have to read 1GB or more of decompressed source just to cover the subset of packages installed on my system.
How fast do you read?
Does a WinNT clone count as “truly different”, though? Maybe Haiku would have been a better choice for that.
Red Hat’s interests often don’t seem to be aligned with those of the average user. The result is that they push for the adoption of software and conventions that make things better for businesses running RHEL, but worse for almost everyone else. This goes back a long way, and makes me question the long-term suitability of any distro Red Hat is involved in for any user who is not paying them for support. It’s the pattern that bothers me, not any single event (and yes, part of that pattern does arise from the fact that they’re a for-profit corporation).
It’s the sort of thing that many people won’t really care about, and if the alternative was Microsoft or even Canonical (which is prone to weird fits of NIH and bad monatization ideas), then fine, I would go with Red Hat. Still, I would recommend a community distro above anything that a corporation has its fingers in.