1 files changed, 9 insertions, 6 deletions

diff --git a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
index 52c5bae61f..29705a7e91 100644
--- a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
@@ -1007,12 +1007,6 @@ Script done, &hellip;</screen>
 	can then build a new kernel based on your normal kernel	configuration
 	file.</para>
 
-      <note><para>If kern.securelevel is elevated, then installkernel may fail
-	due to the system immutable flag option.  Because of this, the user
-	may be required to use &man.chflags.1; with with noschg option.  This
-	will allow the install process to overwrite the currently installed
-	kernel.</para></note>
-
       <para>If you are upgrading to &os; 4.0 or above then the old
 	kernel build procedure (as described in <xref linkend="kernelconfig">)
 	is deprecated.  Instead, you should run these commands
@@ -1024,6 +1018,15 @@ Script done, &hellip;</screen>
 &prompt.root; <userinput>make buildkernel</userinput>
 &prompt.root; <userinput>make installkernel</userinput></screen>
 
+      <para>Note that if you have raised <literal>kern.securelevel</literal>
+	above 1 <emphasis>and</emphasis> you have set either the
+	<literal>noschg</literal> or similar flags to your kernel binary, you
+	might find it necessary to drop into single user mode to use
+	<maketarget>installkernel</maketarget>.  Otherwise you should be able
+	to run both these commands from multi user mode without
+	problems.  See &man.init.8; for details about
+	<literal>kern.securelevel</literal> and &man.chflags.1; for details
+	about the various file flags.</para>
       <para>If you are upgrading to a version of &os; below 4.0 you should
 	use the old kernel build procedure.  However, it is recommended
 	that you use the new version of &man.config.8;, using a command line