

Try adding or removing a closing paren. Seems different apps/clients hsndle this differently.
Try adding or removing a closing paren. Seems different apps/clients hsndle this differently.
Yup, there are attscks. Also ddos on Codeberg and the xz-utils backdoor.
I’d say look after your kid and try out Linux a bit later when you have Leisure for it. You can use Linux and Windows in parallel on two computers networked with Samba.
You could try also:
No, I mean hibernate, with the PC turned off. In sleep state, you return to the running kernel/OS, so no possibility to boot into another distro, therefore no risk of filesystem damage.
The crucial thing is that file systems need to be unmounted before they can be accessed by another distribution or OS.
see
https://askubuntu.com/questions/55527/dual-boot-and-sleep-hibernate-issues
firmware updates matter and depend mostly on the chip manufacturer’s support.
Can you give examples for this?
The deeper problem is that the OS Vendors for phones are already adversial. They want to extract as much pesonal data as possible. IMO, that is not really better than having malware on one’s phone.
As I wrote above, for any safe access the file systems need to be mounted read-only (which is not the default). Otherwise, listing or viewing a file or directory already changes its metadata.
Sailfish OS has very long support times and the licenses I got so far are without time limit. IIRC that has changed or might change but still significantly longer than any vendor Android.
Now I am curious. Is this really web-based? Who has tried it? How useful is it?
The other solution is to mount the shared, or borrowed file systems read-only. That works and is safe, but it could suck after a while for being impractical.
Also, just in case that nobody mentioned that already, a good opportunity to learn how to backup and restore your data ;-)
I can only share experience with Sailfish OS: As long as you don’t drop your phone, it will easily last five years and might last eight. It depends of course as well how much you use some of the cancer that the modetn web is. Looking up the Arch Wiki requires a lot less ressources than browsing LinkedIn.
And, this is another reason to use virtual machines, like GNOME Boxes or virt-manager. Put your sweet little Windows sleeping beauty in a VM so that it wakes up without scratches.
Option (4) is safer in the long run because it prevents boot loaders overwriting each other.
Also, dual-booting and accessing the same data in /home IS ONLY SAFE IF YOU DO A FULL SHUTDOWN ON EACH BOOT OF THE OTHER SYSTEM. No hibernate, because hibernate does not unmount file systems.
If you want to keep both running, a VM (for example running in GNOME Boxes) is both safer and much more convenient.
SuSE (nowadays OpenSUSE LEAP / Tumbleweed) was always said to have the best KDE support; they supported it strongly from the beginning. But I think the differences are becoming smaller over time. KDE had fewer big breaking UI changes in the past than GNOME (and these change were putting off some people, which is the cause MATE still exists). Also, being highly configurable it is also a bit more geared to experienced users, while GNOME since Ubuntu days has tried strongly to make things simpler.
Yeah, that was the point I was trying to explain - it is simple, and this can make it a good choice.
You have become an expert, which is half the way to a master who just looks at things and suddenly they become simple for everyone in the room.
Yeah. Makes it also easy to share files between host and VM via NFS, which can be handy when running cooperating desktop systems.
That’s right, virt-manager is a GUI with many, many options. It is more tailored to run several VMs at once, give limited network access into or out of them, and so on.
Also very handy to run tiny, outdated Windows systems with an app you can’t get rid off isolated from the net because it runs your grandpa’s heart-lung machine or so.
Depends on how important it is to keep confidentiality.
Best way to secure already written unencrypted data is probably putting the device into a microwave, and then burning it.
For new data on Linux, LUKS encryption should probably be fine.