From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Introduce Manual manipulation during an emerge
Date: Sat, 13 Jun 2009 08:57:33 -0500 [thread overview]
Message-ID: <ur5xob5iq.fsf@newsguy.com> (raw)
In-Reply-To: 1244852387.4849.63.camel@alienhaven-ubuntu
"Arttu V." <arttuv69@gmail.com> writes:
> Is there a reason to use i486 stage3? I think an i686 one might have
> been available and a better hit if your system is/was set up as an i686
> before this? Well, not that it counts now, gotta go with what you have
> unpacked.
Looking at those stages again... it is not apparent in any way that I
should have gotten something besides x86.
I see there is an i686. But apparently I was to slow to figure out
that I needed it.
Thanks ... I'm working thru the CHOST doc now.
prev parent reply other threads:[~2009-06-13 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 19:59 [gentoo-user] Introduce Manual manipulation during an emerge Harry Putnam
2009-06-12 20:16 ` Stroller
2009-06-12 20:57 ` [gentoo-user] " Harry Putnam
2009-06-12 20:43 ` [gentoo-user] " Mike Kazantsev
2009-06-12 20:58 ` [gentoo-user] " Harry Putnam
2009-06-12 21:22 ` Harry Putnam
2009-06-12 23:20 ` Arttu V.
2009-06-12 23:39 ` Harry Putnam
2009-06-13 0:19 ` Arttu V.
2009-06-13 13:57 ` Harry Putnam [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=ur5xob5iq.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=gentoo-user@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