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

Various typos fixing. These changes only concern the en_US version.

Browse source 
Submitted by:	Hiten Pandya <hiten@unixdaemons.com>
This commit is contained in:
Marc Fonvieille 2003-01-12 21:25:57 +00:00
parent b71530e931
commit 84f6dbbaa3
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=15627
1 changed files with 18 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -1452,7 +1452,7 @@ export PATH</programlisting>
finally forced the installation of the PAM package, which
worked. For <application>SAP R/3 4.6C SR2</application> I
directly forced the installation of the PAM-RPM, which also
works, so it seems the dependend packages are not needed:</para>
works, so it seems the dependent packages are not needed:</para>
<screen>&prompt.root; <userinput>rpm -i --ignoreos --nodeps --root /compat/linux --dbpath /var/lib/rpm \
@ -1482,7 +1482,7 @@ pam-0.68-7.i386.rpm</userinput></screen>
<title>Creating the SAP/R3 Environment</title>
<sect3 id="filesystemsandmountpoints">
<title>Creating the Necessary Filesystems and Mountpoints</title>
<title>Creating the Necessary File Systems and Mountpoints</title>
<para>For a simple installation, it is sufficient to create the
following file systems:</para>
@ -1799,7 +1799,7 @@ options MSGTQL=2046 #max amount of msgs in system
options SYSVSEM #SYSV-style semaphores
options SEMMNU=256 #number of semaphore UNDO structures
options SEMMNS=1024 #number of semaphores in system
options SEMMNI=520 #number of semaphore indentifiers
options SEMMNI=520 #number of semaphore identifiers
options SEMUME=100 #number of UNDO keys</programlisting>
<para>The minimum values are specified in the documentation that
@ -2540,7 +2540,7 @@ tape_address_rew = /dev/sa0</programlisting>
<para><varname>cpio_in_flags</varname> Flags needed for
loading data back from tape. Format is recognized
automagically.</para>
automatically.</para>
<para><varname>tape_size</varname> This usually gives the raw
storage capability of the tape. For security reason (we use
@ -2662,7 +2662,7 @@ tape_address_rew = /dev/sa0</programlisting>
<screen>&prompt.root; <userinput>./R3SETUP -f CENTRDB.R3S</userinput></screen>
for 4.6B, or with
<screen>&prompt.root; <userinput>./R3SETUP -f CENTRAL.R3S</userinput></screen>
for 4.6C, no matter whether the error occured
for 4.6C, no matter whether the error occurred
with <filename>CENTRAL.R3S</filename> or
<filename>DATABASE.R3S</filename>.</para>
@ -2819,7 +2819,7 @@ SVRMGR&gt; <userinput>exit</userinput></screen>
<sect3 id="ora-27102">
<title><errorcode>ORA-27102</errorcode> (out of memory)</title>
<para>This error happend whilst trying to use values for
<para>This error happened whilst trying to use values for
<emphasis>MAXDSIZ</emphasis> and <emphasis>DFLDSIZ</emphasis>
greater than 1&nbsp;GB (1024x1024x1024). Additionally, I got
<errorname>Linux Error 12: Cannot allocate memory</errorname>.</para>