LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-15-2010, 01:42 PM   #46
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,465

Rep: Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258

Quote:
Originally Posted by samac View Post
It may still be in aaa_base 32-bit, but is this a bug or deliberate?

samac
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.
 
Old 05-15-2010, 02:32 PM   #47
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,922

Original Poster
Blog Entries: 44

Rep: Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158
Hi,

Quote:
Originally Posted by LuckyCyborg View Post
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.
 
Old 05-15-2010, 02:45 PM   #48
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,465

Rep: Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258
Quote:
Originally Posted by onebuck View Post
Hi,



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.
 
Old 05-15-2010, 03:01 PM   #49
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,922

Original Poster
Blog Entries: 44

Rep: Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158
Hi,

Quote:
Originally Posted by LuckyCyborg View Post
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?
Why?

If you want VM then run one from the x86_64.
 
Old 05-15-2010, 03:04 PM   #50
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,882

Rep: Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988
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.
 
Old 05-15-2010, 03:25 PM   #51
mcnalu
Member
 
Registered: Dec 2006
Location: Glasgow, UK
Distribution: Slackware current
Posts: 423

Rep: Reputation: 73
btw I'm also using Alien Bob's mirror-slackware-current.sh script.
 
Old 05-15-2010, 06:20 PM   #52
zordrak
Member
 
Registered: Feb 2008
Distribution: Slackware
Posts: 595

Rep: Reputation: 116Reputation: 116
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.

Thoughts?
 
Old 05-15-2010, 06:51 PM   #53
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 231Reputation: 231Reputation: 231
It'll make it in =)
 
Old 05-15-2010, 06:53 PM   #54
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 203Reputation: 203Reputation: 203
Quote:
Originally Posted by sahko View Post
Check again.
 
Old 05-16-2010, 05:21 AM   #55
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,836
Blog Entries: 1

Rep: Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251
Another shot of updates (including slackpkg). Thanks

Are we there yet?
 
Old 05-16-2010, 05:49 AM   #56
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,465

Rep: Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258
Still we have the /lib64, /usr/lib64 and /usr/local/lib64 directories in the package aaa_base-13.1-i486-1.txz.

Ironically, a "build from source" create a correct package, without x86_64 things...
 
Old 05-16-2010, 06:00 AM   #57
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,882

Rep: Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988
Quote:
Originally Posted by LuckyCyborg View Post
Ironically, a "build from source" create a correct package, without x86_64 things...
Well, that blows my "maybe they're using a unified base directory-tree" idea out of the water.

Have you let Pat know? He may not spot every post in here.
 
Old 05-16-2010, 09:44 AM   #58
gauchao
Member
 
Registered: Dec 2009
Location: Veneto
Distribution: Slackware64
Posts: 364

Rep: Reputation: 138Reputation: 138
How do I upgrade from 13.0 x86_64 to 13.1 RC1 64bit?
 
Old 05-16-2010, 09:49 AM   #59
hitest
Guru
 
Registered: Mar 2004
Location: Canada
Distribution: Void, Slackware
Posts: 7,341

Rep: Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744
Quote:
Originally Posted by gauchao View Post
How do I upgrade from 13.0 x86_64 to 13.1 RC1 64bit?
http://rlworkman.net/howtos/libata-switchover

I've used this method to upgrade from 13.0 to 13.1 RC1.
I hope that helps.
 
1 members found this post helpful.
Old 05-16-2010, 10:04 AM   #60
gauchao
Member
 
Registered: Dec 2009
Location: Veneto
Distribution: Slackware64
Posts: 364

Rep: Reputation: 138Reputation: 138
Thank you very much, Hitest!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Unintended update to KDE 4.3 RC1 YellowHammer Ubuntu 1 07-13-2009 02:47 AM
RC2 Delta ISO's - How to update from RC1 1kyle SUSE / openSUSE 0 04-22-2006 03:36 AM
Update 10.0 to 10.1 RC1: disaster enryfox Mandriva 4 09-08-2004 07:49 AM
update b2 -> rc1 bubbadoe Mandriva 1 08-28-2003 08:24 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:45 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration