[src/netbsd-1-6]: src/share/man/man8 Pullup revs 1.27-1.30 (requested by manu...

[jmc <jmc%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/d97a1ab44759
branches:  netbsd-1-6
changeset: 530948:d97a1ab44759
user:      jmc <jmc%NetBSD.org@localhost>
date:      Wed Oct 22 04:40:07 2003 +0000

description:
Pullup revs 1.27-1.30 (requested by manu in ticket #1444)

Replaced /proc with /emul/linux/proc. Some minor grammar fixes too.

diffstat:

 share/man/man8/compat_linux.8 |  205 +++++++++++++++++++++++------------------
 1 files changed, 114 insertions(+), 91 deletions(-)

diffs (truncated from 399 to 300 lines):

diff -r bc904ad64ebe -r d97a1ab44759 share/man/man8/compat_linux.8
--- a/share/man/man8/compat_linux.8     Wed Oct 22 04:22:25 2003 +0000
+++ b/share/man/man8/compat_linux.8     Wed Oct 22 04:40:07 2003 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: compat_linux.8,v 1.26 2002/03/29 16:07:39 bjh21 Exp $
+.\"    $NetBSD: compat_linux.8,v 1.26.2.1 2003/10/22 04:40:07 jmc Exp $
 .\"
 .\" Copyright (c) 1995 Frank van der Linden
 .\" All rights reserved.
@@ -37,18 +37,15 @@
 .Nd setup procedure for running Linux binaries
 .Sh DESCRIPTION
 .Nx
-supports running Linux binaries.  This applies to arm, alpha, i386, m68k and
-powerpc systems for now.  Both the a.out and ELF binary formats are supported.
+supports running Linux binaries.
+This applies to arm, alpha, i386, m68k and powerpc systems for now.
+Both the a.out and ELF binary formats are supported.
 Most programs should work, including the ones that use the Linux SVGAlib (only
-on i386).  Programs that will not work include some that use the Linux
-.Pa /proc
-filesystem (which is different from the optional
-.Nx
-.Pa /proc
-filesystem), and i386-specific calls, such as
-enabling virtual 8086 mode. Currently, sound is only partially
-supported for Linux binaries (they will probably run, depending on
-what Linux sound support features are used).
+on i386).
+Programs that will not work include some that use 
+i386-specific calls, such as enabling virtual 8086 mode.
+Currently, sound is only partially supported for Linux binaries (they will
+probably run, depending on what Linux sound support features are used).
 .Pp
 The Linux compatibility feature is active
 for kernels compiled with the
@@ -66,19 +63,20 @@
 options (respectively) should be enabled in addition to
 .Dv COMPAT_LINUX .
 .Pp
-A lot of programs are dynamically linked. This means that you will
-also need the Linux shared libraries that the program depends on, and
-the runtime linker. Also, you will need to create a
+A lot of programs are dynamically linked.
+This means that you will also need the Linux shared libraries that the
+program depends on, and the runtime linker.
+Also, you will need to create a
 .Dq shadow root
 directory for Linux binaries on your
 .Nx
-system. This directory
-is named
+system.
+This directory is named
 .Pa /emul/linux .
 Any file operations done by Linux programs run under
 .Nx
-will look in this directory first. So, if a Linux
-program opens, for example,
+will look in this directory first.
+So, if a Linux program opens, for example,
 .Pa /etc/passwd ,
 .Nx
 will
@@ -87,19 +85,21 @@
 and if that does not exist open the
 .Sq real
 .Pa /etc/passwd
-file. It is recommended that you install
+file.
+It is recommended that you install
 Linux packages that include configuration files, etc under
 .Pa /emul/linux ,
 to avoid naming conflicts with possible
 .Nx
-counterparts. Shared
-libraries should also be installed in the shadow tree.
+counterparts.
+Shared libraries should also be installed in the shadow tree.
 .Pp
 Generally, you will need to look for the shared libraries that Linux
 binaries depend on only the first few times that you install a Linux
 program on your
 .Nx
-system. After a while, you will have a sufficient
+system.
+After a while, you will have a sufficient
 set of Linux shared libraries on your system to be able to run newly
 imported Linux binaries without any extra work.
 .Ss Setting up shared libraries
@@ -113,19 +113,20 @@
 .It
 For i386, you can simply install the SuSE shared libs using the
 .Pa pkgsrc/emulators/suse_linux
-package(s). On PowerPC ports, the
+package(s).
+On PowerPC ports, the
 .Pa pkgsrc/emulators/linuxppc_lib
 will install the needed libraries.
 If you are on other platforms, or this doesn't supply you with all
 the needed libraries, read on.
 .It
-You have access to a Linux system. In this case you can
-temporarily install the binary there, see what shared libraries
-it needs, and copy them to your
+You have access to a Linux system.
+In this case you can temporarily install the binary there, see what
+shared libraries it needs, and copy them to your
 .Nx
-system. Example: you have
-just ftp-ed the Linux binary of Doom. Put it on the Linux
-system you have access to, and check which shared libraries it
+system.
+Example: you have just ftp-ed the Linux binary of Doom.
+Put it on the Linux system you have access to, and check which shared libraries it
 needs by running
 .Sq ldd linuxxdoom :
 .Pp
@@ -142,8 +143,8 @@
 put them under
 .Pa /emul/linux ,
 with the names in the first column
-as symbolic links pointing to them. This means you eventually have
-these files on your
+as symbolic links pointing to them.
+This means you eventually have these files on your
 .Nx
 system:
 .Bl -item -compact
@@ -168,11 +169,12 @@
 matching major revision number to the first column of the
 .Xr ldd 1
 output, you won't need to copy the file named in the last column
-to your system, the one you already have should work. It is
-advisable to copy the shared library anyway if it is a newer version,
-though. You can remove the old one, as long as you make the symbolic
-link point to the new one. So, if you have these libraries
-on your system:
+to your system, the one you already have should work.
+It is advisable to copy the shared library anyway if it is a newer version,
+though.
+You can remove the old one, as long as you make the symbolic
+link point to the new one.
+So, if you have these libraries on your system:
 .Pp
 .Bl -item -compact
 .It
@@ -214,7 +216,8 @@
 don't need to worry about that.
 .Pp
 Finally, you must make sure that you have the Linux runtime linker
-and its config files on your system. You should copy these
+and its config files on your system.
+You should copy these
 files from the Linux system to their appropriate place on your
 .Nx
 system (in the
@@ -229,10 +232,10 @@
 .Pa /etc/ld.so.config
 .El
 .It
-You don't have access to a Linux system. In that case, you
-should get the extra files you need from various ftp sites.
-Information on where to look for the various files is appended
-below. For now, let's assume you know where to get the files.
+You don't have access to a Linux system.
+In that case, you should get the extra files you need from various ftp sites.
+Information on where to look for the various files is appended below.
+For now, let's assume you know where to get the files.
 .Pp
 Retrieve the following files (from _one_ ftp site to avoid
 any version mismatches), and install them under
@@ -258,11 +261,11 @@
 .Ic ldd
 don't necessarily need to be under
 .Pa /emul/linux ,
-you can install them elsewhere in the system too. Just make sure
-they don't conflict with their
+you can install them elsewhere in the system too.
+Just make sure they don't conflict with their
 .Nx
-counterparts. A good idea
-would be to install them in
+counterparts.
+A good idea would be to install them in
 .Pa /usr/local/bin
 as
 .Ic ldconfig-linux
@@ -272,8 +275,8 @@
 Create the file
 .Pa /emul/linux/etc/ld.so.conf ,
 containing the directories in which the Linux runtime linker should look
-for shared libs. It is a plain text file, containing a directory
-name on each line.
+for shared libs.
+It is a plain text file, containing a directory name on each line.
 .Pa /lib
 and
 .Pa /usr/lib
@@ -294,7 +297,8 @@
 .Pp
 Run the Linux
 .Ic ldconfig
-program. It should be statically
+program.
+It should be statically
 linked, so it doesn't need any shared libraries by itself.
 It will create the file
 .Pa /emul/linux/etc/ld.so.cache
@@ -303,9 +307,11 @@
 each time you add a new shared library.
 .Pp
 You should now be set up for Linux binaries which only need
-a shared libc. You can test this by running the Linux
+a shared libc.
+You can test this by running the Linux
 .Ic ldd
-on itself. Suppose that you have it installed as
+on itself.
+Suppose that you have it installed as
 .Ic ldd-linux ,
 it should produce something like:
 .Pp
@@ -319,8 +325,8 @@
 if it needs shared libraries, and if so, whether you have
 them installed in the
 .Pa /emul/linux
-tree. To do this, you run
-the Linux
+tree.
+To do this, you run the Linux
 .Ic ldd
 on the new program, and watch its output.
 .Ic ldd
@@ -328,37 +334,48 @@
 .Xr ldd 1 )
 will print a list
 of shared libraries that the program depends on, in the
-form  \*[Lt]majorname\*[Gt] (\*[Lt]jumpversion\*[Gt]) =\*[Gt] \*[Lt]fullname\*[Gt].
+form
+.Aq majorname
+.Pq Aq jumpversion
+=\*[Gt]
+.Aq fullname .
 .Pp
 If it prints
 .Dq not found
-instead of \*[Lt]fullname\*[Gt] it means that
-you need an extra library. Which library this is, is shown
-in \*[Lt]majorname\*[Gt], which will be of the form libXXXX.so.\*[Lt]N\*[Gt]
-You will need to find a libXXXX.so.\*[Lt]N\*[Gt].\*[Lt]mm\*[Gt] on a Linux ftp site,
-and install it on your system. The XXXX (name) and \*[Lt]N\*[Gt] (major
-revision number) should match; the minor number(s) \*[Lt]mm\*[Gt] are
-less important, though it is advised to take the most
-recent version.
+instead of
+.Aq fullname
+it means that you need an extra library.
+Which library this is, is shown in
+.Aq majorname ,
+which will be of the form libXXXX.so.\*[Lt]N\*[Gt]
+You will need to find a libXXXX.so.\*[Lt]N\*[Gt].\*[Lt]mm\*[Gt] on a
+Linux ftp site, and install it on your system.
+The XXXX (name) and
+.Aq N
+(major revision number) should match; the minor number(s)
+.Aq mm
+are less important, though it is advised to take the most recent version.
 .El
 .Ss Setting up procfs
 Some Linux binaries expect procfs to be mounted and that it would
-contain some Linux specific stuff. If it's not the case, they behave
-unexpectedly or even crash.
+contain some Linux specific stuff.
+If it's not the case, they behave unexpectedly or even crash.
 .Pp
-Mount procfs on NetBSD using following command:
+Mount procfs on
+.Nx
+using following command:
 .Bl -tag -width 123 -offset indent
-.It (me@netbsd) mount_procfs -o linux procfs /proc
+.It (me@netbsd) mount_procfs -o linux procfs /emul/linux/proc
 .El
 .Pp
-You can also setup system so that procfs is mounted automatically
-on system boot, by putting entry like below to
+You can also set up your system so that procfs is mounted automatically
+on system boot, by putting an entry like the one below to
 .Pa /etc/fstab .
 .Bl -tag -width 123 -offset indent
-.It procfs /proc procfs ro,linux
+.It procfs /emul/linux/proc procfs ro,linux
 .El
 .Pp
-See also
+See
 .Xr mount_procfs 8
 for further information.
 .Ss Setting up other files