Differences

This shows you the differences between two versions of the page.

--- 64bit-migration [2019/01/15 17:48] – snarg
+++ 64bit-migration [2023/06/21 12:02] (current) – snarg
@@ Line 1: / Line 1: @@
-to 64 migration notes:
+Gentoo Live 32 to 64 migration as clean as possible:
-https://www.hattne.se/articles/migration.html
+This is my method - letting portage track every file and package except glibc and ld-linux.so.2 loader. System and all services can remain running. If this is done correctly only 2 reboots will be required.
-have that web site open... the steps are here, but the explanation is there
-my notes:
+  * Keep in mind that pre profile 17.1 and post profile 17.1 will be slightly different as /lib and /usr/lib are not symlinks. These differences are noted in the relevant steps.
   * make sure system is completely up to date and has been depcleaned, preserved-rebuilt and revdep-rebuild - to clean up old 32bit libraries else lots of work later
-  * make sure you have an *identically* up to date 64bit machine (vm?) to copy libraries from
+  * a full up to date backup of the system is a good idea and has saved me in the past.
+  * make sure you have an *identically* up to date 64bit multilib profile VM to create binary packages on. Ensure CFLAGS is going to be identical, or compatible ("-mtune=generic -O2 -pipe" is safe). Make sure USE flags are the same between the systems as this makes live easier when doing emerge -k binarypackage  on the other side. If changes are required to CFLAGS then emerge -e world.
+  * You can use a portage tree from git (on both target system and migration VM) using something like:
+<code>cd /usr
+git clone https://github.com/gentoo/gentoo.git ./gentoo-git
+cd gentoo-git
+git checkout `git rev-list -n 1 --first-parent --before="2020-09-01" master`
+#note backticks</code>
+  * keep in mind if using a portage git snapshot like the above, you will need to read this for crossdev, particularly the bit regarding "masked by corruption" (search for that). The crossdev overlay will need thin-manifests = true : https://wiki.gentoo.org/wiki/Crossdev
+  * read ahead a few points (or the whole page) when starting a step - several problems may be solved in subsequent notes
+  * if problems arise with libraries and mismatched ABI binaries, scp them over from the donor VM as needed. subsequent emerge will overwrite them later.
 == Steps ==
@@ Line 14: / Line 22: @@
   cp /etc/portage/make.conf /migration-backup/
-  * building cross compiler
-  emerge crossdev -av
+  * build cross compiler. This will be used during emerging the glibc BINARY package. it needs a working gcc-x86_64-pc-linux-gnu compiler (which will be still running as i686 ABI under /usr/i686-pc-linux-gnu/x86_64-pc-linux-gnu)
-convert /etc/portage/package.* into directories
-  crossdev -S -s3 --target x86_64-pc-linux-gnu
+<code>emerge crossdev -av</code>
-  * compile x86_64 kernel with ia32 emulation, reboot into it
+  * convert /etc/portage/package.* into directories
-  * get an identical VM with compat arch processor built in x86_64 multilib profile (make sure CFLAGS is *identical* emerge -e world if not - also make sure USE flags are the same, makes live easier when doing emerge -k binarypackage  on the other side)
+<code>crossdev -S -s3 --target x86_64-pc-linux-gnu</code>
+  * ON THE 64bit VM (which will build ia32 emulation by default):
+<code>genkernel all</code>
+  * copy the resulting kernel, initramfs, system.map,  and lib/modules/x.x directory over
+  * reboot test into the 64bit kernel
   * Change CHOST to x86_64-pc-linux-gnu
   * copy lib and /usr/lib and /bin and /usr/bin and /sbin and /usr/sbin to /migration-backup
@@ Line 32: / Line 43: @@
   ldconfig
-  mkdir /lib32
+  mkdir /lib32        (not if donor VM profile is 17.1 and onwards which uses lib and lib64 with no symlink)
   mkdir /lib64
-  mkdir /usr/lib32
+  mkdir /usr/lib32    (not if donor VM profile is 17.1 and onwards which uses lib and lib64 with no symlink)
   mkdir /usr/lib64
@@ Line 41: / Line 52: @@
   rm -Rf /usr/lib/distcc
-  * possibly dont need to do this if using binary packages from donor VM
+  * back up these 32bit crossdev versions, they may be useful if something goes wrong (experience says it may!)
-  cp -ar /usr/x86_64-pc-linux-gnu/lib64/* /lib64
+  cp -ar /usr/x86_64-pc-linux-gnu /migration-backup/usr/
-  cp -ar /usr/x86_64-pc-linux-gnu/usr/lib64/* /usr/lib64/
+  cp -ar /usr/i686-pc-linux-gnu /migration-backup/usr/
+  cp -ar /usr/libexec /migration-backup/usr/
-  cp -ar /usr/include /migration-backup/include32
+  cp -ar /usr/include /migration-backup/usr
-  cp -ar /usr/x86_64-pc-linux-gnu/usr/include/* /usr/include/
-  emerge -1 sys-kernel/linux-headers
   * put -sandbox -usersandbox in features
@@ Line 55: / Line 64: @@
 <code># cat /etc/portage/profile/use.mask
 -abi_x86_32</code>
-  * change make.profile symlink to point to a multilib amd64 profile
+  * change make.profile symlink to point to a multilib amd64 profile. choose 17.0 or 17.1 based on Donor VM profile. be aware of the difference.
-  * use quickpkg on source VM to grab and then PATH="/migration-backup/bin:/migration-backup/usr/bin:/migration-backup/sbin:/migration-backup/usr/sbin:${PATH}" emerge -1kav to deploy initial binary packages donated from prebuilt VM from /usr/portage/packages:
+  * on donor pc or VM (take note of wildcards, adjust if required):
-Of these, glibc needs to come first, then everything else will come good.
-in the process of deploying glibc, /lib needs to be a symlink to /lib64 which will break 32bit programs. ldconfig is your friend here with the above 99migration env file.  Theres a couple other gotchas as well that need working through.
-  * on donor pc or VM:
+  quickpkg glibc gcc zlib ncurses gmp mpfr util-linux acl attr sandbox coreutils procps binutils libcap libxcrypt mpc cracklib flex =db-5* glib pam pambase =python-3* bash readline findutils install-xattr bzip2 tar xz-utils make grep patch gawk sed libpcre dev-libs/libffi gettext libxml2
-  quickpkg glibc gcc zlib ncurses gmp mpfr util-linux acl attr sandbox coreutils procps binutils libcap mpc cracklib flex =db-5* glib pam pambase =python-3.6* bash readline findutils install-xattr bzip2 tar xz-utils make grep patch gawk sed libpcre
+  * on source VM, scp -r /var/cache/binpkgs to target PC
-  * on target pc, mount or rsync /usr/portage/packages and emerge -1k to install them. If theres any differences in USE, set them in the prefix
+  *for this lib / lib64 link <-> switcheroo
+  ** make sure busybox is functional. run this from busybox
+  ** have a few shells open, in case you break the one you're working from
+  ** remember.. if the source VM is profile 17.1 then this system will need to be built using 17.1, so think about making a /lib and /usr/lib folder (and no lib32 folders) rather than symlinking.
-  USE="fix any differences" emerge -1kav <pasted list>
+  mv /lib oldlib
+  ln -s lib64 lib   (not on 17.1 - mkdir lib)
+  cd /usr
+  mv lib to oldlib
+  ln -s lib64 lib   (not on 17.1 - mkdir lib)
-  mv /usr/lib to /usr/oldlib and symlink lib to lib64
+  * this will get overwritten by emerge at the appropriate time, but lets the 32bit loader continue to work for now
-  * /usr/lib symlink creation will break python. The following will not create orphans as the files are in exactly the same location from portage's point of view.
+  cp migration-backup/lib/ld-linux.so.2 /lib
+  ldconfig
+  * /usr/lib symlink creation or directory move will break python. The following will not create orphans as the files are in exactly the same location from portage's point of view. Modify python version(s) as appropriate.
   cd /usr/oldlib
-  mv python-exec python3.6 libpython* portage gcc ../lib64
+  mv python-exec python3.6 libpython* portage gcc ../lib/
+  cp -r /oldlib/gentoo /lib/
-  * remove crossdev packages (and crossdev) and check gcc sanity
+  * disable collision detection and emerge gcc AND binutils using this method:
+<code>LD_PRELOAD="/migration-backup/usr/lib/gcc/i686-pc-linux-gnu/10.3.0/libgcc_s.so.1:/migration-backup/usr/lib/libffi.so.7" PATH="/migration-backup/bin:/migration-backup/usr/bin:/migration-backup/sbin:/migration-backup/usr/sbin:${PATH}"   FEATURES="-collision-detect -protect-owned" emerge -1kav sys-devel/gcc</code>
-  emerge --unmerge cross-x86_64-pc-linux-gnu/* crossdev -av
+  * check  /usr/libexec/gcc/x86_64-pc-linux-gnu/ for any links pointing at i686 versions. remove.
-  ldconfig
+  * continue to deploy initial binary packages using this method (except with collision detection) donated from prebuilt VM from /usr/portage/packages or /var/cache/binpkgs. Of these, mpc, zlib, glibc needs to come first, then everything else will come good. In the process of deploying glibc, /lib needs to be a symlink to /lib64 which will break 32bit programs. see ld-linux.so.2 trick above. ldconfig is your friend here with the above 99migration env file.
-  * fix 32bit toolchain and python in wrong directory by running:
+  * 202112 notes: had to remove the following files to get glibc binary package to emerge:
+<code>/usr/bin/cal
+/bin/date
+/usr/bin/env
+/usr/bin/free
+/bin/ls
+/usr/bin/uname
+/usr/bin/uptime</code>
+These can be restored from these binary packages immediately after getting glibc working:
+<code>emerge -1kav util-linux coreutils procps</code>
+To emerge coreutils, working mv command is required. libattr.so.1 and libacl.so.1 (symlinks.. copy the actual libraries) were copied over from donor VM lib64 directories and appropriate symlinks made. These belong to packages acl and attr binary packages which can then be emerged to account for those files.
+  * If you get into trouble getting 64bit loader working, do this (only if needed):
+  ** backup these: /etc/env.d/99glibc /etc/gai.conf /etc/host.conf /etc/locale.gen /etc/nsswitch.conf /etc/rpc
+  ** extract glibc tbz2 binary package directly into root of filesystem. subsequent remerge will track the files correctly later.
+  ** restore etc files from above backup
-  emerge -1kav sys-devel/gcc glibc mpfr mpc binutils
+  * Now is the right time to remove crossdev versions of the toolchain, as they are now conflicts with our native amd64 versions.  Take a look in the repo directory and unmerge any crossdev packages like gcc glibc binutils etc (fixme: put actual commands here)
+  * This will be needed for fixing things after removing crossdev versions. Fix 32bit toolchain and python in wrong directory by running:
+<code>PKGDIR=/var/cache/binpkgs emerge -1kav sys-devel/gcc mpfr mpc binutils
+  gcc-config 1
   binutils-config 1
-  . /etc/profile
+  . /etc/profile</code>
-  emerge -1av python-exec
-  emerge -1kav =python-3.6* --binpkg-changed-deps=n
-  mv /lib/modules /lib64
-  mv /lib/gentoo /lib64
-  *for the lib / lib64 link <-> switcheroo
+  * Finally now that theres a working coreutils etc, If you manually extracted glibc in previous step, overwrite it with package copy.
-  ** make sure busybox is functional. run this from busybox
-  ** have a few shells open, in case you break the one you're working from
-  mv /lib/modules /lib64
+  PKGDIR=/var/cache/binpkgs emerge -1kav glibc
-  mv /lib/gentoo /lib64
+Double check /etc/nsswitch.conf and other files backed up above, this may have overwritten them again.
-  cd /
-  mv lib oldlib
+<code>mv /migration-backup/lib/modules /lib64</code>  (or to /lib if 17.1 profile)
-  ln -s lib64 lib
   * Emerging gcc needs to be done now, but also acts as a sanity check to see what we've missed. Repeat the quickpkg / emerge -1k steps for missing things
-  emerge gcc -1av
+<code>emerge gcc -1av</code>
-  * remove /etc/env.d/99migration, env-update, ldconfig, sanity check.
+  * leave /etc/env.d/99migration in place at least until libraries in /lib32 are populated
-  * copy over a valid /etc/nsswitch.conf
   * @system rebuild - adjust USE as needed
-  FEATURES="-sandbox -usersandbox" USE="-X -gtk -qt5 -introspection -cairo -gpm -consolekit -policykit -net -ipv6 -spell -sqlite -nls -berkdb -gdbm -openssl" emerge -1eav @system
+<code>FEATURES="-sandbox -usersandbox" USE="-X -gtk -qt5 -introspection -cairo -gpm -consolekit -policykit -net -ipv6 -spell -sqlite -nls -berkdb -gdbm -openssl" emerge -1eav @system</code>
+  * work through any problems caused by emerge ordering above. If a dependancy problem proves too hard to solve, cheat by grabbing a binary package from the donor VM prepared earier. The subsequent @world emerge will take over the package later.
+  * /etc/env.d/99migration can now be removed. env-update, source /etc/profile, ldconfig
   * remove -sandbox and -usersandbox from features
@@ Line 120: / Line 151: @@
   emerge -eav --keep-going @world
+  * take note of failed, packages - these are usually caused by ordering/dependancy so a subsequent emerge run of the failed list will work. If not, work through the issues.
 == Things to do later ==
@@ Line 126: / Line 158: @@
   * take out /etc/env.d/99migration
   * remove /migration-backup
-  * erase /usr/portage/packages (whole dir)
+  * erase /usr/portage/packages (whole dir) - modern version is /var/cache/binpkgs
   * remove abi_x86_32 from package.use and profiles/use.mask, then emerge --newuse
   * clean up /lib.old and /usr/lib.old
+  * check for packages that own files in 32bit directories:
+<code>emerge -1av /lib32 /usr/lib32</code>
   * check for orphans in /usr/lib and all the other places. (bin sbin /usr/bin /usr/sbin). For finding orphan files after migration in /lib32, /usr/lib32, /usr/lib64
 <code>cd /lib32 ; find  -xdev -type f -exec qfile -o {} + |less</code>