This is more likely someone fucking up and not having a second pair of eyes look at the presumed problem than anything else.
Justice he dicides on and can get away with.
There are some FOSS SMS clients tho. I used to use Simple SMS, but there were no updates for 12 months.
Maybe try Deku SMS: https://github.com/deku-messaging/Deku-SMS-Android
It seems to have at least some traction for what it's worth.
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.
Richtig, und es ist wirklich schade, wenn man sich nicht verwöhnen lässt :(
If I had to do encrypted btrfs RAID from scratch, I would probably:
- Set up LUKS on both discs
- Unlock both
- Create a btrfs partition on one mapper
- Add the other with
btfs device add /path/to/mapper /path/to/btrfs/part
- Balance with
btrfs balance start -mconvert=raid1 -dconvert=raid1 /path/to/btrfs/part
- Add LUKS' to crypttab, btrfs partition to fstab and rebuild/configure bootloader as necessary
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)
Ich finds schön, wenn Kommentatoren sich einfach aufrichtig besorgt zeigen, ohne direkt auszurasten und mit Ferndiagnosen um sich zu werfen :)
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
Ich will nicht lügen: In der Sekunde, wo du eine öffentliche Toilette betrittst, ist mit das letzte, was ich auf meiner Hose will, deine Schuhsohle.
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.
Ein Glück haben wir dafür das Dienstwagenprivileg behalten und Bahn und Brücken trotzdem nicht repariert 🟡🙄
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.
ich🐱iel
Anwohner in Bremerhaven hörten Krach aus der Nachbarwohnung. Dort öffnete jedoch niemand die Tür - und sie riefen die Polizei.
Endlich mal fickend qualitative Nachrichten.
> Zwei Katzen haben in Bremerhaven einen Einsatz der Polizei und Feuerwehr ausgelöst. Wie die Beamten mitteilten, alarmierten Anwohner eines Mehrfamilienhauses in der Nacht zu Mittwoch die Einsatzkräfte, weil laute Geräusche aus der Nachbarwohnung sie um den Schlaf brachten. Vor Ort öffnete den Angaben zufolge niemand die Tür, so dass die Feuerwehr sie aufbrechen musste. In der Wohnung fanden die Polizisten aber keine Menschen - sondern zwei Katzen, die es offenbar geschafft hatten, den Staubsauger einzuschalten. Die Beamten schalteten den Staubsauger aus und "ermahnten die beiden Vierbeiner mündlich, sich für den Rest der Nacht ruhig zu verhalten", so die Polizei weiter.
Seagate Skyhawk HDDs faulty / low quality?
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?