From: Till Kamppeter <till.kamppeter@gmx.net>
To: lsb-f2f@freestandards.org,
printing-architecture <printing-architecture@freestandards.org>
Subject: [Printing-architecture] Another reason why we need a standard directory structure for printer drivers
Date: Mon, 12 Jun 2006 10:58:13 +0200 [thread overview]
Message-ID: <448D2CA5.906@gmx.net> (raw)
In-Reply-To: <1150100858.3652.6.camel@cyberelk.elk>
See below, Fedora/Red Hat uses SELinux as an enhanced security
infrastructure. It seems that there are set certain security policies by
the directory structure which leads to printer drivers not working when
they have files outside the places where printer drivers are expected to
be. Having standard directories for printer driver this problem should
go away.
Till
Tim Waugh wrote today on the CUPS general mailing list:
> On Sun, 2006-06-11 at 17:10 -0400, John Benson wrote:
>
>>Hi, this is just a post to notify people that SELinux in "Enforcing" mode on Red Hat Fedora Core 5 Linux can prevents CUPS jobs from printing. The job status shows as "stopped".
>
>
> Just to clarify: CUPS in Fedora Core 5 works fine with the supplied
> drivers. The problem you have run into, and supplied a link to an FAQ
> for, is that you have installed a 3rd party (Brother) driver which for
> some reason has not taken account of SELinux in its installation script.
>
> In general, if a 3rd party driver adds files to existing CUPS
> directories there should be nothing further to do; but in this case the
> Brother driver uses /usr/local directories.
parent reply other threads:[~2006-06-12 8:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1150100858.3652.6.camel@cyberelk.elk>]
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=448D2CA5.906@gmx.net \
--to=till.kamppeter@gmx.net \
--cc=lsb-f2f@freestandards.org \
--cc=printing-architecture@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.