All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: SELinux List <SELinux@tycho.nsa.gov>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Daniel J Walsh <dwalsh@redhat.com>,
	Joshua Brindle <jbrindle@tresys.com>
Subject: Re: [SEMANAGE,UTILS] Support seusers.system
Date: Sat, 28 Jan 2006 18:31:15 -0700	[thread overview]
Message-ID: <43DC1AE3.20104@cornell.edu> (raw)
In-Reply-To: <43DC18C0.6050901@cornell.edu>

Ivan Gyurdiev wrote:
> Note to joshua:
>
> Those system dbases won't really be necessary after seusers.system, 
> and users_extra.system are added into the package format. Then we can 
> get rid of them, and implement this the same way as file contexts is 
> currently done (see that section in direct_api.c) - extract seusers 
> and users_extra directly into the final files (no .system written). 
> Then merge local modifications on top of that.... very easy patch.
Actually I suppose they're not needed now either - all we need to do is 
copy the .system file over the final file.
That just never occurred to me, I like instantiating the dbase, it's 
extremely easy to do :)

I don't think it's worth changing at this point though - we can fix when 
the corresponding sections are merged into the package format.


--
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:[~2006-01-29  1:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-28 19:17 [SEMANAGE,UTILS] Support seusers.system Ivan Gyurdiev
2006-01-29  1:22 ` Ivan Gyurdiev
2006-01-29  1:31   ` Ivan Gyurdiev [this message]
2006-01-30 20:17 ` Stephen 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=43DC1AE3.20104@cornell.edu \
    --to=ivg2@cornell.edu \
    --cc=SELinux@tycho.nsa.gov \
    --cc=dwalsh@redhat.com \
    --cc=jbrindle@tresys.com \
    --cc=sds@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.