I'm not sure what all the NFSv4 shared superblock magic is, but I think you might need to mount with nosharecache. See if that works for you.... -Eric On Thu, Jul 7, 2011 at 3:19 PM, Russell Coker <russell@xxxxxxxxxxxx> wrote: > # mount TEST:/bin /mnt/tmp2 -o context=rjc:object_r:user_tmp_t:s0 > # mount TEST:/sbin /mnt/tmp -o context=rjc:object_r:user_tmp_t:s0:c1 > mount.nfs: an incorrect mount option was specified > > It seems that if a server named TEST exports two NFS mount points from the > same filesystem (in this case /bin and /sbin both being on the root fs) then I > can't have one NFS client mount them both with different SE Linux contexts. > > As I have subtree_check enabled on the server and the server doesn't export / > it seems to me that there is no good reason for not allowing this. If > everything works as desired the result SHOULD be the same as if I had separate > filesystems for /bin and /sbin. > > Should we consider this a bug or at least a missing feature? > > -- > My Main Blog http://etbe.coker.com.au/ > My Documents Blog http://doc.coker.com.au/ > > -- > 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. > -- 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.
