*.sgml:
- Use trademark entities - Add trademark attributions. - Always use correct case for trademarks. - Don't join trademarks with other words, e.g. using hyphens. trademark.ent: - Add entities for more trademarks / companies. - Sort the Sun trademark attribution entity.
This commit is contained in:
Simon L. B. Nielsen
parent
ada8f32521
commit
2993ccd69a
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=18123
7 changed files with 158 additions and 82 deletions
|
|
@ -6,6 +6,8 @@
|
|||
%man;
|
||||
<!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
|
||||
%freebsd;
|
||||
<!ENTITY % trademarks PUBLIC "-//FreeBSD//ENTITIES DocBook Trademark Entities//EN">
|
||||
%trademarks;
|
||||
]>
|
||||
|
||||
<article>
|
||||
|
|
@ -21,6 +23,16 @@
|
|||
</affiliation>
|
||||
</author>
|
||||
|
||||
<legalnotice id="trademarks" role="trademarks">
|
||||
&tm-attrib.freebsd;
|
||||
&tm-attrib.apple;
|
||||
&tm-attrib.linux;
|
||||
&tm-attrib.opengroup;
|
||||
&tm-attrib.sun;
|
||||
&tm-attrib.xfree86;
|
||||
&tm-attrib.general;
|
||||
</legalnotice>
|
||||
|
||||
<abstract>
|
||||
<para>In the open source world, the word <quote>Linux</quote> is almost
|
||||
synonymous with <quote>Operating System</quote>, but it is not the only
|
||||
|
|
@ -28,7 +40,7 @@
|
|||
to the <ulink
|
||||
url="http://www.leb.net/hzo/ioscount/data/r.9904.txt">Internet
|
||||
Operating System Counter</ulink>, as of April 1999 31.3% of the
|
||||
world's network connected machines run Linux. 14.6% run BSD UNIX.
|
||||
world's network connected machines run Linux. 14.6% run BSD &unix;.
|
||||
Some of the world's largest web operations, such as <ulink
|
||||
url="http://www.yahoo.com/">Yahoo!</ulink>, run BSD. The world's
|
||||
busiest FTP server, <ulink
|
||||
|
|
@ -86,7 +98,7 @@
|
|||
|
||||
<para>The X Window system used in most versions of BSD is maintained
|
||||
by a separate project, the
|
||||
<ulink url="http://www.XFree86.org/">XFree86 project</ulink>.
|
||||
<ulink url="http://www.XFree86.org/">&xfree86; project</ulink>.
|
||||
This is the same code as Linux uses. BSD does not normally
|
||||
specify a <quote>graphical desktop</quote> such as GNOME or KDE,
|
||||
though these are available.</para>
|
||||
|
|
@ -99,16 +111,16 @@
|
|||
</sect1>
|
||||
|
||||
<sect1>
|
||||
<title>What, a real UNIX?</title>
|
||||
<title>What, a real &unix;?</title>
|
||||
|
||||
<para>The BSD operating systems are not clones, but open source
|
||||
derivatives of AT&T's Research UNIX operating system, which is also
|
||||
the ancestor of the modern UNIX System V. This may surprise you. How
|
||||
derivatives of AT&T's Research &unix; operating system, which is also
|
||||
the ancestor of the modern &unix; System V. This may surprise you. How
|
||||
could that happen when AT&T has never released its code as open
|
||||
source?</para>
|
||||
|
||||
<para>It is true that AT&T UNIX is not open source, and in a copyright
|
||||
sense BSD is very definitely <emphasis>not</emphasis> UNIX, but on the
|
||||
<para>It is true that AT&T &unix; is not open source, and in a copyright
|
||||
sense BSD is very definitely <emphasis>not</emphasis> &unix;, but on the
|
||||
other hand, AT&T has imported sources from other projects,
|
||||
noticeably the Computer Sciences Research Group of the University of
|
||||
California in Berkeley, CA. Starting in 1976, the CSRG started
|
||||
|
|
@ -125,10 +137,10 @@
|
|||
1982.</para>
|
||||
|
||||
<para>In the course of the 1980s, a number of new workstation companies
|
||||
sprang up. Many preferred to license UNIX rather than developing
|
||||
sprang up. Many preferred to license &unix; rather than developing
|
||||
operating systems for themselves. In particular, Sun Microsystems
|
||||
licensed UNIX and implemented a version of 4.2BSD, which they called
|
||||
SunOS. When AT&T themselves were allowed to sell UNIX commercially,
|
||||
licensed &unix; and implemented a version of 4.2BSD, which they called
|
||||
&sunos;. When AT&T themselves were allowed to sell &unix; commercially,
|
||||
they started with a somewhat bare-bones implementation called System
|
||||
III, to be quickly followed by System V. The System V code base did not
|
||||
include networking, so all implementations included additional software
|
||||
|
|
@ -138,7 +150,7 @@
|
|||
<emphasis>Berkeley Extensions</emphasis>.</para>
|
||||
|
||||
<para>The BSD tapes contained AT&T source code and thus required a
|
||||
UNIX source license. By 1990, the CSRG's funding was running out, and
|
||||
&unix; source license. By 1990, the CSRG's funding was running out, and
|
||||
it faced closure. Some members of the group decided to release the BSD
|
||||
code, which was Open Source, without the AT&T proprietary code.
|
||||
This finally happened with the <emphasis>Networking Tape 2</emphasis>,
|
||||
|
|
@ -201,10 +213,10 @@
|
|||
that the court case had been <quote>recently settled</quote>.</para>
|
||||
|
||||
<para>One detail that the lawsuit did clarify is the naming: in the
|
||||
1980s, BSD was known as <quote>BSD UNIX</quote>. With the
|
||||
1980s, BSD was known as <quote>BSD &unix;</quote>. With the
|
||||
elimination of the last vestige of AT&T code from BSD, it
|
||||
also lost the right to the name UNIX. Thus you will see
|
||||
references in book titles to <quote>the 4.3BSD UNIX operating
|
||||
also lost the right to the name &unix;. Thus you will see
|
||||
references in book titles to <quote>the 4.3BSD &unix; operating
|
||||
system</quote> and <quote>the 4.4BSD operating
|
||||
system</quote>.</para>
|
||||
</listitem>
|
||||
|
|
@ -225,7 +237,7 @@
|
|||
|
||||
<para>So what is really the difference between, say, Debian Linux and
|
||||
FreeBSD? For the average user, the difference is surprisingly small:
|
||||
Both are UNIX-like operating systems. Both are developed by
|
||||
Both are &unix; like operating systems. Both are developed by
|
||||
non-commercial projects (this does not apply to many other Linux
|
||||
distributions, of course). In the following section, we will look at BSD
|
||||
and compare it to Linux. The description applies most closely to
|
||||
|
|
@ -425,8 +437,8 @@
|
|||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>There are also two additional BSD operating systems which are not
|
||||
open source, BSD/OS and Apple's Mac OS X:</para>
|
||||
<para>There are also two additional BSD &unix; operating systems which are not
|
||||
open source, BSD/OS and Apple's &macos; X:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
|
@ -436,16 +448,16 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink url="http://www.apple.com/macosx/server/">Mac OS
|
||||
<para><ulink url="http://www.apple.com/macosx/server/">&macos;
|
||||
X</ulink> is the latest version of the operating system for
|
||||
<ulink url="http://www.apple.com/">Apple Computer Inc.'s</ulink>
|
||||
Macintosh line. The BSD Unix core of this operating
|
||||
&macintosh; line. The BSD core of this operating
|
||||
system, <ulink
|
||||
url="http://developer.apple.com/darwin/">Darwin</ulink>,
|
||||
is available as a fully functional open source operating
|
||||
system for x86 and PPC computers. The Aqua/Quartz
|
||||
graphics system and many other proprietary aspects of
|
||||
Mac OS X remain closed-source, however. Several Darwin
|
||||
&macos; X remain closed-source, however. Several Darwin
|
||||
developers are also FreeBSD committers, and
|
||||
vice-versa.</para>
|
||||
</listitem>
|
||||
|
|
|
|||
|
|
@ -5,6 +5,8 @@
|
|||
%mailing-lists;
|
||||
<!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
|
||||
%freebsd;
|
||||
<!ENTITY % trademarks PUBLIC "-//FreeBSD//ENTITIES DocBook Trademark Entities//EN">
|
||||
%trademarks;
|
||||
]>
|
||||
|
||||
<article>
|
||||
|
|
@ -23,6 +25,15 @@
|
|||
|
||||
<pubdate>$FreeBSD$</pubdate>
|
||||
|
||||
<legalnotice id="trademarks" role="trademarks">
|
||||
&tm-attrib.freebsd;
|
||||
&tm-attrib.microsoft;
|
||||
&tm-attrib.netscape;
|
||||
&tm-attrib.opengroup;
|
||||
&tm-attrib.qualcomm;
|
||||
&tm-attrib.general;
|
||||
</legalnotice>
|
||||
|
||||
<abstract>
|
||||
<para>This document provides useful information for people looking to
|
||||
prepare an e-mail to the FreeBSD-questions mailing list. Advice and
|
||||
|
|
@ -299,7 +310,7 @@ you consider the question to be pretty technical.</literallayout>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Eudora</para>
|
||||
<para>&eudora;</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -307,24 +318,24 @@ you consider the question to be pretty technical.</literallayout>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Microsoft Exchange</para>
|
||||
<para>µsoft; Exchange</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Microsoft Internet Mail</para>
|
||||
<para>µsoft; Internet Mail</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Microsoft Outlook</para>
|
||||
<para>µsoft; &outlook;</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Netscape</para>
|
||||
<para>&netscape;</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>As you can see, the mailers in the Microsoft world are frequent
|
||||
offenders. If at all possible, use a UNIX mailer. If you must use a
|
||||
offenders. If at all possible, use a &unix; mailer. If you must use a
|
||||
mailer under Microsoft environments, make sure it is set up
|
||||
correctly. Try not to use <acronym>MIME</acronym>: a lot of people
|
||||
use mailers which do not get on very well with
|
||||
|
|
|
|||
|
|
@ -7,6 +7,9 @@
|
|||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
|
||||
%man;
|
||||
|
||||
<!ENTITY % trademarks PUBLIC "-//FreeBSD//ENTITIES DocBook Trademark Entities//EN">
|
||||
%trademarks;
|
||||
]>
|
||||
|
||||
<article>
|
||||
|
|
@ -24,6 +27,12 @@
|
|||
|
||||
<pubdate>3 May 1999</pubdate>
|
||||
|
||||
<legalnotice id="trademarks" role="trademarks">
|
||||
&tm-attrib.freebsd;
|
||||
&tm-attrib.opengroup;
|
||||
&tm-attrib.general;
|
||||
</legalnotice>
|
||||
|
||||
<abstract>
|
||||
<para>You installed IPsec and it seems to be working. How do you
|
||||
know? I describe a method for experimentally verifying that IPsec is
|
||||
|
|
@ -115,7 +124,7 @@
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<para>In the <quote>secure</quote> window, run the Unix
|
||||
<para>In the <quote>secure</quote> window, run the &unix;
|
||||
command &man.yes.1;, which will stream the <literal>y</literal>
|
||||
character. After a while, stop this. Switch to the
|
||||
insecure window, and repeat. After a while, stop.</para>
|
||||
|
|
|
|||
|
|
@ -36,6 +36,9 @@
|
|||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
|
||||
|
||||
<!ENTITY % trademarks PUBLIC "-//FreeBSD//ENTITIES DocBook Trademark Entities//EN">
|
||||
%trademarks;
|
||||
|
||||
<!--
|
||||
URL Entities. These are in place, to allow wrapping long URLs to the 80th
|
||||
column.
|
||||
|
|
@ -54,7 +57,7 @@
|
|||
|
||||
<!-- START of Article Metadata -->
|
||||
<articleinfo>
|
||||
<title>Java and Jakarta Tomcat on FreeBSD</title>
|
||||
<title>&java; and Jakarta Tomcat on FreeBSD</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
|
|
@ -82,13 +85,21 @@
|
|||
|
||||
<pubdate>$FreeBSD$</pubdate>
|
||||
|
||||
<legalnotice id="trademarks" role="trademarks">
|
||||
&tm-attrib.freebsd;
|
||||
&tm-attrib.linux;
|
||||
&tm-attrib.microsoft;
|
||||
&tm-attrib.sun;
|
||||
&tm-attrib.general;
|
||||
</legalnotice>
|
||||
|
||||
<abstract>
|
||||
<para>This document is presented in hopes of making it easier for
|
||||
anyone that needs to get Java up and running on FreeBSD, with the
|
||||
anyone that needs to get &java; up and running on FreeBSD, with the
|
||||
least amount of aggravation. Plan on spending a whole day on such
|
||||
a project as it will take time to assemble all the pieces and
|
||||
compile them individually, and then as a whole. It also shows how
|
||||
to install the famous Jakarta Tomcat Servlet and JSP container on
|
||||
to install the famous Jakarta Tomcat Servlet and &jsp; container on
|
||||
the FreeBSD operating system.</para>
|
||||
</abstract>
|
||||
</articleinfo>
|
||||
|
|
@ -97,18 +108,18 @@
|
|||
<sect1>
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>The Java programming language was birthed on <literal>May 23rd
|
||||
1995</literal>. One would expect that after all this time, Java
|
||||
<para>The &java; programming language was birthed on <literal>May 23rd
|
||||
1995</literal>. One would expect that after all this time, &java;
|
||||
applications would be easy to install and ready to run from a single
|
||||
package, or port on FreeBSD, thus making it available for the
|
||||
<quote>masses</quote>. This is not the case, unfortunately, as
|
||||
the Java distribution is held very closely by Sun Microsystems,
|
||||
and prohibits re-distribution. All Java Applets must be compiled
|
||||
from source code, together with the Java Development Kit from Sun
|
||||
the &java; distribution is held very closely by Sun Microsystems,
|
||||
and prohibits re-distribution. All &java; Applets must be compiled
|
||||
from source code, together with the &java; Development Kit from Sun
|
||||
Microsystems. All these ingredients must be blended together in
|
||||
the right order, assembled, and compiled by the end user. With
|
||||
such distribution philosophies at heart, it is my opinion that
|
||||
Java will always be developer or hacker use only. I certainly
|
||||
&java; will always be developer or hacker use only. I certainly
|
||||
found this to be true when I needed to serve up some
|
||||
<filename>.jsp</filename> pages for a client on my web server,
|
||||
and needed to get <filename
|
||||
|
|
@ -117,23 +128,23 @@
|
|||
system.</para>
|
||||
|
||||
<para>The Tomcat portion of the install is very straight forward, but
|
||||
the difficulty I had was getting Java Development Kit up and
|
||||
the difficulty I had was getting &java; Development Kit up and
|
||||
running for FreeBSD 4.X, as Sun Microsystems only supplies
|
||||
Binaries for Linux, Solaris, and Windows NT. This means that I
|
||||
had to compile my own JDK for FreeBSD. I began by searching for
|
||||
Binaries for Linux, &solaris;, and &windowsnt;. This means that I
|
||||
had to compile my own &jdk; for FreeBSD. I began by searching for
|
||||
documentation on the Internet. I quickly found that there is more
|
||||
source code than I need along with patches to the source code, but
|
||||
very little documentation of what to do after obtaining
|
||||
everything.</para>
|
||||
|
||||
<para>In this article, you will find how to install the Java
|
||||
<para>In this article, you will find how to install the &java;
|
||||
Development Kit for FreeBSD, and how to get up and running with
|
||||
Tomcat. A <xref linkend="ref"> section is also provided for
|
||||
further reading.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1>
|
||||
<title>The Java Environment</title>
|
||||
<title>The &java; Environment</title>
|
||||
|
||||
<para>Ensure that you have the current ports collection as
|
||||
<command>make</command> it will fail if it attempts to build older
|
||||
|
|
@ -241,7 +252,7 @@
|
|||
<note>
|
||||
<para>It is very important for you to read the License Agreement
|
||||
which has been issued by Sun Microsystems Corp. There are
|
||||
several restrictions in place on the use of Java, which you must
|
||||
several restrictions in place on the use of &java;, which you must
|
||||
address. The FreeBSD Project does not take any responsibilities
|
||||
for your actions.</para>
|
||||
|
||||
|
|
@ -314,7 +325,7 @@ MD5 (bsd-jdk131-patches-6.tar.gz) = 9cade10b81d6034fdd2176bef32bdbf9</programlis
|
|||
</procedure>
|
||||
|
||||
<para>The last procedure discussed above (building the native
|
||||
<literal>jdk</literal>) will take some time.</para>
|
||||
&jdk;) will take some time.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1>
|
||||
|
|
@ -323,10 +334,10 @@ MD5 (bsd-jdk131-patches-6.tar.gz) = 9cade10b81d6034fdd2176bef32bdbf9</programlis
|
|||
<sect2>
|
||||
<title>Overview</title>
|
||||
|
||||
<para>Java is becoming an even more popular for making diverse
|
||||
<para>&java; is becoming an even more popular for making diverse
|
||||
and scalable platform independent solutions. One of the most
|
||||
growing needs of Java is in the <acronym>ASP</acronym> (Application
|
||||
Service Provider) market. Java serves as the perfect
|
||||
growing needs of &java; is in the <acronym>ASP</acronym> (Application
|
||||
Service Provider) market. &java; serves as the perfect
|
||||
solution for these types of markets, with the following
|
||||
advantages:</para>
|
||||
|
||||
|
|
@ -353,32 +364,32 @@ MD5 (bsd-jdk131-patches-6.tar.gz) = 9cade10b81d6034fdd2176bef32bdbf9</programlis
|
|||
</itemizedlist>
|
||||
|
||||
<para>A very important and growing technology which has emerged
|
||||
from Java is <acronym>JSP</acronym> (JavaServer Pages).</para>
|
||||
from &java; is <acronym>&jsp;</acronym> (&javaserver.pages;).</para>
|
||||
|
||||
<para><acronym>JSP</acronym> (JavaServer Pages) is a server-side
|
||||
<para><acronym>&jsp;</acronym> (&javaserver.pages;) is a server-side
|
||||
technology introduced by <literal>Sun Microsystems
|
||||
Corp.</literal>, which provides a quick simple way to generate
|
||||
dynamic content from within <acronym>HTML</acronym> pages. It
|
||||
uses <acronym>XML</acronym> tags along with Java scriptlets to
|
||||
uses <acronym>XML</acronym> tags along with &java; scriptlets to
|
||||
encapsulate and separate the logic from the design and display.
|
||||
When a <acronym>JSP</acronym> page is invoked, it is dynamically
|
||||
When a <acronym>&jsp;</acronym> page is invoked, it is dynamically
|
||||
converted into a Servlet and processed by the server to produce
|
||||
the resulting <acronym>HTML/XML</acronym> page for the client.
|
||||
When <acronym>JSP</acronym> is used in conjunction with
|
||||
When <acronym>&jsp;</acronym> is used in conjunction with
|
||||
JavaBeans, it is possible to produce very diverse and scalable
|
||||
applications, which may be combined with the strength and
|
||||
performance of FreeBSD.</para>
|
||||
|
||||
<para><application>Tomcat</application> is an open-source
|
||||
implementation of the Java Servlets and JavaServer Pages
|
||||
implementation of the &java; Servlets and &javaserver.pages;
|
||||
technologies, developed under the Jakarta project at the Apache
|
||||
Software Foundation. Tomcat implements a new Servlet framework
|
||||
(called Catalina) that is based on completely new architecture
|
||||
with the Servlet 2.3 and <acronym>JSP</acronym> 1.2
|
||||
with the Servlet 2.3 and <acronym>&jsp;</acronym> 1.2
|
||||
specifications. It includes many additional features that make
|
||||
it a useful platform for developing and deploying web
|
||||
applications and web services. In a nutshell, Tomcat is an
|
||||
application server written in 100% Pure Java.</para>
|
||||
application server written in 100% Pure &java;.</para>
|
||||
|
||||
<para>Tomcat is used for many purposes, and is not limited to
|
||||
Application Servers. It provides an open platform to develop
|
||||
|
|
@ -387,7 +398,7 @@ MD5 (bsd-jdk131-patches-6.tar.gz) = 9cade10b81d6034fdd2176bef32bdbf9</programlis
|
|||
reliable and fast pacing services.</para>
|
||||
|
||||
<para>Please refer to the <xref linkend="ref"> section for more
|
||||
information on Tomcat and <acronym>JSP</acronym>. The next
|
||||
information on Tomcat and <acronym>&jsp;</acronym>. The next
|
||||
section will demonstrate how to build the <quote>Tomcat
|
||||
Environment</quote> for FreeBSD. The version of Tomcat used in
|
||||
this guide is <literal>4.0.3</literal>. This version contains
|
||||
|
|
@ -413,7 +424,7 @@ MD5 (bsd-jdk131-patches-6.tar.gz) = 9cade10b81d6034fdd2176bef32bdbf9</programlis
|
|||
<title>The Tomcat environment for FreeBSD</title>
|
||||
|
||||
<para>It is very simple to install Tomcat on a FreeBSD machine,
|
||||
after setting up the necessary Java environment, which we have
|
||||
after setting up the necessary &java; environment, which we have
|
||||
previously completed.</para>
|
||||
|
||||
<para>In-order to setup Tomcat on FreeBSD, follow the below
|
||||
|
|
@ -421,15 +432,15 @@ MD5 (bsd-jdk131-patches-6.tar.gz) = 9cade10b81d6034fdd2176bef32bdbf9</programlis
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Follow the above steps to setup the necessary Java
|
||||
<para>Follow the above steps to setup the necessary &java;
|
||||
environment.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Set an environment variable <envar>JAVA_HOME</envar>
|
||||
which, points to the directory where you have installed the
|
||||
JDK (the examples below point to a native build of the
|
||||
JDK). If you are using &man.sh.1; as your shell, you can set
|
||||
&jdk; (the examples below point to a native build of the
|
||||
&jdk;). If you are using &man.sh.1; as your shell, you can set
|
||||
<envar>JAVA_HOME</envar> with:</para>
|
||||
|
||||
<screen>&prompt.root; export JAVA_HOME="/usr/local/jdk1.3.1"</screen>
|
||||
|
|
@ -443,7 +454,7 @@ MD5 (bsd-jdk131-patches-6.tar.gz) = 9cade10b81d6034fdd2176bef32bdbf9</programlis
|
|||
adding it into either <filename>.profile</filename> or
|
||||
<filename>.cshrc</filename>, depending on the shell you are
|
||||
using. This variable is very crucial for the functioning of
|
||||
all the Java based programs, including Tomcat itself.</para>
|
||||
all the &java; based programs, including Tomcat itself.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
|
|
@ -561,13 +572,13 @@ jakarta-tomcat-4.0.3
|
|||
<tbody>
|
||||
<row>
|
||||
<entry>
|
||||
<ulink url="&wwwurl;/java">The FreeBSD Java Project</ulink>
|
||||
<ulink url="&wwwurl;/java">The FreeBSD &java; Project</ulink>
|
||||
</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry>
|
||||
<ulink url="http://java.sun.com">JavaSoft. Home of Java</ulink>
|
||||
<ulink url="http://java.sun.com">JavaSoft. Home of &java;</ulink>
|
||||
</entry>
|
||||
</row>
|
||||
|
||||
|
|
@ -575,7 +586,7 @@ jakarta-tomcat-4.0.3
|
|||
<entry>
|
||||
<ulink
|
||||
url="&sunurl;/software/communitysource/java2/licensing.html">The
|
||||
Sun Community Source Licensing for Java</ulink>
|
||||
Sun Community Source Licensing for &java;</ulink>
|
||||
</entry>
|
||||
</row>
|
||||
|
||||
|
|
@ -594,7 +605,7 @@ jakarta-tomcat-4.0.3
|
|||
|
||||
<row>
|
||||
<entry>
|
||||
<ulink url="&wwwurl;/ports/java.html">FreeBSD Ports - Java
|
||||
<ulink url="&wwwurl;/ports/java.html">FreeBSD Ports - &java;
|
||||
Section</ulink>
|
||||
</entry>
|
||||
</row>
|
||||
|
|
@ -607,7 +618,7 @@ jakarta-tomcat-4.0.3
|
|||
|
||||
<para>Finally, we are at the end of the article and have a working
|
||||
version of Tomcat. We hope that you have learned the basics of
|
||||
installing and building the Java Development Kit on FreeBSD,
|
||||
installing and building the &java; Development Kit on FreeBSD,
|
||||
along with installation of the Tomcat binary distribution
|
||||
application server released by the Apache Software Foundation.
|
||||
The <xref linkend="ref"> section contains pointers to additional
|
||||
|
|
|
|||
|
|
@ -10,6 +10,9 @@
|
|||
|
||||
<!ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
|
||||
%mailing-lists;
|
||||
|
||||
<!ENTITY % trademarks PUBLIC "-//FreeBSD//ENTITIES DocBook Trademark Entities//EN">
|
||||
%trademarks;
|
||||
]>
|
||||
|
||||
<article>
|
||||
|
|
@ -24,6 +27,14 @@
|
|||
to different hardware requirements from desktops, are
|
||||
discussed below.</para>
|
||||
</abstract>
|
||||
|
||||
<legalnotice id="trademarks" role="trademarks">
|
||||
&tm-attrib.freebsd;
|
||||
&tm-attrib.linux;
|
||||
&tm-attrib.microsoft;
|
||||
&tm-attrib.xfree86;
|
||||
&tm-attrib.general;
|
||||
</legalnotice>
|
||||
</articleinfo>
|
||||
|
||||
<para>FreeBSD is often thought of as a server operating system, but
|
||||
|
|
@ -36,7 +47,7 @@
|
|||
However, installing it on laptops often involves problems which
|
||||
are not encountered on desktop machines and are not commonly
|
||||
discussed (laptops, even more than desktops, are fine-tuned for
|
||||
Microsoft Windows). This article aims to discuss some of these
|
||||
µsoft.windows;). This article aims to discuss some of these
|
||||
issues. Several people have also documented their experiences
|
||||
with &os; on specific laptop models on webpages which are not
|
||||
part of the &os; documentation. You might very well find some
|
||||
|
|
@ -51,32 +62,32 @@
|
|||
the &a.mobile.name; list.</para>
|
||||
|
||||
<sect1>
|
||||
<title>XFree86</title>
|
||||
<title>&xfree86;</title>
|
||||
|
||||
<para>Recent versions of <application>XFree86</application> work with most display adapters
|
||||
<para>Recent versions of <application>&xfree86;</application> work with most display adapters
|
||||
available on laptops these days. Acceleration may not be
|
||||
supported, but a generic SVGA configuration should work.</para>
|
||||
|
||||
<para>Check your laptop documentation for which card you have,
|
||||
and check in the <application>XFree86</application> documentation or
|
||||
and check in the <application>&xfree86;</application> documentation or
|
||||
the <ulink
|
||||
url="http://www.xfree86.org/current/Status.html">Driver Status for
|
||||
XFree86</ulink> page
|
||||
&xfree86;</ulink> page
|
||||
to see whether it is specifically supported. If it is not, use
|
||||
a generic device (do not go for a name which just looks
|
||||
similar). In <application>XFree86</application> version 4, you can try your luck
|
||||
similar). In <application>&xfree86;</application> version 4, you can try your luck
|
||||
with the command <userinput>XFree86 -configure</userinput>
|
||||
which auto-detects a lot of configurations.</para>
|
||||
|
||||
<para>The problem often is configuring the monitor. Common
|
||||
resources for <application>XFree86</application> focus on CRT monitors; getting a
|
||||
resources for <application>&xfree86;</application> focus on CRT monitors; getting a
|
||||
suitable modeline for an LCD display may be tricky. You may
|
||||
be lucky and not need to specify a modeline, or just need to
|
||||
specify suitable <literal>HorizSync</literal> and <literal>VertRefresh</literal> ranges. If that
|
||||
does not work, the best option is to check web resources
|
||||
devoted to configuring X on laptops (these are often
|
||||
linux-oriented sites but it does not matter because both systems
|
||||
use <application>XFree86</application>) and copy a modeline posted by someone for similar
|
||||
Linux oriented sites but it does not matter because both systems
|
||||
use <application>&xfree86;</application>) and copy a modeline posted by someone for similar
|
||||
hardware.</para>
|
||||
|
||||
<para>Most laptops come with two buttons on their pointing
|
||||
|
|
@ -90,7 +101,7 @@
|
|||
</programlisting>
|
||||
|
||||
<para>in the <filename>XF86Config</filename> file in the <literal>InputDevice</literal>
|
||||
section (for <application>XFree86</application> version 4; for version 3, put just the line
|
||||
section (for <application>&xfree86;</application> version 4; for version 3, put just the line
|
||||
<literal>Emulate3Buttons</literal>, without the quotes, in the
|
||||
<literal>Pointer</literal> section.)</para>
|
||||
</sect1>
|
||||
|
|
@ -101,7 +112,7 @@
|
|||
Laptops usually come with internal (on-board) modems.
|
||||
Unfortunately, this almost always means they are
|
||||
<quote>winmodems</quote> whose
|
||||
functionality is implemented in software, for which only windows
|
||||
functionality is implemented in software, for which only &windows;
|
||||
drivers are normally available (though a few drivers are beginning
|
||||
to show up for other operating systems; for example, if your modem has a Lucent LT chipset it might be supported by the <filename role="package">comms/ltmdm</filename> port). If that is the case, you
|
||||
need to buy an external modem: the most compact option is
|
||||
|
|
@ -293,7 +304,7 @@ apm_event NORMRESUME, STANDBYRESUME {
|
|||
<sect2>
|
||||
<title>Display Power Management</title>
|
||||
|
||||
<para>The X window system (<application>XFree86</application>) also includes display power
|
||||
<para>The X window system (<application>&xfree86;</application>) also includes display power
|
||||
management (look at the &man.xset.1; manual page, and search for
|
||||
<quote>dpms</quote> there). You may want to investigate this. However, this,
|
||||
too, works inconsistently on laptops: it
|
||||
|
|
|
|||
|
|
@ -1,7 +1,14 @@
|
|||
<!-- $FreeBSD$ -->
|
||||
<!-- FreeBSD Documentation Project -->
|
||||
|
||||
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN">
|
||||
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
|
||||
<!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
|
||||
%freebsd;
|
||||
|
||||
<!ENTITY % trademarks PUBLIC "-//FreeBSD//ENTITIES DocBook Trademark Entities//EN">
|
||||
%trademarks;
|
||||
]>
|
||||
<article>
|
||||
<articleinfo>
|
||||
<title>An MH Primer</title>
|
||||
|
|
@ -22,6 +29,12 @@
|
|||
|
||||
<pubdate>v1.0, 16 January 1996</pubdate>
|
||||
|
||||
<legalnotice id="trademarks" role="trademarks">
|
||||
&tm-attrib.freebsd;
|
||||
&tm-attrib.opengroup;
|
||||
&tm-attrib.general;
|
||||
</legalnotice>
|
||||
|
||||
<abstract>
|
||||
<para>This document contains an introduction to using MH on
|
||||
FreeBSD</para>
|
||||
|
|
@ -345,7 +358,7 @@ which I am probably the guilty party).</screen>
|
|||
into your <filename>inbox</filename> directory with a file name that is
|
||||
equivalent to the message number. So even if you did not have
|
||||
any of the MH tools to read your email you could still use
|
||||
standard Unix commands to munge around in those directories and
|
||||
standard &unix; commands to munge around in those directories and
|
||||
just more your files. It is this simplicity that really gives you
|
||||
a lot of power with what you can do with your email.</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -67,6 +67,10 @@
|
|||
by the Bluetooth SIG, Inc.</para>">
|
||||
<!ENTITY bluetooth "<trademark class='registered'>Bluetooth</trademark>">
|
||||
|
||||
<!ENTITY tm-attrib.broadcom "<para>Broadcom is a registered trademark
|
||||
of Broadcom Corporation and/or its subsidiaries.</para>">
|
||||
<!ENTITY broadcom "<trademark class='registered'>Broadcom</trademark>">
|
||||
|
||||
<!-- http://www.checkpoint.com/copyright.html -->
|
||||
<!ENTITY tm-attrib.check-point "<para>Check Point, Firewall-1, and
|
||||
VPN-1 are trademarks of Check Point Software Technologies
|
||||
|
|
@ -99,14 +103,17 @@
|
|||
trademarks of Heidelberger Druckmaschinen AG in the U.S. and other
|
||||
countries.</para>">
|
||||
|
||||
<!ENTITY tm-attrib.ibm "<para>IBM, AIX, OS/2, PowerPC, PS/2, and S/390 are
|
||||
<!ENTITY tm-attrib.ibm "<para>IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are
|
||||
trademarks of International Business Machines Corporation in the
|
||||
United States, other countries, or both.</para>">
|
||||
<!ENTITY aix "<trademark class='registered'>AIX</trademark>">
|
||||
<!ENTITY etherjet "<trademark>EtherJet</trademark>">
|
||||
<!ENTITY netfinity "<trademark class='registered'>Netfinity</trademark>">
|
||||
<!ENTITY os2 "<trademark class='registered'>OS/2</trademark>">
|
||||
<!ENTITY powerpc "<trademark class='registered'>PowerPC</trademark>">
|
||||
<!ENTITY ps2 "<trademark class='registered'>PS/2</trademark>">
|
||||
<!ENTITY s390 "<trademark class='registered'>S/390</trademark>">
|
||||
<!ENTITY thinkpad "<trademark class='registered'>ThinkPad</trademark>">
|
||||
|
||||
<!ENTITY tm-attrib.ieee "<para>IEEE, POSIX, and 802 are registered
|
||||
trademarks of Institute of Electrical and Electronics Engineers,
|
||||
|
|
@ -240,13 +247,15 @@
|
|||
<!ENTITY ultrasparc "<trademark class='registered'>UltraSPARC</trademark>">
|
||||
<!ENTITY sparcengine "<trademark class='registered'>SPARCEngine</trademark>">
|
||||
|
||||
<!ENTITY tm-attrib.sun "<para>Sun, Sun Microsystems, Netra, StarOffice,
|
||||
Sun Blade, Sun Enterprise, Sun Fire, SunOS, Solaris, Ultra, and Java are trademarks or registered trademarks of
|
||||
<!ENTITY tm-attrib.sun "<para>Sun, Sun Microsystems, Java, Java Virtual Machine, JavaServer Pages, JDK, JSP, JVM, Netra, Solaris, StarOffice,
|
||||
Sun Blade, Sun Enterprise, Sun Fire, SunOS, and Ultra are trademarks or registered trademarks of
|
||||
Sun Microsystems, Inc. in the United States and other
|
||||
countries.</para>">
|
||||
<!ENTITY java "<trademark>Java</trademark>">
|
||||
<!ENTITY java.virtual.machine "<trademark>Java Virtual Machine</trademark>">
|
||||
<!ENTITY javaserver.pages "<trademark>JavaServer Pages</trademark>">
|
||||
<!ENTITY jdk "<trademark>JDK</trademark>">
|
||||
<!ENTITY jsp "<trademark>JSP</trademark>">
|
||||
<!ENTITY jvm "<trademark>JVM</trademark>">
|
||||
<!ENTITY netra "<trademark>Netra</trademark>">
|
||||
<!ENTITY staroffice "<trademark>StarOffice</trademark>">
|
||||
|
|
|
|||
Loading…
Reference in a new issue