From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NFmEJ-00009R-NH for garchives@archives.gentoo.org; Wed, 02 Dec 2009 10:14:40 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 58663E0965 for ; Wed, 2 Dec 2009 10:14:39 +0000 (UTC) Received: from mail-fx0-f217.google.com (mail-fx0-f217.google.com [209.85.220.217]) by pigeon.gentoo.org (Postfix) with ESMTP id 2CFF9E0652 for ; Wed, 2 Dec 2009 09:17:33 +0000 (UTC) Received: by fxm9 with SMTP id 9so5266902fxm.10 for ; Wed, 02 Dec 2009 01:17:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:content-type; bh=0eKK+XMsjniKtMyi9KxNbuv16872+A0ABZObErLaVB4=; b=JdNB2esV0FI99zyT92v60WNF4UfTkluKLnBAMjl/5A3noOLMR1G7kkKuXj6uIXPdDi KKJVB8/eoR+5YXu3fWZXGWy8dukdwCwbnCLmExJbbcCQiIyYIYkEc39yBAURPZBx+YI/ YLXUoVllWGws2OW0E0VCdg/DknWd+tha70e5w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=d1pHcEKjh0T6tBQWpWAnPU0zp87BX1Y4lYbRbpPBQxnKqLVBFAYmRvrkGWRI96tJbk 8mKVdDwomdRq3EARYzfGO1SaTMa9O4sWKVNR0bQT/1ihkeHhLVF2X5oVHy9TmK4Vn7j3 HPYX7BZOwPrpVlP2rpnsLI2AQq0CewgsRhyjo= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-embedded@lists.gentoo.org Reply-to: gentoo-embedded@lists.gentoo.org MIME-Version: 1.0 Received: by 10.223.54.23 with SMTP id o23mr1030261fag.72.1259745452297; Wed, 02 Dec 2009 01:17:32 -0800 (PST) From: Shinkan Date: Wed, 2 Dec 2009 10:17:12 +0100 Message-ID: <166af1cf0912020117u6e0222d8g2edafe5466fb9523@mail.gmail.com> Subject: [gentoo-embedded] Re: [OT] Catalyst To: gentoo-embedded@lists.gentoo.org Content-Type: multipart/alternative; boundary=0015174757a4310e070479bb5870 X-Archives-Salt: dcc1a86b-c07c-4078-b8f3-ba22b2f35046 X-Archives-Hash: d2017dc8822783116696d7bd597624f8 --0015174757a4310e070479bb5870 Content-Type: text/plain; charset=UTF-8 2009/12/2 Eckard Brauer > My favourite target would be to Gentoo-ify a couple of servers -- means > to have a flexible build system. That in turn means to build different > types of targets (database, xen-host, app-engine, web server, etc.; I > already can do that with stage4) and to individually (1) fill that > targets with (1.a) configuration, (1.b) some custom code and data and > (2) build one or more (non-ISO9660) file system image(s) of it, which > can be sent to a LV or a storage system for use (boot) afterwards. > Hi ecki. Looking at catalyst stage4 example spec file (/usr/share/doc/catalyst-x.y/examples/), I would recommend the "stage4/root_overlay" directive, which basically put a layer upon your stage. So let's say you put your additional binaries and conf files in /myfiles/, you'll just have to say : stage4/root_overlay = "/myfiles/" and content of /myfiles/ will be cped over your target stage4 / The same goes with livecd-stage2 spec file : you can put a layer over your CD / filesystem. You can even put files on the CD directly with same kind of var defining. That solves 1). Concerning 2), I have absolutely no idea, but I think it's not possible without hacking in catalyst "bins". -- Pierre. "Sometimes when I'm talking, my words can't keep up with my thoughts. I wonder why we think faster than we speak. Probably so we can think twice." - Bill Watterson --0015174757a4310e070479bb5870 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
2009/12/2 Eckard Brauer &l= t;ecki@intershop.de>
=
My favourite target would be to Gentoo-ify a couple of servers -- means
to have a flexible build system. That in turn means to build different
types of targets (database, xen-host, app-engine, web server, etc.; I
already can do that with stage4) and to individually (1) fill that
targets with (1.a) configuration, (1.b) some custom code and data and
(2) build one or more (non-ISO9660) file system image(s) of it, which
can be sent to a LV or a storage system for use (boot) afterwards.

Hi ecki.

Looking at catalyst stage4 example spec file (/usr/share/doc/catalyst-x.y/examples/), I would recommend the "stage4/root_overlay" directive, which basically put a layer upon= your stage.
So let's say you put your additional binaries and conf files in /myfile= s/, you'll just have to say :
stage4/root_overlay =3D "/myfiles/"
and content of /myfiles/ will be cped over your target stage4 /
The same goes with livecd-stage2 spec file : you can put a layer over your CD / filesystem. You can even put files on the CD directly with same kind of var defining.
That solves 1).
Concerning 2), I have absolutely no idea, but I think it's not possible= without hacking in catalyst "bins".




--
Pierre.
"Sometimes when I'm talking, my= words can't keep up with my thoughts. I wonder why we think faster tha= n we speak. Probably so we can think twice." - Bill Watterson
--0015174757a4310e070479bb5870--