All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@admin.navo.hpc.mil>
To: Tom <tom@lemuria.org>, Russell Coker <russell@coker.com.au>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Core policy
Date: Tue, 25 Feb 2003 08:40:46 -0600	[thread overview]
Message-ID: <200302250840.46512.pollard@admin.navo.hpc.mil> (raw)
In-Reply-To: <20030225092931.A15162@lemuria.org>

On Tuesday 25 February 2003 02:29 am, Tom wrote:
> On Tue, Feb 25, 2003 at 08:45:10AM +0100, Russell Coker wrote:
...
> > Installing xfs policy won't be that difficult if you really need it. 
> > Just as installing gpm policy won't b e difficult.
>
> I was trying to say: Leave it out, it's not important. Even if it's
> installed and used, breaking it will not cause much trouble, only a few
> apps won't look that crisp anymore and a few fonts won't work. Nothing
> serious compared to, say, a failure to boot up correctly.

On a side note: If the X server can access an xfs server on another system
you  may be importing data from a non-trusted host. This is just a reminder
if the X configuration designates an alternate font server host.

It is also entirely reasonable to use one font server for 10-20 workstations
since it doesn't  (at least not in my expierence) put that much of a load
on a system.

There has also been some effort to make use of xfs to provide fonts to
groff/ghostscript for rendering and printing. It has been a while since I
followed their development, so I don't know how far it has gone.
-- 
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2003-02-25 14:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 18:55 Core policy Wayne Salamon
2003-02-24 19:59 ` Russell Coker
2003-02-24 22:51   ` Tom
2003-02-25  3:33     ` Brian May
2003-02-25  7:45     ` Russell Coker
2003-02-25  8:29       ` Tom
2003-02-25 14:40         ` Jesse Pollard [this message]
2003-02-26 13:36   ` Wayne Salamon
2003-02-26 16:08     ` Leslie J. French
2003-02-24 20:08 ` Clem Skorupka
2003-02-24 21:12   ` Russell Coker
2003-02-24 21:29     ` Frank Mayer
2003-02-25 11:35       ` Wayne Salamon
2003-02-25 13:42         ` Frank Mayer
2003-02-25 14:04         ` Frank Mayer
2003-02-25 16:32         ` Russell Coker
2003-02-24 22:19     ` Dale Amon
2003-02-26 14:06   ` Wayne Salamon
  -- strict thread matches above, loose matches on Subject: below --
2003-02-24 19:43 Westerman, Mark
2003-02-25 15:41 Stephen D. Smalley
2003-02-25 16:15 ` Wayne Salamon
2003-02-25 21:54 ` Russell Coker
2003-02-25 15:50 Stephen D. Smalley
2003-02-25 16:48 Stephen D. Smalley

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=200302250840.46512.pollard@admin.navo.hpc.mil \
    --to=pollard@admin.navo.hpc.mil \
    --cc=russell@coker.com.au \
    --cc=selinux@tycho.nsa.gov \
    --cc=tom@lemuria.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.