> From: James Carlson <james.d.carlson at sun.com>
...
> Joseph Kowalski writes:
> > However, because of all the discussion, I just want to verify the following.
>
> We also have to clarify what goes on root. I think it's at most just
> libcmd and libast, as the others seem to have nothing to do with the
> problem. (And libast could be excluded by using a lazy load, as
> nothing from root will ever reach that path.)
April said:
2) /lib/{libast*, libdll*, libshell*} on the root filesystem
The project team agrees to altering the case, such that the libdll and
libshell libraries and links will be delivered on /usr/lib only.
The existing /lib/libcmd.so.1 is already located on the root filesystem,
is currently used by applications that may require the ability to work with
only root filesystem access, and will have a dependency upon libast.
The libcmd dependency requires that libast also be placed in /lib.
Just a different bullet. 8^)
However, I like idea of doing a lazy load on libast (regardless of where
it is).
- jek3
