Principally, change foo(N) to .Xr foo N

Also, do some other mdoc tagging.
This commit is contained in:
fair 1998-04-28 04:07:04 +00:00
parent a6084492d9
commit c46ab392dc
25 changed files with 272 additions and 197 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: countmail.6,v 1.2 1997/10/10 05:39:47 mrg Exp $
.\" $NetBSD: countmail.6,v 1.3 1998/04/28 04:07:04 fair Exp $
.\"
.\" Copyright (c) 1997 Matthew R. Green
.\" All rights reserved.
@ -47,11 +47,12 @@ first appeared in
was first written by Noah Friedman <friedman@splode.com> in 1993.
This version was written by Charles Hannum <mycroft@mit.edu>.
.Sh CAVEATS
The read loop is horrendously slow on every shell implementation
tried.
The read loop is horrendously slow on every shell implementation tried.
.Nm
uses
from(1) and wc(1) instead, though these are
not shell builtins.
.Xr from 1
and
.Xr wc 1
instead, though these are not shell builtins.
.Sh SEE ALSO
.Xr from 1 .

View File

@ -1,4 +1,4 @@
.\" $NetBSD: ldd.1,v 1.2 1995/10/08 23:39:58 pk Exp $
.\" $NetBSD: ldd.1,v 1.3 1998/04/28 04:07:05 fair Exp $
.\"
.\" Copyright (c) 1993 Paul Kranenburg
.\" All rights reserved.
@ -35,13 +35,15 @@
.Nm ldd
.Nd list dynamic object dependencies
.Sh SYNOPSIS
.Nm ldd
.Nm
.Op Fl f Ar format
.Ar program ...
.Sh DESCRIPTION
.Nm ldd
.Nm
displays all shared objects that are needed to run the given program.
Contrary to nm(1), the list includes
Contrary to
.Xr nm 1 ,
the list includes
.Dq indirect
depedencies that are the result of needed shared objects which themselves
depend on yet other shared objects.
@ -51,7 +53,8 @@ options may be given. The argument is a format string passed to
.Xr rtld 1
and allows customization of
.Nm ldd Ns 's
output. See
output.
See
.Xr rtld 1
for a list of recognised conversion characters.
.Sh SEE ALSO
@ -60,6 +63,7 @@ for a list of recognised conversion characters.
.Xr nm 1
.Sh HISTORY
A
.Nm ldd
.Nm
utility first appeared in SunOS 4.0, it appeared in its current form
in NetBSD 0.9a.
in
.Nx 0.9a .

View File

@ -1,4 +1,4 @@
.\" $NetBSD: alarm.3,v 1.12 1998/02/05 18:45:52 perry Exp $
.\" $NetBSD: alarm.3,v 1.13 1998/04/28 04:07:05 fair Exp $
.\"
.\" Copyright (c) 1980, 1991, 1993, 1994
.\" The Regents of the University of California. All rights reserved.
@ -47,7 +47,8 @@
.Fn alarm "unsigned int seconds"
.Sh DESCRIPTION
.Bf -symbolic
This interface is made obsolete by setitimer(2).
This interface is made obsolete by
.Xr setitimer 2 .
.Ef
.Pp
The

View File

@ -1,4 +1,4 @@
.\" $NetBSD: confstr.3,v 1.7 1998/02/05 18:45:58 perry Exp $
.\" $NetBSD: confstr.3,v 1.8 1998/04/28 04:07:05 fair Exp $
.\"
.\" Copyright (c) 1993
.\" The Regents of the University of California. All rights reserved.
@ -47,7 +47,8 @@
.Fn confstr "int name" "char *buf" "size_t len"
.Sh DESCRIPTION
.Bf -symbolic
This interface is obsoleted by sysctl(3).
This interface is obsoleted by
.Xr sysctl 3 .
.Ef
.Pp
The

View File

@ -1,4 +1,4 @@
.\" $NetBSD: fts.3,v 1.15 1998/02/05 18:46:23 perry Exp $
.\" $NetBSD: fts.3,v 1.16 1998/04/28 04:07:05 fair Exp $
.\"
.\" Copyright (c) 1989, 1991, 1993, 1994
.\" The Regents of the University of California. All rights reserved.
@ -149,7 +149,7 @@ A directory that causes a cycle in the tree.
.Fa fts_cycle
field of the
.Fa FTSENT
structure will be filled in as well.)
structure will be filled in as well).
.It Dv FTS_DEFAULT
Any
.Fa FTSENT

View File

@ -1,4 +1,4 @@
.\" $NetBSD: nice.3,v 1.5 1998/02/16 15:47:40 kleink Exp $
.\" $NetBSD: nice.3,v 1.6 1998/04/28 04:07:06 fair Exp $
.\"
.\" Copyright (c) 1980, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -47,7 +47,8 @@
.Fn nice "int incr"
.Sh DESCRIPTION
.Bf -symbolic
This interface is obsoleted by setpriority(2).
This interface is obsoleted by
.Xr setpriority 2 .
.Ef
.Pp
The
@ -77,7 +78,7 @@ function will fail if:
.It Bq Er EPERM
The
.Fa incr
argument is negative and the caller is not the suprt-user.
argument is negative and the caller is not the super-user.
.El
.Sh STANDARDS
The

View File

@ -1,4 +1,4 @@
.\" $NetBSD: pause.3,v 1.8 1998/02/05 18:47:35 perry Exp $
.\" $NetBSD: pause.3,v 1.9 1998/04/28 04:07:06 fair Exp $
.\"
.\" Copyright (c) 1980, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -47,7 +47,8 @@
.Fn pause void
.Sh DESCRIPTION
.Bf -symbolic
Pause is made obsolete by sigsuspend(2).
Pause is made obsolete by
.Xr sigsuspend 2 .
.Ef
.Pp
The

View File

@ -1,4 +1,4 @@
.\" $NetBSD: times.3,v 1.6 1998/02/05 18:48:06 perry Exp $
.\" $NetBSD: times.3,v 1.7 1998/04/28 04:07:06 fair Exp $
.\"
.\" Copyright (c) 1990, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -47,8 +47,10 @@
.Fn times "struct tms *tp"
.Sh DESCRIPTION
.Bf -symbolic
This interface is obsoleted by getrusage(2)
and gettimeofday(3).
This interface is obsoleted by
.Xr getrusage 2
and
.Xr gettimeofday 3 .
.Ef
.Pp
The

View File

@ -1,4 +1,4 @@
.\" $NetBSD: timezone.3,v 1.8 1998/02/05 18:48:07 perry Exp $
.\" $NetBSD: timezone.3,v 1.9 1998/04/28 04:07:06 fair Exp $
.\"
.\" Copyright (c) 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -51,7 +51,8 @@
This interface is available for compatibility;
it is impossible to reliably map timezone's arguments to a time zone
abbreviation.
See ctime(3).
See
.Xr ctime 3 .
.Ef
.Pp
The

View File

@ -1,4 +1,4 @@
.\" $NetBSD: ualarm.3,v 1.9 1998/02/05 18:48:17 perry Exp $
.\" $NetBSD: ualarm.3,v 1.10 1998/04/28 04:07:06 fair Exp $
.\"
.\" Copyright (c) 1986, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -47,7 +47,8 @@
.Fn ualarm "useconds_t microseconds" "useconds_t interval"
.Sh DESCRIPTION
.Bf -symbolic
This is a simplified interface to setitimer(2).
This is a simplified interface to
.Xr setitimer 2 .
.Ef
.Pp
The

View File

@ -1,4 +1,4 @@
.\" $NetBSD: utime.3,v 1.10 1998/02/05 18:48:23 perry Exp $
.\" $NetBSD: utime.3,v 1.11 1998/04/28 04:07:06 fair Exp $
.\"
.\" Copyright (c) 1980, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -48,7 +48,8 @@
.Fn utime "const char *file" "const struct utimbuf *timep"
.Sh DESCRIPTION
.Bf -symbolic
This interface is obsoleted by utimes(2) .
This interface is obsoleted by
.Xr utimes 2 .
.Ef
.Pp
The

View File

@ -1,4 +1,4 @@
.\" $NetBSD: valloc.3,v 1.5 1998/02/12 20:18:23 kleink Exp $
.\" $NetBSD: valloc.3,v 1.6 1998/04/28 04:07:06 fair Exp $
.\"
.\" Copyright (c) 1980, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -47,7 +47,8 @@
.Fn valloc "size_t size"
.Sh DESCRIPTION
.Bf -symbolic
Valloc is obsoleted by the current version of malloc(3),
Valloc is obsoleted by the current version of
.Xr malloc 3 ,
which aligns page-sized and larger allocations.
.Ef
.Pp
@ -75,5 +76,4 @@ function appeared in
.Sh BUGS
A
.Em vfree
function
has not been implemented.
function has not been implemented.

View File

@ -1,4 +1,4 @@
.\" $NetBSD: rand.3,v 1.6 1998/02/05 18:50:14 perry Exp $
.\" $NetBSD: rand.3,v 1.7 1998/04/28 04:07:06 fair Exp $
.\"
.\" Copyright (c) 1990, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -57,7 +57,8 @@
.Fn rand_r "unsigned int *seed"
.Sh DESCRIPTION
.Bf -symbolic
These interfaces are obsoleted by random(3).
These interfaces are obsoleted by
.Xr random 3 .
.Ef
.Pp
The

View File

@ -34,7 +34,7 @@
.\" SUCH DAMAGE.
.\"
.\" from: @(#)strtok.3 8.2 (Berkeley) 2/3/94
.\" $NetBSD: strtok.3,v 1.7 1998/02/05 18:50:59 perry Exp $
.\" $NetBSD: strtok.3,v 1.8 1998/04/28 04:07:07 fair Exp $
.\"
.Dd February 3, 1994
.Dt STRTOK 3
@ -52,7 +52,8 @@
.Fn strtok_r "char *str" "const char *sep" "char **lasts"
.Sh DESCRIPTION
.Bf -symbolic
This interface is obsoleted by strsep(3).
This interface is obsoleted by
.Xr strsep 3 .
.Ef
.Pp
The

View File

@ -1,4 +1,4 @@
.\" $NetBSD: disklabel.5,v 1.5 1997/03/08 13:49:40 mouse Exp $
.\" $NetBSD: disklabel.5,v 1.6 1998/04/28 04:07:07 fair Exp $
.\"
.\" Copyright (c) 1987, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -405,4 +405,4 @@ Disk specific ioctls ar defined in
.Sh SEE ALSO
.Xr disktab 5 ,
.Xr disklabel 8
.Sh HISTORY
.\" .Sh HISTORY

View File

@ -1,4 +1,4 @@
.\" $NetBSD: ccd.4,v 1.13 1998/02/22 07:16:07 enami Exp $
.\" $NetBSD: ccd.4,v 1.14 1998/04/28 04:07:07 fair Exp $
.\"
.\" Copyright (c) 1996, 1997 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -86,15 +86,20 @@ configuration file, and how to partition disks.
Note that the
.Sq raw
partitions of the disks
.Pa should not
be combined. Each component partition should be offset at least one
cylinder from the beginning of the component disk. This avoids potential
conflicts between the component disk's disklabel and the
.Pa must not
be combined.
Each component partition should be offset at least one cylinder
from the beginning of the component disk.
This avoids potential conflicts between the component disk's
disklabel and the
.Nm Ns 's
disklabel. The kernel will only allow component partitions of type
disklabel.
The kernel will only allow component partitions of type
.Dv FS_BSDFFS .
.Pp
In order to compile in support for the ccd, you must add a line similar
In order to compile in support for the
.Nm "" ,
you must add a line similar
to the following to your kernel configuration file:
.Bd -unfilled -offset indent
pseudo-device ccd 4 # concatenated disk devices
@ -102,19 +107,21 @@ pseudo-device ccd 4 # concatenated disk devices
.Pp
The count argument is how many
.Nm Ns s
memory is allocated for at boot time. In this example, no more than 4
memory is allocated for at boot time.
In this example, no more than 4
.Nm Ns s
may be configured.
.Pp
A
.Nm
may be either serially concatenated or interleaved. If a
may be either serially concatenated or interleaved.
If a
.Nm
is interleaved correctly, a
.Dq striping
effect is achieved, which can increase performance. The optimum interleave
factor is typically the size of a track. Since the interleave factor
is expressed in units of
effect is achieved, which can increase performance.
The optimum interleave factor is typically the size of a track.
Since the interleave factor is expressed in units of
.Dv DEV_BSIZE ,
one must account for sector sizes other than
.Dv DEV_BSIZE
@ -124,28 +131,31 @@ of the largest component sector divided by
.Dv DEV_BSIZE .
.Pp
Note that best performance is achieved if all component disks have the same
geometry and size. Optimum striping cannot occur with different
disk types.
geometry and size.
Optimum striping cannot occur with different disk types.
.Pp
The
.Nm
also supports primitive data mirroring. To enable this mirroring support,
the
also supports primitive data mirroring.
To enable this mirroring support, the
.Nm
must be configured with the
.Dv CCDF_MIRROR
flag set. Note that the
flag set.
Note that the
.Dv CCDF_MIRROR
flag implies the
.Dv CCDF_UNIFORM
flag and requires an interleaved even number of components.
.Pp
Mirroring functions by making the second n/2 components exact duplicates
of the first n/2. For example, in a mirrored
of the first n/2.
For example, in a mirrored
.Nm
with components sd0g, sd1g, sd2g, and sd3g, sd2g would mirror sd0g and
sd3g would mirror sd1g. Reads will come from the first n/2 components
(in this example: sd0g and sd1g) while writes will go to all components.
sd3g would mirror sd1g.
Reads will come from the first n/2 components (in this example:
sd0g and sd1g) while writes will go to all components.
.Pp
If a component of a mirrored
.Nm
@ -153,18 +163,31 @@ should fail, the
.Nm
can be reconfigured as a non-mirrored
.Nm
until the failed component can be replaced. For example, using the
hypothetical
until the failed component can be replaced.
For example, using the hypothetical
.Nm
above, the recovery process might look like this:
.Bd -literal -offset indent
* Component sd1g fails. Reconfigure ccd without mirroring
using the same interleave factor with components sd0g and sd3g.
ccd can still be used until replacement drive arrives.
* Replace failed component. Using dd(1), copy the contents of
sd3g to the new sd1g.
* Restore ccd configuration to that of before the component failure.
.Ed
.Bl -enum
.It
Component sd1g fails.
.It
Reconfigure
.Nm
without mirroring using the same interleave factor with components
sd0g and sd3g.
.Nm
can still be used until replacement drive arrives.
.It
Replace failed component.
.It
Using
.Xr dd 1 ,
copy the contents of sd3g to the new sd1g.
.It
Restore
.Nm
configuration to that of before the component failure.
.El
.Pp
There is a run-time utility that is used for configuring
.Nm Ns s.
@ -174,18 +197,16 @@ for more information.
.Sh WARNINGS
If just one (or more) of the disks in a non-mirrored
.Nm
fails, the entire
file system will be lost.
fails, the entire file system will be lost.
.Sh FILES
.Bl -tag -width /dev/XXrXccdX -compact
.It Pa /dev/{,r}ccd*
ccd device special files.
.Nm
device special files.
.El
.Pp
.Sh HISTORY
The concatenated disk driver was originally written at the University of
Utah.
.Sh SEE ALSO
The concatenated disk driver was originally written at the University of Utah.
.Xr MAKEDEV 8 ,
.Xr ccdconfig 8 ,
.Xr config 8 ,

View File

@ -1,4 +1,4 @@
.\" $NetBSD: compat_freebsd.8,v 1.4 1998/02/06 06:14:46 perry Exp $
.\" $NetBSD: compat_freebsd.8,v 1.5 1998/04/28 04:07:07 fair Exp $
.\" from: compat_linux.8,v 1.1 1995/03/05 23:30:36 fvdl Exp
.\"
.\" Copyright (c) 1995 Frank van der Linden
@ -40,11 +40,11 @@
.Nx
supports running
.Fx
binaries. Most binaries should work,
except programs that use
binaries.
Most binaries should work, except programs that use
.Fx Ns -specific
features. These include
i386-specific calls, such as syscons utilities.
features.
These include i386-specific calls, such as syscons utilities.
The
.Fx
compatibility feature is active for kernels compiled
@ -55,27 +55,35 @@ option enabled.
A lot of programs are dynamically linked. This means, that you will
also need the
.Fx
shared libraries that the program depends on, and
the runtime linker. Also, you will need to create a "shadow root"
directory for
shared libraries that the program depends on, and the runtime
linker.
Also, you will need to create a "shadow root" directory for
.Fx
binaries on your
.Nx
system. This directory
is named /emul/freebsd. Any file operations done by
is named
.Pa /emul/freebsd .
Any file operations done by
.Fx
programs
run under
programs run under
.Nx
will look in this directory first. So, if a
will look in this directory first.
So, if a
.Fx
program opens, for example, /etc/passwd,
program opens, for example,
.Pa /etc/passwd ,
.Nx
will
first try to open /emul/freebsd/etc/passwd, and if that does not exist
open the 'real' /etc/passwd file. It is recommended that you install
first try to open
.Pa /emul/freebsd/etc/passwd ,
and if that does not exist open the 'real'
.Pa /etc/passwd
file.
It is recommended that you install
.Fx
packages that include configuration files, etc under /emul/freebsd,
packages that include configuration files, etc under
.Pa /emul/freebsd ,
to avoid naming conflicts with possible
.Nx
counterparts. Shared
@ -102,21 +110,21 @@ binaries need, and where
to get them? Basically, there are 2 possibilities (when following
these instructions: you will need to be root on your
.Nx
system to
do the necessary installation steps).
system to do the necessary installation steps).
.Bl -tag -width 123 -compact
.It 1.
You have access to a
.Fx
system. In this case you can
temporarily install the binary there, see what shared libraries
it needs, and copy them to your
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
system.
Example: you have just ftp-ed the
.Fx
binary of SimCity. Put it on the
binary of SimCity.
Put it on the
.Fx
system you have access to, and check which shared libraries it
needs by running `ldd sim':
@ -134,62 +142,66 @@ needs by running `ldd sim':
.El
.Pp
You would need go get all the files from the last column, and
put them under /emul/freebsd. This means you eventually have
these files on your
put them under
.Pa /emul/freebsd .
This means you eventually have these files on your
.Nx
system:
.Pp
.nf
/emul/freebsd/usr/X11R6/lib/libXext.so.6.0
/emul/freebsd/usr/X11R6/lib/libX11.so.6.0
/emul/freebsd/usr/lib/libc.so.2.1
/emul/freebsd/usr/lib/libm.so.2.0
/emul/freebsd/usr/lib/libgcc.so.261.0
.Pa /emul/freebsd/usr/X11R6/lib/libXext.so.6.0
.Pa /emul/freebsd/usr/X11R6/lib/libX11.so.6.0
.Pa /emul/freebsd/usr/lib/libc.so.2.1
.Pa /emul/freebsd/usr/lib/libm.so.2.0
.Pa /emul/freebsd/usr/lib/libgcc.so.261.0
.fi
.Pp
Note that if you already have a
.Fx
shared library with a
matching major revision number to the first column of the 'ldd'
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. So, if you have these libraries
on your system:
shared library with a matching major revision number to the first
column of the 'ldd' 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.
So, if you have these libraries on your system:
.Pp
.nf
/emul/freebsd/usr/lib/libc.so.2.0
.Pa /emul/freebsd/usr/lib/libc.so.2.0
.fi
.Pp
and you find that the ldd output for a new binary you want to
install is:
.nf
.Pp
-lc.2 => /usr/lib/libc.so.2.1 (0x10144000)
.nf
\-lc.2 => /usr/lib/libc.so.2.1 (0x10144000)
.fi
.Pp
you won't need to worry about copying /usr/lib/libc.so.2.1 too,
You won't need to worry about copying
.Pa /usr/lib/libc.so.2.1 too ,
because the program should work fine with the slightly older version.
You can decide to replace the libc.so anyway, and that should leave
you with:
.Pp
.nf
/emul/freebsd/usr/lib/libc.so.2.1
.Pa /emul/freebsd/usr/lib/libc.so.2.1
.fi
.Pp
Finally, you must make sure that you have the
.Fx
runtime linker
and its config files on your system. You should copy these
files from the
runtime linker and its config files on your system.
You should copy these files from the
.Fx
system to their appropriate place on your
.Nx
system (in the /emul/freebsd tree):
system (in the
.Pa /emul/freebsd
tree):
.Pp
.nf
usr/libexec/ld.so
var/run/ld.so.hints
.Pa usr/libexec/ld.so
.Pa var/run/ld.so.hints
.fi
.Pp
.It 2.
@ -205,27 +217,29 @@ any version mismatches), and install them under /emul/freebsd
(i.e. foo/bar is installed as /emul/freebsd/foo/bar):
.Pp
.nf
sbin/ldconfig
usr/bin/ldd
usr/lib/libc.so.x.y.z
usr/libexec/ld.so
.Pa sbin/ldconfig
.Pa usr/bin/ldd
.Pa usr/lib/libc.so.x.y.z
.Pa usr/libexec/ld.so
.fi
.Pp
ldconfig and ldd don't necessarily need to be under /emul/freebsd,
ldconfig and ldd don't necessarily need to be under
.Pa /emul/freebsd ,
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 /usr/local/bin as ldconfig-freebsd and
ldd-freebsd.
counterparts.
A good idea would be to install them in
.Pa /usr/local/bin
as ldconfig-freebsd and ldd-freebsd.
.Pp
Run the
.Fx
ldconfig program with directory arguments in
which the
ldconfig program with directory arguments in which the
.Fx
runtime linker should look for shared libs.
/usr/lib are standard, you could run like the following:
.Pa /usr/lib
are standard, you could run like the following:
.Pp
.Bl -tag -width 123 -compact -offset indent
.It me@netbsd% mkdir -p /emul/freebsd/var/run
@ -234,30 +248,34 @@ runtime linker should look for shared libs.
.El
.Pp
Note that argument directories of ldconfig are
mapped to /emul/freebsd/XXXX by
mapped to
.Pa /emul/freebsd/XXXX
by
.Nx Ns 's
compat code, and should exist as such on your system.
Make sure /emul/freebsd/var/run/ld.so.hints is exist when you run
Make sure
.Pa /emul/freebsd/var/run/ld.so.hints
is existing when you run
.Fx Ns 's
ldconfig, if not, you may lose
.Nx Ns 's
/var/run/ld.so.hints.
.Pa /var/run/ld.so.hints.
.Fx
ldconfig should be statically
linked, so it doesn't need any shared libraries by itself.
It will create the file /emul/freebsd/var/run/ld.so.hints.
It will create the file
.Pa /emul/freebsd/var/run/ld.so.hints.
You should rerun the
.Fx
version of the ldconfig program
each time you add a new shared library.
version of the ldconfig program each time you add a new shared library.
.Pp
You should now be set up for
.Fx
binaries which only need
a shared libc. You can test this by running the
binaries which only need a shared libc.
You can test this by running the
.Fx
ldd
on itself. Suppose that you have it installed as ldd-freebsd, it
ldd on itself.
Suppose that you have it installed as ldd-freebsd, it
should produce something like:
.Pp
.Bl -tag -width 123 -compact -offset indent
@ -273,28 +291,32 @@ This being done, you are ready to install new
binaries.
Whenever you install a new
.Fx
program, you should check
if it needs shared libraries, and if so, whether you have
them installed in the /emul/freebsd tree. To do this, you run
the
program, you should check if it needs shared libraries, and if so,
whether you have them installed in the
.Pa /emul/freebsd
tree.
To do this, you run the
.Fx
version ldd on the new program, and watch its output.
ldd (see also the manual page for ldd(1)) will print a list
ldd (see also the manual page for
.Xr ldd 1 )
will print a list
of shared libraries that the program depends on, in the
form -l<majorname> => <fullname>.
.Pp
If it prints "not found" in stead of <fullname> it means that
you need an extra library. Which library this is, is shown
you need an extra library.
Which library this is, is shown
in <majorname>, which will be of the form XXXX.<N>
You will need to find a libXXXX.so.<N>.<mm> on a
.Fx
ftp site,
and install it on your system. The XXXX (name) and <N> (major
and install it on your system.
The XXXX (name) and <N> (major
revision number) should match; the minor number(s) <mm> are
less important, though it is advised to take the most
recent version.
.El
.Ss Finding the necessary files.
.Em Note:
the information below is valid as of the time this
@ -304,12 +326,11 @@ may have changed by the time you read this.
.Pp
The
.Fx
distribution is
available on a lot of ftp sites. Sometimes the files are unpacked,
and you can get the individual files you need, but mostly they
are stored in distribution sets, usually consisting of subdirectories
with gzipped tar files in them. The primary ftp sites for the
distributions are:
distribution is available on a lot of ftp sites.
Sometimes the files are unpacked, and you can get the individual
files you need, but mostly they are stored in distribution sets,
usually consisting of subdirectories with gzipped tar files in them.
The primary ftp sites for the distributions are:
.Pp
.nf
ftp.freebsd.org:/pub/FreeBSD
@ -323,9 +344,10 @@ ftp.freebsd.org:/pub/FreeBSD/MIRROR.SITES
.Pp
This distribution consists of a number of tar-ed and gzipped files,
Normally, they're controlled by an install program, but you can
retrieve files "by hand" too. The way to look something up is to retrieve all
the files in the distribution, and ``tar ztvf'' through them for the file
you need. Here is an example of a list of files that you might need.
retrieve files "by hand" too.
The way to look something up is to retrieve all the files in the
distribution, and ``tar ztvf'' through them for the file you need.
Here is an example of a list of files that you might need.
.Pp
.Bd -unfilled -offset indent
Needed Files
@ -345,9 +367,10 @@ libXt.so.6.0 XFree86-3.1.1/X311bin.tgz
The Files called ``bindist.??'' are tar-ed, gzipped and split,
so you can extract contents by ``cat bindist.?? | tar zpxf -''.
.Pp
Extract the files from these gzipped tarfiles in your /emul/freebsd directory
(possibly omitting or afterwards removing files you don't need), and you
are done.
Extract the files from these gzipped tarfiles in your
.Pa /emul/freebsd
directory (possibly omitting or afterwards removing files you don't
need), and you are done.
.Sh BUGS
The information about
.Fx

View File

@ -1,4 +1,4 @@
.\" $NetBSD: compat_linux.8,v 1.10 1998/02/06 06:14:48 perry Exp $
.\" $NetBSD: compat_linux.8,v 1.11 1998/04/28 04:07:07 fair Exp $
.\"
.\" Copyright (c) 1995 Frank van der Linden
.\" All rights reserved.
@ -250,7 +250,9 @@ Whenever you install a new Linux program, you should check
if it needs shared libraries, and if so, whether you have
them installed in the /emul/linux tree. To do this, you run
the Linux version ldd on the new program, and watch its output.
ldd (see also the manual page for ldd(1)) will print a list
ldd (see also the manual page for
.Xr ldd 1 )
will print a list
of shared libraries that the program depends on, in the
form <majorname> (<jumpversion>) => <fullname>.
.Pp

View File

@ -1,4 +1,4 @@
.\" $NetBSD: MAKEDEV.8,v 1.6 1997/11/20 06:17:44 fair Exp $
.\" $NetBSD: MAKEDEV.8,v 1.7 1998/04/28 04:07:08 fair Exp $
.\"
.\" Copyright (c) 1991, 1992, 1993
.\" The Regents of the University of California. All rights reserved.
@ -51,7 +51,7 @@ found in the
directory, is used to create the common special
files.
.\" See
.\" .IR special (8)
.\" .Xr special 8
.\" for a more complete discussion of special files.
.Pp
.Nm

View File

@ -1,4 +1,4 @@
.\" $NetBSD: MAKEDEV.8,v 1.8 1997/11/20 06:17:45 fair Exp $
.\" $NetBSD: MAKEDEV.8,v 1.9 1998/04/28 04:07:08 fair Exp $
.\"
.\" Copyright (c) 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -50,7 +50,7 @@ found in the
directory, is used to create the common special
files.
.\"See
.\".Xr special (8)
.\".Xr special 8
.\"for a more complete discussion of special files.
.Pp
.Nm MAKEDEV
@ -163,4 +163,4 @@ The special file directory.
.Xr intro 4 ,
.Xr config 8 ,
.Xr mknod 8
.\".Xr special (8)
.\".Xr special 8

View File

@ -30,7 +30,7 @@
.\" SUCH DAMAGE.
.\"
.\" from: @(#)MAKEDEV.8 8.1 (Berkeley) 6/5/93
.\" $NetBSD: MAKEDEV.8,v 1.3 1997/11/20 06:17:49 fair Exp $
.\" $NetBSD: MAKEDEV.8,v 1.4 1998/04/28 04:07:08 fair Exp $
.\"
.Dd July 23, 1997
.Dt MAKEDEV 8 x68k
@ -49,7 +49,7 @@ found in the
directory, is used to create the common special
files.
.\"See
.\".Xr special (8)
.\".Xr special 8
.\"for a more complete discussion of special files.
.Pp
.Nm MAKEDEV
@ -153,4 +153,4 @@ The special file directory.
.Xr mknod 1 ,
.Xr intro 4 ,
.Xr config 8
.\".Xr special (8)
.\".Xr special 8

View File

@ -1,4 +1,4 @@
.\" $NetBSD: apply.1,v 1.6 1997/10/18 11:47:18 lukem Exp $
.\" $NetBSD: apply.1,v 1.7 1998/04/28 04:07:08 fair Exp $
.\"
.\" Copyright (c) 1983, 1990, 1993
.\" The Regents of the University of California. All rights reserved.
@ -102,11 +102,14 @@ If this variable is not defined, the Bourne shell is used.
.Sh EXAMPLES
.Bl -tag -width apply -compact
.It Li "apply echo a*"
is similar to ls(1);
is similar to
.Xr ls 1 ;
.It Li "apply \-2 cmp a1 b1 a2 b2 a3 b3"
compares the `a' files to the `b' files;
.It Li "apply \-0 who 1 2 3 4 5"
runs who(1) 5 times; and
runs
.Xr who 1
5 times; and
.It Li "apply \'ln %1 /usr/joe\'" *
links all files in the current directory to the directory
.Pa /usr/joe .

View File

@ -1,4 +1,4 @@
.\" $NetBSD: ldd.1,v 1.2 1995/10/08 23:39:58 pk Exp $
.\" $NetBSD: ldd.1,v 1.3 1998/04/28 04:07:05 fair Exp $
.\"
.\" Copyright (c) 1993 Paul Kranenburg
.\" All rights reserved.
@ -35,13 +35,15 @@
.Nm ldd
.Nd list dynamic object dependencies
.Sh SYNOPSIS
.Nm ldd
.Nm
.Op Fl f Ar format
.Ar program ...
.Sh DESCRIPTION
.Nm ldd
.Nm
displays all shared objects that are needed to run the given program.
Contrary to nm(1), the list includes
Contrary to
.Xr nm 1 ,
the list includes
.Dq indirect
depedencies that are the result of needed shared objects which themselves
depend on yet other shared objects.
@ -51,7 +53,8 @@ options may be given. The argument is a format string passed to
.Xr rtld 1
and allows customization of
.Nm ldd Ns 's
output. See
output.
See
.Xr rtld 1
for a list of recognised conversion characters.
.Sh SEE ALSO
@ -60,6 +63,7 @@ for a list of recognised conversion characters.
.Xr nm 1
.Sh HISTORY
A
.Nm ldd
.Nm
utility first appeared in SunOS 4.0, it appeared in its current form
in NetBSD 0.9a.
in
.Nx 0.9a .

View File

@ -1,4 +1,4 @@
.\" $NetBSD: ldd.1,v 1.2 1995/10/08 23:39:58 pk Exp $
.\" $NetBSD: ldd.1,v 1.3 1998/04/28 04:07:05 fair Exp $
.\"
.\" Copyright (c) 1993 Paul Kranenburg
.\" All rights reserved.
@ -35,13 +35,15 @@
.Nm ldd
.Nd list dynamic object dependencies
.Sh SYNOPSIS
.Nm ldd
.Nm
.Op Fl f Ar format
.Ar program ...
.Sh DESCRIPTION
.Nm ldd
.Nm
displays all shared objects that are needed to run the given program.
Contrary to nm(1), the list includes
Contrary to
.Xr nm 1 ,
the list includes
.Dq indirect
depedencies that are the result of needed shared objects which themselves
depend on yet other shared objects.
@ -51,7 +53,8 @@ options may be given. The argument is a format string passed to
.Xr rtld 1
and allows customization of
.Nm ldd Ns 's
output. See
output.
See
.Xr rtld 1
for a list of recognised conversion characters.
.Sh SEE ALSO
@ -60,6 +63,7 @@ for a list of recognised conversion characters.
.Xr nm 1
.Sh HISTORY
A
.Nm ldd
.Nm
utility first appeared in SunOS 4.0, it appeared in its current form
in NetBSD 0.9a.
in
.Nx 0.9a .

View File

@ -1,4 +1,4 @@
.\" $NetBSD: mountd.8,v 1.16 1998/02/06 06:20:53 perry Exp $
.\" $NetBSD: mountd.8,v 1.17 1998/04/28 04:07:08 fair Exp $
.\"
.\" Copyright (c) 1989, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -83,7 +83,9 @@ When
.Nm
is started,
it loads the export host addresses and options into the kernel
using the mount(2) system call.
using the
.Xr mount 2
system call.
After changing the exports file,
a hangup signal should be sent to the
.Nm