From: Till Kamppeter <till.kamppeter@gmx.net>
To: "McDonald, Ira" <imcdonald@sharplabs.com>
Cc: printing-architecture@lists.freestandards.org
Subject: Re: [Printing-architecture] directory structure / file name conve ntions
Date: Fri, 14 Jul 2006 21:56:30 +0200 [thread overview]
Message-ID: <44B7F6EE.3020207@gmx.net> (raw)
In-Reply-To: <789E617C880666438EDEE30C2A3E8D10EE78@mailsrvnt05.enet.sharplabs.com>
McDonald, Ira wrote:
> Hi,
>
> Staying conformant to FHS (required for LSB conformance)
> appears to need some significant thought and modifications
> to our previous FSG/OP concensus (see Wendy Phillips' note
> yesterday).
>
> For those having trouble finding the authoritative source
> for the FHS spec (I did), below is the home page:
>
> http://www.pathname.com/fhs/
>
> The most recent release is v2.3 (29 January 2004) - there
> are links for PDF, PS, HTML, etc. versions of FHS/2.3 on
> the above web page.
>
> Does anyone know if there is work-in-progress for a newer
> version of FHS? Thirty months is a long time in computers.
>
> I don't think the FSG/OP should recommend a hierarchy std
> for printing that is broken across the 'shipped with system'
> versus 'later vendor packages'. But I suspect that's just
> what Debian, SUSE, and others want, for security reasons.
> Yuck!
>
> Comments?
>
Having one directory would make configuring the security enhancements
(SELinux, AppArmor) easier, but if the appropriate maintainers of the
distros pre-configured them once correctly it should not be a problem.
So we are probably better of to define at least two directories, one for
drivers to be shipped with the distro and one for distro-independent
drivers.
Or can we even go with one directory when it is not in /usr? For example
/opt/(open)printing/ppd/ and /opt/(open)printing/drivers/. Note that for
example the KDE and GNOME which ships with SuSE is also in /opt. Or does
SuSE violate the FHS with that?
Till
prev parent reply other threads:[~2006-07-14 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 15:26 [Printing-architecture] directory structure / file name conve ntions McDonald, Ira
2006-07-14 19:56 ` Till Kamppeter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44B7F6EE.3020207@gmx.net \
--to=till.kamppeter@gmx.net \
--cc=imcdonald@sharplabs.com \
--cc=printing-architecture@lists.freestandards.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.