Date: Sun, 5 Jul 1998 06:12:28 -0300 (EST) From: Joao Carlos Mendes Luis <jonny@jonny.eng.br> To: tlambert@primenet.com (Terry Lambert) Cc: witr@rwwa.com, hackers@FreeBSD.ORG Subject: Loopback mounts (Was: Variant Link implementation) Message-ID: <199807050912.GAA04742@roma.coe.ufrj.br> In-Reply-To: <199807042109.OAA02700@usr02.primenet.com> from Terry Lambert at "Jul 4, 98 09:09:42 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
#define quoting(Terry Lambert) // > Note that AMD solves a similiar problem in different way. For // > example, /usr/global/bin gets directed to the correct filesystem // > based on the architecture/os. // // One issue with amd (which is only partially resolvable using the // symlink generation on the mounted fs instead of loopback) is that // loopback mounts via NFS are poison. It is rather easy to hang // every process using the loopback with a nice starvation deadlock // when using it for programs for which the loopback is a swap store. Is mount_null working ? Last time I tried it paniced my machine very often. And mount_umap would be wonderful for some applications, but the effects were even worse. If they work, we could patch amd to use them IFF rhost==thishost. AFAIK, Solaris has been doing this for a long time. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "There are two major products that come out of Berkeley: LSD and Unix. We don't believe this to be a coincidence." -- Jeremy S. Anderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807050912.GAA04742>