<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dual-Booting on Michael’s Domain</title><link>https://jeltsch.org/en/tags/dual-booting/</link><description>Recent content in Dual-Booting on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/dual-booting/index.xml" rel="self" type="application/rss+xml"/><item><title>Computer time: Windows against the rest of the world</title><link>https://jeltsch.org/en/computer_time_windows_against_the_rest_of_the_world/</link><pubDate>Sat, 10 Feb 2018 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/computer_time_windows_against_the_rest_of_the_world/</guid><description>&lt;p&gt;I am not sure, but Windows seems to be the only operating system, that wants the computer clock to be set to the local time zone instead of universal standard time (UTC). Maybe that is a relic of the times when Microsoft thought that the internet was not very important for the future of computing. All other operating systems apparently use UTC: MacOS, Android, Linux, BSD, … However, if you are dual-booting your computer, you can get into trouble. Not all operating systems detect automatically a dual boot install and adjust their behaviour in order to be compatible with Windows. If this is the case, the easiest is to change the behaviour of Windows. A clear write-up how to do so is available from 
 &lt;a href="https://liliputing.com/2016/03/fix-time-problem-dual-boot-computers-windows-linux-android.html" target="_blank" rel="noopener noreferrer nofollow"&gt;https://liliputing.com/2016/03/fix-time-problem-dual-boot-computers-windows-linux-android.html&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
, but here are the steps in a nutshell:&lt;/p&gt;</description></item><item><title>BSD and Linux</title><link>https://jeltsch.org/en/bsd_and_linux/</link><pubDate>Fri, 10 Jun 2016 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/bsd_and_linux/</guid><description>&lt;p&gt;I am used to the fact that a Linux installer honours a pre-existing install of Windows and offers to setup the computer with a dual-boot option during installation. Vice-versa no Windows installer honours any other pre-exisiting OS. Therefore I was surprised that when I tried to install Ubuntu 16.04 on my PFSense box (FreeBSD), the Ubuntu installer did not even see that a BSD install exists on the drive. I chose the &amp;ldquo;erase all&amp;rdquo; option, but when I rebooted after the installer has finished, the system went straight into PFSense without giving me any option to select Ubuntu. I guess the boot loader had not been touched by the Ubuntu installer. I booted from a live Ubuntu USB stick, reformatted the drive with fdisk and wrote zeros to the boot loader:&lt;code&gt;dd if=/dev/zero of=/dev/sda bs=512 count=1&lt;/code&gt;Then I repeated the install and everything was fine. However, my PFSense installation was lost…&lt;/p&gt;</description></item></channel></rss>