From owner-freebsd-questions Thu May 18 18:39:36 2000 Delivered-To: freebsd-questions@freebsd.org Received: from tdl.com (pm5-90.tdl.com [206.180.234.90]) by hub.freebsd.org (Postfix) with ESMTP id DB3F337BD84 for ; Thu, 18 May 2000 18:39:27 -0700 (PDT) (envelope-from wdr@tdl.com) Received: from localhost (localhost [127.0.0.1]) by tdl.com (8.9.3/8.8.8) with ESMTP id SAA01184; Thu, 18 May 2000 18:40:15 -0700 (PDT) (envelope-from wdr@tdl.com) Date: Thu, 18 May 2000 18:40:15 -0700 (PDT) From: William Richard X-Sender: wdr@wdr.my.domain To: "Adam L. Simpson" Cc: freebsd-questions@FreeBSD.ORG Subject: Re: 4.0-Stable Fatal Trap 12 when increasing maxusers In-Reply-To: <200005181602.LAA14956@hades.netsonic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 May 2000, Adam L. Simpson wrote: > So you are saying do a cvsup, makeworld then rebuild the kernel right away > when you say relink.. sounds like thats what the problem is... > appreciate it. Yes--every time you remake the world, you must rebuild and install the kernel. Try the buildkernel and installkernel make targets from /usr/src: (you've just buildworlded, but haven't yet installworlded) # make buildkernel [ ... cruncha cruncha cruncha ... ] # make installkernel KERNEL=kernel This will install a GENERIC kernel--once you're up and running with the new build, you can build a custom kernel (cvsup doesn't touch your old custom kernel config file). The KERNEL=kernel line will ensure your new kernel is installed as /kernel, rather than /GENERIC, which won't boot (and will leave your old, incompatible kernel in place--I found this out the hard way). In order to rebuild a system which won't boot because it's choking on something it loads at boot time (from /etc/rc and friends), try booting in single-user mode. WR -- William Richard BSD Unix Consultant Tel/Fax: 925-480-2319 x1951 E-Mail: wdr@tdl.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message