>>
>> I dug the archives but [1] does not really seem to be a solution
>> since / is not the nfs and I most likely also get Invalid Arugment on
>> doing that pivot_root.
>>
>> [1]
>> http://www.fsl.cs.sunysb.edu/pipermail/unionfs/2005-June/002830.html
>>
>> # mount /proc; cat /proc/mounts
>> rootfs / rootfs rw 0 0
>> udev /dev tmpfs rw 0 0
>> proc /proc proc rw 0 0
>> sysfs /sys sysfs rw 0 0
>> 192.168.222.1:/tftpboot/terran /.STATIC nfs
>> rw,vers=3,rsize=8192,wsize=8192,hard,intr,proto=tcp,timeo=600,retrans
>>=3,addr=192.168.222.1 0 0 /dev/disk/by-label/tmp /.DYNAMIC xfs rw 0 0
>> none / unionfs
>> rw,dirs=/.DYNAMIC=rw:/.STATIC=nfsro,debug=4294967295,delete=whiteout
>> 0 0
>>
>> Problem remains, programs will have /.STATIC in their /proc/$$/exe
>> link. Some people here seem to have workarounds that involve only
>> binding and mounting. What are the possibilities?
>
>Jan, sorry for the late answer, I'm pretty busy with awful lot of
>different things..
>
>What about dirty fixing it with a symlink, e.g.:
>ln -s . .STATIC
How is that supposed to work? /.STATIC is already a directory so it can't be a
symlink at the same time.
Nevertheless, enabling UNIONFS_MMAP solved it.
-`J'
--
_______________________________________________
unionfs mailing list
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
