SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Konphine, I his hands are intact? Because it is matter of seconds(or of one sed invocation) to replace older version with new one. Or to use makepkg tool. Because moderate user should not ask such questions, unless they are disable.
Sorry I took so long, been busy all morning at work. I'm downloading the version from SlackBuilds.org and will remove the newest installed package from my system and then install the SlackBuild version.
But to FeyFre directly, if I install the 1.2.3 version from SlackBuilds, how would I easily upgrade it to the newest version of Wine? Do I have to use slackpkg? Or is there another way I can upgrade by downloading the newest version from wineHQ and just upgrading it? I have not ran into doing this yet on Slackware and I am on unfamiliar grounds with it.
Also, since samac guessed correctly and I am using 64bit, would I still have to setup my system for multilib?
jdgr, it is easy enough.(Actually this is almost universal algorithm to use slackbuild in order to build newer versions of packages).
1. Download wine.Slackbuild
2. Download wine sources (.tar.bz2 file) of desired version and put it in the same directory as slackbuild
3. Run next command line VERSION="wineversionhere" TAG="_yourtaghere" ./wine.SlackBuild
4. Wait until it done. In /tmp you will see ready package. Install it using installpkg
Of course, x64 means you should built it in multilib environment(or on other x32 machine), you should consult documentation of multilib.(Personally I against running 32 binaries in x64 environments).
Thank you for the very concise instructions. I will attempt to follow them to upgrade wine to the newest version.
I do have a follow up question though. You say you personally are against running 32 bit binaries in an x64 environment, how do you get around that? For example, wine only comes in 32bit flavor. How do you get around this, or do you simply not use those programs?
I've never had much luck with the Slackware packages from winehq. When it comes to packages that work the best you can't do better than slackbuilds.org, Alien Bob, Robbie Workman,Piter Punk and any other of the core team of developers. I use Alien Bob's wine.slackbuild and modify it for the latest version 1.4-rc2 for example.
Consider getting playonlinux and winetricks as well.
jdgr, I use x64 binaries, or I don't use them at all.
First of all: I have bad experience with mixed environments, they all have bugs which cause system down.(I can remember what hell is to run 16bit DOS software on Windows). If I want run 32bit-only application and have not alternative I boot 32bit OS/boot virtual machine with 32bit OS. The same for 64bit. The same for Software for Windows - reboot to Windows or in VM. If I want debug DSP firmware I do it on chip using JTAG or other debugging technique, not on (e|si)mulator.
Second: So happened that most Software I use/support/create is quite complex system of user level application, kernel level driver and hardware peripheral. Coupling 64bit driver on 64bit OS with 32bit user level application is another kind of hell I trying to avoid.
That is my situation. Your situation is probably a lot easier, so you probably will not run into problems I do. Just setup multilib, wine and enjoy. But I suggest to test multilib configuration on something easier than wine(on native 32bit application, wine itself has a lot of bugs which will be multiplied by multilib misconfiguration, and you will probably end up with no results). Good luck!
Thanks for all of the replies guys. Since I am running Slackware 64 bit, I have been trying to get all the 64 bit binaries. And when it comes to M$ software, I try like hell to find a Linux replacement that I can run instead.
But for work, I have 1 stupid program that is only windows based as far as I can find (Remote Admin) for remotely connecting to users PC's. It's running on all of them across about 150 stores (maybe 1000 PC's), and it's our backbone for support. Slowly rolling out Teamviewer to the PC's which does have a Linux version (I'm not sure about Slackware version though, haven't tried installing it yet), but it's a slow process and in the meantime, I have to use what I need. Since it's so often I use it for only a few minutes (and usually urgently), I don't want to reboot into Windows each time. But I understand why some people would. Every situation is different.