Re: [lfs-support] Partial explanation for a test fail in sudo

Paul Rogers wrote: Because of the usefulness of sudo in installing packages, it often gets built as an appendix to LFS using the chroot environment. If you do this, you can expect the failure. I have never built sudo and plan never to do so. I'm the only one that uses my computers, so who am

Re: [lfs-support] Partial explanation for a test fail in sudo

> Because of the usefulness of sudo in installing packages, it often gets > built as an appendix to LFS using the chroot environment. If you do > this, you can expect the failure. I have never built sudo and plan never to do so. I'm the only one that uses my computers, so who am I protecting

Re: [lfs-support] Kernel Config, SSD

On 6 March 2018 at 16:29, Rob wrote: > Does anything special need to be done with the kernel for optimal use > of solid state drives? > I recall something about turning on something called trimming, but > I don't remember much more than that. > Maybe check this out:-

[lfs-support] Kernel Config, SSD

Does anything special need to be done with the kernel for optimal use of solid state drives? I recall something about turning on something called trimming, but I don't remember much more than that. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ:

[lfs-support] Partial explanation for a test fail in sudo

For the last three BLFS versions, I have noticed a single failure in the check tests for sudo. The test that fails is testsudoers/test3. I have now discovered that this failure only occurs if the tests are carried out by root in chroot. For an unprivileged user, all tests pass. Because of the