Various typos fixing. These changes only concern the en_US version.
Submitted by: Hiten Pandya <hiten@unixdaemons.com>
This commit is contained in:
Marc Fonvieille
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
|
|
@ -66,14 +66,14 @@
|
|||
than they do under Linux.</para>
|
||||
<indexterm>
|
||||
<primary>Linux</primary>
|
||||
<secondary><filename>/proc</filename> filesystem</secondary>
|
||||
<secondary><filename>/proc</filename> file system</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>There are, however, some Linux-specific operating system
|
||||
features that are not supported under FreeBSD. Linux binaries will
|
||||
not work on FreeBSD if they overly use the Linux
|
||||
<filename>/proc</filename> filesystem (which is different from
|
||||
FreeBSD's <filename>/proc</filename> filesystem), or i386-specific
|
||||
<filename>/proc</filename> file system (which is different from
|
||||
FreeBSD's <filename>/proc</filename> file system), or i386-specific
|
||||
calls, such as enabling virtual 8086 mode.</para>
|
||||
|
||||
<para>After reading this chapter, you will know:</para>
|
||||
|
|
@ -1317,7 +1317,7 @@ export PATH</programlisting>
|
|||
<tgroup cols="4">
|
||||
<thead>
|
||||
<row>
|
||||
<entry>Filesystem</entry>
|
||||
<entry>File system</entry>
|
||||
<entry>Size (1k-blocks)</entry>
|
||||
<entry>Size (GB)</entry>
|
||||
<entry>Mounted on</entry>
|
||||
|
|
@ -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,16 +1482,16 @@ 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 filesystems:</para>
|
||||
following file systems:</para>
|
||||
|
||||
<informaltable>
|
||||
<tgroup cols="2">
|
||||
<thead>
|
||||
<row>
|
||||
<entry>mountpoint</entry>
|
||||
<entry>mount point</entry>
|
||||
<entry>size in GB</entry>
|
||||
</row>
|
||||
</thead>
|
||||
|
|
@ -1546,7 +1546,7 @@ ERROR 2002-03-19 16:45:36 R3LINKS_IND_IND Ins_SetupLinks:0
|
|||
<title>Creating Users and Directories</title>
|
||||
|
||||
<para><application>SAP R/3</application> needs two users and
|
||||
three groups. The usernames depend on the
|
||||
three groups. The user names depend on the
|
||||
<application>SAP</application> system id (SID) which consists
|
||||
of three letters. Some of these SIDs are reserved
|
||||
by <application>SAP</application> (for example
|
||||
|
|
@ -1600,7 +1600,7 @@ ERROR 2002-03-19 16:45:36 R3LINKS_IND_IND Ins_SetupLinks:0
|
|||
<thead>
|
||||
<row>
|
||||
<entry>user id</entry>
|
||||
<entry>username</entry>
|
||||
<entry>user name</entry>
|
||||
<entry>generic name</entry>
|
||||
<entry>group</entry>
|
||||
<entry>additional groups</entry>
|
||||
|
|
@ -1665,7 +1665,7 @@ Shell: bash (/compat/linux/bin/bash)</programlisting>
|
|||
<title>Creating Directories</title>
|
||||
|
||||
<para>These directories are usually created as separate
|
||||
filesystems. This depends entirely on your requirements. I
|
||||
file systems. This depends entirely on your requirements. I
|
||||
choose to create them as simple directories, as they are all
|
||||
located on the same RAID 5 anyway:</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
|
||||
|
|
@ -2454,7 +2454,7 @@ LICENSE KEY = <replaceable>license key, 24 chars</replaceable></programlisti
|
|||
<para>Create a user within client 000 (for some tasks required
|
||||
to be done within client 000, but with a user different from
|
||||
users <username>sap*</username> and
|
||||
<username>ddic</username>). As a username, I usually choose
|
||||
<username>ddic</username>). As a user name, I usually choose
|
||||
<replaceable>wartung</replaceable> (or
|
||||
<replaceable>service</replaceable> in English). Profiles
|
||||
required are <emphasis>sap_new</emphasis> and
|
||||
|
|
@ -2530,8 +2530,8 @@ tape_address_rew = /dev/sa0</programlisting>
|
|||
bad.</para>
|
||||
|
||||
<para><varname>cpio_flags</varname> Default is to use -B which
|
||||
sets blocksize to 5120 Bytes. For DLT-Tapes, HP recommends at
|
||||
least 32 K blocksize, so I used --block-size=128 for
|
||||
sets block size to 5120 Bytes. For DLT-Tapes, HP recommends at
|
||||
least 32 K block size, so I used --block-size=128 for
|
||||
64 K. --format=newc is needed I have inode numbers greater than
|
||||
65535. The last option --quiet is needed as otherwise
|
||||
<command>brbackup</command>
|
||||
|
|
@ -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> <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 GB (1024x1024x1024). Additionally, I got
|
||||
<errorname>Linux Error 12: Cannot allocate memory</errorname>.</para>
|
||||
|
|
|
|||
Loading…
Reference in a new issue