Sudo cp /mnt/etc/hosts /mnt/etc/hosts.old To do that, run these commands (to leave the chroot, copy the relevant configuration files from the live CD system into the chroot, and re-enter the chroot): sudo cp /mnt/etc/nf /mnt/etc/ If, instead, you were unable to transmit or receive packets, then you'll have to set up Internet connectivity in the chroot. Run ping -c 4 to see if Internet connectivity works fully from within the chroot. Now, run these commands to chroot into your installed system: sudo mount -bind /dev /mnt/dev If your installed system has a separate /boot partition, run sudo mount /dev/sda1 /mnt/boot (replace /dev/sda1 with the device name you got in step 2, if different). Open a Terminal window and run sudo mount /dev/sda2 /mnt (replace /dev/sda2 with the device name you got in step 1, if different). Go into a web browser and make sure that Internet connectivity is fully functional. Remember or write this down as well.īoot from an Oneiric amd64 (i.e., 64-bit) live CD and select "Try Ubuntu" rather than "Install Ubuntu". You'll see something like /dev/sda1 on /boot type ext2 (rw). So in that case, run mount | grep ' on /boot '. If you have a separate /boot partition, then you'll need to know the device name for that as well. Step 1 gave you the device name of the / partition. The part you're interested is the device name before on (in this example, it's /dev/sda2).
You should see something like /dev/sda2 on / type ext4 (rw,errors=remount-ro,commit=0). In your installed Ubuntu system, open a Terminal window ( Ctrl+ Alt+ T) and run mount | grep ' on / ' (by pasting it into the Terminal and pressing enter). (I have chrooted into installed Ubuntu systems from live CD's and performed package management and other operations, but I have not attempted the cross-architecture operations suggested here.) Here are specific instructions for doing that.but please do not take this to mean that I'm saying it will work.
Gta 4 32 bit or 64 bit install#
There are various ways of attempting to install a 64-bit kernel onto a 32-bit system, but they are all extremely complicated, so instead I recommend that you boot from a 64-bit Oneiric live CD (which itself runs a 64-bit kernel), chroot into the installed Ubuntu system, and use the recently installed 64-bit apt and dpkg to install a 64-bit kernel.
In fact, they might not even finish installing, as they might have post-install scripts that invoke their unrunnable 64-bit executables. Of course, once you've installed them, they won't actually run, because their executables are 64-bit and your 32-bit Ubuntu system is running a 32-bit kernel (which will only run 32-bit executables).
You can install all these packages by putting them in a folder that contains nothing else (suppose the folder is called debs and is inside your Downloads directory), and then running this command: sudo dpkg -Ri ~/Downloads/debs Specifically, the files you'll want are: this one for dpkg (and the others listed, too, if you have those packages installed) and this and this and this and this and this for apt.īefore you do anything with these files, you should make sure to back up all important documents in your installed Ubuntu system and any other important files (e.g., music, ebooks, videos), because it is rather likely that attempting this technique will backfire badly and leave your Ubuntu system completely unusable. You can find them at the dpkg in Ubuntu and apt in Ubuntu pages on Launchpad-expand the latest version under "The Oneiric Ocelot" that is marked as release, security, and/or updates (but you probably don't want a version marked only proposed and/or backports, if there ever is one).
Gta 4 32 bit or 64 bit download#
However, if you do wish to attempt this technique, you will have to manually download the. You would be well-advised to instead replace your existing Ubuntu system with a new, 64-bit installation. Furthermore, there is certainly no official support for such an approach. Since some packages will not receive any updates throughout the entire support cycle of your Ubuntu release, you will likely never have a fully amd64 system using such a technique. Only packages that actually receive upgrades will likely be changed in architecture, and probably only if no other packages not being upgraded rely on their being of the i386 architecture. Such an approach is very complicated, and is unlikely to ever result in all your packages being the amd64 version instead of the i386 version.
0 kommentar(er)
