[6370fa6] | 1 | <sect1 id="ch02-commands">
|
---|
| 2 | <title>Download the LFS Commands</title>
|
---|
| 3 |
|
---|
| 4 | <para>
|
---|
| 5 | LFS Commands is a tarball containing files which list the installation
|
---|
[fec335e] | 6 | commands for the packages installed in this book.
|
---|
[6370fa6] | 7 | </para>
|
---|
| 8 |
|
---|
| 9 | <para>
|
---|
[fec335e] | 10 | These files can also be used to quickly find out which commands have
|
---|
| 11 | been changed between the different LFS versions as well. Download the
|
---|
| 12 | lfs-commands tarball for this book version and the previous book
|
---|
| 13 | version and run a diff on the files. That way it is possible to see which
|
---|
| 14 | packages have updated installation instructions, so any scripts you may
|
---|
| 15 | have can be modified, or you can reinstall a package if you think that
|
---|
[3c6ec690] | 16 | necessary.
|
---|
[6370fa6] | 17 | </para>
|
---|
| 18 |
|
---|
[fec335e] | 19 | <para>
|
---|
| 20 | A side effect is that these files can be used to dump to a shell and
|
---|
| 21 | install the packages, though some files need to be modified (for
|
---|
| 22 | example, when the kbd package is installed, you needed to select the
|
---|
| 23 | keyboard layout file, becaue it can't reliably be guessed). Keep in
|
---|
| 24 | mind, please, that these files are not checked for correctness,
|
---|
| 25 | integrity and so forth. There may be bugs in the files (since they are
|
---|
| 26 | manually created, typo's are often inevitable) so do check them and
|
---|
| 27 | don't blindly trust them.
|
---|
| 28 | </para>
|
---|
| 29 |
|
---|
| 30 | <para>
|
---|
| 31 | If you decide to use these files for scripting purposes, then don't
|
---|
| 32 | place the files inside the directory of a package. For example, don't
|
---|
| 33 | put the autoconf file from the lfs-commands package into the autoconf
|
---|
| 34 | directory. The files may interfere with the actual package files, which
|
---|
| 35 | may contain a file with the same name. Autoconf is one
|
---|
| 36 | example of this: if an autoconf file is present in the autoconf
|
---|
| 37 | directory, the configure script won't create a new autoconf file. You
|
---|
| 38 | will end up with /usr/bin/autoconf containing autoconf's installation
|
---|
| 39 | instructions, rather than the real autoconf perl script. There may be
|
---|
| 40 | other packages that behave in similar ways, so just keep the
|
---|
| 41 | lfs-commands files outside the package directory.
|
---|
| 42 | </para>
|
---|
| 43 |
|
---|
[6370fa6] | 44 | <para>
|
---|
| 45 | The lfscommands can be downloaded from <ulink
|
---|
[b16c005] | 46 | url="http://packages.linuxfromscratch.org/lfs-commands/">
|
---|
| 47 | http://packages.linuxfromscratch.org/lfs-commands/</ulink> or <ulink
|
---|
| 48 | url="ftp://packages.linuxfromscratch.org/lfs-commands/">
|
---|
| 49 | ftp://packages.linuxfromscratch.org/lfs-commands/</ulink>.
|
---|
[6370fa6] | 50 | </para>
|
---|
| 51 |
|
---|
| 52 | </sect1>
|
---|
| 53 |
|
---|
| 54 |
|
---|