This is more likely someone fucking up and not having a second pair of eyes look at the presumed problem than anything else.
This is more likely someone fucking up and not having a second pair of eyes look at the presumed problem than anything else.
It depends on the brand I guess. Some Canon Pixma did immediately worked with my distro, like literally zero setup required. However, it refuses duplexing. It just won’t do it. Not driverless and not with gutenprint, although it lists the specific model, not when setting it as the default, not when setting it per job.
Yet it works on Android no problem.
If I had to do encrypted btrfs RAID from scratch, I would probably:
btfs device add /path/to/mapper /path/to/btrfs/part
btrfs balance start -mconvert=raid1 -dconvert=raid1 /path/to/btrfs/part
In that scenario, you would probably want to use a keyfile to unlock the other disc without rentering some password.
Now, that’s from the top of my head and seems kinda stupidly complicated to me. iirc btrfs has a stable feature to convert ext4 to btrfs. It shouldn’t matter whatever happens outside, so you could take your chances and just try that on your ext volume
(Edit: But to be absolutely clear: I would perform a backup first :D)
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…)
I don’t think that’s really their main strategy anymore. They try to lock you in their ecosystem to make you subscribe to stuff and buy other, sometimes digital stuff.
Google is trying something similar with their 7 years of support for Pixel devices. I think it’s because the development of smartphones (and also computer hardware) has slowed down a lot overall (again, after Apple and AMD shaking it up really well).
Upgrading every year is even less compelling than it used to be, when there were much more significant upgrades.
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.
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.
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.
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.
To add to this, there aren’t that many forks (in the true sense of the word) of Arch for the same reason.
Because they worry about any other weapon? Or the extremely rare case that someone actually has a highly dangerous fire arm? My point is that they can have much less drastic standard procedures (and equipment), because the standard scenario of operation is significantly less threatening.
There are special forces that get involved with the real shit. But the bar for real shit here is someone has any gun.
He probably wasn’t arrested. It sounds like the police handcuffed him while checking whether he was indeed alone and then asked about what he was doing at his computer. After he explained, they asked him to turn off the stream, at which point I would assume he was freed again.
I assume they went on to explain the situation and then questioned him. If there is no evidence of any crime, they will just take his personals so they can contact him on any development. He is the victim of a crime after all.
Isn’t it amazing how you can “SWAT” (from the looks of it that weren’t special forces btw.) someone by knocking on the door, instead of blasting through it and charging in, ready to shoot anything that moves?
That’s something you can do if you don’t have to be afraid of shotguns and full-auto rifles when going into random people’s houses.
Tons of people making Python comparisons regarding indentation here. I disagree. If you make an indentation error in Python, you will usually notice it right away. On the one hand because the logic is off or you’re referencing stuff that’s not in scope, on the other because if you are a sane person, you use a formatter and a linter when writing code.
The places you can make these error are also very limited. At most at the very beginning and very end of a block. I can remember a single indentation error I only caught during debugging and that’s it. 99% of the time your linter will catch them.
YAML is much worse in that regard, because you are not programming, you are structuring data. There is a high chance nothing will immediately go wrong. Items have default values, high-level languages might hide mistakes, badly trained programmers might be quick to cast stuff and don’t question it, and most of the time tools can’t help you either, because they cannot know you meant to create a different structure.
That said, while I much prefer TOML for being significantly simpler, I can’t say YAML doesn’t get the job done. It’s also very readable as long as you don’t go crazy with nesting. What’s annoying about it is the amount of very subtle mistakes it allows you to make. I get super anxious when writing YAML.
tldr: Linux can have driver issues and programs or updates might not work as expected. So anything you can expect from any major OS.
You can reinstall stuff without uninstalling it first (
yay -S <package>
). To add to the other comment suggesting a driver reinstall, you can usedowngrade
to revert back to old versions (and also to keep it fixed till you wanna give it another go, don’t forget if you do so tho!).Moreover, set up snapshots! They provide a very straightforward way to recover from failed updates.
If you are on btrfs, you need: snapper, snap-pac, btrfs-assistant (optional, but provides a GUI and more automation…)
If you are on ext4: timeshift, timeshift-autosnap
Im both cases you need to create a profile for root (
/
), although when it comes to Timeshift I think you need (/ want to) exclude/home
. (On the default btrfs setup, you don’t need to do this, because/home
is it’s own subvolume).