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.
My problem occurs while unzipping files with the command tar -jxvf /lfs-sources/gcc-4.0.3.tar.bz2 That command seems to be doing the right thing, but it doesn't finish due to running out of space.
df -h gives me /dev/hdc1 4.8G, used 138M, so I think I have enough space in my target partition. But /dev/mapper/lfs-cd is size 1.5G, used 1.5G, so my assumption that it's the CD doesn't look right. Could /dev/mapper/lfs-cd be memory plus swapfile? It's the right size for that - in which case would a bigger swap file help?
I don't know how to post the output from the machine I'm trying to build, but mount tells me /dev/hdc1 is mounted rw - and indeed the tar utility spent an hour unpacking files to it before the error came up. So no, I'm not untaring on the CD - I imagine that would stop immediately.
df - h gives me
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/lfs-cd 1.5G 1.5G 16K 100% /
/dev/hdc1 4.8G 175M 4.4G 4% /mnt/lfs
Before getting to step 5.4, I'd already completed step 5.3 (binutils)successfully, so I think my method is OK, but something is getting filled up - I just don't see what that something is! I'd be grateful for any further advice.
1) Do you see any output, besides the error, when untarring? You should see at least a line for every file/dir that is extracted. If there were other messages, please post them.
2) Did you check the sanity of the gcc package on the cd? There should be a md5 sum for the gcc file, to check if all is correct:
The number returned (something like: 6ff1af12c53cbb3f79b27f2d6a9a3d50) should exactly match with the md5 sum given. If this is not the case: Your gcc package is corrupt/tampered with. Download a fresh copy.
3) Check if bunzip or tar is the problem. Although you did say that binutils was no problem to unpack/untar, maybe you end up with a more detailed error message.
Make it a 2 step process. First bunzip the file: bunzip2 gcc-4.0.3.tar.bz2. You should end up with: gcc-4.0.3.tar. Then untar the file tar xf gcc-4.0.3.tar.
I have the same problem.Although I have reached this stage and have successfully installed binutils, I get error messages saying "No space left on device". My PC is P Core 2 Duo , Ram 2GB, one partition 15GB and one for swap 2GB. I was trying first to unzip-untar once and out and I was getting errors. I also tried to unzip first and I get the error:
bunzip2: I/O or other error, bailing out. Possible reason follows.
bunzip2: No space left on device
Input file = gcc-4.3.2.tar.bz2, output file = gcc-.4.3.2.tar
bunzip2: Deleting output file gcc-.4.3.2.tar, if it exists.
The df -u shows:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/lfs-cd 1.5G 1.3G 126M 92% /
/dev/sda5 15G 215M 14G 2% /mnt/lfs
PS: I am tryin to unzip and untar from /tmp if that matters.