On Sat, Oct 10, 2015 at 05:48:15PM -0500, William Hubbs wrote: > All, > > fhs 3.0 was approved in June this year [1] [2]. > > The piece of it that I want to bring up is the lib and libxx > directories, both in / and /usr. The way I read the fhs, /lib and > /usr/lib should hold the files for the default abi and /libxx and > /usr/libxx should hold the files for the alternate abis. In earlier fhs, > there was an exception for amd64 which stated that the default libraries > should be in /lib64 and /usr/lib64. However, that exception is now gone. > > I know there was discussion/work in the past on removing the lib->lib64 > symlinks on amd64, but I don't remember what happened to that > discussion. So, I would like to bring it up again and get the info. > > What would it take for us to remove the lib->lib64 links? > > What would it take for us to do this migration on live systems? > > William > > [1] https://wiki.linuxfoundation.org/en/FHS > [2] http://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html
Not sure we have to move it. "3.10. /lib<qual> : Alternate format essential shared libraries (optional) 3.10.1. Purpose There may be one or more variants of the /lib directory on systems which support more than one binary format requiring separate libraries. [13]" Note 13 is: "[13] This is commonly used for 64-bit or 32-bit support on systems which support multiple binary formats, but require libraries of the same name. In this case, /lib32 and /lib64 might be the library directories, and /lib a symlink to one of them." Unless im misunderstanding, we are fine as is with lib32, lib64 and lib->lib64 -- Jason
