From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 32bit or 64bit
Date: Tue, 17 Jul 2012 11:36:27 +0800 [thread overview]
Message-ID: <1342496187.15312.7.camel@troll> (raw)
In-Reply-To: <CAK2H+edta5J11ppugd4DSn9hYShqhtKHXitNwHLTZDOnQLbLVA@mail.gmail.com>
On Mon, 2012-07-16 at 19:52 -0700, Mark Knecht wrote:
> On 7/16/12, Nilesh Govindrajan <contact@nileshgr.com> wrote:
> > So the same old query again I guess.
> > What architecture should I use for a machine with 3GB RAM and a 64bit
> > processor?
> >
> > I believe 64bit should be given serious consideration only if RAM is gt or
> > = 4 GB, even there 32bit is allowable with PAE if I'm not wrong.
> >
> > So what is recommended? There are as such no special use cases to go 64bit
> > for me.
> >
>
> Why 32? ... Flash, win32 codecs, probably Wine but not sure as it has
> been years...
>
> Why 64? ... Virtualization...
>
> Depends on what you want and/or need.
>
> HTH,
> Mark
>
Virtualisation ? I am running qemu (windows, gentoo), vbox (windows,
gentoo, fedora) and gxemul (ultrix) all 32 bit guests on 32 bit systems
on either 32 or 64 bit hardware running gentoo - can you confirm you
need 64bit for 64bit guests as I will be moving that way eventually?
That being said, I think for future proofing 64bit is the way to go, I
can see a time when 32bit is going to get deprecated.
Billk
next prev parent reply other threads:[~2012-07-17 3:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 2:22 [gentoo-user] 32bit or 64bit Nilesh Govindrajan
2012-07-17 2:39 ` [gentoo-user] " »Q«
2012-07-17 2:52 ` [gentoo-user] " Mark Knecht
2012-07-17 3:04 ` Michael Mol
2012-07-17 3:29 ` Mark Knecht
2012-07-17 4:23 ` Michael Mol
2012-07-17 14:18 ` Mark Knecht
2012-07-17 14:32 ` Michael Mol
2012-07-18 11:20 ` Neil Bothwick
2012-07-17 13:36 ` Pandu Poluan
2012-07-17 13:49 ` Leiking
2012-07-17 14:04 ` Nilesh Govindrajan
2012-07-17 16:34 ` Volker Armin Hemmann
2012-07-17 3:36 ` Bill Kenworthy [this message]
2012-07-17 4:25 ` Michael Mol
2012-07-17 6:25 ` J. Roeleveld
2012-07-17 7:05 ` Volker Armin Hemmann
2012-07-17 8:57 ` [gentoo-user] " Nikos Chantziaras
2012-07-17 16:31 ` [gentoo-user] " Volker Armin Hemmann
2012-07-17 16:38 ` Michael Mol
2012-07-17 16:43 ` Alecks Gates
2012-07-17 20:57 ` [gentoo-user] " Nikos Chantziaras
2012-07-17 21:14 ` Alecks Gates
2012-07-19 12:55 ` Nikos Chantziaras
2012-07-19 13:03 ` Michael Mol
2012-07-19 13:31 ` Nikos Chantziaras
2012-07-19 13:43 ` Alan McKinnon
2012-07-19 13:53 ` Michael Hampicke
2012-07-19 14:06 ` Michael Mol
2012-07-19 14:14 ` Nikos Chantziaras
2012-07-19 14:33 ` Michael Mol
2012-07-19 21:42 ` Alan McKinnon
2012-07-17 21:21 ` Paul Hartman
[not found] ` <CAHgBc-sQm0VVUGHWG8E2q=DGKs_iaMHsmw1-5s-F7ozvX_vsKg@mail.gmail.com>
2012-07-18 2:19 ` Nilesh Govindrajan
2012-07-17 16:44 ` [gentoo-user] " Mark Knecht
2012-07-17 18:13 ` Michael Hampicke
2012-07-17 18:23 ` Mark Knecht
2012-07-17 18:32 ` Michael Mol
2012-07-17 18:47 ` Michael Hampicke
2012-07-17 18:49 ` Mark Knecht
2012-07-17 18:58 ` Michael Mol
2012-07-17 19:18 ` Mark Knecht
2012-07-19 5:34 ` J. Roeleveld
2012-07-19 12:57 ` Mark Knecht
2012-07-19 16:30 ` Volker Armin Hemmann
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=1342496187.15312.7.camel@troll \
--to=billk@iinet.net.au \
--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