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.
I've been advised by the SlackStore that the 64bit DVD will be dual sided and have both 64 and 32 bit versions on it
I am revising my subscription to that DVD
john
That would be wonderful indeed!
My subscription is already for the DVD, so I'm covered 100%
So I'll buy something else from the store when Slackware 13 is released as a gesture to say "thank you!".
shingoshi thank you very much for the slamd64 suggestion. I downloaded the packages from slamd64 c and wine runs great in slackware64. I'm able to use dvdflick to convert .avi to dvd.
Shingoshi opened another thread on upgrading Slack to Slack64. I wish he had done that much earlier, the information there will certainly be useful for some of us and they can continue there. It's absolutely fine to discuss various upgrade scenarios for those interested but no one has the right to blame the developers about things they don't have to do.
Anyway, hoping this is all over, I want to say a second "hooray!" for the wonderful news about Slack 64 .
Actually, I'm running Firefox in Wine right now. Need I say anymore? And no, this IS Slackware64, albeit, with real multilib now!
Shingoshi
>=(o_O)=>
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 - Build ID: 2009042316
shingoshi thank you very much for the slamd64 suggestion. I downloaded the packages from slamd64 c and wine runs great in slackware64. I'm able to use dvdflick to convert .avi to dvd.
This isn't rocket science! Using packages that install in /lib32 and /usr/lib32, means you can never accidently overwrite them.
For one reason, the project supports doing this! I was able to upgrade my existing Slackware system ON THE FLY simply by installing these packages first. Then when I went to upgrade to Slackware64, there were no issues. I only had to reboot to get my new Glibc working.
Just make absolutely certain that you install the Slackware64 kernel FIRST. If you don't, you won't be able to reboot your system in an emergency. And as always, run LILO immediately after the kernel installation.
Shingoshi
>=(o_O)=>
It would be nice if those of you who find my instructions useful, would give them a thumbs-up. Just so the others can have some idea of how many have followed my lead here.
I have a Slackware 32 chroot running just fine in Slackware64, to run wine and Google Earth. Works great and avoids having to use packages from other distributions (although I'm sure it works fine.)
I have a Slackware 32 chroot running just fine in Slackware64, to run wine and Google Earth. Works great and avoids having to use packages from other distributions (although I'm sure it works fine.)
Better than you realize!
Unless you like wasting your time transferring from one environment to another, a chroot is never a decent solution. Only for the building of applications is a chroot ever preferred. And then, specifically for the very reasons that it's not useful for general daily activities. A chroot will always segregate your actions from the system on which you're working. The consequence is a much greater effort to transfer files from one location to the other. And the fact is, with a chroot, you can only move files into, not out of the chroot while using it.
So by all means, please be satisfied with the method you're using, no matter how impractical it is.
Wine: Always available, all the time! Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090524 Shiretoko/3.5pre - Build ID: 20090524041949
You see the Gentoo-Amd64 in the side column. I know a thing or two about chroots. But then, I only used it for application development.
shingoshi, I think 32bit layer compatibility is planned.
the simplest evidence about it is that it would not have sense to have 64bit libs in /usr/lib64, don't you think?
having all the 64 bit libs in /usr/lib64 has been done maybe for downward compatibility for old 32bit sources.
This is just a guess, obviously I'm not one of the developers: but I respect their choices (if not probably I would have chosen another distribution).
and btw it's so easy to adapt their works to my needs with slackbuilds: you can try compile everything in /usr/lib if you like, setting LIBSUFFIXDIR to ''
one of the best things about slackware is easiness of customization
so we simply have to wait, and maybe stop spamming
shingoshi, I think 32bit layer compatibility is planned.
the simplest evidence about it is that it would not have sense to have 64bit libs in /usr/lib64, don't you think?
having all the 64 bit libs in /usr/lib64 has been done maybe for downward compatibility for old 32bit sources.
This is just a guess, obviously I'm not one of the developers: but I respect their choices (if not probably I would have chosen another distribution).
and btw it's so easy to adapt their works to my needs with slackbuilds: you can try compile everything in /usr/lib if you like, setting LIBSUFFIXDIR to ''
one of the best things about slackware is easiness of customization
so we simply have to wait, and maybe stop spamming
Actually it has already been explained elsewhere by Gnashley that $LIBSUFFIXDIR is required by the FHS, whether a system is multilib or not. Having $LIBSUFFIXDIR does not give indication of anything, except conformance to a known standard.
And as far as the rest goes. This isn't something I have to guess about.
Shingoshi
>=(o_O)=>
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090524 Shiretoko/3.5pre - Build ID: 20090524041949
Unless you like wasting your time transferring from one environment to another, a chroot is never a decent solution. Only for the building of applications is a chroot ever preferred. And then, specifically for the very reasons that it's not useful for general daily activities. A chroot will always segregate your actions from the system on which you're working. The consequence is a much greater effort to transfer files from one location to the other. And the fact is, with a chroot, you can only move files into, not out of the chroot while using it.
So by all means, please be satisfied with the method you're using, no matter how impractical it is.
Wine: Always available, all the time! Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090524 Shiretoko/3.5pre - Build ID: 20090524041949
You see the Gentoo-Amd64 in the side column. I know a thing or two about chroots. But then, I only used it for application development.
Shingoshi
>=(o_O)=>
Personally I don't consider installing packages from another distribution a decent long term solution.
Also, wine doesn't work very well this way, Firefox may work but many other applications I've tried do not.
If you set a chroot up properly it should hardly be impractical.
As with all things in Linux there are many ways of doing things, and all are right, at least for the person that is doing them. This goes for many things. Some people would consider it wrong to have a phone that played music and took photos and acted like a diary, yet they exist and sell well.
I personally have a separate phone, mp4 player and camera, but I like my OS multilib, this is a personal choice and one that I have achieved by using another very similar Slackware like system (Slamd64). Others use chroot. Others still are pure 64 and pure 32. All are correct and it is incorrect to sneer at people who have different opinions to you.
It reminds me of a saying, "opinions are like armpits, we all have them and they stink".
I have a Slackware 32 chroot running just fine in Slackware64, to run wine and Google Earth. Works great and avoids having to use packages from other distributions (although I'm sure it works fine.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
