On 07/08/2012 07:04 AM, Bruce Dubbs wrote: > Ken Moffat wrote: >> On Sat, Jul 07, 2012 at 07:14:49PM -0500, Bruce Dubbs wrote: >>> >>> I realized that some of these are from LFS. If we decide to change, it >>> would need to be updated too. >>> >> I thought BLFS was a sub-project of LFS : cart, horse ? > > I look at them together. I thought about posting to lfs-dev, but > figured everyone there is also here. > >>> One of the points I tried to make was that it does not affect building >>> or running the programs. gcc/ld automatically search /lib and ld.so >>> does also. >>> >>> The question was a bit more subtle. Is it OK to put things only needed >>> for building in /lib? Historically, that location was only for the >>> minimum needed to get critical programs running at boot time before /usr >>> was mounted. >>> >>> So it doesn't make a practical difference. It's sort of an "artistic" >>> (for lack of a better word) thing that certain files should be in >>> 'standard' locations. The reason I brought it up is just that the file >>> locations don't feel right to me. > >> Iff you have a separate /usr partition, and can demonstrate that >> some things in /lib are *not* needed to boot, then yes, there is a >> case to answer. > > I think it's pretty easy to demonstrate that .la files are not used at > boot. Documentation also says that .so files (links) are not used either. > > The libraries used at boot are those used by the executables in /bin or > /sbin: > > All except linux-gate.so.1 (and one exception below) are in /lib. > linux-gate.so.1 is a virtual library in the kernel. > > $ sudo ldd /bin/* /sbin/* |cut -d" " -f1|sort|grep -v :|uniq > > gives the libraries used. I do note that I have an executable > /sbin/umount.udisks that has several libraries in /usr: > > /usr/lib/libdbus-glib-1.so.2 > /usr/lib/libgobject-2.0.so.0 > /usr/lib/libglib-2.0.so.0 > /usr/lib/libdbus-1.so.3 > /usr/lib/libgio-2.0.so.0 > /usr/lib/libgthread-2.0.so.0 > /usr/lib/libffi.so.6 > /usr/lib/libgmodule-2.0.so.0 > > No other programs link to a library not in /lib. Why a umount command > needs all those libraries is beyond me. The only programs that use > udisks2 are a part of the core gnome and kde desktops. I think the > location is a part of the "we don't support separate /usr" attitude. > > Checking deeper, the udisks source has tools/Makefile.am > > bin_PROGRAMS = udisks > slashsbin_PROGRAMS = umount.udisks > > both programs should be in bin_PROGRAMS just to create a clean, > consistent system. I also have no idea why a umount program needs dbus. > > ---------- > > I think I'll just ponder all this for now. Changes are not really > necessary to the book, but I may apply my rules to my distro. :) > > -- Bruce >
Well, for some reason unknown to me, umount helpers are always installed into /sbin. That file has no use on boot really. It is linked to D-Bus because daemon uses D-Bus calls and so the helper knows if media has been mounted via udisksd or not. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
