Search the Community
Showing results for tags 'upgrade'.
Found 2 results
So I noticed multilib support is being removed with the 1.3 release. I personally welcome moving to pure AMD64 and have done so ages ago on most machines I manage, but then there's all that pesky ｐｒｏｐｒｉｅｔａｒｙ ｓｏｆｔｗａｒｅ that cannot be recompiled at-will. I've seen the wiki guide on running a x86 chroot as a workaround, but it looks like it creates a purely AMD64 system with a purely x86 system in a chroot. But I'd like to clear something out: with this particular approach, is it possible to somehow fuse the base system with whatever is in the chroot to make a makeshift multilib-like system? Reason for asking this is because in particular, some games require additional x86 software to launch / run, while the game itself outright requires AMD64 (e.g. running a AMD64-only game on steam, which itself needs x86). How about Wine, too? To quote Wine Wiki: "Even many 64-bit programs still include 32-bit components" (applicable to windows software), so being able to have a WoW64 build of wine would also be preferred, again, mostly for AMD64-only games. If that is not possible, I suppose I could try to run a gentoo chroot within my funtoo gaming machine, but this brings a multitude of other problems, so I'd rather not, if possible. :V TL;DR how do I run games that effectively require both x86 and AMD64 to function after upgrading Funtoo to 1.3?
Yesterday night I performed a global upgrade of all my packages, noticed that it had genkernel updates included. The system upgraded nice and clean. I was doing my work while it worked. Turned off my PC after a depclean. But it seems that I had to eselect and boot-update the new kernel before doing that for now I can't boot to my OS anymore. Ok... Burned a System rescuecd 4.7.1 (the most recent on the install page). To try mounting my Funtoo installation directories and doing what I forgot last night. My problem is, everytime I boot this System rescuecd from my pen or any of the latest versions of it. I get at certain boot part of this cd what follows: 'Error: Cannot mount sysrcd.dat (none ....kernel details....)' and it gives me the basic terminal. (By the way, I'm currently having to use my Windows instalation, that's the only one that still works and burning the systemrescuecd with lili, (this kind of thing) is one of those situations that never gave any problem such as I reported... I'm stuck, for it never happened to me before. My computer hardware is very recent too. Can any of you guys possibly have an idea for me? Thanks in advance.