From: Barry.SCHWARTZ@chemoelectric.org
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] 64-bit or 32-bit?
Date: Tue, 12 Jul 2005 09:58:37 -0500 [thread overview]
Message-ID: <20050712145837.GA17898@crud.crud.mn.org> (raw)
In-Reply-To: <42D3A936.8060306@anand.org>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Anand Buddhdev <arb@anand.org> wrote:
> One of the choices I'm facing is whether to install gentoo 64-bit, or
> 32-bit. Installing 32-bit on the AMD64 would make life easy, but kind of
> defeats the purpose of having a 64-bit processor. Hence my request for
> opinions. Should I go 64-bit, or stay in the 32-bit world for now?
If you need to run DOSEMU, you need to go 32-bit, and it's going to
stay that way. (The same is _not_ true for Wine, you can run that in
64-bit Gentoo.) Otherwise IMO if you like playing with the OS then go
64, otherwise consider going 32. If you don't like playing with the
OS, however, then why use Gentoo? :) So that probably means you
should go 64.
I have a 32-bit chroot that is almost as complete as my 64-bit stuff.
Effectively this means I can often use a 32-bit program from within
the chroot in nearly the same fashion as if I were running it on a
separate 32-bit installation. It means more system maintenance work,
however.
--
Barry.SCHWARTZ@chemoelectric.org http://www.chemoelectric.org
Esperantistoj rajtas skribi al Barijo.SXVARCO@chemoelectric.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-12 15:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 11:27 [gentoo-amd64] 64-bit or 32-bit? Anand Buddhdev
2005-07-12 13:01 ` Mike Melanson
2005-07-12 14:24 ` Bob Sanders
2005-07-12 14:57 ` Zac Medico
2005-07-12 14:58 ` Barry.SCHWARTZ [this message]
2005-07-12 15:37 ` [gentoo-amd64] " Duncan
2005-07-12 17:51 ` Kyle Liddell
2005-07-12 20:19 ` Richard Freeman
2005-07-12 16:51 ` [gentoo-amd64] " Richard Freeman
2005-07-12 17:27 ` gh
-- strict thread matches above, loose matches on Subject: below --
2006-03-26 15:33 JimD
2006-03-26 15:45 ` Mike Arthur
2006-03-26 17:09 ` Simon Stelling
2006-03-26 17:50 ` Hemmann, Volker Armin
2006-03-26 18:27 ` Jim
2006-03-26 19:03 ` Hemmann, Volker Armin
2006-03-26 21:20 ` Barry.SCHWARTZ
2006-03-26 23:08 ` Jim
2006-03-27 0:10 ` Barry.SCHWARTZ
2006-03-28 15:17 ` Bertrand Jacquin
2006-03-28 22:06 ` Barry.SCHWARTZ
2006-03-28 22:20 ` Simon Stelling
2006-03-28 22:27 ` Barry.SCHWARTZ
2006-03-29 10:21 ` Bertrand Jacquin
2006-03-29 15:35 ` Simon Stelling
2006-03-29 17:25 ` Mike Arthur
2006-03-29 17:36 ` Simon Stelling
2006-03-29 17:58 ` Mike Arthur
2006-03-29 20:43 ` Barry.SCHWARTZ
2006-03-28 22:49 ` Marco Matthies
2006-03-29 10:19 ` Bertrand Jacquin
2006-03-29 11:14 ` Marco Matthies
2006-03-29 12:58 ` Vladimir G. Ivanovic
2006-03-29 15:30 ` Simon Stelling
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=20050712145837.GA17898@crud.crud.mn.org \
--to=barry.schwartz@chemoelectric.org \
--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