Hi,
now I have my MSI K8T Neo mainboard with an Athlon64 3200+. I intend to start testing the FC2 development tree.
Before I start installing it, I would like to ask how can I make a dual arch system from both te i386 and the x86_64 packages?
Can anaconda detect the situation where I already instelled the i386 version and keep them while installing the x86_64 version?
Justin M. Forbes suggested (Re: Fedora/x86_64 vs 32-bit user space) that I try to make a dual boot. How can I share /boot? Both kernel-2.6.1-1.34.i686.rpm and kernel-2.6.1-1.34.x86_64.rpm has the same kernel filename.
On Tue, Jan 13, 2004 at 10:23:12AM +0100, Boszormenyi Zoltan wrote:
Before I start installing it, I would like to ask how can I make a dual arch system from both te i386 and the x86_64 packages?
You might be better off starting off with a proper biarch tree. If you look at the AMD64 FAQ http://wwww.linuxtx.org/amd64faq.html it will point you to the FC1 preview tree. Once you install that, you can point yum to the development repositories and it should do the right thing (update the proper packages both 32bit and 64bit).
Can anaconda detect the situation where I already instelled the i386 version and keep them while installing the x86_64 version?
This method is not recommended as most packages are actually conflicting. libs are meant to be installed biarch and libtool handles things to make sure the right bin gets the right libs.
Justin M. Forbes suggested (Re: Fedora/x86_64 vs 32-bit user space) that I try to make a dual boot. How can I share /boot? Both kernel-2.6.1-1.34.i686.rpm and kernel-2.6.1-1.34.x86_64.rpm has the same kernel filename.
By dual boot, I was referring to a full installation of both the 32bit FC OS and the 64bit FC OS. They can share /home and data filesystems, but they definately need seperate /boot, /usr, and preferably /etc and /var. This is only really of use if you need to run 32bit games (64bit DRI cannot run 32bit with hardware acceleration), or perhaps for running things like VMWare or other 32bit apps which include kernel modules.
Hope this helps, Justin M. Forbes
Hi,
thanks for the answer.
Justin M. Forbes írta:
You might be better off starting off with a proper biarch tree. If you look at the AMD64 FAQ http://wwww.linuxtx.org/amd64faq.html it will point
Thanks for the pointer.
you to the FC1 preview tree. Once you install that, you can point yum to the development repositories and it should do the right thing (update the proper packages both 32bit and 64bit).
Can anaconda detect the situation where I already instelled the i386 version and keep them while installing the x86_64 version?
This method is not recommended as most packages are actually conflicting. libs are meant to be installed biarch and libtool handles things to make sure the right bin gets the right libs.
I see.
Justin M. Forbes suggested (Re: Fedora/x86_64 vs 32-bit user space) that I try to make a dual boot. How can I share /boot? Both kernel-2.6.1-1.34.i686.rpm and kernel-2.6.1-1.34.x86_64.rpm has the same kernel filename.
By dual boot, I was referring to a full installation of both the 32bit FC OS and the 64bit FC OS. They can share /home and data filesystems, but they definately need seperate /boot, /usr, and preferably /etc and /var. This is only really of use if you need to run 32bit games (64bit DRI cannot run 32bit with hardware acceleration), or perhaps for running things like VMWare or other 32bit apps which include kernel modules.
Yes, I already guessed that I will need separate / (containing /etc ...), /usr, /var for a dual boot. What I wanted to achieve is to have a single boot menu. As the current situation stands, I will need two /boot and manually set up an entry in the default one -it would be the 32 bit Fedora- so it boots another grub (that boots the 64 bit Fedora). An entry similar to one that boots into a Win* should do, at least I hope.
Hope this helps, Justin M. Forbes
Thanks.
On Tue, Jan 13, 2004 at 03:06:21PM +0100, Boszormenyi Zoltan wrote:
Yes, I already guessed that I will need separate / (containing /etc ...), /usr, /var for a dual boot. What I wanted to achieve is to have a single boot menu. As the current situation stands, I will need two /boot and manually set up an entry in the default one -it would be the 32 bit Fedora- so it boots another grub (that boots the 64 bit Fedora). An entry similar to one that boots into a Win* should do, at least I hope.
When you do the install, I believe it will set this up automatically, if not, simply add the entry from grub.conf in the first installation to the grub.conf on the second installation. The second will overwrite the first, so its grub.conf will be the one that matters. That grub instance can boot any other linux image.
Justin
Justin M. Forbes írta:
On Tue, Jan 13, 2004 at 03:06:21PM +0100, Boszormenyi Zoltan wrote:
Yes, I already guessed that I will need separate / (containing /etc ...), /usr, /var for a dual boot. What I wanted to achieve is to have a single boot menu. As the current situation stands, I will need two /boot and manually set up an entry in the default one -it would be the 32 bit Fedora- so it boots another grub (that boots the 64 bit Fedora). An entry similar to one that boots into a Win* should do, at least I hope.
When you do the install, I believe it will set this up automatically, if not, simply add the entry from grub.conf in the first installation to the grub.conf on the second installation. The second will overwrite the first, so its grub.conf will be the one that matters. That grub instance can boot any other linux image.
Justin
I downloaded the preview and I used the network install with the boot.iso. It didn't find any previous Fedora install but the 32 bit Fedora was already installed. So no automatic GRUB setup. I choose to install GRUB into the /boot boot sector of the x86_64 installation instead of letting overwrite the previously installed GRUB in the MBR. In the 32 bit /boot I have this GRUB entry:
title Fedora Core AMD64 GRUB rootnoverify (hd0,1) makeactive chainloader +1
It then correctly boot the x86_64 /boot GRUB which then boots the 64 bit kernel... This has the advantage that the two /boot/grub/grub.conf are not confused on kernel upgrades. I am not sure that what you suggested keeps everyone happy on kernel upgrades. I think the %post scripts watch the kernel versions in the GRUB entries and update every matching one.
Now I can go and upgrade to Fedora Core 2 Devel... :-)