Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
09-15-2013, 11:32 PM
|
#16
|
Member
Registered: Sep 2013
Location: Sydney, Australia
Distribution: Slackware, xBSD, Gentoo, Calculate
Posts: 55
Original Poster
Rep:
|
Hello YellowApple,
I agree with all your points, I am sure that if there was a problem with glibc in Slackware64 13.37 it would have been fixed years ago. Perhaps Linode should have said:
Code:
This issue is due to a bug in the version of glibc in our Slackware 13.37 64bit build.
I did not switch from 64-bit to 32-bit, no.
Anyway I have found a way around it, I don't think I will notice much performance hit by using the 32bit version. Next time I buy hosting I might do a bit more research, or search this forum for the most Slackware-friendly webhost.
I must say that the response time from Linode support is very good, though.
|
|
|
09-15-2013, 11:39 PM
|
#17
|
Member
Registered: Mar 2013
Location: Reno, Nevada, United States
Distribution: Slackware, OpenBSD, openSUSE, Android
Posts: 95
Rep:
|
Quote:
Originally Posted by canadensis
Hello YellowApple,
I agree with all your points, I am sure that if there was a problem with glibc in Slackware64 13.37 it would have been fixed years ago. Perhaps Linode should have said:
Code:
This issue is due to a bug in the version of glibc in our Slackware 13.37 64bit build.
I did not switch from 64-bit to 32-bit, no.
Anyway I have found a way around it, I don't think I will notice much performance hit by using the 32bit version. Next time I buy hosting I might do a bit more research, or search this forum for the most Slackware-friendly webhost.
I must say that the response time from Linode support is very good, though.
|
Well, it's probably not anything in Slackware 13.37 *itself* that they rebuilt, since you're downloading the requisite packages from the mirrors (I'm assuming you *are* updating all packages to the latest available versions from the Slackware mirrors). However, they do use custom kernels, which - to me at least - would appear to be the suspect; perhaps their kernel builds aren't compatible with excessively-ancient versions of glibc for some reason?
Either way, at least you're up and running now, which is the most important thing.
|
|
|
09-15-2013, 11:49 PM
|
#18
|
Member
Registered: Sep 2013
Location: Sydney, Australia
Distribution: Slackware, xBSD, Gentoo, Calculate
Posts: 55
Original Poster
Rep:
|
Yes, thanks, time to get on with building the website!
Linode also offer the option of uploading your own Linux VirtualBox image, so I might try that in the future.
|
|
|
All times are GMT -5. The time now is 11:47 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|