UnfortunateShort

joined 1 year ago
[–] UnfortunateShort@lemmy.world 2 points 1 day ago* (last edited 1 day ago) (4 children)

I just noticed how that Arch is in quotes and "64 bit" was added. Does anyone use 32 Bit Arch for gaming? Is it even possible to run Steam on that?

And why not go with:

Arch Linux (rolling-release) 64 bit

I think there are good kinds of fragmentation (choice and/or competition) and many bad kinds/causes of fragmentation (clinging to abandonware, reinventing the wheel, rejecting reasonable changes, "rewrite it in X-lang", demanding complete control, style/design choices that don't actually matter...)

That's bad and all, but it's only because the dems manipulated everything and everyone /s

[–] UnfortunateShort@lemmy.world 2 points 4 days ago (1 children)

That I can understand, however I want to piont out that this is an Nvidia problem entirely. Wayland works perfectly fine under 2/3 hardware vendors.

Luckily, they finally open-sourced their shit so going forward, this will probably change. But chances are only from the 2000 series on, so it might take an upgrade for many folks...

All I know is that there are VNC and RDP solutions for Plasma and VNC solutions for Wayland in general.

You can autostart anything on any distro by putting the command in a startup script.

[–] UnfortunateShort@lemmy.world 151 points 5 days ago (30 children)

I love how people are complaining about Wayland not being ready or being unstable (whatever that even means, because it's a protocol), while it's the default on both GNOME and Plasma now, which combined probably run on more than 50% of Linux desktops these days.

And not only that, but Cinnamon, Xfce and others want to follow, so very clearly people who know a fair bit about desktops seem to disagree with Wayland being "not ready".

It does not and whatever distro you choose, it will not.

[–] UnfortunateShort@lemmy.world 2 points 6 days ago (2 children)

And yet I never do and it hardly ever does. And if it does, it's more often than not application specific and fixed by loading a snapshot and updating again after a week or so, which is next to 0 effort.

100% agree, anonymized data is pretty much irrelevant to the GDPR. An exception would be if it can be de-anonymized with reasonable means.

[–] UnfortunateShort@lemmy.world 3 points 6 days ago (4 children)

From anecdotal experience I can only tell you that not once have I witnessed a showstopper bug on Arch. I recommend using btrfs and snapshots to really make sure however.

[–] UnfortunateShort@lemmy.world 6 points 1 week ago* (last edited 1 week ago) (1 children)

I'm gonna go with no, because of containerization and permission management. On your computer, any program can do pretty much anything, unless you explicitly take measures against this. On a smartphone, you get a lot of control over your apps. In newer Android versions you can even completely disable cameras and microphones (even if only in software).

I would use a throwaway account and avoid giving Google any personal data tho. Of course they could still figure stuff out, but it's harder and unreliable, not to mention super-duper illegal (at least in the EU), so I kinda doubt they go the extra mile.

[–] UnfortunateShort@lemmy.world 25 points 1 week ago

To add to this, there aren't that many forks (in the true sense of the word) of Arch for the same reason.

 
 

Hey, so I have brand new HDDs I intend to put in a btrfs software RAID. They're Seagate ST4000VX016-3CV104 4TB Skyhawks. Workload is basically write and forget, I will probably never delete a thing.

However I decided to test them first and noticed that after writing about 160 GB, some SMART counters have gone up significantly. Read error rate went from 6.632 to 90.238.872 for example (seemingly all correct by hardware ECC), seek error rate from 143 to 87.661.

Am I reading things correctly? This does not seem like the way healthy drives should behave, does it? It similar on all of them tho. Are they just trash-tier drives they somehow got to work with ECC?

view more: next ›