Re: Going to 64bit
Using instructions on http://www.v13.gr/blog/?p=11, I have available a
debootstraped amd64 squeeze using a dselect-upgrade based on my existing
installation (which is Sid). Since his instructions are older than multiarch
and based on lenny, I would like to know how to proceed. The gyst is:
1. mv /usr out of way and replace with that from the amd64. OK, better, do not
copy over after saving a copy?
2. Back up /etc just in case.
I am not sure if these are correct now:
3. mv any /lib32, lib64 out of the way (I have no emul) He mv to an /i386
folder
4 ln -s /lib /lib64
5. ln -s /emul/ia32-linux/lib /lib32
Or these:
mv /myamd64/emul /
// probably corret:
mv /sbin /i386
mv /myamd64/sbin /
mv /bin /i386
/i386/bin/mv /myamd64/bin / (note his trick here--would cp -a be better for
all this stuff?)
This is worst part:
mv /lib /i386
export LD_LIBRARY_PATH=/i386/lib
/i386/lib/ld-2.7.so /i386/bin/mv /myamd64/lib /
Note this trick as well. Versions may be different.
After this, one has options what to do with /var
I would probalby replace the /var/cache and /var/lib with those in myamd64
He then mv the System*, iniitrd* vmlinuz* config* to the i386 save directory
Reinstall the 64 bit kernels
lilo.conf just to use those, etc., reboot and LOL :-)
He does NOT treat /usr/local et all. I would most likely want to keep this and
upgrade/recompile stuff there as need be. I have a lot of cruft but also
varioius lv2 plugins, KDE plasmoids, etc., They most likely should be
recompiled before trying to get KDE running again (or just manually remove
from the rc file if it crashes out which has happened before).
I wouild want to upgrade to Sid (or can the deboostrap make it Sid in the
first place? All this did not take so long once I got it right!)
Another aside question: From the first attempt, I have a folder with some
stranded /sys /proc /dev/pts folder which the system will not let me delete.
How do I get rid of them (not in use)?
If I had space on the root partition, I could have done this all there and
simply booted into this root to try it out but that was not to be.
Reply to: