Opened 16 years ago
Closed 16 years ago
#2405 closed task (wontfix)
Zlib in /usr/lib
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Book | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description
When the fPIC patch was added to Zlib instructions, the instructions to move libz.so* to /lib were removed. However, Util-linux-ng installs fsck.cramfs and mkfs.cramfs are installed into /sbin, and anything in /{s,}bin generally should use libs in /lib. So the instructions for moving /usr/lib/libz.so* to /lib should be put back.
Change History (4)
comment:1 by , 16 years ago
comment:3 by , 16 years ago
Perhaps the solution is to put mkfs.cramfs in /usr/bin.
"The compressed ROM file system (or cramfs) is a free (GPL'ed) read-only Linux file system designed for simplicity and space-efficiency. It is mainly used in embedded systems and small-footprint systems." If cramfs is read only, then there is no need for the utilities to be in /bin/.
If it is zlib is really required to be in /lib, then why do none of the other distros do it?
comment:4 by , 16 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
I moved zlib to /usr/lib on purpose because I couldn't see any other distro having zlib in /lib. I just checked and RH and Ubuntu have no problem with mkfs.cramfs in /sbin with a dependency to /usr/lib/zlib.
I think that leaving zlib in /usr/lib is OK. It is really a corner case to have /usr on a remote filesystem, not being able to access it, and needing cramfs.
Putting zlib on /lib then has the contradicting case where a user that mounts /usr remotely on several machines would have to update each system separately instead of in the expected common location. That's a corner case too.
I'd mark this as invalid, but I'm leaving it open for other comments.