On Thu, May 14, 2009 at 9:51 AM, Justin Mattock <justinmattock@xxxxxxxxx> wrote: > I've seen this with earlier versions of refpolicy(when making mcs) > > Validating mcs file_contexts. > /sbin/setfiles -q -c /etc/selinux/mcs/policy/policy.22 file_contexts > Installing file_contexts. > install -m 644 file_contexts /etc/selinux/mcs/contexts/files/file_contexts > install -m 644 homedir_template /etc/selinux/mcs/contexts/files/homedir_template > python -E support/genhomedircon -d /etc/selinux -t mcs > The user "staff_u" is not present in the passwd file, skipping... > The user "sysadm_u" is not present in the passwd file, skipping... > The user "unconfined_u" is not present in the passwd file, skipping... > make: *** No rule to make target > `/etc/selinux/mcs/contexts/default_contexts', needed by `install'. > Stop. > > when making the policy > I have the policy in my home directory > usually do a chown -R name:name refpolicy > (before building) > then: > make conf > make policy > sudo make install > > do I need to build this thing always as root? > > -- > Justin P. Mattock > my bad, I guess you can't compile a new refpolicy as mcs first(using standard first compiled cleanly) -- Justin P. Mattock -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
