aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* glibc: Decapitalize nsswitch.confXi Ruoyao2022-11-181-1/+1
| | | | | In UNIX file names are case-sensitive. You cannot capitialize it even if it appears in a title.
* kernfs: reword the description of bind mountXi Ruoyao2022-11-181-2/+2
| | | | | | | | | | | "Duplicated copy" is wrong IMO. If you copy A to B, B won't be changed when you modify A. But if you bind mount A to B, B will reflect any change made to A. Again copy something from mount(2): A bind mount makes a file or a directory subtree visible at another point within the single directory hierarchy.
* kernfs: remove a false noteXi Ruoyao2022-11-181-2/+1
| | | | | | | | | | | | | | | | | | | | | Things are a little tricky: 1. If the host is "modern" (any desktop distro after 2013), the kernel supports devtmpfs and the host udev will do adjustments to the devtmpfs. All instances of devtmpfs shares the same content so we'll see the work of both the kernel and the host udev in chroot. 2. If the host is old but the kernel supports devtmpfs (i. e. the host is not using devtmpfs for its /dev), when we mount devtmpfs on $LFS/dev we'll see the work of the kernel in chroot, but not the work of udev. **Building LFS does not need any work of udev.** 3. If the host is very old and the kernel does not support devtmpfs at all, we can't mount devtmpfs. Mounting a devtmpfs will work for 1 and 2, while bind mounting will work for 1, 2, and 3. So we use bind mounting here. I don't want to squash all these details into the book, so just remove the false statement here.
* chroot: reword how chroot worksXi Ruoyao2022-11-181-3/+4
| | | | | | | | | | | | | | | Technically chroot command "tells" bash nothing. It basically calls chroot("$LFS"), then chdir("/"), then execve(["/usr/bin/env", "-i", ...]). The kernel also does not tell bash something like "hey, the root is now $LFS" but just executes (almost) all system calls from bash as-if $LFS is /. The man page of chroot says: DESCRIPTION Run COMMAND with root directory set to NEWROOT. Just use the same grammar construction here.
* glibc: it should be --disable-werror, not --disable-WerrorXi Ruoyao2022-11-181-1/+1
| | | | | | | | | | | | | Please try not to use the "replace" feature of the text editor blindly. Appendix C of the GNU C Library Reference Manual clearly says: '--disable-werror' By default, the GNU C Library is built with '-Werror'. If you wish to build without this option (for example, if building with a newer version of GCC than this version of the GNU C Library was tested with, so new warnings cause the build with '-Werror' to fail), you can configure with '--disable-werror'.
* Correctd the spelling of "Werror" -- it's "-Werror" in GCC, butDavid Bryant2022-11-171-2/+2
| | | | | it's "--disable-error" in Glibc. Thanks to Thomas Trepl for spotting my mistake.
* Correct capitalization, spelling, grammar, and idiom. Tighten theDavid Bryant2022-11-173-29/+30
| | | | prose by removing some circumlocutions.
* Corrected grammar, spelling, and idiom in chapter 7.David Bryant2022-11-164-58/+54
|
* Shadow: /usr/include/shadow is an installed dirPierre Labastie2022-11-161-2/+2
|
* Fix type (replace a / by a \ as line continue maker)Thomas Trepl (Moody)2022-11-161-1/+1
|
* Tidy up some spacing issuesBruce Dubbs2022-11-153-12/+12
|
* Update currency for sysvinitwqBruce Dubbs2022-11-141-0/+4
|
* packages: also use &pypi-src; for Jinja2 and MarkupSafeXi Ruoyao2022-11-121-2/+2
| | | | The md5sums are not changed.
* changelog: fix a ticket numberXi Ruoyao2022-11-121-1/+1
|
* stylesheets: add Simplified Chinese for lfs-l10nXi Ruoyao2022-11-121-0/+22
| | | | It should not affect English book.
* Package updates and a fix.Bruce Dubbs2022-11-118-52/+110
| | | | | | | | | | | | | Fix make-4.4 bug. Update to wheel-0.38.4 (Python Module). Update to texinfo-7.0. Update to sysvinit-3.05. Update to shadow-4.13. Update to sed-4.9. Update to meson-0.64.0. Update to linux-6.0.7. Update to elfutils-0.188. Update to bc-6.1.1.
* wheel: switch download URLXi Ruoyao2022-11-112-3/+4
| | | | | Avoid the necessity to upload a tarball onto anduin. The URL does not contain long checksum and it produces a tarball with the same md5sum.
* systemd: fix and simply the command to disable systemd-sysupdateXi Ruoyao2022-11-041-7/+3
| | | | | | | "systemd disable" seems a typo... And we don't need the ".timer" suffix because these .service units are tied to the .timer units.
* Edit English idiom. punctuation, etc., throughout chapter 6.David Bryant2022-11-035-29/+29
|
* Update to systemd-252.Douglas R. Reno2022-11-036-10/+30
|
* Edited for clarity, punctuation, and English idiom.David Bryant2022-11-031-16/+16
|
* grub: copy the "no tuning" warning from BLFSXi Ruoyao2022-11-031-0/+11
| | | | It's reported that a GRUB build with CFLAGS=-O2 is broken.
* Update to openssl-3.0.7 (Security update).Bruce Dubbs2022-11-013-5/+9
|
* glibc: fix parallel build issue with make-4.4Xi Ruoyao2022-11-012-9/+10
| | | | | | | | | | | | | We only need a one-line change in upstream fix (because we don't use "make --shuffle"). Add it as a sed for both Chapter 5 and Chapter 8. Note that the "minimal" sed would be '/MAEKFLAGS :=/s/r/ -r/'. I included an additional ')' so it won't modify "-r" again to "- -r". Tested "make" and "make check" on a x86_64 with -j8 and an arm64 with -j24. Link: https://sourceware.org/git/?p=glibc.git;a=commit;h=2d7ed98add14
* Package updates.Bruce Dubbs2022-10-314-44/+97
| | | | | | | | | | | | | | | | | | Update to iana-etc-20221025. Update to tzdata-2022f. Update to Python3-3.11.0. Update to procps-ng-4.0.1. Update to man-pages-6.01. Update to man-db-2.11.0. Update to make-4.4. Update to linux-6.0.6. Update to libffi-3.4.4. Update to inetutils-2.4. Update to expat-2.5.0. Note: I had to run glibc in Chapter 8 at -j1 to avoid an apparant race condition. With a little more investigation I may be able to find a better solution.
* toolchaintechnotes: reword the explanation about rebuild libstdc++ in gcc pass 2Xi Ruoyao2022-10-311-4/+7
|
* toolchaintechnotes: fix a typoXi Ruoyao2022-10-301-1/+1
|
* toolchaintechnotes: reword the reason "cc-lfs not usable on pc"Xi Ruoyao2022-10-301-5/+22
| | | | | | | | The problem is not "gcc building system doesn't know cc-lfs can run on pc", but "cc-lfs really cannot run on pc". Let's stop anyone from thinking about "why not just tell the gcc building system the fact".
* Corrected spelling here and there. Regularized capitaization of packageDavid Bryant2022-10-304-38/+38
| | | | names, corrected idiom / punctuation, and removed extraneous verbiage.
* Patched up an ambiguous sentence. Thank you for pointing it out, Xi.David Bryant2022-10-301-1/+1
|
* Orthography: spell cross-compile and its derived forms consistently.David Bryant2022-10-281-56/+59
| | | | | Add some paragraph breaks to enhance readability. Correct English idiom here and there. Capitalize titles consistently, fix punctuation.
* Standardize spelling of "cross-compile" and its derivatives. Clean upDavid Bryant2022-10-281-15/+14
| | | | English idiom. Remove some superfluous verbiage here and there.
* Cleaned up English idiom just a trifle.David Bryant2022-10-281-2/+2
|
* Typo fix from rhubarbpieguyDouglas R. Reno2022-10-271-1/+1
|
* Dependencies: util-linux can use libcap-ng, not libcap.Ken Moffat2022-10-271-2/+4
|
* errata: some reword about security advisoryXi Ruoyao2022-10-231-5/+7
| | | | | | | | | Do not use "whether there are any known security vulnerabilities" because it's highly unlikely there was none. Many people just build LFS for an experiment, then they don't need to maintain their system. The maintaining is only necessary for a real desktop or server system.
* Edited fpr idiom and style. Broke up a couple of run-on sentences.David Bryant2022-10-211-16/+16
| | | | | Mr. Webster says it's "up-front". Reworked one sentnece to avoid using a colon after the verb "to be".
* Edited for style, idiom, and punctuation. Emphasized the need to continueDavid Bryant2022-10-211-9/+9
| | | | applying security patches even after LFS is "complete".
* man-pages: update the number of provided pages for 6.00Xi Ruoyao2022-10-181-1/+1
| | | | | $ find -name '*.[0-9]' | wc -l 2438
* Use FAQ page instead of just FAQPierre Labastie2022-10-181-3/+3
| | | | so that whether FAQ is plural or singular is not important :)
* Clarify why pie might be disabledPierre Labastie2022-10-181-3/+3
| | | | Just reading a textbook and LFS does not imply anything for compilation...
* chapter01/how: small fixXi Ruoyao2022-10-181-1/+1
| | | | I guess a "chroot environment" don't know how to use the tools?
* resources: remove bad usage of <uri>Xi Ruoyao2022-10-181-2/+4
| | | | | | | | | | | | | RFC 3986: URI = scheme ":" hier-part [ "?" query ] [ "#" fragment ] hier-part = "//" authority path-abempty / path-absolute / path-rootless / path-empty So "linuxfromscratch.org" is not a URI, nor "irc.libera.chat".
* prologue/why: paramaterize "eudev" with revision attributeXi Ruoyao2022-10-181-1/+3
|
* prologue/why: mention that less is used by many packagesXi Ruoyao2022-10-181-2/+2
| | | | | Why remove "used by man-db"? Now some user may think "I don't use this thing, I'll just use vim" and skip it :(.
* prologue/why: another "device" -> "device nodes" changeXi Ruoyao2022-10-181-1/+1
| | | | You can't throw a NVIDIA GTX 690 into /dev.
* prologue/standards: rewrite LSB descriptionXi Ruoyao2022-10-181-5/+5
| | | | | | | | | | | | | Well, somehow this paragraph has become too imprecise. 1. We don't support IA64. Both Intel and AMD uses x86_64 now, which is referred as "AMD64" because it's first proposed by AMD. Intel attempted to use IA64 (which is a VLIW architecture completely different with x86_64) to compete with AMD64, but failed. Then Intel adapted x86_64. 2. The architecture specific part belongs to Core and Desktop. 3. LFS cannot conform to both AMD64 and IA32 because we don't support multilib. It's "or", not "and".
* Clarified verbiage here and there. Used the present perfect tense insteadDavid Bryant2022-10-171-11/+11
| | | | of the simple present to make the order of events clearer.
* Websters spells it up-to-date. Added one word for clarity.David Bryant2022-10-171-2/+2
|
* Made grammatical corrections, clarified a few things.David Bryant2022-10-171-5/+5
|
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-01-07 16:15:32 +0000