Originally Posted by rm%rf
Thanx for the help, will give it a bash tonight, btw is there any advantages to running Slack64 as opposed to Slack32 ?
Well, yes and no: depends (mostly) on what you're doing.
With Slackware-64 you can address more than 4G of RAM without having to recompile your kernel, plus, if you're doing heavy math (as in engineering and scientific calculations), it's going to be faster/better/slicker. The downside is that you won't be able to use 32-bit applications; e.g., GoogleEarth, Adobe Reader and the like, without adding Multilib (from Alian BOB at http://alien.slackbook.org/dokuwiki/...kware:multilib
) which give you the capability to use 32-bit software directly (and, yes, it works just fine and is not a lot of hassle to install or use).
Note that there are not many 32-bit only software packages and, if you're adding software of your own or the packages from, say, SlackBuilds.org
pretty much everything will build and run on either platform. I understand that some games and the like may present a problem but I cannot vouch for that.
I use 64-bit VirtualBox to run 32-bit XP as a guest operating system on my 64-bit boxes and have zero problems doing that if XP or some other OS matters to you.
The world is going to catch up and more and more 64-bit applications will become available, negating the need for things such as Multilib but, for now, that's the solution for mixing 32- and 64-bit software on the same platform.
If you've got a 64-bit box, I'd go with 64-bit Slackware -- 32-bit will install and work just fine on 64-bit hardware (including multi-core processors). And, if you buy the dual-side DVD (http://store.slackware.com/cgi-bin/store
) you can try both and see what you think -- doesn't take that long to install and you can always do a clean install of the other if you don't like the first one.
So, I guess I'm saying, go with 64-bit unless you have a particular need for 32-bit.
Hope this helps some.