On 09/29/2018 08:51 PM, Ken Moffat wrote:
On Sat, Sep 29, 2018 at 07:23:40PM -0500, DJ Lucas wrote:
Last thing for these changes is whether or not to add fstrim and uuidd
bootscripts to the lfs bootscripts tarball for SysV book. The fstrim
bootscript is fairly obvious in its purpose, but I've no idea the real world
purpose for uuidd. For systemd, these are installed by the util-linux
package but not enabled.
For uuidd, no idea if a bootscript is sensible. But for fstrim,
after looking at the manpage, I can't see the point. I happen to
use 'discard' in fstab so I have no reason to use fstrim[ยน], but the
manpage suggests that running it weekly per mountpoint will often be
sufficient.
So I assume that people who use fstrim, at least on sysv, put it in
a cron job.
1. I did forget to add it to fstab on one system, and had to run it
manually after I noticed that repeated runs of an SBU build were
getting slower and slower.
"The uuidd daemon is used by the UUID library to generate universally
unique identifiers (UUIDs), especially time-based UUIDs, in a secure and
guaranteed-unique fashion, even in the face of large numbers of threads
running on different CPUs trying to grab UUIDs. "
I believe that the most frequent use if UUIDs is in databases as keys,
although they are used in a GUID Partition Table (GPT) and in ext based
partition superblocks. uuidd is not needed if only a few UUIDs are
needed or their generation is infrequent.
I do not think the uuidd daemon is useful for most LFS based systems.
The reason most distros have it available is because they have a
one-size-fits-all approach.
-- Bruce
P.S. See, for instance,
https://www.scribd.com/document/275520308/1391070-Linux-UUID-Solutions
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
