Hi Eric,

No need to apologize :)
Looping the list again, sorry for replying directly to you Eric. It was not my intention.

Regarding your question:

# ls -ltr /selinux/
total 0
-rw-rw-rw- 1 root root    0 Jan 23 09:56 user
-rw-rw-rw- 1 root root    0 Jan 23 09:56 relabel
-r--r--r-- 1 root root    0 Jan 23 09:56 policyvers
crw-rw-rw- 1 root root 1, 3 Jan 23 09:56 null
-r--r--r-- 1 root root    0 Jan 23 09:56 mls
-rw-rw-rw- 1 root root    0 Jan 23 09:56 member
-rw------- 1 root root    0 Jan 23 09:56 load
-rw-r--r-- 1 root root    0 Jan 23 09:56 enforce
--w------- 1 root root    0 Jan 23 09:56 disable
-rw-rw-rw- 1 root root    0 Jan 23 09:56 create
-rw-rw-rw- 1 root root    0 Jan 23 09:56 context
-rw-r--r-- 1 root root    0 Jan 23 09:56 compat_net
--w------- 1 root root    0 Jan 23 09:56 commit_pending_bools
-rw-r--r-- 1 root root    0 Jan 23 09:56 checkreqprot
dr-xr-xr-x 2 root root    0 Jan 23 09:56 booleans
dr-xr-xr-x 2 root root    0 Jan 23 09:56 avc
-rw-rw-rw- 1 root root    0 Jan 23 09:56 access

Thanks,
Paulo

On Thu, Jan 29, 2009 at 2:12 PM, Eric Paris <eparis@redhat.com> wrote:

On Thu, 2009-01-29 at 09:40 +0100, Paulo Santos wrote:
> Hi all,
>
> Is there any other information i'm able to provide, to help
> troubleshooting this issue ?

I'm sorry, I totally forgot about this conversation. I apologize.

Does your image contain an empty /selinux directory to which selinuxfs
can be mounted? Looks like that directory not existing and mount
failing could be a cause for what you are seeing...

-Eric