> On May 11, 2019, at 02:51, Pierre Labastie via lfs-dev > <[email protected]> wrote: > > On 10/05/2019 22:52, Bruce Dubbs via lfs-dev wrote: >> On 5/10/19 3:12 PM, Pierre Labastie via lfs-dev wrote: >>> On 10/05/2019 14:33, Douglas R. Reno via lfs-dev wrote: >>>> >>>> On 5/10/19 2:21 AM, Pierre Labastie via lfs-dev wrote: >>>>> Hi, >>>>> >>>>> I now build the systemd book. I may come back to SysV later, but ATM, I >>>>> want >>>>> to test the BLFS book, and the systemd revision has more thorough coverage >>>>> than SysV. >>>>> >>>>> Since i'm new to systemd, I try various commands. That's how I realized >>>>> there >>>>> was a unit (man-db.timer) for running a daily update of the man database. >>>>> So I >>>>> enabled the unit, and after one day, I received an error concerning the >>>>> associated service. >>>>> >>>>> Investigating, it turns out that /usr/bin/find is hardcoded in the unit, >>>>> and >>>>> we have find in /bin... >>>>> Why is LFS moving find to /bin ?
I built my last build from 2017 and find is in /usr/bin Outside of the clear situation here, not having hardcoded paths, but still, why is LFS putting find in /bin ? I understand that the author did this because GNU find installs to prefix, but outside of prefix it is /usr/bin. Don't see the problem. Perhaps contact the man-db author and get it fixed if LFS is the right way. Which bootscripts require find in /bin ? Sincerely, William Harrington -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
