linux-from-scratch/lfs-buildscripts
1
0
Fork 0
mirror of https://github.com/YellowJacketLinux/lfs-buildscripts.git synced 2025-01-23 22:42:28 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

typo/grammar fixes

Browse Source
This commit is contained in:
YellowJacketLinux 2024-10-09 16:59:48 -07:00
parent aee26b83da
commit 6815262bcf
2 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
CH8Build/BLFS.02-systemd-units.sh
View File

@ -8,5 +8,6 @@ GLSOURCES="/sources"
pushd /usr/local/src pushd /usr/local/src
tar -Jxf ${GLSOURCES}/${systemd_units_tarball} tar -Jxf ${GLSOURCES}/${systemd_units_tarball}
chown -R root:root blfs-systemd-units-${systemd_units_version}
popd popd

12
THE_WHY.md
View File

@ -104,8 +104,8 @@ multiple physical drives.
For the home user and even for the corporate workstation, I really do not see For the home user and even for the corporate workstation, I really do not see
the need for it and prefer the simplicity of not having it. the need for it and prefer the simplicity of not having it.
Even where LVM2 does make sense, where it makes is for partitions that need to Even where LVM2 does make sense, where it makes sense is for partitions that
use large amounts of data. That is not the root `/` filesystem that the need to use large amounts of data. That is not the root `/` filesystem that the
operating system lives on, but is typically `/home` or `/srv` or something operating system lives on, but is typically `/home` or `/srv` or something
similar. similar.
@ -118,9 +118,9 @@ frequently patch `e2fsprogs` to provide features that are not standard which
then make it difficult to mount the partition on a different GNU/Linux system then make it difficult to mount the partition on a different GNU/Linux system
for recovery. I have run into this issue several times in the past. for recovery. I have run into this issue several times in the past.
Only vanilla `e2fsprogs` should be used in and even then, bleeding edge features Only vanilla `e2fsprogs` should be used in the distribution installer and even
should be disabled by default (for example, the `metadata_csum_seed` feature in then, bleeding edge features should be disabled by default (for example, the
current `ext4`). `metadata_csum_seed` feature in current `ext4`).
If bleeding edge features are *truly* needed, the user can manually enable them. If bleeding edge features are *truly* needed, the user can manually enable them.
If non-standard filesystem features are *truly* needed, they can be provided by If non-standard filesystem features are *truly* needed, they can be provided by
@ -153,7 +153,7 @@ Foo
### Fonts ### Fonts
In my opinion, fonts in GNU/Linux is a mess. The problem is there are far too In my opinion, fonts in GNU/Linux is a mess. The problem is there are far too
many installed, making it difficult to select a font. many installed, making it difficult from a UI perspective to select a font.
Back when the Apple Macintosh first shipped, there was a small collection of Back when the Apple Macintosh first shipped, there was a small collection of
high quality variable-width bitmap fonts. The ‘Desktop Publishing’ era had high quality variable-width bitmap fonts. The ‘Desktop Publishing’ era had