From owner-freebsd-stable Fri Jul 16 7: 1:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from king.ki.informatik.uni-frankfurt.de (king.ki.informatik.uni-frankfurt.de [141.2.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 3750F150AB for ; Fri, 16 Jul 1999 07:01:30 -0700 (PDT) (envelope-from marko@king.ki.informatik.uni-frankfurt.de) Received: (from marko@localhost) by king.ki.informatik.uni-frankfurt.de (8.8.6 (PHNE_14041)/8.7.1) id QAA07613; Fri, 16 Jul 1999 16:01:29 +0200 (MESZ) To: freebsd-stable@FreeBSD.ORG Subject: Re: status of union fs??? References: <86u2r4hgg6.fsf@king.ki.informatik.uni-frankfurt.de> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=NIL From: Marko Schuetz Date: 16 Jul 1999 16:01:28 +0200 In-Reply-To: Marko Schuetz's message of "16 Jul 1999 15:28:25 +0200" Message-ID: <86r9m8hex3.fsf@king.ki.informatik.uni-frankfurt.de> Lines: 22 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In an explanation by Terry Lambert in the handbook In addition, the Linux emulation dynamically reroots lookups; this is, in effect, what the union option to FS mounts ( not the unionfs!) does. First, an attempt is made to lookup the file in What is the difference between the unionfs and mount_union? the /compat/linux/original-path directory, then only if that fails, the lookup is done in the /original-path directory. This makes sure that binaries that require other binaries can run (e.g., the Linux toolchain can all run under emulation). It also means that the Linux binaries can load and exec FreeBSD binaries, if there are no corresponding Linux binaries present, and that you could place a uname(1) command in the /compat/linux directory tree to ensure that the Linux binaries could not tell they were not running on Linux. So does that mean it works and the man page is out of date? Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message