zeroday0619/MahiroOS-jhalfs
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

README fixes:

Browse source 
Changed temptools by tools in the BUILDDIR layout.
Removed all references to ./blfs. We will need a separate README.BLFS.
This commit is contained in:
Manuel Canales Esparcia 2006-05-27 08:30:58 +00:00
parent ca4c634a22
commit d3b8635fe6
1 changed files with 14 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
README
View file

@ -34,7 +34,7 @@ $Id$
supplied symlinks. After editing the config file for the project you wish supplied symlinks. After editing the config file for the project you wish
to build, run the script. to build, run the script.
The term <symlink> refers to the 1 of 4 package symlinks, lfs,hlfs,clfs,blfs. The term <symlink> refers to the 1 of 3 package symlinks, lfs,hlfs,clfs.
Replace <symlink> with your choice of packages; i.e.: ./lfs Replace <symlink> with your choice of packages; i.e.: ./lfs
./<symlink> eg: ./lfs or ./hlfs ./<symlink> eg: ./lfs or ./hlfs
@ -52,14 +52,10 @@ $Id$
5. LAYOUT:: 5. LAYOUT::
/BLFS/config
/master.sh
/xxxx.xsl
/CLFS/config /CLFS/config
/master.sh /master.sh
/xxxx.xsl /xxxx.xsl
/HLFS/config /HLFS/config
/master.sh /master.sh
/xxxx.xsl /xxxx.xsl
@ -85,34 +81,32 @@ $Id$
README README
README.PACO README.PACO
TODO TODO
./blfs ---+
./clfs ---| ./clfs ---|
+---> master.sh ./hlfs ---|+---> master.sh
./hlfs ---| ./lfs ---|
./lfs ---+
6. FAQ:: 6. FAQ::
Q. "It doesn't work!" Q. "It doesn't work!"
A. Yes it does, try ./lfs --help A. Yes it does, try ./lfs --help
Q. "How do I specify the build location?" Q. "How do I specify the build location?"
A. The original LFS document worked against the well know location /mnt/lfs. A. The original LFS document worked against the well know location /mnt/lfs.
This script automates the build of all of the LFS series of books and uses This script automates the build of all of the LFS series of books and uses
a generic location $BUILDDIR with a default value a /mnt/build_dir. a generic location $BUILDDIR with a default value a /mnt/build_dir.
You may change this value to suit your needs. You may change this value to suit your needs.
The layout below $BUILDDIR is as follows. The layout below $BUILDDIR is as follows.
$BUILDDIR/ $BUILDDIR/
jhalfs (makefile,cmd scripts,logs..etc) jhalfs (makefile,cmd scripts,logs..etc)
sources (where packages reside) sources (where packages reside)
temptools (temporary bootstrap system) tools (temporary bootstrap system)
cross-tools (temporary CLFS only) cross-tools (temporary CLFS only)
... ...
FHS dir structure FHS dir structure
... ...
Q. "What is the function of the SRC_ARCHIVE variable?" Q. "What is the function of the SRC_ARCHIVE variable?"
A. When then symlinked master.sh runs it creates a local copy of the A. When then symlinked master.sh runs it creates a local copy of the
necessary packages in BUILDDIR/sources by downloading the files. If necessary packages in BUILDDIR/sources by downloading the files. If
@ -120,13 +114,13 @@ $Id$
this location for the file and, if found, will copy it to BUILDDIR/sources. this location for the file and, if found, will copy it to BUILDDIR/sources.
If the files are not found in SRC_ARCHIVE _and_ you have write priv to If the files are not found in SRC_ARCHIVE _and_ you have write priv to
the directory any downloaded files will be mirrored there. the directory any downloaded files will be mirrored there.
Q. "How do I set the SRC_ARCHIVE location?" Q. "How do I set the SRC_ARCHIVE location?"
A. The best way to set the value of SRC_ARCHIVE is A. The best way to set the value of SRC_ARCHIVE is
export SRC_ARCHIVE=/wherever/you/store/downloaded/packages export SRC_ARCHIVE=/wherever/you/store/downloaded/packages
OR OR
you can change the setting in .common/config. you can change the setting in .common/config.
Q. "Why have 2 copies of the files?" Q. "Why have 2 copies of the files?"
A. The package files must be visible during the chroot phase and this is a A. The package files must be visible during the chroot phase and this is a
simple and reliable method of doing so. This method also handles the CLFS simple and reliable method of doing so. This method also handles the CLFS