I believe I have solved my LVM booting problem with the kernel not finding the
root filesystem.
# Start the udev daemon to continually watch for, and act on,
# uevents
/sbin/udevd --daemon
# Now traverse /sys in order to coldplug devices that have
# already been
Hello All -- just starting with LFS and learning a lot so far.
HELLO! Welcome!
I have a couple of questions as I start the builds in Ch. 5.
1. many commands have file arguments with relative
paths, eg. the very first two commands in Sec. 5.5.1:
tar -jxf ../mpfr-3.1.0.tar.bz2
mv -v mpfr-3.1.0
On Jan 30, 2012, at 4:31 PM, rafe_b wrote:
Hello All -- just starting with LFS and learning a lot so far.
Howdy. GL to you!
1. many commands have file arguments with relative
paths, eg. the very first two commands in Sec. 5.5.1:
tar -jxf ../mpfr-3.1.0.tar.bz2
mv -v mpfr-3.1.0 mpfr
On 31 January 2012 00:31, rafe_b ra...@speakeasy.net wrote:
Hello All -- just starting with LFS and learning a lot so far.
I have a couple of questions as I start the builds in Ch. 5.
1. many commands have file arguments with relative
paths, eg. the very first two commands in Sec. 5.5.1:
The 'patch' command in the LFS book (Sec. 5.5.1)
immediately follows three un-tar operations where the
'root' directories of the three newly-created source trees
are renamed to mpfr, gmp, and mpc.
I understand that the patchfile (by virtue of its name)
has something to do with gcc. But I can't
Raphael Bustin wrote:
The 'patch' command in the LFS book (Sec. 5.5.1)
immediately follows three un-tar operations where the
'root' directories of the three newly-created source trees
are renamed to mpfr, gmp, and mpc.
I understand that the patchfile (by virtue of its name)
has something
Hi Bruce, I'm trying desperately to understand.
I did read Sec. 5.3 carefully -- I printed it out and
read it prior to doing any builds -- but the subsequent
build steps don't seem to line up. The tree that
I have is:
/mnt/lfs/sources # (1) contains downloaded tarballs
/mnt/lfs/sources/mpfr
Le lundi 30 janvier 2012 à 22:47 -0500, rafe_b a écrit :
Hi Bruce, I'm trying desperately to understand.
I did read Sec. 5.3 carefully -- I printed it out and
read it prior to doing any builds -- but the subsequent
build steps don't seem to line up. The tree that
I have is:
On 31 January 2012 03:47, rafe_b ra...@speakeasy.net wrote:
Hi Bruce, I'm trying desperately to understand.
I did read Sec. 5.3 carefully -- I printed it out and
read it prior to doing any builds -- but the subsequent
build steps don't seem to line up. The tree that
I have is:
On 31 January 2012 04:08, Alain Toussaint alain.toussa...@securivm.ca wrote:
Le lundi 30 janvier 2012 à 22:47 -0500, rafe_b a écrit :
Hi Bruce, I'm trying desperately to understand.
I did read Sec. 5.3 carefully -- I printed it out and
read it prior to doing any builds -- but the subsequent
On 01/30/2012 11:33 PM, Firerat wrote:
On 31 January 2012 03:47, rafe_bra...@speakeasy.net wrote:
Hi Bruce, I'm trying desperately to understand.
I did read Sec. 5.3 carefully -- I printed it out and
read it prior to doing any builds -- but the subsequent
build steps don't seem to line up.
On 31 January 2012 04:50, rafe_b ra...@speakeasy.net wrote:
To Firerat and Alain and Bruce: There is a major
discrepancy between the V.6.8 and V.7.0 LFS books
in Section 5.5.1. I have been working from the
V.7.0 book. From a private response from Bruce,
it occured to me to check the prior
Secondly, there was no 'gcc-4.x.x' directory
created from the three un-tar operations in my
case (from the V.7.0 LFS commands.)
there are 4 untar operation, gcc-4.6.1, mpfr, gmp and mpc.
you have to untar gcc-4.6.1 first with:
tar xjvf gcc-4.6.1.tar.bz2
the book assume that you unpacked
I'm wondering if some re-wording, and verbose tar is worth considering
To re-emphasize the build process:
1 / Place all the sources and patches in a directory that will be
accessible from the chroot environment such as /mnt/lfs/sources/. Do
not put sources in /mnt/lfs/tools/.
2 / Change to the
14 matches
Mail list logo
