Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
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.
Please don't be insulted if I remind you that those are 5 seperate commands. I know that konsole doesn't like it if I copy and paste the entire block. To make sure it is done correctly the best thing to do is copy and paste the commands one by one, ignoring all of the "&&"
gcc -print-libgcc-file-name is a command that needs to be executed. Try echo $SPECFILE after the first command, it should print a directory structure ending with /specs. It should not print dirname $(gcc -print-libgcc-file-name)/specs
I've been thinking about going thru LFS somewhere down the road, but I'm really curious, "How much are you learning by going thru LFS?" Like this problem you posted, do you understand what all those commands are doing and why you're executing them?
Maybe at the end you can post an evaluation of the project, the time it took, and how much you think you got out of it for the time invested.
I bet others would find it informative, too.
Thanks and best regards as you go thru LFS, and maybe BLFS afterwards,
If I can throw in my 2 cents in response to penguin_powered. I've waded through LFS and BLFS recently - not really done yet, but are you ever?
I've found it a very useful exercise. I know what patches are now and how to apply and troubleshoot them. I have a better grip on libraries, dependencies, system configuration, and partitioning strategies. It exposed me more to the choices that are available - e.g. I finally checked out XFce. I picked up lots of little bash tips (admittedly I was a tcsh user before, so that's not surprising). And, most useful of all, the configure/make/make install cycle no longer holds any terrors for me (this isn't the same thing as saying that it always works for me, or that I always know what to do when it doesn't )
If I add it all up, I probably spent at least a fortnight to get my system to the point where I regarded it as useable (networking, X11). I regard this as time well spent for the reasons above. It's not something to pursue if you need a functional linux system for the day after tomorrow, I know I hardly need to say that. But if you enjoy using linux and like getting an ever deeper understanding of it and especially if, like me, you don't have a formal IT background, (B)LFS is a great exercise.
Thanks guys for your responses! Your comments were very encouraging, John.
I plan on going thru LFS and BLFS as soon as I am able to build another machine to experiment on.
In the meantime, there's plenty to learn. John, you mentioned learning more about Bash; well, a recent Googling session landed me on a link almost 10 years old with some great Bash tricks I have not seen anywhere else. Here's the link: