Installed Mint last week. I already ported most of my personal stuff there ; as a user of FOSS software, it was a breeze. Still dual booting Windows because of work, but I’ll start trying to see if I can get the required tools to work on there too.
For now, my biggest issue was that connecting my Bluetooth headphones to both Linux and Windows was fucky but, lo and behold, there was a guide online that told me exactly how to make sure both OS had the same device ID.
It’s not a painless experience yet, but it’s way less painful than what it was running Win95 back then. And it feels so good to finally flip Microsoft the bird.
YOu didn’t (fully) fix it. This is something I don’t see a lot of people talking about regarding Windows/Linux dual boot.
Unix-like systems like Linux set the computer’s built-in real-time clock to UTC and then do any conversions to local time on the fly. I think that traces back to UNIX’s origins as a minicomputer OS; it needed to talk to other minicomputers across time zones from the beginning.
Windows, like DOS before it, is designed to sit on a desk by itself plugged into nothing but power and accept data one, maybe two floppy disks at a time. Why would the user care about anything other than the local time? Hell the original IBM 5150 didn’t even have a built-in RTC. It would forget what time it was when powered off and it would ask you when DOS booted.
Either OS can be set to do it either way in the modern era; pick one to change so that they don’t fight. It’s done with a registry edit in Windows or a bash command in Linux. Do one, or the other, but not both. I recommend changing Windows, because Windows will reset the RTC every daylight savings time and on a mobile system every time it crosses a time zone, Linux doesn’t.
Installed Mint last week. I already ported most of my personal stuff there ; as a user of FOSS software, it was a breeze. Still dual booting Windows because of work, but I’ll start trying to see if I can get the required tools to work on there too.
For now, my biggest issue was that connecting my Bluetooth headphones to both Linux and Windows was fucky but, lo and behold, there was a guide online that told me exactly how to make sure both OS had the same device ID.
It’s not a painless experience yet, but it’s way less painful than what it was running Win95 back then. And it feels so good to finally flip Microsoft the bird.
Have you run into the system clock issue yet?
I think I did, but nothing that a resync didn’t fix.
YOu didn’t (fully) fix it. This is something I don’t see a lot of people talking about regarding Windows/Linux dual boot.
Unix-like systems like Linux set the computer’s built-in real-time clock to UTC and then do any conversions to local time on the fly. I think that traces back to UNIX’s origins as a minicomputer OS; it needed to talk to other minicomputers across time zones from the beginning.
Windows, like DOS before it, is designed to sit on a desk by itself plugged into nothing but power and accept data one, maybe two floppy disks at a time. Why would the user care about anything other than the local time? Hell the original IBM 5150 didn’t even have a built-in RTC. It would forget what time it was when powered off and it would ask you when DOS booted.
Either OS can be set to do it either way in the modern era; pick one to change so that they don’t fight. It’s done with a registry edit in Windows or a bash command in Linux. Do one, or the other, but not both. I recommend changing Windows, because Windows will reset the RTC every daylight savings time and on a mobile system every time it crosses a time zone, Linux doesn’t.