From 00f18547b59d9136963a86fb39dc0059d8b5ad01 Mon Sep 17 00:00:00 2001 From: Tom Rhodes Date: Tue, 16 Jul 2002 02:11:35 +0000 Subject: [PATCH] Move the installkernel information that I added down a bit, and clarify Submitted by: keramida --- .../books/handbook/cutting-edge/chapter.sgml | 15 +++++++++------ 1 file 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, … can then build a new kernel based on your normal kernel configuration file. - 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. - If you are upgrading to &os; 4.0 or above then the old kernel build procedure (as described in ) is deprecated. Instead, you should run these commands @@ -1024,6 +1018,15 @@ Script done, … &prompt.root; make buildkernel &prompt.root; make installkernel + Note that if you have raised kern.securelevel + above 1 and you have set either the + noschg or similar flags to your kernel binary, you + might find it necessary to drop into single user mode to use + installkernel. Otherwise you should be able + to run both these commands from multi user mode without + problems. See &man.init.8; for details about + kern.securelevel and &man.chflags.1; for details + about the various file flags. 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