Bug 48341 MBR OverWrites
"Frank Mitchell" <[email protected]> Wed, 29 Nov 2006 00:11:57 -0000
| Newsgroups | gmane.os.freebsd.devel.quality-assurance |
|---|---|
| Message-ID | <000001c7134b$a82c50e0$fed3ae51@hal> |
Re: Problem 48341: sysinstall deletes mbr I just bought a new computer and installed NetBSD, followed by FreeBSD. The NetBSD Boot Selector has advantages, so I installed it and told sysinstall to Leave MBR Unaltered. And apparently it did. I encountered the MBR issue earlier this year, and John Baldwin supplied an alternative explanation: ====================================================== From: "John Baldwin" <[email protected]> To: <[email protected]> Cc: "Frank Mitchell" <[email protected]>; <[email protected]>; <[email protected]> Subject: Re: bin_48341 & Dual-Booting Date: 22 March 2006 21:56 On Wednesday 22 March 2006 11:20, Frank Mitchell wrote: > Dear Matteo Riondato, > Being new to FreeBSD, I wanted to re-run sysinstall a few times without > disturbing my Windows Me boot set-up. So I chose the "Boot Manager = None" > Option, intending to leave the MBR untouched while I investigated the > possibility of booting from a Floppy. But I soon found my machine rebooted > into FreeBSD every time. I didn't see Windows Me again until I installed the > FreeBSD Boot Manager, which luckily dual-booted okay. (Windows Me gave > problems using Lilo). This is because the default boot manager windows installs just boots the 'active' slice, and sysinstall marked the FreeBSD slice as active. John Baldwin <[email protected]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ====================================================== Faictz Ce Que Vouldras: Frank Mitchell -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.430 / Virus Database: 268.14.19/556 - Release Date: 28/11/2006 15:22 _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-qa To unsubscribe, send any mail to "[email protected]"