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.
As I have backups of the VM, I decided to try a fresh install. Using the defaults, the install script spews errors such as:
/sbin/ldconfig: /lib/libattr.so.1 is not an ELF file - it has the wrong magic bytes at the start
/sbin/ldconfig: /lib/libuuid.so.1.3.0 is not an ELF file - it has the wrong magic bytes at the start
/sbin/ldconfig: /lib/libcomm_err.so.2.1 is not an ELF file - it has the wrong magic bytes at the start
/sbin/ldconfig: /lib/libdevmapper_event.so.1.02 is not an ELF file - it has the wrong magic bytes at the start
When I try to update the system I saw this message repeated many times:
I guess with "Looks like the problem is the 32-bit disk. No ELF errors with the 64-bit disk." you are referring to an unofficial slackware-current install DVD ISO? Which one are you using (timestamp, md5sum, origin) ?
All I know is I see the ELF messages with the 32-bit DVD and not with the 64-bit DVD and I can't update the VM in any way I tried.
Typically I don't use a DVD to update. I use my local repo, created with rsync and upstream mirrors. Typically I sync with tds.net but I also resynced against osuosl.org in the hope I would notice errors.
In this case I also tested a DVD that I made from the local repo. Same results.
I checked the md5sums per the instructions in CHECKSUMS.md5. Everything looks fine.
Could be PEBKAC, but I haven't changed anything that I'm aware in my rsync and updating process. Been using the same process for years. Could be that I have not updated Current in several weeks and something related. Could be some weird corruption in the VM. I don't know. I have a test partition on my system that I use when Currrent gets closer to release, but I have been hesitant to update the partition after the results with the VM. Because Current can sometimes be volatile, I always first update the VM before updating the partition. I'll make a backup and then see what happens.
I updated my physical Current partitions without a hitch. I updated directly from my local repo and with slackpkg. I didn't even bother changing to init 1.
That leaves the VM as suspicious. As I never had a problem before yesterday, I'm at a loss what might be the problem. The only change I remember since the last time I updated the VM is I updated to KDE 4.10.1, which means I updated Qt from 4.8.2 to 4.8.4, which means I probably should have rebuilt VirtualBox, but with that all said, none of my other VMs exhibit any problems and the Current 64-bit DVD does not exhibit any of the errors I'm seeing.
I created a new 32-bit Current VM and I again saw the same ELF errors trying to install Current.
I will rebuild VirtualBox against Qt 4.8.4, but I suspect that won't change anything.
Interesting. I am running 32 bit -current using a DVD ISO I created using Eric's -current build script. I updated my install this morning with the latest updates and all went without a hitch. I've also upgraded to -current using the official 32 bit 14.0 ISO. Very odd. I will assume you used slackpkg install-new when upgrading. Maybe take a look at slackpkg clean-system? Best of luck.