The Linux Thread - The Autist's OS of Choice

[prollyanotherlurker]

I completely forgot about Spectre and i didn't know about the hyperthreading vulnerability. Ah well no point spending $30 more for something i don't need. I don't really play PS3 games all that much anyways and i can always pony up for a more powerful system at a later date.

are you going to do anything that actually risks it being compromised? if not it's a literal non-issue.

 

[Hakase Shinonome]

is there any actual downside for older hardware that doesn't need cutting-edge drivers and such

No.

Additionally, any and all CVE's are mostly because of internet access, you're basically indestructible if you rip that ethernet cord out, no lube. Windows XP PCs are still perfectly fine when only dealing with intranet. Needing to update/upgrade your PC is a psyop made up by the elite for you to keep buying the newest goyim hardware. Beyond this, having old drivers and such is only beneficial to others, because old software has the very fun benefit of getting removed for being "too outdated for regular use". Older hardware is also either going down or up in price depending on its age. Some shitty GT710 will clearly only go down in price but something like a HD5750 will only be getting more expensive.

tl;dr
Keep using that hardware of yours for as long as you can.

 

[prollyanotherlurker]

No.

Additionally, any and all CVE's are mostly because of internet access, you're basically indestructible if you rip that ethernet cord out, no lube. Windows XP PCs are still perfectly fine when only dealing with intranet. Needing to update/upgrade your PC is a psyop made up by the elite for you to keep buying the newest goyim hardware. Beyond this, having old drivers and such is only beneficial to others, because old software has the very fun benefit of getting removed for being "too outdated for regular use". Older hardware is also either going down or up in price depending on its age. Some shitty GT710 will clearly only go down in price but something like a HD5750 will only be getting more expensive.

tl;dr
Keep using that hardware of yours for as long as you can.

I have some older stuff, and newer stuff. I use both. The downside I've noticed is the obvious one. Performance. I can noticably see a difference. I get higher clock speeds and more threads from the newer hardware. Better memory speeds. more memory, etc.

 

[Pluciferous]

Speaking of vibes, what is the actual, real, tangible downside to localmodconfig pinning a kernel? And I don't mean LTS, I mean proper kernel pinning to a specific, locally compiled version that does not get updated whatsoever until otherwise specified by the operator? Yes, yes, 200000000 CVEs and LoC per patch o algo, but really, is there any actual downside for older hardware that doesn't need cutting-edge drivers and such?

You will eliminate a bunch of vulnerable code from your kernel, making it more difficult for hackers and malicious nations to compromise your computer. This is widely considered to be a bad idea. [/sarcasm]

 

[Curry Teafag]

is there any actual downside for older hardware that doesn't need cutting-edge drivers and such?

Lack of support for newer codecs, instructions sets, and peripherals comes to mind.

 

[Hannibalistique]

I mean, sure, as long as a) the maintainers aren't malicious themselves b) they haven't been hacked and the chroot compromised without their knowledge c) noone is standing behind them with a rubber hose.

That's why reproducible builds were (are, idk, I don't follow arch anymore) a big thing for arch, with automated independent rebuilder infrastructure etc.
Anyone who uploaded a binary that went from reproducible to non-reproducible (by sneaking in something) would set off a ton of alarms (IRC pings) before it could spread far on the mirrors (or moved out of testing).

 

[prollyanotherlurker]

Speaking of vibes, what is the actual, real, tangible downside to localmodconfig pinning a kernel? And I don't mean LTS, I mean proper kernel pinning to a specific, locally compiled version that does not get updated whatsoever until otherwise specified by the operator? Yes, yes, 200000000 CVEs and LoC per patch o algo, but really, is there any actual downside for older hardware that doesn't need cutting-edge drivers and such?

being too giga is a real concern with that setup.

 

[777-]

So what distro is someone supposed to use if they want something that just works yet doesn't force you into doing everything one way?

 

[hotpocket]

So what distro is someone supposed to use if they want something that just works yet doesn't force you into doing everything one way?

You're giving poorly defined and conflicting requirements. If "just works" means never looking at a console, that's simply not happening on Linux. If "doesn't force you into doing everything one way" means different init systems, Artix and Gentoo give you a choice of those and much else, but it's become common for software projects to assume that you use SystemD and refuse to work if you don't. Flatpak does that, so installing software that isn't included in your distro's repo becomes more complicated as one example for how freedom and choice usually is a trade-off against ease of use. Tutorials can also become more difficult to follow the further your configuration deviates from the norm.
Linux Mint should be a good distro to start learning though.

 

[Ferryman]

So what distro is someone supposed to use if they want something that just works yet doesn't force you into doing everything one way?

istnall gnteoo

Additionally, any and all CVE's are mostly because of internet access, you're basically indestructible if you rip that ethernet cord out, no lube. Windows XP PCs are still perfectly fine when only dealing with intranet. Needing to update/upgrade your PC is a psyop made up by the elite for you to keep buying the newest goyim hardware. Beyond this, having old drivers and such is only beneficial to others, because old software has the very fun benefit of getting removed for being "too outdated for regular use". Older hardware is also either going down or up in price depending on its age. Some shitty GT710 will clearly only go down in price but something like a HD5750 will only be getting more expensive.

Based and TRVE, was mostly just referring to using a perma pinned kernel on a machine that does not need nor can make use of cutting edge developments, i.e. Haswell era. But absolutely correct nonetheless. Core 2 Duo ftw!

 

[The Ugly One]

View attachment 9585473
Almost as if certain someone embraced the use of LLM's in development, and it just so happens that LLM's are pretty good at finding code faults...

I have a chart somewhere, can't find it, but Linux has always had a shitload of CVEs from the beginning, especially at the distro level.

 

[Curry Teafag]

Linux has always had a shitload of CVEs from the beginning, especially at the distro level.

Though, if the device is going to be kept offline and won't run any VMs, most CVEs can be treated as harmless.

I did mention HT because it played a role in my setup where the system is online 24/7 and runs several VMs. Turning off HT mitigated three CVEs on its Skylake CPU that apparently couldn't be mitigated through microcode.

 

[The Ugly One]

Though, if the device is going to be kept offline and won't run any VMs, most CVEs can be treated as harmless.

True, my Gamecube has never been hacked and used to access my bank account.

 

[moocow]

Speaking of vibes, what is the actual, real, tangible downside to localmodconfig pinning a kernel? And I don't mean LTS, I mean proper kernel pinning to a specific, locally compiled version that does not get updated whatsoever until otherwise specified by the operator? Yes, yes, 200000000 CVEs and LoC per patch o algo, but really, is there any actual downside for older hardware that doesn't need cutting-edge drivers and such?

Actual downsides? None. Odds are eventually (like five or six years down the road), some part of your distro will decide it absolutely cannot function without some fancy new feature added by a kernel released after the one you picked, and it'll be up to you to decide whether that part of the distro is worth upgrading for, or whether you can live without it. If shit works now, it'll probably keep working. It's pretty rare for literal greenfield new features to appear in a kernel that become absolutely required for baseline functionality in a linux distro.

But if you're like me, that urge to occasionally test new kernels (and features) anyway will creep in and you'll find yourself building a newer one to test out, and occasionally finding the newer one works fine too so you'll switch to it anyway, and that's almost always "up-to-date enough" to keep even retarded distros happy.

 

[⠠⠠⠅⠑⠋⠋⠁⠇⠎ ⠠⠠⠊⠎ ⠠⠠⠁ ⠠⠠⠋⠁⠛]

That's why reproducible builds were (are, idk, I don't follow arch anymore) a big thing for arch, with automated independent rebuilder infrastructure etc.
Anyone who uploaded a binary that went from reproducible to non-reproducible (by sneaking in something) would set off a ton of alarms (IRC pings) before it could spread far on the mirrors (or moved out of testing).

So what you're saying is that nation state actors will be doing this with the nearly a quarter of Arch packages which do not have reproducible builds, rather than those which do, to avoid attention?

https://reproducible.archlinux.org/

 

[moocow]

So what you're saying is that nation state actors will be doing this with the nearly a quarter of Arch packages which do not have reproducible builds, rather than those which do, to avoid attention?

https://reproducible.archlinux.org/

The smart ones will, yes.

The script kiddies? They'll probably still just target whatever's popular (and/or low-hanging fruit).

 

[Hannibalistique]

True, my Gamecube has never been hacked and used to access my bank account.

To the best of your knowledge anyways.

Phantasy Star Online would never have been exploited if it was written in retard-Haskal (dba. rust).

 

[Trans Fat 41g]

Linux Mint is benefiting from the longer development cycle.

 

[Darkholme's Dungeon]

Speaking of vibes, what is the actual, real, tangible downside to localmodconfig pinning a kernel? And I don't mean LTS, I mean proper kernel pinning to a specific, locally compiled version that does not get updated whatsoever until otherwise specified by the operator? Yes, yes, 200000000 CVEs and LoC per patch o algo, but really, is there any actual downside for older hardware that doesn't need cutting-edge drivers and such?

Does the rest of the system get updated? If yes.
If you made everything built in and not a module, then you're fucked if you left out a feature.
Tool chain drift (hello systemd and docker) is pretty notorious for this.

If you aren't updating not much aside from getting raped by CVEs. Maybe if you plug in software via a USB, etc. But that device shouldn't be accessible from the internet then.

Doesn't stop state level actors but you got bigger issues then.

 

[777-]

the real truth that trannies hate to hear is cves don't matter on a desktop system unless you're a cryptonigger or a pedophile. the real malware is the bloatware and telemetry that comes with "updates"