From owner-freebsd-questions@FreeBSD.ORG Sat Mar 11 19:38:41 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F02CC16A424 for ; Sat, 11 Mar 2006 19:38:40 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB94E43D5A for ; Sat, 11 Mar 2006 19:38:38 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 9EFC81A4D8E; Sat, 11 Mar 2006 11:38:38 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A87555186D; Sat, 11 Mar 2006 14:38:37 -0500 (EST) Date: Sat, 11 Mar 2006 14:38:37 -0500 From: Kris Kennaway To: "lars@gmx.at" Message-ID: <20060311193837.GA71085@xor.obsecurity.org> References: <20060311105201.p0d50a73fwys80s0@webmail.dommel.be> <20060311100132.GA44110@xor.obsecurity.org> <4412B460.9050800@gmx.at> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <4412B460.9050800@gmx.at> User-Agent: Mutt/1.4.2.1i Cc: freebsd-questions@freebsd.org Subject: Re: make installworld fails X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Mar 2006 19:38:41 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 11, 2006 at 12:28:32PM +0100, lars@gmx.at wrote: > Kris Kennaway wrote: > >>The error message is wrong. > > > >Actually it's correct, just a bit unclear. UPDATING includes the > >complete procedure you should always follow when building world. It > >includes a 'mergemaster -p' step, precisely for the purpose of adding > >new users and groups when they appear. > Dear Kris > I have a few questions related to this error message > ERROR: Required audit group is missing, see /usr/src/UPDATING >=20 > I know that updating requires the mergemaster steps because I read the=20 > handbook. But I don't understand why this message tells me to look > in that file, when there's nothing about that in it. >=20 > Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? Yes. =20 -- Updating Information for FreeBSD STABLE users This file is maintained and copyrighted by M. Warner Losh . See end of file for further details. For commonly done items, please see the COMMON ITEMS: section later in the file. [...] [...special items applicable to special situations...] COMMON ITEMS: General Notes ------------- =2E.. To build a kernel ----------------- =2E.. To rebuild everything and install it on the current system. ----------------------------------------------------------- # Note: sometimes if you are running current you gotta do more than # is listed here if you are upgrading from a really old current. make buildworld make kernel KERNCONF=3DYOUR_KERNEL_HERE [1] [3] mergemaster -p [5] <-------------= -------here make installworld make delete-old mergemaster [4] > Or is there a file which describes how I can manually insert needed groups > and users when I mess up mergemaster runs? I think you can just rerun mergemaster -p. If you mess up a full mergemaster, you can use mergemaster -s to repair it. > And finally, is it really necessary to reboot after 'mergemaster -p'? > Lately I've skipped that step with no adverse side-effects, saves me one= =20 > reboot :-) No, it just adds the users/groups, and rebooting won't gain you anything. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEEyc9Wry0BWjoQKURAsn/AKC85dJoTasgsnjlGQFfvibnl7jmNACfTiZV x4QmDYSgDTKevR+ZFFn/wNc= =OcRI -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--