East Grand Forks Police posted, “A second officer was also injured, and we hope they will have a safe recovery. This senseless act of violence also claimed the lives of two other civilians, and injured one. This marks the 60th Police Officer who has been killed in the line of duty this year, with this being the third from Minnesota.”

(KNOX) – Minnesota Governor Tim Walz has ordered all U.S. and state flags to fly at half-staff at all state buildings today to honor Minneapolis Police Officer Jamal Mitchell, who died in the line of duty.

Other boot loaders used by third-party boot managers (such as GRUB or XOSL) can be installed to a master boot record and can boot primary or extended partitions, which do not have the boot flag set.

There are many disk editors that can modify the boot flag, such as Disk Management in Windows,[5] GPartEd in Linux, and fdisk.

Its primary function is to indicate to a MS-DOS/MS Windows-type boot loader which partition to boot. In some cases it is used by Windows XP/2000 to assign the active partition the letter "C:".[3] The active partition is the partition where the boot flag is set. DOS and Windows allow only one boot partition to be set with the boot flag.[4]

The Polk County Sheriff’s Office posted, “Our hearts are breaking for our brothers and sisters of the Minneapolis Police Department as they mourn the death of one of their own. Please keep the injured officer and civilians as well as the families of all who lost their friends and loved ones in your thoughts and prayers.”

Some BIOSes test if the boot flag of at least one partition is set, otherwise they ignore the device in boot-order. Therefore, even if the bootloader does not need the flag, it has to be set to start the boot code from BIOS.[6]

A boot flag is a 1-byte value in a non-extended partition record, within a master boot record. It appears at the beginning of a partition record, as the value 0x80. A value of 0x00 indicates the partition does not have the boot flag set.[1][2] Any other value is invalid.