Meta tags:

Headings (most frequently used words):

introduction, chapter, packages, and, patches, linux, from, scratch, version, 12,

Text of the page (most frequently used words):
the (52), and (19), lfs (15), packages (13), files (10), this (9), #patches (8), sources (8), will (8), that (8), directory (8), all (7), file (7), for (7), can (7), downloaded (6), wget (6), book (6), version (6), root (5), are (5), user (5), using (5), tarball (5), build (5), may (5), release (5), system (4), uid (4), not (4), with (4), list (4), download (4), versions (4), sticky (4), repository (4), work (4), next (3), these (3), used (3), listed (3), available (3), command (3), one (3), https (3), www (3), snapshot (3), different (3), home (2), prev (2), owned (2), owner (2), needed (2), md5sums (2), starting (2), there (2), which (2), before (2), place (2), input (2), sysv (2), use (2), described (2), from (2), linuxfromscratch (2), org (2), mirrors (2), html (2), means (2), even (2), have (2), write (2), following (2), need (2), stored (2), working (2), also (2), required (2), tarballs (2), published (2), google (2), search (2), some (2), specified (2), problems (2), chapter (2), linux (2), arounds (2), introduction (2), chown, non, records, its, normal, host, distro, assigned, left, unnamed, final, you, won, assign, same, your, change, owners, now, avoid, issue, check, after, retrieving, any, methods, above, pushd, md5sum, popd, additionally, separate, verify, correct, proceeding, run, continue, prefix, below, stable, mirror, sites, individually, two, sections, several, ways, obtain, necessary, chmod, make, writable, multiple, users, permission, only, delete, within, enable, modes, mkdir, create, execute, session, somewhere, conveniently, throughout, entire, unpack, them, both, store, elements, located, partition, during, stages, building, process, locations, always, accessible, location, has, changed, since, was, provides, useful, engine, most, unsuccessful, try, alternative, downloading, com, git, svn, similar, identical, names, but, contain, essential, despite, example, script, generated, addition, contents, corresponding, uses, whenever, possible, instead, cause, autoconf, configure, includes, order, basic, numbers, correspond, software, known, based, their, highly, recommend, against, because, commands, unless, erratum, security, advisory, newest, package, require, developed, stabilized, development, scratch,

Text of the page (random words):
3 1 introduction linux from scratch version 12 4 chapter 3 packages and patches prev packages and patches next all packages up home 3 1 introduction this chapter includes a list of packages that need to be downloaded in order to build a basic linux system the listed version numbers correspond to versions of the software that are known to work and this book is based on their use we highly recommend against using different versions because the build commands for one version may not work with a different version unless the different version is specified by an lfs erratum or security advisory the newest package versions may also have problems that require work arounds these work arounds will be developed and stabilized in the development version of the book for some packages the release tarball and the git or svn repository snapshot tarball for that release may be published with similar or even identical file names but the release tarball may contain some files which are essential despite not stored in the repository for example a configure script generated by autoconf in addition to the contents of the corresponding repository snapshot the book uses release tarballs whenever possible using a repository snapshot instead of a release tarball specified by the book will cause problems download locations may not always be accessible if a download location has changed since this book was published google https www google com provides a useful search engine for most packages if this search is unsuccessful try one of the alternative means of downloading at https www linuxfromscratch org lfs mirrors html files downloaded packages and patches will need to be stored somewhere that is conveniently available throughout the entire build a working directory is also required to unpack the sources and build them lfs sources can be used both as the place to store the tarballs and patches and as a working directory by using this directory the required elements will be located on the lfs partition and will be available during all stages of the building process to create this directory execute the following command as user root before starting the download session mkdir v lfs sources make this directory writable and sticky sticky means that even if multiple users have write permission on a directory only the owner of a file can delete the file within a sticky directory the following command will enable the write and sticky modes chmod v a wt lfs sources there are several ways to obtain all the necessary packages and patches to build lfs the files can be downloaded individually as described in the next two sections for stable versions of the book a tarball of all the needed files can be downloaded from one of the mirror sites listed at https www linuxfromscratch org mirrors html files the files can be downloaded using wget and a wget list as described below to download all of the packages and patches by using wget list sysv as an input to the wget command use wget input file wget list sysv continue directory prefix lfs sources additionally starting with lfs 7 0 there is a separate file md5sums which can be used to verify that all the correct packages are available before proceeding place that file in lfs sources and run pushd lfs sources md5sum c md5sums popd this check can be used after retrieving the needed files with any of the methods listed above if the packages and patches are downloaded as a non root user these files will be owned by the user the file system records the owner by its uid and the uid of a normal user in the host distro is not assigned in lfs so the files will be left owned by an unnamed uid in the final lfs system if you won t assign the same uid for your user in the lfs system change the owners of these files to root now to avoid this issue chown root root lfs sources prev packages and patches next all packages up home