From: Garrett C. <yan...@gm...> - 2010-01-08 22:08:56
|
On Fri, Jan 8, 2010 at 2:00 PM, Stephen Smalley <sd...@ty...> wrote: > On Fri, 2010-01-08 at 13:38 -0800, Garrett Cooper wrote: >> On Fri, Jan 8, 2010 at 10:50 AM, Stephen Smalley <sd...@ty...> wrote: >> > On Fri, 2010-01-08 at 13:47 -0500, Stephen Smalley wrote: >> >> On Fri, 2010-01-08 at 10:20 -0800, Garrett Cooper wrote: >> >> > Thanks for the feedback and details Stephen. >> >> > Would you be kind enough to try out the version from CVS to see >> >> > whether or not it resolves your issue? You'll also need to update >> >> > $LTPROOT/scripts in order to use the new version as I added a distro >> >> > detection script which opens up /etc/redhat-release (for redhat) as >> >> > opposed to using rpm to query the release. >> >> > Thanks, >> >> > -Garrett >> >> >> >> The attempt to make the test policy immediately dies with: >> >> detect_distro.sh: ERROR: Bad release file: /etc/redhat-release >> > >> > I should note that I'm running it on Fedora, so I wouldn't expect that >> > file to exist. But the script needs to handle it gracefully; we just >> > use the generic test policy files in that situation. >> >> What does /etc/redhat-release look like (feel free to reply to me off-list)? > > On RHEL5, it can look like one of the following: > Red Hat Enterprise Linux Server release 5 (Tikanga) > Red Hat Enterprise Linux Server release 5.x (Tikanga) > Red Hat Enterprise Linux Client release 5 (Tikanga) > Red Hat Enterprise Linux Client release 5.x (Tikanga) Interesting. They switched over to more of the Fedora-style branding, maybe?. [garrcoop@halflife ~]$ cat /etc/redhat-release Red Hat Enterprise Linux AS release 4 (Nahant Update 6) Thanks, -Garrett |