public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@robin.gentoo.org
Subject: Re: [gentoo-catalyst] LiveCD Stage 2 Question
Date: Thu, 31 Mar 2005 15:39:57 -0500	[thread overview]
Message-ID: <1112301597.24040.195.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <424C59A0.6060506@gmail.com>

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

On Thu, 2005-03-31 at 14:12 -0600, Artanin wrote:
> Hello,
> 
> I am working on setting up a custom livecd.  Right now I am just trying
> to get the image to build correctly for the first time.  Right now I am
> working on the livecd-stage2, and I am getting an error with genkernel. 
> I have pulled the config file for the kernel off a running 2005.0 livecd
> (/proc/config.gz > ftp'ed), and working with the 2005.0 templates.  I am

emerge livecd-kconfigs livecd-specs

> working out of a /catalyst directory, so all included spec files are
> working off that assumption.  I have so far had to edit the stage1 fstab
> to remove an error about not being able to mount /boot, as well as had
> to add "sys-kernel/gentoo-sources" to package.keywords and
> package.unmask.  I also have to run catalyst with 'ARCH="x86" catalyst
> -f blah.spec' or I get an error saying that ARCH is undefined.  

If you're having these problems, then you have much bigger problems that
need to be addressed before we will ever be able to troubleshoot
anything else.  I would suggest starting from the specs/kconfigs above,
as they are the 2005.0 versions used to build the release.

> Included with this is my stage1 and stage2 specs, the last log of
> catalyst stage 2 build, and the kernel config I pulled.  Any help would

Yeah, I pretty much didn't read this because of all that extra garbage
that was luckily stripped by my mail server.  Please don't attach this
sort of thing in the future to a mailing list unless it is asked for, it
is not only rude to anyone on dial-up that has to wait for the enormous
email to download, but it also uses up significant resources on Gentoo's
mail server to process.

> be much appreciated.  This work is being done on behalf of a nonprofit
> project that requires a type of re imaging capability and we do not have
> money to buy ghost proper, so we are going to be creative and simulate
> it.  Right now I need to be able to get a default livecd working before
> I can put my overlays onto of it.  I am familiar with Linux, just have
> never tried to build a LiveCD before.

Well, starting from the "official" specs will definitely get you going
in the right direction.  Hopefully you can also solve your problems with
things being masked, which will more than likely just require an update
to your snapshot to something made after the 2005.0 release.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2005-03-31 20:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31 20:12 [gentoo-catalyst] LiveCD Stage 2 Question Artanin
2005-03-31 20:39 ` Chris Gianelloni [this message]

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=1112301597.24040.195.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-catalyst@gentoo.org \
    --cc=gentoo-catalyst@robin.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