Subject: Re: docs/154931: handbook/install/chapter.sgml - repeated chunk of text
Warren Block
wblock at wonkity.com
Mon Feb 21 15:07:59 UTC 2011
I did reply to keramida@ earlier about this problem with 154837, but
neglected to include bug-followup at FreeBSD.org. Here's the message,
along with a patch that fixes a couple of other problems.
---------- Forwarded message ----------
Date: Thu, 17 Feb 2011 08:17:39
From: Warren Block <wblock at wonkity.com>
To: keramida at FreeBSD.org
Subject: Re: docs/154837: [patch] update Handbook for writing memstick image
with Windows
On Thu, 17 Feb 2011, keramida at FreeBSD.org wrote:
> Synopsis: [patch] update Handbook for writing memstick image with Windows
>
> State-Changed-From-To: open->closed
> State-Changed-By: keramida
> State-Changed-When: Thu Feb 17 09:20:55 UTC 2011
> State-Changed-Why:
> Committed, in revision 1.417 of handbook/install/chapter.sgml
>
> Thanks!
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=154837
The patch didn't quite apply as planned; there's a duplicate section at the
start of the FreeBSD procedure (two warnings, and the sysctl line). Possibly
due to the original having changed since the patch was created.
Two other notes: the Windows section warns about the H: drive shown in the
example, which is not actually shown, and the link should probably go to the
project page, not a direct download that may be outdated.
The following patch applies to the latest source to correct these three things.
--- en_US.ISO8859-1/books/handbook/install/chapter.sgml.orig 2011-02-17
08:07:54.000000000 -0700
+++ en_US.ISO8859-1/books/handbook/install/chapter.sgml 2011-02-17
08:12:24.000000000 -0700
@@ -644,17 +644,6 @@
may destroy your existing data.</para>
</warning>
- <para>Set the <varname>kern.geom.debugflags</varname> sysctl to be
- able to write a master boot record to the target device.</para>
-
- <warning>
- <para>The example below
- lists <filename class="devicefile">/dev/da0</filename> as the
- target device where the image will be written. Be very careful
- that you have the correct device as the output target, or you
- may destroy your existing data.</para>
- </warning>
-
<step>
<title>Writing the Image with &man.dd.1;</title>
@@ -679,11 +668,8 @@
<title>Using &windows To Write the Image</title>
<warning>
- <para>The example below
- lists <filename class="devicefile">H:</filename> as the drive
- letter of the device where the image will be written. Be very
- careful that you have the correct device as the output target,
- or you may destroy existing data.</para>
+ <para>Make sure you use the correct drive letter as the output
+ target, or you may overwrite and destroy existing data.</para>
</warning>
<step>
@@ -691,8 +677,8 @@
<para><application>Image Writer for Windows</application> is a
free application that can correctly write an image file to a
- memory stick. Download it
- from <ulink
url="http://launchpad.net/win32-image-writer/0.2/0.2/+download/win32diskimager-RELEASE-0.2-r23-win32.zip"></ulink>
+ memory stick. Download it from
+ <ulink url="https://launchpad.net/win32-image-writer"></ulink>
and extract it into a folder.</para>
</step>
More information about the freebsd-doc
mailing list