FW: FW: Shibboleth - Default installation

Alan Buxey alan.buxey at myunidays.com
Thu Apr 9 12:57:37 EDT 2020

It's a shame that the fileststem heirarchy standard was never fully adopted
by the *nix community , the idea of all added application software living
in their own /opt/ spaces this leaving the rest of the filesystem perky for
operating system purposes kept the OS easier to maintain and lockdown

but hey.


On Thu, 9 Apr 2020, 17:09 Peter Schober, <peter.schober at univie.ac.at> wrote:

> * Phanieshwar Nalluri <nalluri at bc.edu> [2020-04-09 15:18]:
> > I tried RMP install available for CentOS 7 and installation was
> > successful but I downloaded RPM in /opt/shibboleth and installed RPM
> > in that directory
> You shouldn't "download" anything manually. Add the YUM repo as per
> the documentation, install via yum and be done with it.
> > but still the packages were installed under /etc/shibboleth
> The packages are not installed under /etc/shibboleth, some files are
> (the configuration, as per the Linus FHS). Other files are in /usr
> others are in var. That's why package management exists and the FHS
> exists.
> > I'll have to look for container options and building from scratch.
> On the one hand you want to use RPM-packaged
> perfectly-integraded-with-the-OS peckages but then you insist that the
> software has to store all its files in an arbitrary location of your
> chosing at the same time. That's not how it works, with basically none
> of the software that takes care to integrate with the OS well ad
> adhere to published standards.
> So by all means don't use any of the integration provided out of the
> box by the RPM packaging and build the software yourself only so that
> you can have the files in a non-standard location -- at the price of
> having to take care of any updates and security fixes yourself in
> perpetuity, i.e., by subscribing to mailing lists, automating your
> local build, automating the deployment to servers, etc.
> Of course with Docker the files put into containers also wouldn't be
> in /opt of your CentOS system, they'd be hidden away in
> /var/lib/docker/ somewhere, equally *not* fulfilling your (IMHO
> absurd) "requirements". And if someone arbitrarily declares that
> method to be satisfying your requirements, well, so should be putting
> a symlink to /etc/shibboleth into your /opt directory or adding a
> bind mount.
> Personally I find this all very silly.
> -peter
> --
> For Consortium Member technical support, see
> https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20200409/7f3da1f4/attachment.html>

More information about the users mailing list