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/partbtrfs balance start -mconvert=raid1 -dconvert=raid1 /path/to/btrfs/partIn 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 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
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.
There is hard evidence these checks prevent crime (i.e. smuggling and human trafficking), as well as evasion of judicial measures. So, since these checks will not just go away in the foreseeable future, he needs to provide a better alternative.
Edit: I don’t really get Denmark and Benelux tho. I doubt there is that much going on via these borders, but maybe I’m mistaken? I can see smuggling over their ports could be a problem, but that could be resolved by tightening security there instead of at the borders.
Casual reminder that Politico is owned by Spring SE, which makes it inherently unreliable since it’s held and led by (very) few ultra rich people.
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 finally, there are many instances, where a tool simply 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.
(This is also used for Plasma’s performance profiles, not just GNOME’s)
Eh, in terms of UI and shortcuts, Plasma is very close. If you sit a Windows poweruser in front of Plasma, I’m quite confident they will feel right at home.
That’s actually how I got introduced to Linux. Then I discovered the Settings app. Fast forward: EndeavourOS btw.
Ya know, Signal has been audited multiple times. It’s OSS. IT sec elite has looked at it and says it’s sound. If anything is plausible, it would be your device spying on you rather than Signal.
What’s weird tho is how people think this has anything do with messaging or data privacy. This is about Telegram being used as a public platform. They can’t force Durov to decrypt anything, nor do they need to, because they already know your groups…
This is more likely someone fucking up and not having a second pair of eyes look at the presumed problem than anything else.