public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: Re: VMware Player on Gentoo question
Date: Sun, 12 Mar 2006 02:19:50 -0700	[thread overview]
Message-ID: <pan.2006.03.12.09.19.49.405720@cox.net> (raw)
In-Reply-To: 1142129346.11048.1.camel@localhost

Antoine Martin posted <1142129346.11048.1.camel@localhost>, excerpted
below,  on Sun, 12 Mar 2006 02:09:06 +0000:

>> What would I need to do to get the 32-bit area to build a 32-bit
>> kernel? When I run make menuconfig and try to change the processor I'm
>> only given 2 64-bit options.
> Have you tried:
> make ARCH=i386 menuconfig
> make ARCH=i386

This was news to me -- I hadn't tried that.

What I would have done if I were creating a 32-bit chroot I intended to
boot, would be start from a 32-bit liveCD and do the entire Gentoo install
as if I were on a 32-bit machine installing Gentoo in its own partitions
along with some other OS -- that the other OS was Gentoo for amd64
wouldn't matter, as the two would be entirely separate installs -- only
from the 64-bit install some of the 32-bit could be mounted as a 32-bit
chroot.

I had always wondered how one got a 32-bit kernel config from a 64-bit
system, without starting from a 32-bit system already.  Assuming this is
correct, very cool, my wondering answered! =8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-03-12  9:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08  1:06 [gentoo-amd64] VMware Player on Gentoo question Mark Knecht
2006-03-08  6:25 ` Thierry de Coulon
2006-03-09  1:54   ` Richard Freeman
2006-03-09  2:45   ` Mark Knecht
2006-03-09 12:44     ` Thierry de Coulon
2006-03-09 14:30       ` Mark Knecht
2006-03-11  7:58         ` Thierry de Coulon
2006-03-11 15:30           ` Mark Knecht
2006-03-11 16:29             ` Thierry de Coulon
2006-03-11 16:58               ` Mark Knecht
2006-03-11 17:22                 ` Thierry de Coulon
2006-03-11 18:53                   ` Mark Knecht
2006-03-11 18:57                     ` Mark Knecht
2006-03-11 19:05                       ` Thierry de Coulon
2006-03-11 19:27                         ` Mark Knecht
2006-03-11 23:52                           ` [gentoo-amd64] " Duncan
2006-03-12  0:52                             ` Mark Knecht
2006-03-12  2:09                               ` Antoine Martin
2006-03-12  9:19                                 ` Duncan [this message]
2006-03-12 19:36                                 ` Mark Knecht
2006-03-13 15:05                           ` [gentoo-amd64] " Mark Knecht
2006-03-09 16:22       ` Marco Matthies
2006-03-09 17:30         ` Thierry de Coulon
2006-03-09 18:05           ` Marco Matthies
2006-03-09 18:28         ` Mark Knecht
2006-03-09 19:09           ` Nuitari
2006-03-09 19:32           ` Marco Matthies
2006-03-09 14:22     ` Paul de Vrieze
2006-03-09 14:45       ` Nuitari
2006-03-09 14:51         ` Mark Knecht
2006-03-10  9:00           ` Paul de Vrieze

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=pan.2006.03.12.09.19.49.405720@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@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