From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-catalyst+bounces-2564-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 1B9C6138B45
for <garchives@archives.gentoo.org>; Wed, 20 Feb 2013 16:55:34 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id EBF87E0539;
Wed, 20 Feb 2013 16:55:31 +0000 (UTC)
Received: from mail-ia0-f175.google.com (mail-ia0-f175.google.com [209.85.210.175])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 6D32CE0539
for <gentoo-catalyst@lists.gentoo.org>; Wed, 20 Feb 2013 16:55:31 +0000 (UTC)
Received: by mail-ia0-f175.google.com with SMTP id r4so7254735iaj.20
for <gentoo-catalyst@lists.gentoo.org>; Wed, 20 Feb 2013 08:55:30 -0800 (PST)
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:content-type;
bh=quJeJGmze+jsYVQZQn0q5BJa1kkX67Mtc/L1Yc5cqUY=;
b=KRa8so+Bsn5o9GovWFlwfxfKhHcuMczWs2mmowhr08p9Tk+8LK1fJhyQSsfIZF9Y4Q
+jDLYV9IxF59KvEUIQQz/LEdV/cda7tF1qQJnmBR+ZDqrZ8AqlnQsbBX3USk03qE1nI7
EHyJWm15k1ART/kjdzAQjMkD0tVPkMLK6vqCN4IA2NeTbjlrN+SvEl+gBoC1Ohjjb3oC
NX10SGkvS+SUxdItrp63YflCAw1hRCX2PEQN2QXvtggnEhLEyWgliuVWqo8qKqjKevVj
4WTnQwA6Ifq5BO5RFVgYBIMkAds+FYvnzt0hZyXh+1tDY3qbVEDMtQ1x2yZwnNbMsm1Q
GGTA==
Precedence: bulk
List-Post: <mailto:gentoo-catalyst@lists.gentoo.org>
List-Help: <mailto:gentoo-catalyst+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-catalyst+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-catalyst+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-catalyst.gentoo.org>
X-BeenThere: gentoo-catalyst@lists.gentoo.org
Reply-to: gentoo-catalyst@lists.gentoo.org
MIME-Version: 1.0
X-Received: by 10.50.194.129 with SMTP id hw1mr11361911igc.8.1361379330691;
Wed, 20 Feb 2013 08:55:30 -0800 (PST)
Received: by 10.64.176.161 with HTTP; Wed, 20 Feb 2013 08:55:30 -0800 (PST)
In-Reply-To: <5124FF04.5020201@arskom.com.tr>
References: <5124FF04.5020201@arskom.com.tr>
Date: Wed, 20 Feb 2013 08:55:30 -0800
Message-ID: <CA+_+8cpQw6NPqZCD5Zf=L36YBNs2kzXmz=wSP_EvwR59P_O-uA@mail.gmail.com>
Subject: Re: [gentoo-catalyst] ship /usr/portage with stage4
From: Chris White <chris.chriswhite@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Content-Type: multipart/alternative; boundary=14dae9340e5b6911d804d62ad32e
X-Archives-Salt: 7a1c763b-e89b-4110-a411-88f406b9d1fe
X-Archives-Hash: 5cdf55125a8a562bd8b02d56b4ecff60
--14dae9340e5b6911d804d62ad32e
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Feb 20, 2013 at 8:51 AM, Burak Arslan <burak.arslan@arskom.com.tr>wrote:
> Hi there,
>
> I've set up my first stage4 catalyst job and everything seems to be in
> order.
>
> My final gripe with it is that I couldn't get it to ship the contents of
> /usr/portage inside the stage4 tarball. Having looked at the source, I
> guess that's because the latest portage snapshot is mount --bind'ed to the
> chroot environment, which is unmounted before creating the tarball.
>
> Any suggestions? Am I missing something obvious here?
>
Yes, you need to disable snapcache in your catalyst config `options` value:
# snapcache = cache the snapshot so that it can be bind-mounted into the
chroot.
# WARNING: moving parts of the portage tree from within fsscript *will*
break
# your cache. The cache is unlinked before any empty or rm processing,
though.
#
In general I tend to keep a different catalyst config for stage 4 and stage
1-3, passing in the appropriate config file using `-c`
- Chris
--14dae9340e5b6911d804d62ad32e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">On Wed, Feb 20, 2013 at 8:51 AM, Burak Arslan <span dir=3D=
"ltr"><<a href=3D"mailto:burak.arslan@arskom.com.tr" target=3D"_blank">b=
urak.arslan@arskom.com.tr</a>></span> wrote:<br><div class=3D"gmail_extr=
a"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">Hi there,<br>
<br>
I've set up my first stage4 catalyst job and everything seems to be in =
order.<br>
<br>
My final gripe with it is that I couldn't get it to ship the contents o=
f /usr/portage inside the stage4 tarball. Having looked at the source, I gu=
ess that's because the latest portage snapshot is mount --bind'ed t=
o the chroot environment, which is unmounted before creating the tarball.<b=
r>
<br>
Any suggestions? Am I missing something obvious here?<br>
</blockquote></div><br></div><div class=3D"gmail_extra" style>Yes, you need=
to disable snapcache in your catalyst config `options` value:</div><div cl=
ass=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><div class=3D"gmai=
l_extra">
# snapcache =3D cache the snapshot so that it can be bind-mounted into the =
chroot.</div><div class=3D"gmail_extra">#<span class=3D"" style=3D"white-sp=
ace:pre"> </span>WARNING: moving parts of the portage tree from within fssc=
ript *will* break</div>
<div class=3D"gmail_extra">#<span class=3D"" style=3D"white-space:pre"> </s=
pan>your cache. The cache is unlinked before any empty or rm processing, th=
ough.</div><div class=3D"gmail_extra">#</div><div class=3D"gmail_extra"><br=
></div>
<div class=3D"gmail_extra" style>In general I tend to keep a different cata=
lyst config for stage 4 and stage 1-3, passing in the appropriate config fi=
le using `-c`</div><div class=3D"gmail_extra" style><br></div><div class=3D=
"gmail_extra" style>
- Chris</div></div></div>
--14dae9340e5b6911d804d62ad32e--