My biggest worry for this is, there’s probably dozens of black hats out there that have found some very large exploit for Windows 10, and are holding off on abusing it until the day Microsoft ends support.
Currently, my plan is to make a partition for Linux Mint, set up dual boot, see how much of my daily computer obsession I can execute through there, and then try to slowly transition while slowly moving stuff from Windows. (I am vaguely worried I’ll run into that Windows issue where files accessed from outside the OS login are security-restricted. That has even screwed up my Windows reformat fixes)
Mint’s sweet I switched from 10 a few months back. Biggest difference is getting use to the different file system, only 2 games have been unplayable (didn’t try to make them work tbh).
Microsoft took a big bite out of GRUB, which is the utility that your motherboard uses to dual boot OSes. A Windows update basically borked it and set Windows as the mandatory default OS. It basically makes it so your motherboard can’t properly identify your Linux install(s).
Luckily, you can fix it directly in Windows Command Prompt. But still, it’s a dirty trick that Microsoft has been using recently. Windows has historically been a bad neighbor for other OSes, (for instance, the Secure Boot Module is basically an attempt to make booting other OSes difficult,) but this was the first time in recent history that they have outright prevented another existing OS from booting.
Just keep regular full system images (as you should be anyways, as part of your 3-2-1 backup plan), and you’ll be fine as you can just restore an image if everything gets broken.
NTFS file reading and writing is reasonably well supported under Linux, though exFAT or native filesystems are preferable. Actually finding software that will understand your files is one level removed, and getting equivalent or even the same software running is another level still. e.g. reading MS Office documents - LibreOffice is pretty good at that. For games, Steam and Proton have a lot of that covered.
If all you do is on websites, most if not all of the usual web browsers are available and work indistinguishably.
That said, I will leave you with these three words: Backups. Backups. Backups.
I’m not worried about interpreting the NTFS filesystem or individual files of given formats. Mainly, I’m worried about a Windows security-level problem I’ve had where Windows restricts access to whole directories based on user-level permissions, since the old “user” that owned them on a given operating system has been obliterated. It’s an issue I’ve had even when reinstalling Windows to the same computer.
As far as I know, Linux ignores NTFS permissions when given raw access to a disk, or rather, acts as thought it’s SYSTEM or some other high-level user, working around anything Windows might have set.
Worst case, you could still move your important files to an exFAT partition (or into an archive) where permissions don’t apply.
As far as I know, Linux ignores NTFS permissions when given raw access to a disk, or rather, acts as thought it’s SYSTEM or some other high-level user, working around anything Windows might have set.
I think that was the case for ntfs-3g.
I’m not certain that’s the case anymore with the new kernel NTFS driver, though I havent tested it. If it isn’t, it should be correctly handling the file premissions.
LMDE6 still uses ntfs-3g as far as I can tell, so I’m going to assume that regular Mint does too. lsmod reports nothing like ntfs, and the tried and tested, if no longer developed, ntfs-3g suite is installed.
Things might change as and when the kernel driver is more stable for writing. I’m sure more bleeding-edge distros are already running the kernel driver, but then, those who run those distros are deep into Linux and NTFS is not really something they deal with regularly.
I believe it actually is used in regular Mint (the Debian kernel doesn’t include it, but it looks like Ubuntu’s and Mint’s do). But yes, I suppose it is still in the process of being adopted by various distributions.
My biggest worry for this is, there’s probably dozens of black hats out there that have found some very large exploit for Windows 10, and are holding off on abusing it until the day Microsoft ends support.
Currently, my plan is to make a partition for Linux Mint, set up dual boot, see how much of my daily computer obsession I can execute through there, and then try to slowly transition while slowly moving stuff from Windows. (I am vaguely worried I’ll run into that Windows issue where files accessed from outside the OS login are security-restricted. That has even screwed up my Windows reformat fixes)
Mint’s sweet I switched from 10 a few months back. Biggest difference is getting use to the different file system, only 2 games have been unplayable (didn’t try to make them work tbh).
might be better to separate drives, windows has been known to fuck up Linux partitions recently.
This sounds like something I should be wary of, but it’s the first I’m hearing of it. Any other info?
Microsoft took a big bite out of GRUB, which is the utility that your motherboard uses to dual boot OSes. A Windows update basically borked it and set Windows as the mandatory default OS. It basically makes it so your motherboard can’t properly identify your Linux install(s).
Luckily, you can fix it directly in Windows Command Prompt. But still, it’s a dirty trick that Microsoft has been using recently. Windows has historically been a bad neighbor for other OSes, (for instance, the Secure Boot Module is basically an attempt to make booting other OSes difficult,) but this was the first time in recent history that they have outright prevented another existing OS from booting.
https://arstechnica.com/security/2024/08/a-patch-microsoft-spent-2-years-preparing-is-making-a-mess-for-some-linux-users/
I haven’t booted into Windows since
It typically happens during updates. People have reported their grub screwing up. If you’re able I would honestly suggest separate drives
only anecdotes unfortunately.
Just keep regular full system images (as you should be anyways, as part of your 3-2-1 backup plan), and you’ll be fine as you can just restore an image if everything gets broken.
My what now?
PR nightmares will keep significant exploit fixes coming. Microsoft isn’t that stupid.
NTFS file reading and writing is reasonably well supported under Linux, though exFAT or native filesystems are preferable. Actually finding software that will understand your files is one level removed, and getting equivalent or even the same software running is another level still. e.g. reading MS Office documents - LibreOffice is pretty good at that. For games, Steam and Proton have a lot of that covered.
If all you do is on websites, most if not all of the usual web browsers are available and work indistinguishably.
That said, I will leave you with these three words: Backups. Backups. Backups.
I’m not worried about interpreting the NTFS filesystem or individual files of given formats. Mainly, I’m worried about a Windows security-level problem I’ve had where Windows restricts access to whole directories based on user-level permissions, since the old “user” that owned them on a given operating system has been obliterated. It’s an issue I’ve had even when reinstalling Windows to the same computer.
As far as I know, Linux ignores NTFS permissions when given raw access to a disk, or rather, acts as thought it’s SYSTEM or some other high-level user, working around anything Windows might have set.
Worst case, you could still move your important files to an exFAT partition (or into an archive) where permissions don’t apply.
I think that was the case for ntfs-3g.
I’m not certain that’s the case anymore with the new kernel NTFS driver, though I havent tested it. If it isn’t, it should be correctly handling the file premissions.
LMDE6 still uses ntfs-3g as far as I can tell, so I’m going to assume that regular Mint does too.
lsmodreports nothing like ntfs, and the tried and tested, if no longer developed, ntfs-3g suite is installed.Things might change as and when the kernel driver is more stable for writing. I’m sure more bleeding-edge distros are already running the kernel driver, but then, those who run those distros are deep into Linux and NTFS is not really something they deal with regularly.
I believe it actually is used in regular Mint (the Debian kernel doesn’t include it, but it looks like Ubuntu’s and Mint’s do). But yes, I suppose it is still in the process of being adopted by various distributions.