From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: "David O'Brien" <david.obrien@redhat.com>
Cc: James Antill <jantill@redhat.com>, selinux@tycho.nsa.gov
Subject: Re: User home directory creation with useradd (rhbz#217441)
Date: Mon, 04 Dec 2006 08:49:36 -0500 [thread overview]
Message-ID: <45742770.50001@mentalrootkit.com> (raw)
In-Reply-To: <200612041239.21597.david.obrien@redhat.com>
David O'Brien wrote:
> On Saturday 02 December 2006 06:22, Karl MacMillan wrote:
>>> 4. Document that you need to call the list of programs in #3.
>> Nobody reads documentation - this isn't viable. <-------- !!
>
> Karl... be nice. Tech writers are sensitive beings ;-)
>
Sorry! What I really should have said is, people don't normally find
features through documentation. Rather, they resort to docs once what
they have found doesn't work correctly. So in this case, if the features
aren't part of useradd it is unlikely they will find semanage or any
other SELinux feature.
Karl
--
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:[~2006-12-04 13:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 20:08 User home directory creation with useradd (rhbz#217441) James Antill
2006-12-01 20:22 ` Karl MacMillan
2006-12-04 2:39 ` David O'Brien
2006-12-04 13:49 ` Karl MacMillan [this message]
2006-12-04 23:38 ` David O'Brien
2006-12-01 20:47 ` Linda Knippers
2006-12-02 0:21 ` Russell Coker
2006-12-02 3:20 ` Joshua Brindle
2006-12-02 4:27 ` Russell Coker
2006-12-02 5:00 ` Joshua Brindle
2006-12-02 19:21 ` Linda Knippers
2006-12-02 19:29 ` Joshua Brindle
2006-12-05 8:42 ` Russell Coker
2006-12-02 23:08 ` Russell Coker
2006-12-04 17:43 ` Casey Schaufler
2006-12-04 18:10 ` Karl MacMillan
2006-12-04 19:34 ` Casey Schaufler
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=45742770.50001@mentalrootkit.com \
--to=kmacmillan@mentalrootkit.com \
--cc=david.obrien@redhat.com \
--cc=jantill@redhat.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.