| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Add some paragraph breaks to enhance readability. Correct English idiom
here and there. Capitalize titles consistently, fix punctuation.
|
|
|
|
| |
English idiom. Remove some superfluous verbiage here and there.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Mr. Webster says it's "up-front". Reworked one sentnece to avoid
using a colon after the verb "to be".
|
|
|
|
| |
applying security patches even after LFS is "complete".
|
|
|
|
|
| |
$ find -name '*.[0-9]' | wc -l
2438
|
|
|
|
| |
so that whether FAQ is plural or singular is not important :)
|
|
|
|
| |
Just reading a textbook and LFS does not imply anything for compilation...
|
|
|
|
| |
I guess a "chroot environment" don't know how to use the tools?
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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".
|
| |
|
|
|
|
|
| |
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 :(.
|
|
|
|
| |
You can't throw a NVIDIA GTX 690 into /dev.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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".
|
|
|
|
| |
of the simple present to make the order of events clearer.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to introduce some variety by rephrasing "This package contains ...".
|
| |
|
| |
|
|
|
|
| |
punctuation here and there.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update to iana-etc-20221007.
Update to vim-9.0.0739.
Add upstream patches to readline and bash.
Update to zlib-1.2.13.
Update to man-pages-6.00.
Update to gettext-0.21.1.
Update to iproute2-6.0.0.
Update to meson-0.63.3.
Update to Python-3.10.8.
Update to xz-5.2.7.
Update to tzdata-2022e.
Update to linux-6.0.1.
Update to dbus-1.14.4.
|
|
|
|
|
| |
Some kernel features (like, building the kernel with LTO) already
requires Clang.
|
| |
|
| |
|
|
|
|
|
| |
In bash-5.2 tarball config.guess is not executable, so we need to run
the script with an explicit "sh".
|
| |
|
|
|
|
|
|
| |
When I changed the sanity check to remove the "dummy.c" file, I
inadvertently used "gcc" instead of "$LFS_TGT-gcc". Which of course
finds the host gcc...
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Update to Linux-5.19.13
If you are using a laptop with an Intel GPU, it's imperative that you
update immediately if you are running Linux-5.19.12. Failure to upgrade
may result in permanent damage to the LCD display on your laptop.
The root cause of this is improper backporting of bugfixes for the i915
DRM driver in the kernel.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I have:
2 FAIL
5092 PASS
67 UNSUPPORTED
16 XFAIL
4 XPASS
Let's not be too precise (or we'll need to explain the meaning of
"UNSUPPORTED"). IMO "over 5000" is fine (until we get 5500 tests).
|
|
|
|
|
| |
"gold" is not an installed program (it's named "ld.gold"). So IMO it's
not proper to use <command>.
|
|
|
|
| |
Again, I sincerely wish libtool can suffer a painful death.
|
| |
|
|
|
|
|
|
|
|
| |
to root
Many users will create a user with the same username and UID so the
files will still be owned by his/her. So make it optional by "If you
won't assign the same UID for your user in the LFS system".
|
|
|
|
| |
/dev/shm may be a mount point, or a symlink.
|
|
|
|
|
| |
Now that /dev/shm is always a mountpoint, it needs to be umounted
otherwise dev cannot be umounted.
|
| |
|
| |
|
|
|
|
| |
You cannot throw a NVIDIA GTX 690 into /dev :).
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If you are using a "modern" distro (with devtmpfs and a modern udev
implementation), a bind mounting is actually not needed because you can
mount devtmpfs anyway. The only reason for bind mounting is to be
compatible with old host distros where /dev is a directory containing
many static device nodes, or is a tmpfs (not same as devtmpfs) popluated
by bootscript or an old udev (modern udev implementations, including
eudev and systemd-udev used by LFS, strictly requires a devtmpfs on
/dev).
So update the explanation to match the status quo.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Chroot command itself does not require kernel VFS mounted. You can mount
/proc, /sys, and /run after entering chroot with
"mount -v -t proc proc /proc" etc. For /dev, if the host kernel
supports devtmpfs, you can also mount /dev in chroot with
"mount -v -t devtmpfs devtmpfs /dev". Even if the host does not support
devtmpfs, it's still possible to mount /proc in chroot, then use
"mount --bind /proc/1/dev /dev".
It's just LFS editors decide to mount them before chroot. So reword
some untrue assertions.
|
| |
|