Opened 9 years ago
Last modified 8 years ago
#1062 new task
Findutils 4.6.0 find location
Reported by: | William Harrington | Owned by: | |
---|---|---|---|
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 by , 9 years ago
comment:2 by , 9 years ago
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 by , 9 years ago
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 by , 8 years ago
Summary: | Findutils 4.4.2 find location → Findutils 4.6.0 find location |
---|
Replying to kb0iic:
I've always put it /bin, haven't uncovered any problems, could be a hardcoded path somewhere along the line