Converting From 13.0 32-bit to 64-bit
 

What do I need to know or do to move from 13.0 32-bit to 64-bit?

I have 13.0 32-bit installed on a new (64-bit) box.

I've been browsing the various discussions but haven't yet found anything specific about updating from 13.0 32-bit to 64-bit. If I understand correctly, the correct approach is a clean installation of 64-bit, which means wiping the 32-bit install.

I've done a lot of customizing of the KDE4 desktop. I don't want to lose that. Trying to learn KDE4 has been frustrating enough. :)

I also do not want to lose most/all of my /etc config files, possibly others too. Lots of work there through the years. :D

Backing up those directories is straightforward but is there more I should know about converting? I don't want to start completely from scratch --- I'd rather remain with the 32-bit. :)

I presume all third-party packages must be rebuilt.

Thanks.

If you have /home on a separate partition I would guess that KDE4 would just keep using your settings in ~/.kde and ~/.kderc, the same goes for your backed up configuration files. After all a plain txt file shouldn't care if it is on a 32-bit or 64-bit environment. As for re-compiling, again I would guess, that it would be best to re-compile, however I would also say that Alien Bob's 32-bit compatibility is excellent.

Hope this helps.

samac

Woodsman: I also have the same problem, and I cannot achieve any "official", or even non-official road to change slack platform :( The only answer I get is to do a fresh install.
I know, that the best way, but how about the hardest way? ;) Which packages should i upgrade first and in which order not to kill the system? If You find something usefull, please, share with LQ Community :) TIA :)

I did it on May 21, so I may not remember everything... And it was not yet the final 13.0.

First, install a 64-bit kernel. The huge one is good, I guess. (I used a custom kernel.) You might want to copy the old one first to a different name before installing the 64-bit one and edit lilo.conf so that you can boot either one. Run lilo and reboot to the 64-bit kernel. Make sure that you booted to the 64-bit kernel. "uname -m" should say "x86_64". Only then continue.

installpkg slackware64/*/glibc*x86_64*.t?z

installpkg slackware64/a/aaa_elflibs*.txz

(now the basic libraries are present both in 32 and 64 bit versions)

installpkg slackware64/a/*x86_64*.t?z

(now the basic executables are 64 bit. 32 bit versions exist no more)

installpkg slackware64/l/*x86_64*.t?z

(some other libraries are now present is both 32 and 64 bit)

for other directories but NOT a and l do:
upgradepkg --reinstall --install-new *.t?z

(most files are now only 64-bit, but most libraries are still present in both 32 and 64 bit)

reboot

(now restarted all daemons etc in 64 bit)

upgradepkg --reinstall --install-new slackware64/*/*.t?z

(reinstall everything once more, removing old versions)

removepkg /var/adm/packages/*[3456]86*

(some old trash, I guess)

reboot

If I forgot something, I hope you have the install disk ready to boot so you can fix everything that broke.

(I did it via an ssh connection...)

Yes, I have long used a separate /home partition. As KDE configuration is based upon text files, I presumed I would not need to modify anything with KDE and did not raise that issue here. :)

Can I use my 32-bit config file? Which kernel config options must be modified to create a 64-bit kernel?

Clarification: I can and will install 64-bit into unused partitions. My primary focus is ensuring in the end I have the same functionality as I do with 32-bit.

Hi Woodsman,

You will want to backup and/or remove the .kde folder in your /home/username directory, as has been suggested elsewhere (changelog? UPGRADE.TXT maybe?) because it's possible that the new KDE uses some different options in there, and the older KDE configuration files might cause weird or unexpected results.

Also, as for the kernel: I just took my 32 bit .config, and loaded it into xconfig under the 64bit -current OS, and rebuilt the kernel using basically the same file. The 64-bit-ness will be automatically picked up by xconfig, and will adjust itself accordingly; but you still might want to review the uppermost areas of the kernel- configuration, like CPU type, architecture, etc., to make sure it all looks correct for you. Also, you might want to build into the kernel, the "32 bit compatibility" option, which allows you to boot 32bit OS with it.

After building the kernel, just proceed to install it as you normally would :)

Sasha

This is a 13.0 KDE 4 install. :) No need to modify or remove that directory. I want only to migrate from 32-bit 13.0 to 64-bit. Actually, run both systems in different partitions but using common partitions such as /home, /usr/local, /boot.

Ah, good to know. Great. :)

Good reminder. Thanks.

I have been thinking about that ever since the related infamous thread appeared at LQ a few months ago. I think as this box is experimental and not my office production box, initially I want to forego 32-bit compatibility. That means rebuilding some third-party packages, but being an experimental box, I can afford either route right now. :)

I'm just looking for any known stumbling blocks with moving from 13.0 32-bit to 13.0 64-bit.

Oh goodness, I forgot about that! I must admit, I sometimes give *slightly* dated or, in this case, uninformed information about this transition, since I went from Slack-11 to Slack64 :p so I missed the initial conversion to KDE4.x

Cheers,
Sasha

PS - Plus, including the 32bit compatibility into the 64 bit kernel has proven useful to me if for only ONE reason: I can boot Slack11 (which I still have installed) using my 64bit kernel (discovered that by accident via a LILO PEBKAC error). Now, maybe there's no real benefit to this, but it could decrease the number of bzimages you have about if nothing else, and maybe allow for (what I do regularly) trouble-free chrooting into my Slack11 partition. :)

Hmm... Which tools are recommended to cross-compiling kernel? I want to make custom kernel (latest-one) myself, as usually do, but I want to change the architecture to 64-bit... I know it's possible, but when I was trying some time ago, I've got huge amount of error during compilation time :/ I'm not programmer, so those errors tells me nothing ;)
I don't remember the name of that tool, but now it's not important. Of course, I can use original slack kernel, but I don't want to move back to older kernel ;)

Petri: thank You very much for Your prescription :) I think it will be very useful for me :) Soon I try to follow Your steps :)

Sasha: those 32-bit compatibility helps something in multilib environment? If I choose to disable this compatibility, so be able to run 32-bit apps in multilib system (ie. Skype)?

Woohoo!!! I did it :D Finely, I have Slack64 up and running just fine :)
Almost all features are working with multilib environment.

Only one wall I cannot pass: I have no clue to get my scanner working :( Sadly, it's SQ113 chip based flatbed Mustek scanner, and there is no working driver for 64-bit. The only and unofficial driver came from Mustek long time ago as a binary for RedHat and Debian i586 arch :( While those drivers worked for me in Slack-current, it doesn't working in Slack64 even using 32-bit compilation of sane, and I have no ideas, how to get it working... I've even try to do some hacks with sane sources, but no effect. I'll do it, but I don't know how and when ;)
Real slacker never gives up, right? :D
Oh, I forgott to mention, that I've recompiled my compis-fusion environment successful, but that was a road of pain and headache... Tons of packages to build from GNOME project... Ughhh...