Migrating to slackware64
in [Slackware]
|
Prev: Qemu help
Next: Settung keyboard in Slack 13.0
From: Joerg on 29 Dec 2009 10:10 Peter Chant wrote: > 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 > I guess that's what I have to find out: Can I mgrate all my non- slack apps? Joerg -- For email use g m x d o t n e t
From: Peter Chant on 29 Dec 2009 15:20 Joerg wrote: > > I guess that's what I have to find out: Can I mgrate all my non- > slack apps? What non-slack apps do you have? How did you install them? If they are from slackbuilds I suspect there will be little problem and that will also likely be the general case if you build from source. Have you anything else? That leaves any proprietary drivers - I don't think that there are likely to be any differences between 32 and 64 bit support in general for graphics. Printers are what bit me - did you need to load proprietary drivers there? Pete -- http://www.petezilla.co.uk
From: Joerg on 29 Dec 2009 17:01 Peter Chant wrote: > Joerg wrote: > > >> >> I guess that's what I have to find out: Can I mgrate all my >> non- slack apps? > > What non-slack apps do you have? How did you install them? If > they are from slackbuilds I suspect there will be little problem > and that will also > likely be the general case if you build from source. Have you > anything else? > > That leaves any proprietary drivers - I don't think that there > are likely to be any differences between 32 and 64 bit support > in general for graphics. Printers are what bit me - did you need > to load proprietary drivers there? > > Pete > That wasn't really a question, more a reminder for me to test that everything I have installed will work on slack64 :-) The few proprietary apps and drivers I have do all come in x86-64 as well and are already installed, so no problems here. In most other cases it's mainly a matter of recompiling I guess. I made my own kdesdk3-compat package to have Quanta running on kde4, so I have to rebuild that and Quanta, but all in all the switch doesn't seem to be to difficult. Joerg -- For email use g m x d o t n e t
From: danube on 29 Dec 2009 17:53 On Tue, 29 Dec 2009 16:10:45 +0100, Joerg wrote: > Peter Chant wrote: > >> 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 >> >> > I guess that's what I have to find out: Can I mgrate all my non- slack > apps? > > Joerg I found a few Tcl/Tk applications did not run under 64 (Tkrat being one of them). I am sure one could have fixed that with some tricks but I didn't want to spend too much time on it. Also, an old Afterstep WM I am using did not run and I didn't want to use the latest, rather bloated, version. Seeing the time to boot and the responsiveness between 64 and 32 are indistinguishable I returned to 32 after 2 months of 64 trial. JB
From: Joerg on 30 Dec 2009 03:26
danube wrote: > I found a few Tcl/Tk applications did not run under 64 (Tkrat > being one of them). I am sure one could have fixed that with > some tricks but I didn't want to spend too much time on it. > Also, an old Afterstep WM I am using did not run and I didn't > want to use the latest, rather bloated, version. Seeing the time > to boot and the responsiveness between 64 and 32 are > indistinguishable I returned to 32 after 2 months of 64 trial. I do not expect a great improvement in performance running the usual office type apps, but I guess I will see an improvement in video encoding/decoding and in audio editing/recording. I already use Studio64 (the 64 bit version) and that's doing better than the 32 bit version. Anyway, on a machine with 64 bit architecture but I/O bottlencks, RAM <= 4 GB and insufficient CPU cache, you probably won't see any improvement in performance at all. Joerg -- For email use g m x d o t n e t |