http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2339
--- Comment #3 from Guy Harris <guy@xxxxxxxxxxxx> 2008-03-07 20:33:07 GMT ---
So presumably the distinction the FHS is drawing is between files that might be
configured on a per-system basis and files that, even though they're in theory
read-only, might be modified to add updates, e.g. the RADIUS and DIAMETER
dictionaries? (I.e., the changes would be appropriate for all machines, rather
than machine-specific tweaks - the sort of changes that might show up in a
later release?)
("/usr/share" dates back to SunOS 4.0, where it was intended to be for files
that could be shared by multiple diskless clients regardless of the processor
architecture of the client. It was used for, among other things, the compiled
Olson time zone files, which aren't "read-only" in the sense that nobody would
ever change them - if your locale, or some other locale that matters to you,
changes its time zone rules, presumably you'd apply an update if your OS didn't
update the files soon enough.)
Or, to put it another way, there are files that we wouldn't expect most users
to change, but that might be changed at a site. Those files aren't
host-specific, and we wouldn't expect them to frequently vary over time, but
there might be occasions that would mean that they should be changed (e.g., if
you need to update them before the next release updates them). The updates
would make sense to apply to all installations of the application. What's the
appropriate location for them?
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.