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 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 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…
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.
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.
We have not failed to prevent climate change. We have failed to prevent some climate change. How much more we get depends directly on what we do about it now. And now the best you can do is keeping that in mind when going to vote and spending money.
I used to always have a ChatGPT tab pinned, so I wouldn’t mind. That said, the integration is just plain terrible. To be more precise, the whole experience with the sidebar is terrible. Why can I only have one and not even choose the default one? I need two clicks to get to the assistant, which is one more than just pinning a tab…
In Brave, the integration is so much better. They have a dedicated button (that you can also disable iirc), that opens a sidebar with only the chatbot. Moreover, you can choose from a bunch of models or link your own. You are not constantly at risk of accidentally sending something to it when selecting text, because neither is “AI” the top option in context menus, nor is one opening automatically. AI doesn’t appear in search. And it can even do more (e.g. “summarize this entire page”), while there is also no need to log in.
In short: This seems not thought through at all. And if it was, maybe the reactions would be less negative.
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.
There’s a solution for that tho: Tags. If you have sane (default) tags, you type ‘terminal’ and konsole pops up. And I feel like KDE mostly has that.
What an extremely complicated way to voice a single, vague concern.