public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Shinkan <shinkan@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] Re: [OT] Catalyst
Date: Wed, 2 Dec 2009 10:17:12 +0100	[thread overview]
Message-ID: <166af1cf0912020117u6e0222d8g2edafe5466fb9523@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]

2009/12/2 Eckard Brauer <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 /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

[-- Attachment #2: Type: text/html, Size: 1845 bytes --]

                 reply	other threads:[~2009-12-02 10:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=166af1cf0912020117u6e0222d8g2edafe5466fb9523@mail.gmail.com \
    --to=shinkan@gmail.com \
    --cc=gentoo-embedded@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox