From afe034d8a4e5f4ecbb1533e6e27a4f79610c1383 Mon Sep 17 00:00:00 2001 From: John Fieber <jfieber@FreeBSD.org> Date: Thu, 18 Sep 1997 13:27:22 +0000 Subject: [PATCH] Changes: . Removed references that dangerously dedicated disks won't boot. Several people on -questions have proved me wrong. . Add credit to Greg Lemis for the above note. Submitted by: Doug White <dwhite@gdi.uoregon.edu> --- en/tutorials/diskformat/diskformat.docb | 22 +++++++++---------- .../articles/formatting-media/article.sgml | 22 +++++++++---------- .../articles/formatting-media/article.sgml | 22 +++++++++---------- 3 files changed, 33 insertions(+), 33 deletions(-) diff --git a/en/tutorials/diskformat/diskformat.docb b/en/tutorials/diskformat/diskformat.docb index 5f1167da82..f2f70b7d2e 100644 --- a/en/tutorials/diskformat/diskformat.docb +++ b/en/tutorials/diskformat/diskformat.docb @@ -1,5 +1,5 @@ <!DOCTYPE BOOK PUBLIC "-//Davenport//DTD DocBook V3.0//EN"> -<!-- $Id: diskformat.docb,v 1.1 1997-09-13 04:24:28 jfieber Exp $ --> +<!-- $Id: diskformat.docb,v 1.2 1997-09-18 13:27:22 jfieber Exp $ --> <book> <bookinfo> @@ -121,16 +121,13 @@ represents 512 bytes of data.</para></listitem> to destroy the contents of other disks in your system if the proper precautions are not taken.</para> -<para>In particular, note the following: -<orderedlist> -<listitem><para><emphasis>Type carefully.</> One wrong number can wipe out -the wrong disk. Double check your typing before entering the command. When -in doubt consult the kernel boot output for the proper device.</para></listitem> -<listitem><para><emphasis>Never set up a boot disk as dangerously dedicated.</> Some PC BIOSs cannot understand the bootblocks and start your system properly. -Make the first disk in <quote>compatibility mode</quote> just to be safe. -Subsequent non-booting disks are OK to dangerously dedicate.</para></listitem> -</orderedlist> -</para> +<para><emphasis>Check your work carefully.</> It is very simple to destroy +the incorrect disk when working with these commands. When +in doubt consult the kernel boot output for the proper device.</para> + +<para>Needless to say, we are not responsible for any damage to any data +or hardware that you may experience. You work at your own risk!</para> + </sect1> <sect1> @@ -408,6 +405,9 @@ sysinstall useful for this type of task.</para></listitem> (<email>jfieber@indiana.edu</email>) for making information and examples of the DocBook DTD on which this document is based.</para></listitem> +<listitem><para>Greg Lemis (<email>grog@lemis.de</email>) for checking my work +and pointing out inaccuracies, as well as miscellaneous support. +</para></listitem> </itemizedlist> </para> diff --git a/en_US.ISO8859-1/articles/formatting-media/article.sgml b/en_US.ISO8859-1/articles/formatting-media/article.sgml index 474648ed69..74e3f761fa 100644 --- a/en_US.ISO8859-1/articles/formatting-media/article.sgml +++ b/en_US.ISO8859-1/articles/formatting-media/article.sgml @@ -1,5 +1,5 @@ <!DOCTYPE BOOK PUBLIC "-//Davenport//DTD DocBook V3.0//EN"> -<!-- $Id: article.sgml,v 1.1 1997-09-13 04:24:28 jfieber Exp $ --> +<!-- $Id: article.sgml,v 1.2 1997-09-18 13:27:22 jfieber Exp $ --> <book> <bookinfo> @@ -121,16 +121,13 @@ represents 512 bytes of data.</para></listitem> to destroy the contents of other disks in your system if the proper precautions are not taken.</para> -<para>In particular, note the following: -<orderedlist> -<listitem><para><emphasis>Type carefully.</> One wrong number can wipe out -the wrong disk. Double check your typing before entering the command. When -in doubt consult the kernel boot output for the proper device.</para></listitem> -<listitem><para><emphasis>Never set up a boot disk as dangerously dedicated.</> Some PC BIOSs cannot understand the bootblocks and start your system properly. -Make the first disk in <quote>compatibility mode</quote> just to be safe. -Subsequent non-booting disks are OK to dangerously dedicate.</para></listitem> -</orderedlist> -</para> +<para><emphasis>Check your work carefully.</> It is very simple to destroy +the incorrect disk when working with these commands. When +in doubt consult the kernel boot output for the proper device.</para> + +<para>Needless to say, we are not responsible for any damage to any data +or hardware that you may experience. You work at your own risk!</para> + </sect1> <sect1> @@ -408,6 +405,9 @@ sysinstall useful for this type of task.</para></listitem> (<email>jfieber@indiana.edu</email>) for making information and examples of the DocBook DTD on which this document is based.</para></listitem> +<listitem><para>Greg Lemis (<email>grog@lemis.de</email>) for checking my work +and pointing out inaccuracies, as well as miscellaneous support. +</para></listitem> </itemizedlist> </para> diff --git a/en_US.ISO_8859-1/articles/formatting-media/article.sgml b/en_US.ISO_8859-1/articles/formatting-media/article.sgml index 474648ed69..74e3f761fa 100644 --- a/en_US.ISO_8859-1/articles/formatting-media/article.sgml +++ b/en_US.ISO_8859-1/articles/formatting-media/article.sgml @@ -1,5 +1,5 @@ <!DOCTYPE BOOK PUBLIC "-//Davenport//DTD DocBook V3.0//EN"> -<!-- $Id: article.sgml,v 1.1 1997-09-13 04:24:28 jfieber Exp $ --> +<!-- $Id: article.sgml,v 1.2 1997-09-18 13:27:22 jfieber Exp $ --> <book> <bookinfo> @@ -121,16 +121,13 @@ represents 512 bytes of data.</para></listitem> to destroy the contents of other disks in your system if the proper precautions are not taken.</para> -<para>In particular, note the following: -<orderedlist> -<listitem><para><emphasis>Type carefully.</> One wrong number can wipe out -the wrong disk. Double check your typing before entering the command. When -in doubt consult the kernel boot output for the proper device.</para></listitem> -<listitem><para><emphasis>Never set up a boot disk as dangerously dedicated.</> Some PC BIOSs cannot understand the bootblocks and start your system properly. -Make the first disk in <quote>compatibility mode</quote> just to be safe. -Subsequent non-booting disks are OK to dangerously dedicate.</para></listitem> -</orderedlist> -</para> +<para><emphasis>Check your work carefully.</> It is very simple to destroy +the incorrect disk when working with these commands. When +in doubt consult the kernel boot output for the proper device.</para> + +<para>Needless to say, we are not responsible for any damage to any data +or hardware that you may experience. You work at your own risk!</para> + </sect1> <sect1> @@ -408,6 +405,9 @@ sysinstall useful for this type of task.</para></listitem> (<email>jfieber@indiana.edu</email>) for making information and examples of the DocBook DTD on which this document is based.</para></listitem> +<listitem><para>Greg Lemis (<email>grog@lemis.de</email>) for checking my work +and pointing out inaccuracies, as well as miscellaneous support. +</para></listitem> </itemizedlist> </para>