Migrating to slackware64
in [Slackware]
|
Prev: Qemu help
Next: Settung keyboard in Slack 13.0
From: Joerg on 29 Dec 2009 02:28 Grant wrote: > On Mon, 28 Dec 2009 22:58:43 +0100, Joerg > <jstadermann(a)see_signature.net> wrote: > >>Hi, >> >>currently I'm test driving Slackware64 and it's working out >>pretty good, so good that I think about migrating my existing >>slack installation to Slackware64. Now I wonder if there are any >>hints, gotchas, etc I should be aware of and what the smoothest >>path of migration is. Usually I would go on the following way: >> >>- back up my current system >>- wipe the partitions > > only the OS partitions ,not your data > Well, usually I would agree, but that's a good opportunity, cleaning out a lot of unused stuff in $HOME, left over from old apps. >>- install Slackware64 >>- install kernel and modules from my test installation > > recompile? Not necessary, same config, same machine. I guess, I could simply move the test installation over to the real system partitions. > >>- restore /home and /etc >>- sync with current > > Huh? Only do this if yoiu don't mind beta bugs biting I run current for years now,and I never came across a real show- stopper. >>- re-build my own packages >> >>but probably there is an easier way doing it, like upgrading the >>system. > > Nah, slack64 is a new, separate install -- everything is > compiled for 64bit. > Ah, that's why it is called Slackware64 ;-) No seriously, I was wondering if I could trick slacks packet mnagement into updating the system, replacing all with the corresponding x86_64 packages, but I guess, I have to do the new installation. Joerg -- For email use g m x d o t n e t
From: Joerg on 29 Dec 2009 02:33 barnabyh wrote: > On Mon, 28 Dec 2009 22:58:43 +0100 > Joerg <jstadermann(a)see_signature.net> wrote: > >> Hi, >> >> currently I'm test driving Slackware64 and it's working out >> pretty good, so good that I think about migrating my existing >> slack installation to Slackware64. Now I wonder if there are >> any hints, gotchas, etc I should be aware of >> >> TIA >> Joerg > > As usual all depends on your needs. Some packages don't compile > well for 64 bit, like Wine and Gambas, or the VirtualBox OSE > build from SlackBuilds will not compile at all on 64. You will > have to use the non-free one from VB website. > > Stuff like this. > > Barnabyh > Thanks for the information. I compiled some of my packages and so far there were no problems. VirtualBox could be an issue though. Joerg -- For email use g m x d o t n e t
From: Robby Workman on 29 Dec 2009 03:13 On 2009-12-29, Joerg <jstadermann(a)see_signature.net> wrote: > > Ah, that's why it is called Slackware64 ;-) No seriously, I was > wondering if I could trick slacks packet mnagement into updating > the system, replacing all with the corresponding x86_64 packages, > but I guess, I have to do the new installation. Well, it *can* be done, even though the only valid reason to do it that way would be as an academic exercise - I certainly wouldn't *depend* on a system that was upgraded like this: 1) Install a 64bit kernel (use installpkg instead of upgradepkg so that you'll still have your 32bit kernel). 2) boot the 64bit kernel 3) Install the slackware64 A/glibc-solibs package (using installpkg) - see #4 for why. 4) Install the slackware64 A/ series packages (use installpkg instead of upgradepkg). Since slackware64 uses the /lib64 and /usr/lib64 directories, you'll have a base system in both 32bit (/lib) and 64bit (/lib64) when you're done with this step. This is important, because everything you're actually using right now is 32bit, but you're about to be needing the 64bit versions, so you need libc and other core libraries in both architectures to be present. 5) Use "upgradepkg --reinstall --install-new" to walk the entire tree now. 6) Use removepkg (if needed) to remove any packages that aren't present in the x86_64 tree. 7) Move/merge config files (most will need to be moved). 8) Sacrifice a goat. Perhaps you should have done that sooner. 9) Blame someone else if it didn't work right ;-) -RW
From: Joerg on 29 Dec 2009 05:07 Robby Workman wrote: > On 2009-12-29, Joerg <jstadermann(a)see_signature.net> wrote: >> >> Ah, that's why it is called Slackware64 ;-) No seriously, I was >> wondering if I could trick slacks packet mnagement into >> updating the system, replacing all with the corresponding >> x86_64 packages, but I guess, I have to do the new >> installation. > > > Well, it *can* be done, even though the only valid reason to do > it that way would be as an academic exercise - I certainly > wouldn't *depend* on a system that was upgraded like this: > > 1) Install a 64bit kernel (use installpkg instead of upgradepkg > so that you'll still have your 32bit kernel). > > 2) boot the 64bit kernel > > 3) Install the slackware64 A/glibc-solibs package (using > installpkg) - see #4 for why. > > 4) Install the slackware64 A/ series packages (use installpkg > instead of upgradepkg). Since slackware64 uses the /lib64 > and /usr/lib64 directories, you'll have a base system in > both 32bit (/lib) and 64bit (/lib64) when you're done with > this step. This is important, because everything you're > actually using right now is 32bit, but you're about to be > needing the 64bit versions, so you need libc and other core > libraries in both architectures to be present. > > 5) Use "upgradepkg --reinstall --install-new" to walk the > entire tree now. > > 6) Use removepkg (if needed) to remove any packages that > aren't present in the x86_64 tree. > > 7) Move/merge config files (most will need to be moved). > > 8) Sacrifice a goat. Perhaps you should have done that sooner. No problem, standard practice when starting such ventures ;-) It also helps having the cats performing ritual dances. > > 9) Blame someone else if it didn't work right ;-) Also standard practice, it can't be my fault ;-) > > -RW Thanks a lot Robby, I think I'll stick to the conventional approach, even though it sounds tempting. Joerg -- For email use g m x d o t n e t
From: Peter Chant on 29 Dec 2009 07:03
Joerg wrote: > Hi, > > currently I'm test driving Slackware64 and it's working out pretty > good, so good that I think about migrating my existing slack > installation to Slackware64. Now I wonder if there are any hints, > gotchas, etc I should be aware of and what the smoothest path of > migration is. Usually I would go on the following way: The one thing that bit me was that my printer needs a binary propritary driver to be installed. That is available in 32 bit only. Once I had found that I needed multilib support that fixed it. Pete -- http://www.petezilla.co.uk |