[prev in list] [next in list] [prev in thread] [next in thread]
List: freebsd-bugs
Subject: misc/161113: bsdinstall: 9.0-BETA3: overwrites Win*-bootcodes
From: Kalten <kalten () gmx ! at>
Date: 2011-09-28 22:29:02
Message-ID: 201109282229.p8SMT2ma070913 () red ! freebsd ! org
[Download RAW message or body]
> Number: 161113
> Category: misc
> Synopsis: bsdinstall: 9.0-BETA3: overwrites Win*-bootcodes without warning?
> Confidential: no
> Severity: non-critical
> Priority: low
> Responsible: freebsd-bugs
> State: open
> Quarter:
> Keywords:
> Date-Required:
> Class: sw-bug
> Submitter-Id: current-users
> Arrival-Date: Wed Sep 28 22:30:08 UTC 2011
> Closed-Date:
> Last-Modified:
> Originator: Kalten
> Release:
> Organization:
> Environment:
FreeBSD freeHugin.​Walhalla.​Leben 9.0-BETA3 #0: Sat Sep 24 21:21:28 UTC \
2011 root@​farrell.​cse.​buffalo.​edu:/​usr/​obj/​usr/​src/​sys/​GENERIC \
amd64
> Description:
Created new partitions and slices (MBR-Mode).
bsdinstall has overwritten Win7 boot code, es it seems---no questions any more (like \
in sysinstall) wether we want it to do this or not!?
(Win7 still there (mountable in freeBSD), but not bootable.
Neither ``Startup repair'' nor bootrec in the ``command Prompt'' of Win7's DVD could \
repair it---althoug dir works on it in the mentioned win-cmd-prompt.)
I am sure, that I am not the only one who would appreciate it very much, if we had \
the chance to choose wether to write down a bootloader into the disk or not (as we \
had with sysinstall)
> How-To-Repeat:
Created new partitions and slices (MBR-Mode) in new installer called bsdinstall.
> Fix:
> Release-Note:
> Audit-Trail:
> Unformatted:
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic