We will call this update Slackware 13.1 RC1, Now RC2
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 don't see WHY Master Of Slackverse want to introduce /lib64 and /usr/lib64 in a standard Linux tree.
In fact, even this concept of "lib64" thing was introduced to support the LinuxOnLinux thing aka multilib.
Opinions are like a certain orifice, everyone has one. I for one believe the methodology that is utilized by PV and especially Alien_Bob for the way that x86_64 is implemented for Slackware is brilliant.
As a user you have the choice of x86_32 or x86_64 singular or by using multilib the user can have both. Your choice! If you happen to have a problem that doesn't work out for you then hopefully someone is able to resolve the issue thus helping others that may experience the same.
Opinions are like a certain orifice, everyone has one. I for one believe the methodology that is utilized by PV and especially Alien_Bob for the way that x86_64 is implemented for Slackware is brilliant.
As a user you have the choice of x86_32 or x86_64 singular or by using multilib the user can have both. Your choice! If you happen to have a problem that doesn't work out for you then hopefully someone is able to resolve the issue thus helping others that may experience the same.
A great speach, thanks!
BUT I talk about Slackware (aka the Slackware32?), so I don't see a common sense to introduce X86_64 directories in this Pure32 Linux. The Great P want to support the reverse multilib? A 32 bit operating system able to run 64 bit binaries?
Last edited by LuckyCyborg; 05-15-2010 at 02:49 PM.
BUT I talk about Slackware (aka the Slackware32?), so I don't see a common sense to introduce X86_64 directories in this Pure32 Linux. The Great P want to support the reverse multilib? A 32 bit operating system able to run 64 bit binaries?
It's probably just that the developers are using a single unified base directory-tree to build the base package with, which would make a lot of sense.
Now granted, that means a 32bit system will have a couple of unnecessary ../lib64 directories cluttering the place up, but they're easily removed if you can't close your eyes and ignore them.
Personally, I'd have preferred the /lib and /lib32(for multilib) approach that some other distros decided to take, but at the same time I understand the arguments for using /lib and /lib64. I also preferred the /var/state/<package> directories that were in FHS2.0 over the /var/lib/<package> that they went back to in FHS 2.1 (or was it 2.1 and 2.2 I forget.), but I guess I just have to live with disappointment.
Gary is right. Sometimes opinions on how best to do something don't always agree with your own. Live with it.
Somewhat straying from the thread, but still on-topic:
slackpkg is still at v2.81, however several bugfixes and the mirror updates have been released as v2.81.1. Are we expecting Pat to issue this at the point of release? I would have expected it to enter Slack pre-RC.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.