From owner-freebsd-current@FreeBSD.ORG  Sat Apr 20 12:30:27 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id AE5E37FC;
 Sat, 20 Apr 2013 12:30:27 +0000 (UTC)
 (envelope-from kpaasial@gmail.com)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com
 [IPv6:2a00:1450:400c:c05::22d])
 by mx1.freebsd.org (Postfix) with ESMTP id F216B1B7A;
 Sat, 20 Apr 2013 12:30:26 +0000 (UTC)
Received: by mail-wi0-f173.google.com with SMTP id c10so2093165wiw.0
 for <multiple recipients>; Sat, 20 Apr 2013 05:30:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:in-reply-to:references:date:message-id
 :subject:from:to:cc:content-type;
 bh=WetEaqd0L2smFm4B0R6yqhJWyrGjd/RwWz/3ruCDZMo=;
 b=o3VczXVIFbpuK88HVI9X0J1AFo+F+KhgHQFAxegzqMhbO6Ur6dvhwY33Hys6SI7qHS
 TmyaSx5chOogxiYVlyPhk2GRWahWUbPOLoSfoaIK0QchSkm+X7p7aHGzi3AS4y8hPE/q
 zZLEfVM7/Sxp/SEw4aC83gAdJNTGM3/jKtcsPNUwWjOWayOFYjrMTLHFxPP/BErbQPSL
 b+zWqPNhq9PhaWN9Cu17+FzkVdq4sGx9HIjDJ/314ROiH7KiJ6WXlnOHXicAj08WcJEo
 n0t5MXAEOklIiakC9kqZAnT4AcJkEaTpKoCFCHlTz5xWl51jOzrtYuqYykg4dPgFP/RB
 fa2w==
MIME-Version: 1.0
X-Received: by 10.194.157.138 with SMTP id wm10mr34326957wjb.28.1366461026164; 
 Sat, 20 Apr 2013 05:30:26 -0700 (PDT)
Received: by 10.216.139.72 with HTTP; Sat, 20 Apr 2013 05:30:26 -0700 (PDT)
In-Reply-To: <60A8F6C1-2A06-4646-9A28-83608FF23443@FreeBSD.org>
References: <CA+7WWScx1kR3HhNQ_K2hpOh0SFSQnQXwho13QbCB3WtyNjHGig@mail.gmail.com>
 <60A8F6C1-2A06-4646-9A28-83608FF23443@FreeBSD.org>
Date: Sat, 20 Apr 2013 15:30:26 +0300
Message-ID: <CA+7WWSe9GSsVaHBw9F+-anPWwzU4xDQZ4Kc0O9popsKmpREP4w@mail.gmail.com>
Subject: Re: WORLDTMP on a ram disk
From: Kimmo Paasiala <kpaasial@gmail.com>
To: Dimitry Andric <dim@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Cc: freebsd-hackers@freebsd.org, FreeBSD current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Apr 2013 12:30:27 -0000

On Sat, Apr 20, 2013 at 3:16 PM, Dimitry Andric <dim@freebsd.org> wrote:
> On Apr 20, 2013, at 11:55, Kimmo Paasiala <kpaasial@gmail.com> wrote:
>> Poking around the /usr/src/Makefile.inc1 I see that there's a variable
>> called "WORLDTMP" that seems to set the location for temporary files
>> during the world build. My question is now:
>>
>> Is it safe to put WORLDTMP on a ram disk, for example tmpfs(5)?
>>
>> Looking at the build process it seems to me that the temporary files
>> are no longer needed after make buildworld has finished?
>
>
> The problem is that you need those temporary files for installworld, and
> you must reboot with your new kernel before running that...
>

Well that was what I was after, I was somehow under the impression
that the files in WORLDTMP would be moved to more permanent location
under /usr/obj for installworld to find them.

-Kimmo