SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The hard drive that I used with Slackware64 has died, so it's time to reinstall and start from scratch.
I have been using Slackware64 for over a year now and I enjoyed it...but now with a fresh start, I'm thinking about either going to Slackware64 -Current or going to the 32 bit version.
Things I wanted in Slackware64, but couldn't get, were WINE, Skype and VirtualBox. I could have gotten those if I went "MultiLib" but I didn't want to do that, I wanted a pure 64 bit system.
If you had to redo your system again, would you stick with your current O/S or would you change it up...and why?
The 32-bit layer works perfectly and does not impede the 64 bit version of Slackware at all. I used Slackware64-13.0 (multi-lib) and then changed to Slackware-13.1, but I am going to revert to Slackware64 (multi-lib) with version 13.2 as I feel that the 64-bit version is a bit more responsive on my machine.
The question you should be asking yourself is why you want a pure 64-bit or 32-bit system when Alien Bob's 32-bit compatibility layer works so well and is unobtrusive.
I'm using a modified -current 64-bit system. I do use Eric's KDE-4.6 packages & Robbie's XFCE-4.8 packages. I don't need Wine or Skype & am happily using VirtualBox. Why do you say you can't use it on 64-bit?
Regards,
Bill
I'm using a modified -current 64-bit system. I do use Eric's KDE-4.6 packages & Robbie's XFCE-4.8 packages. I don't need Wine or Skype & am happily using VirtualBox. Why do you say you can't use it on 64-bit?
Regards,
Bill
I think my thought reasoning was getting 64 bit WINE to work was way above my head, so I would use VirtualBox, but VirtualBox wouldn't allow me to run 3D applications with Windows...or something along those lines. It may not have been that I couldn't run it, but it didn't do what I wanted it to do.
The question you should be asking yourself is why you want a pure 64-bit or 32-bit system when Alien Bob's 32-bit compatibility layer works so well and is unobtrusive.
samac
The reason is...
If I'm going to install a 64 bit system, it should be 64 bit. If I wanted 32 bit stuff, I'd install a 32 bit operating system.
The hard drive that I used with Slackware64 has died, so it's time to reinstall and start from scratch.
...
...
If you had to redo your system again, would you stick with your current O/S or would you change it up...and why?
One of my hard drives died on Thursday (the OS drive not my /home drive thankfully). Had to visit several places to find an IDE drive (old hardware!!) but decided to take the leap from 12.2, which I have been running since it was released, and install 13.1.
I had Slackware 13.0 running on vbox but I never liked it, could never get the network to work 100% and i'm still not sure about KDE 4 and i have some funny graphics issues (could be my older machine though).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.