Thanks Nico,
I'm working my way through the FHS document. It sorta helps, it
doesn't really explain all the decisions the packagers made.
I guess I'll try to figure it out and write it up somewhere.
Best,
Joe
On 6/23/16 11:12 PM, Nico Kadel-Garcia wrote:
On Thu, Jun 23, 2016 at 6:22 PM, Joseph Areeda <[email protected]> wrote:
Greetings,
On SL6 we were using the tar file from Apache to get a newer version.
On SL7 trying to use the packaged version, many things are different, files
and working directories are in different places.
Yup. this came up for me today in connection with the File System
Hiearchy, published at
http://www.linuxfoundation.org/collaborate/workgroups/lsb/fhs, and
which RHEL and thus SL 7 try to follow. And welcome to welcome
"systemd", and the "file system hierarchy", which the tarball
distribution basically ignored in favor of modularity as a tarball.
They're basically following the standards used by RHEL in their daemon
deployment, and using Java keystores for SSL and daemontools to run
privileged pot 443 operations with the necessary hacks and privileges
to run privileged operations on port 80 or 443 as necessary. I'd
review the spec form the SRPM, and the systemd configurations for more
detail, especially for the relevant SELinux configurations.
I'm starting to understand by looking at the configuration files, where the
package put things in other reverse engineering techniques. I think it is
well thought out and make sense. I would like to avoid installing the tar
file and setting up my own init/unit scripts but that is certainly possible
if this doesn't work.
What I haven't been able to find is any documentation on let's: the
decisions the packagers made on how they should work. The docs for Centos
are different.
Is anyone seen documentation like this?
Best,
Joe
