Many people do dual drives, but if you install linux second and it is a distro thay uses grub with probe foreign OS them you don’t really need two drives. make space on windows drive, in the linux installer create another boot partition, root and home. You set bios to boot Linux grub. Grub will launch and give you linux or choice to chainload to Windows. Windows is unaware it is getting kicked off by grub so the Windows and Lunux boot partitions leave each other alone. i can’t vouch for every distro letting you setup like this but this is how my OoenSUSE has been since 2017
Also, I’d say install Windows first, then Linux. Windows assumes it’s the only OS in the universe and tends to steamroll over the whole boot setup, so I’ve found it much easier to just let Windows do whatever it wants first, then fix it with Linux afterwards.
Yes. But since we’re in Linux land, you may be able to replay the journal and un-dirty your disk by mounting with the ntfs3 driver listed here docs.kernel.org/filesystems/ntfs3.html, or you could try using ‘ntfsfix -d [your device]’ from the ntfs-3g package to clear the journal and the dirty bit, although whatever the last operation was on the filesystem may be left in an incomplete state since the journal is not replayed.
I haven’t done it in a while, but with virtualbox I have used direct disk access by creating a special vmdk with vboxmanage to give a VM access to real partitions.
I did this way back in the day on my Mandrake installation with a 1.44" floppy. Only tricky part was that I had to run cp from the floppy instead of from normal $PATH as I’d wiped out /bin.
Debian is my go-to. So long as you’re already comfortable with Linux, you can get gaming working with a tiny bit of elbow grease… and unlike some other distros, Debian is rock-solid.
I’m guessing that you’ve been using kernels from packages provided by your distribution and its maintainers simply haven’t decided yet that Wayland is used wide enough to put things it needs into default kernel. But that’s just a matter of time.
On distribution I use, for example, I did not have to compile my own kernel when I decided to check Wayland out. But that’s only because kernel package maintainers of my distribution have decided to enable it earlier
Follow the blogs for Year of the Voice initiative from Home Assistant. There will be lots of pointers for the journey they’ve taken this year getting TTS and STT working for HA.
All I know is wine-mono and wine-gecko doesn’t come in any default package lists on apt that you get on Linux Mint (which should include Debian and Ubuntu packages), not sure if they exist on some other mirror list somewhere but it didn’t seem like it, while on Arch I got them directly from Extra (not even AUR).
Well you technically don’t need mono or gecko, especially not if you’re just going to use Steam Proton to play, but I use pure WINE a lot and it was a pain having to install them manually. Eventually I gave up on using mono and just downloaded the .net runtimes I needed through winetricks.
There were also some lib32 package I got from AUR on Arch that didn’t exist on apt. One of those gst plugins (ugly/good/bad/nice/whatever)
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.