From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 15:03:30 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D70C5EF2; Thu, 24 Jan 2013 15:03:30 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id C707CD89; Thu, 24 Jan 2013 15:03:30 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0OF3UWA077014; Thu, 24 Jan 2013 15:03:30 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0OF3U5J077013; Thu, 24 Jan 2013 15:03:30 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301241503.r0OF3U5J077013@svn.freebsd.org> From: Dru Lavigne Date: Thu, 24 Jan 2013 15:03:30 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40735 - head/en_US.ISO8859-1/books/handbook/linuxemu X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 15:03:30 -0000 Author: dru Date: Thu Jan 24 15:03:30 2013 New Revision: 40735 URL: http://svnweb.freebsd.org/changeset/doc/40735 Log: White space fix only. Translators can ignore. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml Thu Jan 24 14:57:42 2013 (r40734) +++ head/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml Thu Jan 24 15:03:30 2013 (r40735) @@ -32,7 +32,9 @@ Synopsis - Linux binary compatibility + + Linux binary + compatibility binary compatibility Linux @@ -41,52 +43,57 @@ FreeBSD provides binary compatibility with several other &unix; like operating systems, including Linux. At this point, you may be asking yourself why exactly, does - FreeBSD need to be able to run Linux binaries? The answer to that - question is quite simple. Many companies and developers develop - only for Linux, since it is the latest hot thing in - the computing world. That leaves the rest of us FreeBSD users - bugging these same companies and developers to put out native - FreeBSD versions of their applications. The problem is, that most - of these companies do not really realize how many people would use - their product if there were FreeBSD versions too, and most continue - to only develop for Linux. So what is a FreeBSD user to do? This - is where the Linux binary compatibility of FreeBSD comes into - play. - - In a nutshell, the compatibility allows FreeBSD users to run - about 90% of all Linux applications without modification. This - includes applications such as &staroffice;, - the Linux version of &netscape;, + FreeBSD need to be able to run Linux binaries? The answer to + that question is quite simple. Many companies and developers + develop only for Linux, since it is the latest hot + thing in the computing world. That leaves the rest + of us FreeBSD users bugging these same companies and developers + to put out native FreeBSD versions of their applications. The + problem is, that most of these companies do not really realize + how many people would use their product if there were FreeBSD + versions too, and most continue to only develop for Linux. + So what is a FreeBSD user to do? This is where the Linux binary + compatibility of FreeBSD comes into play. + + In a nutshell, the compatibility allows FreeBSD users to + run about 90% of all Linux applications without modification. + This includes applications such as + &staroffice;, the Linux version of + &netscape;, &adobe; &acrobat;, &realplayer;, &oracle;, - &wordperfect;, Doom, + &wordperfect;, + Doom, Quake, and more. It is also reported - that in some situations, Linux binaries perform better on FreeBSD - than they do under Linux. + that in some situations, Linux binaries perform better on + FreeBSD than they do under Linux. 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 &i386; specific + features that are not supported under FreeBSD. Linux binaries + will not work on FreeBSD if they overly use &i386; specific calls, such as enabling virtual 8086 mode. After reading this chapter, you will know: - How to enable Linux binary compatibility on your system. + How to enable Linux binary compatibility on your + system. How to install additional Linux shared libraries. - + - How to install Linux applications on your FreeBSD system. + How to install Linux applications on your FreeBSD + system. - The implementation details of Linux compatibility in FreeBSD. + The implementation details of Linux compatibility in + FreeBSD. @@ -95,7 +102,7 @@ Know how to install additional third-party - software (). + software (). @@ -104,7 +111,8 @@ Installation - KLD (kernel loadable object) + KLD (kernel loadable + object) Linux binary compatibility is not turned on by default. The easiest way to enable this functionality is to load the @@ -127,19 +135,22 @@ Id Refs Address Size Name 1 2 0xc0100000 16bdb8 kernel 7 1 0xc24db000 d000 linux.ko + kernel options COMPAT_LINUX - If for some reason you do not want to or cannot load the KLD, - then you may statically link Linux binary compatibility into the kernel - by adding options COMPAT_LINUX to your kernel - configuration file. Then install your new kernel as described in + If for some reason you do not want to or cannot load the + KLD, then you may statically link Linux binary compatibility + into the kernel by adding options + COMPAT_LINUX to your kernel configuration file. + Then install your new kernel as described in . Installing Linux Runtime Libraries + Linux installing Linux libraries @@ -150,36 +161,38 @@ Id Refs Address Size Name by installing them manually. - - Installing Using the linux_base Port - Ports Collection - - This is by far the easiest method to use when installing the - runtime libraries. It is just like installing any other port - from the Ports Collection: + + Installing Using the linux_base Port - &prompt.root; cd /usr/ports/emulators/linux_base-f10 + Ports Collection + + This is by far the easiest method to use when installing + the runtime libraries. It is just like installing any other + port from the Ports + Collection: + + &prompt.root; cd /usr/ports/emulators/linux_base-f10 &prompt.root; make install distclean On &os; systems prior to &os; 8.0, you will have to use the emulators/linux_base-fc4 port + role="package">emulators/linux_base-fc4 port instead of emulators/linux_base-f10. + role="package">emulators/linux_base-f10. You should now have working Linux binary compatibility. - Some programs may complain about incorrect minor versions of the - system libraries. In general, however, this does not seem to be - a problem. + Some programs may complain about incorrect minor versions + of the system libraries. In general, however, this does + not seem to be a problem. There may be multiple versions of the emulators/linux_base port available, - corresponding to different versions of various Linux distributions. - You should install the port most closely resembling the - requirements of the Linux applications you would like to - install. + role="package">emulators/linux_base port + available, corresponding to different versions of various + Linux distributions. You should install the port most + closely resembling the requirements of the Linux + applications you would like to install. @@ -187,48 +200,52 @@ Id Refs Address Size Name Installing Libraries Manually If you do not have the ports collection - installed, you can install the libraries by hand instead. You - will need the Linux shared libraries that the program depends on - and the runtime linker. Also, you will need to create a - shadow root directory, - /compat/linux, for Linux libraries on your - FreeBSD system. Any shared libraries opened by Linux programs - run under FreeBSD will look in this tree first. So, if a Linux - program loads, for example, /lib/libc.so, - FreeBSD will first try to open - /compat/linux/lib/libc.so, and if that does - not exist, it will then try /lib/libc.so. - Shared libraries should be installed in the shadow tree + installed, you can install the libraries by hand instead. + You will need the Linux shared libraries that the program + depends on and the runtime linker. Also, you will need to + create a shadow root directory, + /compat/linux, for Linux libraries + on your FreeBSD system. Any shared libraries opened by + Linux programs run under FreeBSD will look in this tree + first. So, if a Linux program loads, for example, + /lib/libc.so, FreeBSD will first try + to open /compat/linux/lib/libc.so, + and if that does not exist, it will then try + /lib/libc.so. Shared libraries should + be installed in the shadow tree /compat/linux/lib rather than the paths that the Linux ld.so reports. - Generally, you will need to look for the shared libraries - that Linux binaries depend on only the first few times that you - install a Linux program on your FreeBSD system. After a while, - you will have a sufficient set of Linux shared libraries on your - system to be able to run newly imported Linux binaries without - any extra work. + Generally, you will need to look for the shared + libraries that Linux binaries depend on only the first few + times that you install a Linux program on your FreeBSD + system. After a while, you will have a sufficient set of + Linux shared libraries on your system to be able to run + newly imported Linux binaries without any extra work. How to Install Additional Shared Libraries + shared libraries - What if you install the linux_base port - and your application still complains about missing shared - libraries? How do you know which shared libraries Linux - binaries need, and where to get them? Basically, there are 2 - possibilities (when following these instructions you will need - to be root on your FreeBSD system). + What if you install the linux_base + port and your application still complains about missing + shared libraries? How do you know which shared libraries + Linux binaries need, and where to get them? Basically, + there are 2 possibilities (when following these instructions + you will need to be root on your + FreeBSD system). If you have access to a Linux system, see what shared - libraries the application needs, and copy them to your FreeBSD - system. Look at the following example: + libraries the application needs, and copy them to your + FreeBSD system. Look at the following example: - Let us assume you used FTP to get the Linux binary of - Doom, and put it on a Linux system you have access to. You - then can check which shared libraries it needs by running + Let us assume you used FTP to get the Linux binary + of Doom, and put it on a Linux + system you have access to. You then can check which + shared libraries it needs by running ldd linuxdoom, like so: &prompt.user; ldd linuxdoom @@ -237,10 +254,11 @@ libX11.so.3 (DLL Jump 3.1) => /usr/X1 libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 symbolic links - You would need to get all the files from the last column, - and put them under /compat/linux, with - the names in the first column as symbolic links pointing to - them. This means you eventually have these files on your + You would need to get all the files from the last + column, and put them under + /compat/linux, with the names in + the first column as symbolic links pointing to them. + This means you eventually have these files on your FreeBSD system: /compat/linux/usr/X11/lib/libXt.so.3.1.0 @@ -252,15 +270,16 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/
- Note that if you already have a Linux shared library - with a matching major revision number to the first column - of the ldd output, you will not 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, as long as you make - the symbolic link point to the new one. So, if you have - these libraries on your system: + Note that if you already have a Linux shared + library with a matching major revision number to the + first column of the ldd output, + you will not 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, as long as you make the symbolic + link point to the new one. So, if you have these + libraries on your system: /compat/linux/lib/libc.so.4.6.27 /compat/linux/lib/libc.so.4 -> libc.so.4.6.27 @@ -271,13 +290,13 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/ libc.so.4 (DLL Jump 4.5pl26) -> libc.so.4.6.29 - If it is only one or two versions out of date in the - trailing digit then do not worry about copying - /lib/libc.so.4.6.29 too, because the - program should work fine with the slightly older version. - However, if you like, you can decide to replace the - libc.so anyway, and that should leave - you with: + If it is only one or two versions out of date + in the trailing digit then do not worry about copying + /lib/libc.so.4.6.29 too, because + the program should work fine with the slightly older + version. However, if you like, you can decide to + replace the libc.so anyway, and + that should leave you with: /compat/linux/lib/libc.so.4.6.29 /compat/linux/lib/libc.so.4 -> libc.so.4.6.29 @@ -287,10 +306,10 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/
The symbolic link mechanism is - only needed for Linux binaries. The - FreeBSD runtime linker takes care of looking for matching - major revision numbers itself and you do not need to worry - about it. + only needed for Linux binaries. + The FreeBSD runtime linker takes care of looking for + matching major revision numbers itself and you do not + need to worry about it.
@@ -299,21 +318,23 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/ Installing Linux ELF Binaries + Linux ELF binaries ELF binaries sometimes require an extra step of - branding. If you attempt to run an unbranded ELF - binary, you will get an error message like the following: + branding. If you attempt to run an unbranded + ELF binary, you will get an error message like the + following: &prompt.user; ./my-linux-elf-binary ELF binary type not known Abort - To help the FreeBSD kernel distinguish between a FreeBSD ELF - binary and a Linux binary, use the &man.brandelf.1; + To help the FreeBSD kernel distinguish between a FreeBSD + ELF binary and a Linux binary, use the &man.brandelf.1; utility. &prompt.user; brandelf -t Linux my-linux-elf-binary @@ -327,19 +348,19 @@ Abort Installing a Random Linux RPM Based Application - FreeBSD has its own package database and it is used to track - all ports (&linux; ports as well). So the &linux; RPM database is not - used (not supported). + FreeBSD has its own package database and it is used to + track all ports (&linux; ports as well). So the &linux; RPM + database is not used (not supported). - However if you need to install a random &linux; RPM-based - application it can be achieved by: + However if you need to install a random &linux; + RPM-based application it can be achieved by: &prompt.root; cd /compat/linux &prompt.root; rpm2cpio -q < /path/to/linux.archive.rpm | cpio -id Then brandelf installed ELF binaries (not libraries!). - You will not be able to do a clean uninstall, but it may help you - to do tests. + You will not be able to do a clean uninstall, but it may + help you to do tests. @@ -357,14 +378,16 @@ Abort order hosts, bind multi on - The order here specifies that /etc/hosts - is searched first and DNS is searched second. When + The order here specifies that + /etc/hosts is searched first and DNS + is searched second. When /compat/linux/etc/host.conf is not installed, Linux applications find FreeBSD's /etc/host.conf and complain about the incompatible FreeBSD syntax. You should remove - bind if you have not configured a name server - using the /etc/resolv.conf file. + bind if you have not configured a name + server using the /etc/resolv.conf + file. @@ -389,7 +412,8 @@ multi on version of &mathematica; 5.X onto a FreeBSD system. - The Linux version of &mathematica; + The Linux version of + &mathematica; or &mathematica; for Students can be ordered directly from Wolfram at . @@ -433,9 +457,10 @@ multi on The shell scripts that &mathematica; created during - installation have to be modified before you can use them. If - you chose /usr/local/bin - as the directory to place the + installation have to be modified before you can use them. + If you chose /usr/local/bin as the directory + to place the &mathematica; executables in, you will find symlinks in this directory to files called math, mathematica, @@ -472,10 +497,10 @@ done &mathematica; on different machines. - When you register with Wolfram, either by email, phone or fax, - you will give them the machine ID and they will - respond with a corresponding password consisting of groups of - numbers. + When you register with Wolfram, either by email, phone + or fax, you will give them the machine ID and + they will respond with a corresponding password consisting + of groups of numbers. @@ -483,25 +508,27 @@ done &mathematica; uses some special fonts to display characters not - present in any of the standard font sets (integrals, sums, Greek - letters, etc.). The X protocol requires these fonts to be install - locally. This means you will have to copy - these fonts from the CDROM or from a host with - &mathematica; - installed to your local machine. These fonts are normally stored - in /cdrom/Unix/Files/SystemFiles/Fonts on the - CDROM, or - /usr/local/mathematica/SystemFiles/Fonts on - your hard drive. The actual fonts are in the subdirectories - Type1 and X. There are - several ways to use them, as described below. - - The first way is to copy them into one of the existing font - directories in /usr/X11R6/lib/X11/fonts. - This will require editing the fonts.dir file, - adding the font names to it, and changing the number of fonts on - the first line. Alternatively, you should also just be able to - run &man.mkfontdir.1; in the directory you have copied + present in any of the standard font sets (integrals, sums, + Greek letters, etc.). The X protocol requires these fonts + to be install locally. This means you + will have to copy these fonts from the CDROM or from a host + with &mathematica; installed to + your local machine. These fonts are normally stored in + /cdrom/Unix/Files/SystemFiles/Fonts on + the CDROM, or + /usr/local/mathematica/SystemFiles/Fonts + on your hard drive. The actual fonts are in the + subdirectories Type1 and + X. There are several ways to use them, + as described below. + + The first way is to copy them into one of the existing + font directories in + /usr/X11R6/lib/X11/fonts. This will + require editing the fonts.dir file, + adding the font names to it, and changing the number of fonts + on the first line. Alternatively, you should also just be + able to run &man.mkfontdir.1; in the directory you have copied them to. The second way to do this is to copy the directories to @@ -524,14 +551,16 @@ done &prompt.root; xset fp+ /usr/X11R6/lib/X11/fonts/MathType1 &prompt.root; xset fp rehash - If you are using the &xorg; server, you can have these font - directories loaded automatically by adding them to your + If you are using the &xorg; + server, you can have these font directories loaded + automatically by adding them to your xorg.conf file. fonts - If you do not already have a directory - called /usr/X11R6/lib/X11/fonts/Type1, you + If you do not already have a + directory called + /usr/X11R6/lib/X11/fonts/Type1, you can change the name of the MathType1 directory in the example above to Type1. @@ -564,36 +593,40 @@ done Maple - &maple; is a commercial mathematics program similar to - &mathematica;. You must purchase this software from and then register there - for a license file. To install this software on FreeBSD, please - follow these simple steps. - - - Execute the INSTALL shell - script from the product distribution. Choose the - RedHat option when prompted by the - installation program. A typical installation directory - might be &maple; is a commercial + mathematics program similar to + &mathematica;. You must purchase + this software from and then register + there for a license file. To install this software on FreeBSD, + please follow these simple steps. + + + Execute the INSTALL shell + script from the product distribution. Choose the + RedHat option when prompted by the + installation program. A typical installation directory + might be /usr/local/maple. - If you have not done so, order a license for &maple; - from Maple Waterloo Software () - and copy it to + If you have not done so, order a license for + &maple; from Maple Waterloo + Software () and copy it + to /usr/local/maple/license/license.dat. - Install the FLEXlm + Install the FLEXlm license manager by running the INSTALL_LIC install shell script that comes with &maple;. Specify the primary hostname for your machine for the license server. - Patch the - /usr/local/maple/bin/maple.system.type - file with the following: - ----- snip ------------------ + Patch the + /usr/local/maple/bin/maple.system.type + file with the following: + ----- snip ------------------ *** maple.system.type.orig Sun Jul 8 16:35:33 2001 --- maple.system.type Sun Jul 8 16:35:51 2001 *************** @@ -608,18 +641,19 @@ done # We have two Linux implementations, one for Red Hat and ----- snip end of patch ----- - Please note that after the "FreeBSD"|\ no other - whitespace should be present. - - This patch instructs &maple; to - recognize FreeBSD as a type of Linux system. - The bin/maple shell script calls the - bin/maple.system.type shell script - which in turn calls uname -a to find out the operating - system name. Depending on the OS name it will find out which - binaries to use. + Please note that after the + "FreeBSD"|\ no other whitespace should + be present. + + This patch instructs &maple; + to recognize FreeBSD as a type of Linux + system. The bin/maple shell script + calls the bin/maple.system.type shell + script which in turn calls uname -a to + find out the operating system name. Depending on the OS + name it will find out which binaries to use. - Start the license server. + Start the license server. The following script, installed as /usr/local/etc/rc.d/lmgrd.sh is a @@ -653,29 +687,34 @@ exit 0 ----- snip ------------ - Test-start &maple;: - &prompt.user; cd /usr/local/maple/bin + Test-start + &maple;: + + &prompt.user; cd /usr/local/maple/bin &prompt.user; ./xmaple - You should be up and running. Make sure to write + You should be up and running. Make sure to write Maplesoft to let them know you would like a native FreeBSD version! - + - - Common Pitfalls + + Common Pitfalls - - The FLEXlm license manager can be a difficult - tool to work with. Additional documentation on the subject - can be found at . - - lmgrd is known to be very picky - about the license file and to core dump if there are any - problems. A correct license file should look like this: + + The FLEXlm + license manager can be a difficult tool to work with. + Additional documentation on the subject can be found at + . + + lmgrd is known to be very + picky about the license file and to core dump if there + are any problems. A correct license file should look + like this: -# ======================================================= + # +======================================================= # License File for UNIX Installations ("Pointer File") # ======================================================= SERVER chillig ANY @@ -687,27 +726,27 @@ FEATURE Maple maplelmg 2000.0831 permane ISSUED=11-may-2000 NOTICE=" Technische Universitat Wien" \ SN=XXXXXXXXX - Serial number and key 'X''ed out. chillig is a - hostname. - - Editing the license file works as long as you do not - touch the FEATURE line (which is protected by the - license key). - - - + Serial number and key 'X''ed out. + chillig is a hostname. - - - - - Dan - Pelleg - Contributed by - + Editing the license file works as long as you do not + touch the FEATURE line (which is protected + by the license key). + + + + + + + + + Dan + Pelleg + Contributed by + - - + + Installing &matlab; @@ -721,11 +760,11 @@ FEATURE Maple maplelmg 2000.0831 permane &java.virtual.machine; (see ). - The Linux version of &matlab; can be - ordered directly from The MathWorks at . Make sure you also get - the license file or instructions how to create it. While you - are there, let them know you would like a native &os; + The Linux version of &matlab; + can be ordered directly from The MathWorks at . Make sure you also + get the license file or instructions how to create it. While + you are there, let them know you would like a native &os; version of their software. @@ -746,28 +785,31 @@ FEATURE Maple maplelmg 2000.0831 permane The installer is graphical. If you get errors about not being able to open a display, type - setenv HOME ~USER, - where USER is the user you did a - &man.su.1; as. + setenv HOME + ~USER, + where USER is the user you + did a &man.su.1; as. - When asked for the &matlab; root - directory, type: + When asked for the &matlab; + root directory, type: /compat/linux/usr/local/matlab. For easier typing on the rest of the installation process, type this at your shell prompt: - set MATLAB=/compat/linux/usr/local/matlab + set + MATLAB=/compat/linux/usr/local/matlab Edit the license file as instructed when - obtaining the &matlab; license. + obtaining the &matlab; + license. You can prepare this file in advance using your @@ -789,9 +831,11 @@ FEATURE Maple maplelmg 2000.0831 permane License Manager Startup + - Create symlinks for the license manager scripts: + Create symlinks for the license manager + scripts: &prompt.root; ln -s $MATLAB/etc/lmboot /usr/local/etc/lmboot_TMW &prompt.root; ln -s $MATLAB/etc/lmdown /usr/local/etc/lmdown_TMW @@ -801,9 +845,9 @@ FEATURE Maple maplelmg 2000.0831 permane Create a startup file at /usr/local/etc/rc.d/flexlm.sh. The example below is a modified version of the distributed - $MATLAB/etc/rc.lm.glnx86. The changes - are file locations, and startup of the license manager - under Linux emulation. + $MATLAB/etc/rc.lm.glnx86. The + changes are file locations, and startup of the license + manager under Linux emulation. #!/bin/sh case "$1" in @@ -861,8 +905,7 @@ exit 0 Place the following startup script in - /usr/local/bin/matlab: - + /usr/local/bin/matlab: #!/bin/sh /compat/linux/bin/sh /compat/linux/usr/local/matlab/bin/matlab "$@" @@ -876,9 +919,9 @@ exit 0 Depending on your version of - emulators/linux_base, you - may run into errors when running this script. To avoid that, - edit the file + emulators/linux_base, + you may run into errors when running this script. To avoid + that, edit the file /compat/linux/usr/local/matlab/bin/matlab, and change the line that says: @@ -915,14 +958,14 @@ exit 0 your workspace before quitting. If you use either of them, insert the line above immediately after the save command. - + - - Create a file - $MATLAB/bin/finish.sh, which will - contain the following: + + Create a file + $MATLAB/bin/finish.sh, which will + contain the following: - #!/compat/linux/bin/sh + #!/compat/linux/bin/sh (sleep 5; killall -1 matlab_helper) & exit 0 @@ -963,49 +1006,61 @@ exit 0 Preface - This document describes the process of installing &oracle; 8.0.5 and - &oracle; 8.0.5.1 Enterprise Edition for Linux onto a FreeBSD - machine. + + This document describes the process of installing + &oracle; 8.0.5 and + &oracle; 8.0.5.1 Enterprise Edition + for Linux onto a FreeBSD machine. Installing the Linux Environment - Make sure you have both emulators/linux_base and - devel/linux_devtools from the Ports Collection - installed. If you run into difficulties with these ports, - you may have to use - the packages or older versions available in the Ports Collection. + Make sure you have both emulators/linux_base and + devel/linux_devtools + from the Ports Collection installed. If you run into + difficulties with these ports, you may have to use the + packages or older versions available in the Ports + Collection. If you want to run the intelligent agent, you will also need to install the Red Hat Tcl package: - tcl-8.0.3-20.i386.rpm. The general command - for installing packages with the official RPM port (archivers/rpm) is: + tcl-8.0.3-20.i386.rpm. The general + command for installing packages with the official + RPM port (archivers/rpm) is: &prompt.root; rpm -i --ignoreos --root /compat/linux --dbpath /var/lib/rpm package - Installation of the package should not generate any errors. + Installation of the package + should not generate any errors. Creating the &oracle; Environment - Before you can install &oracle;, you need to set up a proper - environment. This document only describes what to do - specially to run &oracle; for Linux on FreeBSD, not - what has been described in the &oracle; installation guide. + Before you can install + &oracle;, you need to set up a + proper environment. This document only describes what to do + specially to run + &oracle; for Linux on FreeBSD, not + what has been described in the + &oracle; installation guide. - Kernel Tuning + Kernel Tuning + kernel tuning - As described in the &oracle; installation guide, you need to set - the maximum size of shared memory. Do not use - SHMMAX under FreeBSD. SHMMAX - is merely calculated out of SHMMAXPGS and + As described in the &oracle; + installation guide, you need to set the maximum size of + shared memory. Do not use SHMMAX under + FreeBSD. SHMMAX is merely calculated + out of SHMMAXPGS and PGSIZE. Therefore define - SHMMAXPGS. All other options can be used as - described in the guide. For example: + SHMMAXPGS. All other options can be + used as described in the guide. For example: options SHMMAXPGS=10000 options SHMMNI=100 @@ -1014,38 +1069,43 @@ options SEMMNS=200 options SEMMNI=70 options SEMMSL=61 - Set these options to suit your intended use of &oracle;. + Set these options to suit your intended use of + &oracle;. - Also, make sure you have the following options in your kernel - configuration file: + Also, make sure you have the following options in your + kernel configuration file: -options SYSVSHM #SysV shared memory + options SYSVSHM #SysV shared memory options SYSVSEM #SysV semaphores options SYSVMSG #SysV interprocess communication - &oracle; Account + &oracle; Account - Create an oracle account just as you would create any other - account. The oracle account is special only that you need to give - it a Linux shell. Add /compat/linux/bin/bash to - /etc/shells and set the shell for the oracle - account to /compat/linux/bin/bash. + Create an oracle account just as + you would create any other account. The + oracle account is special only that + you need to give it a Linux shell. Add + /compat/linux/bin/bash to + /etc/shells and set the shell for + the oracle account to + /compat/linux/bin/bash. - Environment + Environment - Besides the normal &oracle; variables, such as - ORACLE_HOME and ORACLE_SID you must - set the following environment variables: + Besides the normal &oracle; + variables, such as ORACLE_HOME and + ORACLE_SID you must set the following + environment variables: - - + + *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***