Umami and Curl Shims

*sigh* I forgot sparsefiles don’t automatically grow.

The repair:
[code language=”text”]
[ root@LFS-HOST ] << ~ >>

[- umount $LFS

[ root@LFS-HOST ] << ~ >>

[- truncate /lfs.sparsefile -s 100G

[ root@LFS-HOST ] << ~ >>

[- mkfs.ext3 /lfs.sparsefile
mke2fs 1.42.13 (17-May-2015)
/lfs.sparsefile contains a ext3 file system
last mounted on /mnt/lfs on Fri Jan 6 05:56:22 2017
Proceed anyway? (y,n) y
Discarding device blocks: done
Creating filesystem with 26214400 4k blocks and 6553600 inodes
Filesystem UUID: e5bc2c6b-26e4-4ac1-97e8-1095f7c8c843
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

[ root@LFS-HOST ] << ~ >>

[- mount /lfs.sparsefile $LFS

[ root@LFS-HOST ] << ~ >>

[- chown -R phanes:heaven $LFS
[/code]

http://www.linuxfromscratch.org/lfs/view/systemd/chapter03/introduction.html

In other notes, did not know about sticky folders all these years.
That’s crazy. It’s like the Umami of ACLs!

Also don’t replace the wget call’s input with a command pipe to a curl call for that list.

One thing I did not see suggested, which really should be suggested is to check your work.

If you’re lazy like me, you have N items being downloaded and X items downloaded when you’re done. To see if X is N, run:

diff <(ls -1 | sort) <(curl -s http://www.linuxfromscratch.org/lfs/view/systemd/wget-list | sed 's/.*\///' | sort)

You'll only get a message if there's a problem.