Date: Thu, 27 Sep 2007 13:26:46 -0600 From: John E Hein <jhein@timing.com> To: "Tuc at T-B-O-H.NET" <ml@t-b-o-h.net> Cc: emulation@freebsd.org Subject: Re: Signal 12 on simple ldd / Linux Message-ID: <18172.1014.867507.713218@gromit.timing.com> In-Reply-To: <200709271817.l8RIHWK9020208@himinbjorg.tucs-beachin-obx-house.com> References: <20070927173022.GA39854@freebsd.org> <200709271817.l8RIHWK9020208@himinbjorg.tucs-beachin-obx-house.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Tuc at T-B-O-H.NET wrote at 14:17 -0400 on Sep 27, 2007: > I'm finding out that this also ISN'T happening on systems where > the Linux install is local, and used local. I'm finding 100% so far that > it only happens where /compat is NFS mounted. Is this something someone > has ever done, and are there any gotchas that I am running into because > of it, or is it just "One of those things you figure out that leads you > down the completely wrong path". We mount /compat/linux over NFS. I have not found any problems like the one you are having with it after doing so on some boxes for years (from 4.x to 6.x). Sometimes, I experience permission problems if, for instance, the app tries to write to /var/db or something (I don't export it with maproot=0). So occasionally I'll add a sym link in the nfs compat/linux tree to point to a local native directory.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18172.1014.867507.713218>