FreeBSD installer changed my MBR-only partition table to MBR+GPT partition table. The other OS does not have GPT logic; I want to be at least warned this is happening and prefer to have the option at least. Alternatively, the installer may opt not to install a GPT if the disk does not require it (as in the case in this machine) Fix: Best solution: deduce from disk size that GPT is not required and in that case, proceed to not use it Alternative solution: ask user (for userfriendliness, tell them if the present layout does or does not use GPT) Worst solution: warn them this is happening How-To-Repeat: Install FreeBSD 9.0 RELEASE next to another OS that does not have GPT (Windows XP in my case)
Responsible Changed From-To: freebsd-bugs->freebsd-sysinstall assign and fix synopsis
I am experiencing the same problem ... with sysinstall(8)!!! I used /usr/src/release/Makefile.sysinstall to cut myself a legacy installe= r for the 9.0 branch ... a sysinstall(8) installer versus the new bsdinstal= l installer cut from /usr/src/release/Makefile. When all was said and done (sysinstall crunched into boot_crunch using /usr= /src/release/i386/boot_crunch.conf), sysinstall(8) is for some reason writi= ng GPT labels even though it never has done so before. I'll go into sysinstall's disk partition editor, lay down a legacy filesyst= em, write it out, and then look at /dev to find that it didn't create /dev/= ada0s* but instead /dev/ada0p* (what's worse is that gpart subsequently sho= ws GPT but with "[CORRUPT]" next to it). This is completely hampering my ability to use sysinstall(8) as-built from = RELENG_9 to install RELENG_9. I'm left wondering if something changed in devfs or in libdisk. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped