thanks for your replies. i`m confused a little bit now.
what is simply want is that an nfs share behaves just as another ordinary filesystem share. if i share a directory via samba, it doesn`t matter how the mount strcuture looks like, i.e. it simply exports a directory structure. it`s irrelevant if it`s a single tree or a tree which is built from 2314 different filesystems , i.e. which has 2314 mountpoints inside. the user can just see (and reach) dirs and files. same with ftp. same with http. same with rsync. same with webdav. same with (insert your preffered net-filesystem here) i`d like to just have "showmount -e" show some export: /myExport (myesxserver) so, myExport simply should be to upper level to be exported, no matter what filesystem is mounted some dirs below that. they just should be accessible via this single share. I don`t want any additional share like "/myExport/anothermountbelowmyExport (myesxserver)". this is my linux cd-rom server: cdromix:/iso-images # cat /etc/exports /cd-roms *(ro,root_squash,subtree_check,crossmnt) below cd-roms there is a large collection of loopback-mounted iso-images. this is exported via nfs and i can mount it on the client with ONE single nfs mount commmand and access _all_ cdroms below that. so the question again, where`s the problem to have that on solaris and where`s the real culprit here. maybe nfs is just too different and too (let`s call it) "filesystem agnostic" ? -- This message posted from opensolaris.org
