Hello,

I've never tried LFS on a virtual machine so cannot really comment on it, though I think that there might be 'issues' when trying it.

Kind regards,

Eric

When you use the LiveCD, the writable space is a small ram disk. If you give the LFS build machine a lot of ram, this can seem large, but it's not big enough to download and build all the packages.

The book guides you to download your files to the hard drive of the machine you are building, but doesn't suggest you use it's space for chapter 5 work (when you move to the chroot in chapter 6, that's automatic).

So, create a working directory under /mnt/lfs and do your work there, e.g.

mkdir -v $LFS/work
cd $LFS/work

then

tar xfvz <package>
cd <package>

and follow the instructions in the book.

(and remember, if the package is .tar.bz2, the letters are tar xfvj)

-----Burton

@BStrauss3: The solution you suggest won't work, the OP hasn't reached this point yet. As you correctly stated, the livecd needs some room to work on and it doesn't have that (or not enough). This is why the cat command (see post #14) cannot do its thing.

Too my knowledge, changing the VM settings is the only why to solve this.

BTW: The LFS book does suggest a place to store packages and patches and to work from: $LFS/sources (see 3.1 Introduction).

Hope this clears things up a bit.

Many people end up overlooking the highlighted part, and work from ~. If you are using the LiveCD, then ~ is on the ramdisk during section 5 and without remastering the LiveCD, you can't make ~ big enough to get to section 6.