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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
Would also be good to know what the optimization
flags are that you chose/use... if, for example, you
compiled for a PIV while in fact you're on a PIII you
may come across op-codes that the PIII can't handle.
I've seen similar things on a SuSE install (supposedly
PIV capable, oldest release [Server 7]) falling over on
a HT PIV 2.6GHz ...
egag: Yes, I was asking about shared compiling, and I fetched distcc after it was recommended. I'm going to try it on my next major compile (which may be coming up sooner than I'd thought ...).
Tinkster: I believe I did choose the right CPU optimization options: PIII, in my case.
Cedrik: For real? A recompile of the kernel? I checked the stock kernel and it has the same CONFIG_BINFMT_AOUT setting. But I guess I'll try a recompile, anyway, since I wanted to experiment with distcc and (the real reason) I wanna get Tux back.
Thanks, guys (gals? don't wanna make assumptions here).
I decided to go ahead and recompile my 2.6.9 kernel to include the CONFIG_BINFMT_AOUT feature, following Cedrik's suggestion. Big problem: I'm getting a possibly related error messages when I do "make xconfig" from /usr/src/linux. (Same with "make oldconfig", "make menuconfig", etc.).
I know you guys have all been on pins and needles to know whether I've gotten this fixed :-] .
In fact, I have. I can now compile programs just fine. To fix the problem, I had to reinstall my glibc* packages. I don't know exactly which was the culprit, but everything is cool (for now, anyway).
Warning: Don't be as dumb as I was and just do "removepkg glibc*", thinking that you can turn right around and "installpkg glibc*". Removing glibc crippled my system, and I had to send up a distress call to this forum to find out how to reinstall it (see http://www.linuxquestions.org/questi...hreadid=255487 to read the exciting account).
I really appreciate this forum. I wish I didn't do so many dumb things, but maybe others will learn from my mistakes (I hope so, 'cause I'm apparently not ...).