From: Vikram Ambrose <Vikram.Ambrose@windriver.com>
To: Nick Gray <nick@austin.rr.com>
Cc: SELinux List <selinux@tycho.nsa.gov>
Subject: Re: SELinux backups
Date: Thu, 26 Jun 2008 16:03:07 -0400 [thread overview]
Message-ID: <4863F5FB.3040601@windriver.com> (raw)
In-Reply-To: <905B4D2C-5075-465B-89D2-E320F3DAB85C@austin.rr.com>
Nick Gray wrote:
> All,
>
> I would like to speak to anyone who has worked on, has experience
> with, or just has a general interest in system/database backups on
> SELinux.
>
What do you mean exactly?
a) Backing up the SELinux policy store on the system?
b) Backing up a system that runs SELinux?
c) Backing up a database running in an SELinux environment?
d) Storing system backups on an SELinux enabled filesystem?
> I searched my mail folder going back to about 2003 and found very
> little said about it.
>
> I have been assigned this by the company I am working for and would
> like to get a little insight into what has been done so far, methods
> and issues encountered.
>
> Nick G.
>
> --
> 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.
--
Vikram Ambrose | Linux Products Division | WindRiver Corporation
--
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.
next prev parent reply other threads:[~2008-06-26 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 19:10 SELinux backups Nick Gray
2008-06-26 20:03 ` Vikram Ambrose [this message]
[not found] ` <26BD11F7-FA5A-4D58-A62D-A040148278A7@austin.rr.com>
2008-06-27 20:50 ` Nick Gray
-- strict thread matches above, loose matches on Subject: below --
2007-06-13 17:32 selinux backups david carvalho
2007-06-13 18:18 ` Stephen Smalley
2007-06-14 2:49 ` Kazuki Omo
2007-06-14 10:56 ` Stephen Smalley
2007-06-14 9:08 ` Russell Coker
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=4863F5FB.3040601@windriver.com \
--to=vikram.ambrose@windriver.com \
--cc=nick@austin.rr.com \
--cc=selinux@tycho.nsa.gov \
/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.