From owner-cvs-sys Thu May 11 21:08:25 1995 Return-Path: cvs-sys-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA29292 for cvs-sys-outgoing; Thu, 11 May 1995 21:08:25 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA29282 ; Thu, 11 May 1995 21:08:17 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id VAA02234; Thu, 11 May 1995 21:08:11 -0700 From: Poul-Henning Kamp Message-Id: <199505120408.VAA02234@ref.tfs.com> Subject: Re: cvs commit: src/sys/vm vm_swap.c To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Thu, 11 May 1995 21:08:11 -0700 (PDT) Cc: phk@freefall.cdrom.com, CVS-commiters@freefall.cdrom.com, cvs-sys@freefall.cdrom.com In-Reply-To: <199505120403.VAA14015@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 11, 95 09:03:54 pm Content-Type: text Content-Length: 873 Sender: cvs-sys-owner@freebsd.org Precedence: bulk > > I'm about to jump on the swap-initialization, and having talked > > with davidg about it, I hereby kill two undocumented misfeatures: > ... > > We are getting very close to code freeze for 2.0.5, is this such a good > idea at this time? The kernel seems to be very stable right now, and > as soon as Jordan reviews a document why I am saying this will become > obvious. > The problem is that we will have problems if we don't do this. What I'm gonna do is essentially to move the swapinit() call to when the first swapon is done. That way sysinstall can safely fiddle swap-partitions and later swapon to one of them. Long range plans are more comprehensive, but not 2.0.5 stuff. -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'