From: "James Bishop" <james.bishop@jrc.it>
To: Stephen Smalley <sds@tislabs.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: Compiling for SuSE 7.2
Date: Mon, 08 Oct 2001 18:31:00 +0200 [thread overview]
Message-ID: <3BC1D4C4.4070500@jrc.it> (raw)
In-Reply-To: Pine.GSO.4.33.0110080939300.9507-100000@raven
Thanks for your suggestion. On SuSE 7.2, the /bin/login program comes
from the RPM "shadow.rpm". MCONFIG in the SuSE 7.2 util-linux.spm
defines HAVE_SHADOW="yes", whereas the SELinux util-linux MCONFIG
defines HAVE_SHADOW="no".
So when I built util-linux from the SuSE SPM, /bin/login didn't change.
I'll poke around in the shadow.spm and see if I can find something in
the login.c there.
At this point, I doubt that my login problems are FLASK-related.
James
--
You have received this message because you are subscribed to the selinux 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:[~2001-10-08 16:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 13:17 Compiling for SuSE 7.2 James Bishop
2001-10-03 14:01 ` Stephen Smalley
2001-10-04 12:58 ` James Bishop
2001-10-04 15:24 ` Stephen Smalley
2001-09-04 21:45 ` John Scroggins
2001-10-05 12:56 ` Stephen Smalley
2001-10-05 7:21 ` James Bishop
2001-10-05 12:40 ` Russell Coker
2001-10-05 15:35 ` Stephen Smalley
2001-10-05 13:39 ` Stephen Smalley
2001-10-08 10:14 ` James Bishop
2001-10-08 13:50 ` Stephen Smalley
2001-10-08 16:31 ` James Bishop [this message]
2001-10-08 17:41 ` Stephen Smalley
2001-10-11 16:43 ` James Bishop
2001-10-04 17:05 ` debugging tools Conan Callen
2001-10-04 18:08 ` Stephen Smalley
2001-10-04 19:01 ` Jose Nazario
2001-10-04 12:47 ` Compiling for SuSE 7.2 Russell Coker
-- strict thread matches above, loose matches on Subject: below --
2001-10-05 17:09 Westerman, Mark
[not found] <Pine.GSO.4.33.0110111248230.18477-100000@raven>
2001-10-15 15:33 ` James Bishop
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=3BC1D4C4.4070500@jrc.it \
--to=james.bishop@jrc.it \
--cc=sds@tislabs.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.