aboutsummaryrefslogtreecommitdiff
path: root/manual/resource.texi
diff options
context:
space:
mode:
authorAndreas Jaeger <aj@suse.de>2001-02-11 12:07:07 +0000
committerAndreas Jaeger <aj@suse.de>2001-02-11 12:07:07 +0000
commit5a7eedfbe62cfbf1485dda60b350d3fb4867fedd (patch)
tree8e34770d4ce2e5a37f9a7d46efc4f783355383fb /manual/resource.texi
parent27844eed6cae55f7dfdbf5480ad228c2519878b0 (diff)
downloadglibc-5a7eedfbe62cfbf1485dda60b350d3fb4867fedd.zip
glibc-5a7eedfbe62cfbf1485dda60b350d3fb4867fedd.tar.gz
glibc-5a7eedfbe62cfbf1485dda60b350d3fb4867fedd.tar.bz2
Use run_program_prefix.
Diffstat (limited to 'manual/resource.texi')
-rw-r--r--manual/resource.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/manual/resource.texi b/manual/resource.texi
index 3aa3f16..48e0ac0 100644
--- a/manual/resource.texi
+++ b/manual/resource.texi
@@ -1244,11 +1244,11 @@ nice (int increment)
The amount of memory available in the system and the way it is organized
determines oftentimes the way programs can and have to work. For
-functions like @code{mman} it is necessary to know about the size of
+functions like @code{mmap} it is necessary to know about the size of
individual memory pages and knowing how much memory is available enables
a program to select appropriate sizes for, say, caches. Before we get
into these details a few words about memory subsystems in traditional
-Unix systems.
+Unix systems will be given.
@menu
* Memory Subsystem:: Overview about traditional Unix memory handling.