From owner-freebsd-questions Sun Jul 22 17: 6:46 2001 Delivered-To: freebsd-questions@freebsd.org Received: from w2xo.pgh.pa.us (18.gibs5.xdsl.nauticom.net [209.195.184.19]) by hub.freebsd.org (Postfix) with ESMTP id 49D3537B401 for ; Sun, 22 Jul 2001 17:06:43 -0700 (PDT) (envelope-from durham@w2xo.pgh.pa.us) Received: from jimslaptop.int (jimslaptop.int [192.168.5.8]) by w2xo.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f6N0Btm29914; Sun, 22 Jul 2001 20:11:55 -0400 (EDT) (envelope-from durham@w2xo.pgh.pa.us) Date: Sun, 22 Jul 2001 20:04:27 -0400 (EDT) From: Jim Durham X-X-Sender: To: Mark Rowlands Cc: matt , Subject: Re: Security Issues And Iso Images In-Reply-To: <01072211572403.30084@pcmarpxy.tninet.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 22 Jul 2001, Mark Rowlands wrote: > 9) cd /usr/src > > make buildworld && make buildkernel KERNCONF=YOURKERNEL \ I don't want to confuse the issue... but I have "an issue" 8-) . Aren't you building your kernel against old libs? IMHO you want to do your buildworld, then drop to single-user (you can't install a running binary), do your installworld, then buildkernel, then installkernel, so that your new kernel is built against the newly installed libraries. Also, if you are running securelevel > 0, then you *must* reboot and come up in single user to replace any chflagged binaries. > && make installkernel KERNCONF=YOURKERNEL && make installworld > > 10) mergemaster > > 11) reboot > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message