On 2/10/07, Tony Earnshaw <tonni@xxxxxxxxx> wrote:
Hi list,
Inspired by a very recent (irate) Suse post to the Courier IMAP list, I
ask the following of the main vendor packages here.
Quoting a line of the posting out of context, the @suse.de poster
writes, complaining of the Courier install file hierarchy:
"/usr might be mounted read-only according to FHS, and is not expected
to contain variable or machine-specific data." This in respect to
Courier IMAP certificate .pem files within /usr that have to able to be
be generated on the fly.
Ok, the standard %{prefix} for rpm installs is /usr. AFAICS, at no stage
during an rpm install is there ever any attempt to mount and remount
/usr (or any other file hierarchy which might be mounted ro) to enable
installation. How does an rpm install cope with ro files systems such as
/usr?
If /usr is mounted RO it is a very specific configuration that someone
has likely setup for security reasons. In that context, then only the
persons managing the machine will know the proper context where-in one
should remount /usr RW. Therefore it seems reasonable to leave that
responsibility to the local managers of the said system, in which case
the package management system should not worry the least about such
matters, and by extension the same is true of the person creating a
package, for why should they worry about that over which they have no
control.
Now as for generated files, well they typically should go under /var
not /usr, in all implentations of unix that I know of (var is for
variable, that is changing and as such local to the site).
Cheers...james
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
