I’ve been using Mint for a few months now after initially trying Fedora and Kubuntu. Mint has been by far my favorite experience and I’ve even gotten a few people converted to Linux via Mint. Definitely my recommendation for any Linux newbies.
It was my first distro I liked it at the time, but after they killed of the KDE Edition I tried out Manjaro and the rolling release with up to date software just fits my use case much better.
Oh you again, yes Linux supports every normal hardware, and even a lot of crazy ones like Risc-V
On Android the system is bundled with the firmware as it comes from the same people. And for some reason those people dont like providing updates for sane amounts of time, like… 20 years?
haha yes me, no I was wondering about running the latest versions of linux on older machines. are they capable or more limited to older versions just because the age and the older hardware?
But I just may not be able to run the newer releases that come out and continue to come out? if the machine is a tad old? is that what I’m getting? because that’s what im trying to figure out
My gut here is saying you have a mismatched combo of how Coreboot is treating these, and how they are written. From what I’m reading, Coreboot should support Legacy, UEFI, or SeaBIOS, so go set that in the BIOS setup, then make absolutely sure your disks are being written as such (NOT mbr). Ventoy should be the tool to use here for testing different distros out, so good on finding that.
Nearly all hardware support is kept in the kernel until and unless it bitrots to the point of unusability. I’ve had no issues with a 5.10-series kernel on my 2008 laptop, and I don’t expect any issues when I finally get around to upgrading it to 6.x (well, except the usual tedium of compiling a kernel on a machine that weak).
The difference isn’t all that noticeable, to be honest, or at least I’ve never found it so. If you’re using older hardware, you’re going to get an older “experience” anyway. The most user-visible kernel improvements tend to be improvements in hardware support, which is irrelevant if your hardware is already fully supported. However, I don’t do anything fancy with my machines—no full-disc encryption or the like. I usually don’t even need an initram to boot the system. So maybe you would notice something if your machines were more complicated.
(Note that the laptop I mentioned above started out with, um, a 3.x kernel? It gets a new one every year or so. The only kernel changes affecting it that were significant enough to draw my attention since 2008 were a fix in the support for the Broadcom wireless card it carries, and some changes to how hibernation works, which didn’t matter in the end because I basically never did try all that hard to get hibernation working on that machine.)
See I fear this, being stuck to only kernels up to a certain version. Because don’t the older ones lose support and stuff like that? how the heck do you maintain your system if the distro isn’t pushing anymore updates and such?
You’re unlikely to have issues unless an entire architecture loses support from your distro, and if you’re running x86_64, that isn’t going to happen for a long, long time. I’ve never been in a position where I couldn’t compile a new workable kernel for an existing system out of Gentoo’s repositories. The only time I’ve ever needed to put an upgrade aside for a few months involved a machine’s video card losing driver support from nvidia—I needed a few spare hours to make sure there were no issues while over to nouveau before I could install a new kernel.
Note that you can run an up-to-date userland on an older kernel, too, provided you make sensible software choices. Changes to the kernel are not supposed to break userspace—that’s meant to keep older software running on newer kernels, but it also works the other way around quite a bit of the time.
I have never used those tools, I usually just dd the iso to a usb. I am assuming you are on a linux distribution already. I would download a fresh iso and verify the checksum. Then use dd to write to the usb. I use this format, and of course replace the path to iso bit and /dev/sdx (your usb)with what is relevant to your situation. Just open terminal and type
It attempts to copy binaries onto a system on a manner that avoids the single source of truth used for regular installables. So it invites dependency hell.
Is this the one that seems to need a binary running constantly in the vast in-between times when no installation is taking place? That would be a risk.
Never used it. I worked in OS security and don’t need that stress either at work or home.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.