From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] hang up on generating modprobe.conf
Date: Sun, 08 Apr 2007 09:09:05 -0400 [thread overview]
Message-ID: <1176037745.2048.24.camel@vertigo.twi-31o2.org> (raw)
In-Reply-To: <200704072129.10612.SirTwist@web.de>
[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]
On Sat, 2007-04-07 at 21:29 +0200, Simon Schäfer wrote:
> Why? Its used for the minimal installation cd of gentoo. (I got it from
> their .spec - file). This is exactly what i want a minimal linux system with
> nothing then a bootup that detects all my hardware loads all modules and as a
> plus it should have a xinit to start a x based application (yes i know adding
> X will increase the minimal CD by aprox. 25MB).
This is not what you will get. If you are not a member of Release
Engineering, you should *never* use gentoo-release-* for livecd/type as
they are custom tailored to produce the output Release Engineering
expects, including ignoring certain spec fields and overriding them.
You *must* use generic-livecd if producing a CD o fyour own, especially
one with X on it.
> We (me and my roommate) are trying to build a small gentoo-based bootcd with
> xinit. I hoped it could be easy to use catalyst, just some work on spec files
> and then let catalyst do all the work instead of our collection of shell
> scripts. I still hope it could be done this way couse sharing spec files is a
> lot easier then sharing shell scripts and a not so simple howto
It would be fairly easy if you weren't fighting catalyst. Use
livecd/type; generic-livecd and see things become dramatically easier
when stuff quits being done for you, assuming it'll be an official
Gentoo release and built 100% to Release Engineering standards and
practices.
--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-08 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 22:46 [gentoo-catalyst] hang up on generating modprobe.conf Simon Schäfer
2007-04-05 23:09 ` Chris Gianelloni
2007-04-06 0:47 ` Simon Schäfer
2007-04-06 14:37 ` Nelson Batalha
2007-04-07 19:29 ` Simon Schäfer
2007-04-07 20:41 ` Nelson Batalha
2007-04-08 13:15 ` Chris Gianelloni
2007-04-08 14:33 ` Isidore Ducasse
2007-04-08 13:09 ` Chris Gianelloni [this message]
2007-04-06 19:13 ` [gentoo-catalyst] genkernel initramfs overlay older than initramfs' files Isidore Ducasse
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=1176037745.2048.24.camel@vertigo.twi-31o2.org \
--to=wolf31o2@gentoo.org \
--cc=gentoo-catalyst@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