public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Rosset <schizoid29@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] making of a catalyst livecd
Date: Fri, 30 Sep 2005 12:35:20 -0700	[thread overview]
Message-ID: <2d28d7d90509301235i502d7566t9916e83ef527d0f3@mail.gmail.com> (raw)
In-Reply-To: <BAY106-F79E44B0F58EB2A180A249D08F0@phx.gbl>

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

 Chip:

If that's all you really need to do then possible the knoppix livecd might
be a better choice. But if you what to hack through catalyst. can you post
the actual error message you are getting.

Regrads,

Mike Rosset

On 9/30/05, Chip DeVoge <bflochip@msn.com> wrote:
>
> Hello I am having a difficult time building a livecd. It is an older AMD,
> connected by network card (unknown model) to interrnet, all they want to
> with it is access hazard.com <http://hazard.com> with firefox and print to
> a HP Laserjet 5i.
> /usr/share/doc/catalyst-1.1.10.10/examples/livecd-stage1_template.spec<http://1.1.10.10/examples/livecd-stage1_template.spec>
> finishes without error. I have eliminated several use flags and packages
> to
> get this far. Then stage2 does not finish. I am using subarch x86. But it
> is
> showing -mcpu-i686 while compiling. Finally stage 2 crashes while
> genkernel
> is compiling the prepare target.
> Any help appreciated,
> Chip
>
>
> --
> gentoo-catalyst@gentoo.org mailing list
>
>

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

  reply	other threads:[~2005-09-30 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 19:12 [gentoo-catalyst] making of a catalyst livecd Chip DeVoge
2005-09-30 19:35 ` Mike Rosset [this message]
2005-09-30 21:25   ` Chip DeVoge
2005-09-30 22:07     ` Mike Rosset
2005-10-03 12:30       ` Chris Gianelloni

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=2d28d7d90509301235i502d7566t9916e83ef527d0f3@mail.gmail.com \
    --to=schizoid29@gmail.com \
    --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