From: "James Bishop" <james.bishop@jrc.it>
To: selinux@tycho.nsa.gov
Subject: Compiling for SuSE 7.2
Date: Wed, 03 Oct 2001 15:17:37 +0200 [thread overview]
Message-ID: <3BBB0FF1.6060309@jrc.it> (raw)
Good afternoon,
This is my first posting to this list, so "hello world!\n".
I'm building the lsm-selinux-200109261436.tgz distribution on my SuSE
7.2 system. Up to item 6) in the installation instructions, everything
has worked without a hitch.
Compilation of the modified applications in the selinux/utils
sub-directory required commenting out the contents of the
fileutils-4.0/m4/isc-posix.m4 file (I don't know m4); and changing the
Makefile in psmisc to link pstree with the ncurses library instead of
the termcap library.
Now I'm up against the differences between the RedHat 7.1 and SuSE 7.2
distributions. The MCONFIG files of the util-linux package are different
(also SuSE 7.2 uses util-linux-2.11). I know from past experience that
getting things wrong with util-linux is "a bit of a bore".
If I proceed to install the utils package as is, can anyone tell me
whether login will still work? Or could / should I modify the MCONFIG
file of SELinux to bring it closer into line with the SuSE 7.2 version?
I see that the SELinux Makefile moves the original /bin/login to
/bin/login.old and then installs the new /bin/login. If I could ensure
that /bin/login.old was used (perhaps on the basis of the result of the
uname command - SuSE 7.2 is kernel version 2.4.4)I would feel better.
How could I do this?
Should I remove shadow passwords from the SuSE 7.2 system before
proceeding, or can I leave them in place?
All the best,
James Bishop
--
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 reply other threads:[~2001-10-03 13:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 13:17 James Bishop [this message]
2001-10-03 14:01 ` Compiling for SuSE 7.2 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
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=3BBB0FF1.6060309@jrc.it \
--to=james.bishop@jrc.it \
--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.