32- or 64-bit OS for AMD64 Mythtv
Jarod Wilson
jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org
Thu May 17 15:41:21 EDT 2007
On Thursday 17 May 2007 15:29:53 Derek Atkins wrote:
> Jarod Wilson <jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org> writes:
> >> > Probably won't matter a huge amount. Personally, I've been doing
> >> > 64-bit Myth boxes for a few years now.
> >>
> >> Hmm, then I guess the real question is: how much disk space will
> >> a 64-bit v. 32-bit OS take up? I got a 4GB flash module to use
> >> as my drive for this box so the core OS needs to live on that.
> >
> > My 64-bit Fedora 7 myth backend box has a full compiler toolchain and an
> > assortment of libraries, 64-bit and 32-bit, and it takes up about 2.9G of
> > space. If you nuke all the 32-bit stuff, which it sounds like you won't
> > want (and don't need) for your frontend box, install footprint should be
> > pretty damned similar between 64-bit and 32-bit. Heh, my 32-bit core duo
> > mac mini frontend actually has a larger installation on it than the
> > 64-bit backend (also bigger than my prior 64-bit AMD64 frontend).
>
> Well, in this case I only want it to be a frontend, but I think I want
> to install both the frontend and backend. Good to know it will
> fit :) I'll start the F7t4 x86_64 download now. Hopefully
> converting from F7t4 to F7 will be a simple yum reconfiguration.
> (I've never actually installed a test release before) :)
My frontend (i686), backend (x86_64), laptop (ppc), mail/web server (x86_64)
and workstation (x86_64) have all been running the F7 development tree stuff
for a few months now, with very few ill effects. I do plan to flip them over
to F7-final rather than continuing to track devel (at least for the first few
weeks after release, since rawhide tends to get more explodey during that
time frame). We can compare notes. :)
--
Jarod Wilson
jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the Discuss
mailing list