os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

In "Advanced Topics" section:

Browse source 
- Some punctuation fixes
- s/exec/execute s/FS/file system
- Some tags fixes.
This commit is contained in:
Marc Fonvieille 2003-10-24 07:18:34 +00:00
parent cc5b0f4cb9
commit 6e44992223
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=18561
1 changed files with 5 additions and 5 deletions

10
en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml
View file

@ -3214,7 +3214,7 @@ options SHMMAXPGS=393216
binaries.</para>
<para>For Linux binaries to function, they must be
<emphasis>branded</emphasis> as type <literal>Linux</literal>;
<emphasis>branded</emphasis> as type <literal>Linux</literal>
from &man.brandelf.1;:</para>
<screen>&prompt.root; <userinput>brandelf -t Linux file</userinput></screen>
@ -3247,8 +3247,8 @@ options SHMMAXPGS=393216
<para>In addition, the Linux mode dynamically
<emphasis>reroots</emphasis> lookups; this is, in effect, what the
<literal>union</literal> option to FS mounts
(<emphasis>not</emphasis> the unionfs!) does. First, an attempt
<option>union</option> option to file system mounts
(<emphasis>not</emphasis> the <literal>unionfs</literal> file system type!) does. First, an attempt
is made to lookup the file in the
<filename>/compat/linux/<replaceable>original-path</replaceable></filename>
directory, <emphasis>then</emphasis> only if that fails, the
@ -3257,7 +3257,7 @@ options SHMMAXPGS=393216
directory. This makes sure that binaries that require other
binaries can run (e.g., the Linux toolchain can all run under
Linux ABI support). It also means that the Linux binaries can
load and exec FreeBSD binaries, if there are no corresponding
load and execute FreeBSD binaries, if there are no corresponding
Linux binaries present, and that you could place a &man.uname.1;
command in the <filename>/compat/linux</filename> directory tree
to ensure that the Linux binaries could not tell they were not
@ -3282,7 +3282,7 @@ options SHMMAXPGS=393216
Basically the only difference is that (currently; this could
easily be changed in a future release, and probably will be after
this) the FreeBSD <emphasis>glue</emphasis> functions are
statically linked into the kernel, and the Linux glue functions
statically linked into the kernel, and the Linux <emphasis>glue</emphasis> functions
can be statically linked, or they can be accessed via a kernel
module.</para>