Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Jun 2000 16:26:33 +0100 (BST)
From:      Mark Ovens <mark@ukug.uk.freebsd.org>
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   docs/19174: [PATCH] Correct serious error in FAQ
Message-ID:  <200006101526.QAA02849@parish.my.domain>

next in thread | raw e-mail | index | archive | help

>Number:         19174
>Category:       docs
>Synopsis:       [PATCH] Correct serious error in FAQ
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jun 10 08:30:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Mark Ovens
>Release:        FreeBSD 4.0-STABLE i386
>Organization:
>Environment:

	

>Description:

	An addition of mine, docs/13207, in the System Administration
	section of the FAQ entitled "How can I use the NT loader
	to boot FreeBSD?" is incorrect. It was submitted to document
	information that appeared in a long thread on -questions,
	however, it is not possible to use /boot/boot0 as described.
	Doing so will result in a trashed Partition Table. I and
	at least 2 other people have done this.

	This patch is a re-write of the last paragraph and details
	how boot0 works, including a warning of the potential
	dangers.

	Given the serious nature of the problems that can be caused
	this should be committed ASAP.

>How-To-Repeat:

	I wouldn't try if I were you

>Fix:


*** book.sgml.orig	Sat Jun 10 13:55:37 2000
--- book.sgml	Sat Jun 10 16:25:13 2000
***************
*** 4390,4399 ****
  <para>For FreeBSD 3.x systems the procedure is somewhat simpler.</para>
  
  <para>If FreeBSD is installed on the same disk as the NT boot partition
! copy <filename>/boot/boot1</filename> to <filename>c:\bootsect.bsd</filename>
! or if FreeBSD is installed on a different disk copy
! <filename>/boot/boot0</filename> to <filename>c:\bootsect.bsd</filename>.
! Then edit <filename>c:\bootsect.ini</filename> as described earlier.</para>
  
  </answer></qandaentry>
  
--- 4390,4420 ----
  <para>For FreeBSD 3.x systems the procedure is somewhat simpler.</para>
  
  <para>If FreeBSD is installed on the same disk as the NT boot partition
! simply copy <filename>/boot/boot1</filename> to <filename>C:\BOOTSECT.BSD
! </filename> However, if FreeBSD is installed on a different disk
! <filename>/boot/boot1</filename> will not work, <filename>/boot/boot0
! </filename> is needed.
! 
! <warning>
!   <para>DO NOT SIMPLY COPY <filename>/boot/boot0</filename> INSTEAD OF
!   <filename>/boot/boot1</filename>, YOU WILL OVERWRITE YOUR PARTITION TABLE 
!   AND RENDER YOUR COMPUTER UN-BOOTABLE!</para></warning>
! 
! <filename>/boot/boot0</filename> needs to be installed using sysinstall by
! selecting the FreeBSD boot manager on the screen which asks if you wish to
! use a boot manager. This is because <filename>/boot/boot0</filename> has the
! partition table area filled with NULL characters but sysinstall copies the
! partition table before copying <filename>/boot/boot0</filename> to the MBR.
! </para>
! 
! <para>When the FreeBSD boot manager runs it records the last OS booted by
! setting the active flag on the partition table entry for that OS and then
! writes the whole 512-bytes of itself back to the MBR so if you just copy
! <filename>/boot/boot0</filename> to <filename>C:\BOOTSECT.BSD</filename>
! then it writes an empty partition table, with the active flag set on one
! entry, to the MBR.</para>
! 
! <para>I write from bitter personal experience of this.</para>
  
  </answer></qandaentry>
  


>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006101526.QAA02849>