From: <burlingk@cv63.navy.mil>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] Semi OT: 64 bit processors, the Linux Kernel, and x86 Gentoo.
Date: Fri, 25 May 2007 18:09:00 +0900 [thread overview]
Message-ID: <AA0639A1EB70AE409130258CE7BDC3183237ED@messenger.cv63.navy.mil> (raw)
> -----Original Message-----
> From: Boyd Stephen Smith Jr. [mailto:bss03@volumehost.net]
> Sent: Friday, May 25, 2007 5:07 PM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] Semi OT: 64 bit processors, the
> Linux Kernel, and x86 Gentoo.
>
>
> On Friday 25 May 2007 02:12:49 burlingk@cv63.navy.mil wrote:
> > My question is this, If I enabel 64 bit support in the kernel,
>
> You mean run a 64-bit kernel with 32-bit support. There's no
> such thing as a
> 32-bit kernel with 64-bit support (at least not in x86-land).
>
> > is that
> > likely to cause any issues with running the 32bit compiled software?
>
> No, it won't, but it's a little bit tricky to set up. You'll
> want to use an
> i686 stage3, and set ARCH to x86 or ~x86. Then, you'll have
> to install a
> cross compiler (and binutils, IIRC) and cross-compile your kernel.
>
> You could always just use a 32-bit kernel. Do you have 3G or
> more RAM or need
> to run 64-bit programs?
So, unless I need the upper memory support, it may be better for me to
just not click the flag for 64bit memory support, and move on?
This is on a laptop, and it is not a critical system (i.e. it is not
going to require that I get those last few dredges of CPU time out of
the system). The main things it will be used for until I build my next
system is dataprocessing, and Pencil and Paper gaming. I plan to
install a couple graphics related apps to mess with and practice with as
well. :P
I'm not exactly the average user, but I will be using it for average
user level work, so it doesn't HAVE to have 64 bit support. :P From
what I understand, the processor handles 32 bit emulation just fine.
(It was running Windows XP fine until a runin with the emphamous Gentoo
GTK installer.)
:P I'm not blaming the software though. The Walkthrough, and the
readme both warn that it is experimental. ^^;; Then there is the fact
that I had just butted a 700MB CD, that loaded a compressed file system
into 512MB of ram, and told it to load a GUI, and a GUI driven install
system. *shrugs* Live and learn, and kick yourself when you do
something stupid. :P
^_^
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2007-05-25 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 9:09 burlingk [this message]
2007-05-25 9:28 ` [gentoo-user] Semi OT: 64 bit processors, the Linux Kernel, and x86 Gentoo Boyd Stephen Smith Jr.
-- strict thread matches above, loose matches on Subject: below --
2007-05-25 14:12 burlingk
2007-05-25 19:54 ` Peter Alfredsen
2007-05-25 12:44 burlingk
2007-05-25 13:54 ` Peter Alfredsen
2007-05-25 9:53 burlingk
2007-05-25 11:08 ` Boyd Stephen Smith Jr.
2007-05-25 12:31 ` Denis
2007-05-25 13:06 ` Florian Philipp
2007-05-25 7:12 burlingk
2007-05-25 8:07 ` Boyd Stephen Smith Jr.
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=AA0639A1EB70AE409130258CE7BDC3183237ED@messenger.cv63.navy.mil \
--to=burlingk@cv63.navy.mil \
--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