Opened 5 years ago

Last modified 4 years ago

#1062 new task

Findutils 4.6.0 find location

Reported by: William Harrington Owned by: clfs-commits@…
Priority: minor Milestone: CLFS Standard 3.1.0
Component: BOOK Version: CLFS Standard GIT
Keywords: Cc: berzerkula@…, jonathan@…, chris@…

Description

Do we need to move find to /bin?

LFS states that some packages in BLFS and beyond expect find to be in /bin. Has anyone ran across any packages which require that?

mv -v /usr/bin/find /bin
sed -i 's|find:=${BINDIR}|find:=/bin|' /usr/bin/updatedb

Change History (5)

comment:1 in reply to:  description Changed 5 years ago by Martin Ward

Replying to kb0iic:

Do we need to move find to /bin?

LFS states that some packages in BLFS and beyond expect find to be in /bin. Has anyone ran across any packages which require that?

mv -v /usr/bin/find /bin
sed -i 's|find:=${BINDIR}|find:=/bin|' /usr/bin/updatedb

I've always put it /bin, haven't uncovered any problems, could be a hardcoded path somewhere along the line

comment:2 Changed 5 years ago by chris@…

I'm pretty sure the only reason for that is that find is used in the bootscripts. Therefore the location shouldn't matter when used with systemd.

That being said, systemd does have one file in its testsuite that looks specifically for /bin/find, though it also looks for /sbin/find which we know doesn't exist so I'm not sure if /bin/find is really required for that.

comment:3 Changed 5 years ago by chris@…

I've built a system several times with find in /usr/bin, and had no problems. Though, the sysvinit CLFS book does use find in the bootscripts, so /usr/bin/find probably should be moved to /bin for sysvinit.

comment:4 Changed 4 years ago by William Harrington

Summary: Findutils 4.4.2 find locationFindutils 4.6.0 find location

comment:5 Changed 4 years ago by William Harrington

For this next release we can make sure that find is in /bin

Note: See TracTickets for help on using tickets.