From owner-freebsd-current Mon Oct 19 15:03:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24736 for freebsd-current-outgoing; Mon, 19 Oct 1998 15:03:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24695 for ; Mon, 19 Oct 1998 15:03:01 -0700 (PDT) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id TAA09608; Mon, 19 Oct 1998 19:02:17 -0300 (ADT) Date: Mon, 19 Oct 1998 19:02:16 -0300 (ADT) From: Marc Fournier X-Sender: marc@iceberg To: John Birrell cc: eculp@webwizard.org.mx, freebsd-current@FreeBSD.ORG Subject: Re: paranoid question: aout vs ELF... In-Reply-To: <199810192200.IAA21511@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, John Birrell wrote: > Marc Fournier wrote: > > Unless you can suggestion something else, I don't have much choice in this > > matter :( My history file for news is at ~700Meg, and expire won't work > > because it can't allocate memory due to a hard limit in my kernel.. :( > > Is it possible for you to just build a new kernel to get around the > hard limit problem? Introducing a significant emotional event like upgrading > to elf at the same time seems unnecessary. The problem is that my last upgrade was around mid-July...prior to CAM being integrated, so it was all 'hand-patched'...if I upgrade just the 'current kernel', I *have* to upgrade the rest, no? I don't want to go back to the mid-Jully source tree, since there has been alot of stuff done with CAM since then :( Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message