From owner-freebsd-doc Wed Jul 18 9:14:29 2001 Delivered-To: freebsd-doc@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.39]) by hub.freebsd.org (Postfix) with SMTP id 44AD937B405 for ; Wed, 18 Jul 2001 09:14:22 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 75308 invoked by uid 1000); 18 Jul 2001 16:18:37 -0000 Date: Wed, 18 Jul 2001 19:18:37 +0300 From: Peter Pentchev To: doc@FreeBSD.org Subject: [CFR] Handbook doc for installkernel failure at securelevel Message-ID: <20010718191837.E29731@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, As noted in PR conf/29043, sometimes people are not immediately aware of the effect of securelevel > 0 on the immutable flag, or of the fact that 'chflags -[no]schg' has to do with the immutable flag at all. Any reason not to add some explanatory text to the trouble-shooting section of handbook/kerneldebug, as in the attached patch? This might have been done as an additional paragraph in the 'make fails' item in the list, but I have some vague plans of also documenting the problem with a non-existent modules directory, discussed in PR kern/26317, and (to some extent) addressed in my commit to src/sys/conf/kmod.mk earlier today. I think that it would only be logical to separate build and install failures. Any style floggings (first head-on collision with DocBook here ;) and any general comments are welcome! G'luck, Peter PS. OK, so I can notice a style nit myself. I know that the 'command' part in the explanation "(the make install or make installkernel command failed)" is superfluous according to the FDP, but I only mimicked the rest of this particular chapter; after all, this is also intended for newbies to read and understand, right? :) -- This sentence contains exactly threee erors. Index: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v retrieving revision 1.52 diff -u -r1.52 chapter.sgml --- doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml 2001/07/17 22:20:49 1.52 +++ doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml 2001/07/18 16:10:37 @@ -1118,7 +1118,7 @@ If Something Goes Wrong - There are four categories of trouble that can occur when + There are five categories of trouble that can occur when building a custom kernel. They are: @@ -1153,6 +1153,24 @@ over your configuration, and if you still cannot resolve the problem, send mail to the &a.questions; with your kernel configuration, and it should be diagnosed very quickly. + + + + + Installing the new kernel fails + + + If the kernel compiled fine, but failed to install + (the make install or + make installkernel command failed), + the first thing to check is if your system is running at + securelevel 1 or higher (see &man.init.8;). The kernel + installation tries to remove the immutable flag from + your old kernel file, and set + the immutable flag on the new one. Since securelevel 1 + or higher prevents changing the immutable flag for any + files on the system, the kernel installation needs to be + performed at securelevel 0 or lower. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message