From 84f6dbbaa36e030571e91ac81726346e4f963f02 Mon Sep 17 00:00:00 2001 From: Marc Fonvieille Date: Sun, 12 Jan 2003 21:25:57 +0000 Subject: [PATCH] Various typos fixing. These changes only concern the en_US version. Submitted by: Hiten Pandya --- .../books/handbook/linuxemu/chapter.sgml | 36 +++++++++---------- 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml index 6e05b5aa4e..c8bb5fd1ab 100644 --- a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml @@ -66,14 +66,14 @@ than they do under Linux. Linux - /proc filesystem + /proc file system 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 - /proc filesystem (which is different from - FreeBSD's /proc filesystem), or i386-specific + /proc file system (which is different from + FreeBSD's /proc file system), or i386-specific calls, such as enabling virtual 8086 mode. After reading this chapter, you will know: @@ -1317,7 +1317,7 @@ export PATH - Filesystem + File system Size (1k-blocks) Size (GB) Mounted on @@ -1452,7 +1452,7 @@ export PATH finally forced the installation of the PAM package, which worked. For SAP R/3 4.6C SR2 I directly forced the installation of the PAM-RPM, which also - works, so it seems the dependend packages are not needed: + works, so it seems the dependent packages are not needed: &prompt.root; rpm -i --ignoreos --nodeps --root /compat/linux --dbpath /var/lib/rpm \ @@ -1482,16 +1482,16 @@ pam-0.68-7.i386.rpm Creating the SAP/R3 Environment - Creating the Necessary Filesystems and Mountpoints + Creating the Necessary File Systems and Mountpoints For a simple installation, it is sufficient to create the - following filesystems: + following file systems: - mountpoint + mount point size in GB @@ -1546,7 +1546,7 @@ ERROR 2002-03-19 16:45:36 R3LINKS_IND_IND Ins_SetupLinks:0 Creating Users and Directories SAP R/3 needs two users and - three groups. The usernames depend on the + three groups. The user names depend on the SAP system id (SID) which consists of three letters. Some of these SIDs are reserved by SAP (for example @@ -1600,7 +1600,7 @@ ERROR 2002-03-19 16:45:36 R3LINKS_IND_IND Ins_SetupLinks:0 user id - username + user name generic name group additional groups @@ -1665,7 +1665,7 @@ Shell: bash (/compat/linux/bin/bash) Creating Directories 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: @@ -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 The minimum values are specified in the documentation that @@ -2454,7 +2454,7 @@ LICENSE KEY = license key, 24 charsCreate a user within client 000 (for some tasks required to be done within client 000, but with a user different from users sap* and - ddic). As a username, I usually choose + ddic). As a user name, I usually choose wartung (or service in English). Profiles required are sap_new and @@ -2530,8 +2530,8 @@ tape_address_rew = /dev/sa0 bad. cpio_flags 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 brbackup @@ -2540,7 +2540,7 @@ tape_address_rew = /dev/sa0 cpio_in_flags Flags needed for loading data back from tape. Format is recognized - automagically. + automatically. tape_size This usually gives the raw storage capability of the tape. For security reason (we use @@ -2662,7 +2662,7 @@ tape_address_rew = /dev/sa0 &prompt.root; ./R3SETUP -f CENTRDB.R3S for 4.6B, or with &prompt.root; ./R3SETUP -f CENTRAL.R3S - for 4.6C, no matter whether the error occured + for 4.6C, no matter whether the error occurred with CENTRAL.R3S or DATABASE.R3S. @@ -2819,7 +2819,7 @@ SVRMGR> exit <errorcode>ORA-27102</errorcode> (out of memory) - This error happend whilst trying to use values for + This error happened whilst trying to use values for MAXDSIZ and DFLDSIZ greater than 1 GB (1024x1024x1024). Additionally, I got Linux Error 12: Cannot allocate memory.