@ralpy, thanks for the input. So are you recommending _not_ creating a package for LMS itself but maybe just the dependencies, like Perl and the openrc scripts? What about the modules?
Roland0 wrote: > The method to customize LMS for an unsupported OS platform is described > 'here' > (http://wiki.slimdevices.com/index.php/Customizing_Logitech_Media_Server_using_Slim::Utils::OS::Custom) > Which type of data should go where in the Linux file hierarchy is > described in the 'Filesystem Hierarchy Standard' > (https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) Thanks for the links Roland0, I'm not unfamiliar with the FHS, in fact I was looking at it last night prior to writing the above post and wasn't able to come to a conclusion that I felt confident about. LMS is more a server application (the S in LMS) than an end user application, no? Ralphy uses /opt/logitechmediaserver which sort of makes sense by the FHS: > > /opt is reserved for the installation of add-on application software > packages. > ... > Programs to be invoked by users must be located in the directory > /opt/<package>/bin or under the /opt/<provider> hierarchy. If the > package includes UNIX manual pages, they must be located in > /opt/<package>/share/man or under the /opt/<provider> hierarchy, and the > same substructure as /usr/share/man must be used. > But I think you could kind of read that to mean that end user applications go under /opt, not necessarily a daemon type of application started by the system at boot. I took a look at apache2 in Alpine thinking it has some similarities as an application, and it's files are mostly in /usr/lib and /usr/sbin. The FHS has this to say about /usr/sbin (and sbin generally): > > This directory contains any non-essential binaries used exclusively by > the system administrator. System administration programs that are > required for system repair, system recovery, mounting /usr, or other > essential functions must be placed in /sbin instead. > ... > Deciding what things go into "sbin" directories is simple: if a normal > (not a system administrator) user will ever run it directly, then it > must be placed in one of the "bin" directories. Ordinary users should > not have to place any of the sbin directories in their path. > I wouldn't classify /usr/sbin/httpd as a system administration program and it's probably never run as either a system administrator or a normal user, or at least it drops privileges after it's executed. In other words, I don't see how Alpine packagers determined that Apache2's binaries should live in /usr/sbin if they were following the FHS so either they weren't, or I don't know how to interpret the FHS. ------------------------------------------------------------------------ sodface's Profile: http://forums.slimdevices.com/member.php?userid=19057 View this thread: http://forums.slimdevices.com/showthread.php?t=111401 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
