aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books/faq/book.sgml
diff options
context:
space:
mode:
authorEitan Adler <eadler@FreeBSD.org>2012-04-14 13:52:52 +0000
committerEitan Adler <eadler@FreeBSD.org>2012-04-14 13:52:52 +0000
commitd9418c027ecd87d11081f74d6f50c9115e24288c (patch)
treed433f2c9e080972cdf80e831c3d92b0e2b1a3f52 /en_US.ISO8859-1/books/faq/book.sgml
parentafe36eee75068435fba420fd40f44894588b2b48 (diff)
downloaddoc-d9418c027ecd87d11081f74d6f50c9115e24288c.tar.gz
doc-d9418c027ecd87d11081f74d6f50c9115e24288c.zip
- Remove old, outdated FAQ entries.
- Prefer csup to cvsup - Prefer pkill to killall - Prefer X.org to XFree86 PR: docs/166273 Reviewed by: gjb Approved by: gabor
Notes
Notes: svn path=/head/; revision=38674
Diffstat (limited to 'en_US.ISO8859-1/books/faq/book.sgml')
-rw-r--r--en_US.ISO8859-1/books/faq/book.sgml158
1 files changed, 7 insertions, 151 deletions
diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml
index de76a8c975..2479f5eada 100644
--- a/en_US.ISO8859-1/books/faq/book.sgml
+++ b/en_US.ISO8859-1/books/faq/book.sgml
@@ -77,7 +77,6 @@
&tm-attrib.sparc;
&tm-attrib.sun;
&tm-attrib.usrobotics;
- &tm-attrib.xfree86;
&tm-attrib.general;
</legalnotice>
@@ -4400,7 +4399,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
tree.</para>
<para>This is particularly a problem for &os; users who
- utilize &man.cvsup.1; (or &man.csup.1;) to track the Ports
+ utilize &man.csup.1; to track the Ports
Collection but choose not to install certain categories by
specifying them in <filename>refuse</filename>. In theory,
one should be able to refuse categories, but in practice
@@ -5238,15 +5237,6 @@ use "disklabel -r" to install initial label</screen>
</varlistentry>
<varlistentry>
- <term>ReiserFS</term>
-
- <listitem>
- <para>&os; includes a read-only ReiserFS driver. For
- more information, see &man.mount.reiserfs.8;.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
<term>ZFS</term>
<listitem>
@@ -6313,7 +6303,7 @@ options SYSVMSG # enable for messaging</programlisting>
</question>
<answer>
- <para>Use &man.killall.1;.</para>
+ <para>Use &man.pkill.1;.</para>
</answer>
</qandaentry>
@@ -6356,21 +6346,6 @@ options SYSVMSG # enable for messaging</programlisting>
world.</para>
</answer>
</qandaentry>
-
- <qandaentry>
- <question id="where-is-makedev">
- <para>What happened to
- <filename>/dev/MAKEDEV</filename>?</para>
- </question>
-
- <answer>
- <para>&os;&nbsp;5.<replaceable>X</replaceable> and beyond use
- the &man.devfs.8; device-on-demand system. Device drivers
- automatically create new device nodes as they are needed,
- obsoleting <filename>/dev/MAKEDEV</filename>.</para>
- </answer>
- </qandaentry>
-
<qandaentry>
<question id="add-pty">
<para>How do I add pseudoterminals to the system?</para>
@@ -6765,85 +6740,6 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="which-X">
- <para>Which X implementations are available for &os;?</para>
- </question>
-
- <answer>
- <para>Historically, the default implementation of X on &os;
- has been &xfree86; which is maintained by <ulink
- url="http://www.xfree86.org">The XFree86 Project, Inc.</ulink>
- This software was installed by default on &os; versions up
- until 4.10 and 5.2. Although &xorg; itself maintained an
- implementation during that time period, it was basically
- only provided as a reference platform, as it had suffered
- greatly from bitrot over the years.</para>
-
- <para>However, early in 2004, some XFree86 developers left
- that project over issues including the pace of code changes,
- future directions, and interpersonal conflicts, and are now
- contributing code directly to &xorg; instead. At that time,
- &xorg; updated its source tree to the last &xfree86; release
- before its subsequent licensing change (<application>XFree86
- version 4.3.99.903</application>), incorporated many changes
- that had previously been maintained separately, and has
- released that software as
- <application>X11R6.7.0</application>. A separate but
- related project, <ulink
- url="http://www.freedesktop.org/wiki/">freedesktop.org</ulink>
- (or <literal>fd.o</literal> for short), is working on
- rearchitecting the original &xfree86; code to offload more
- work onto the graphics cards (with the goal of increased
- performance) and make it more modular (with the goal of
- increased maintainability, and thus faster releases as well
- as easier configuration). &xorg; intends to incorporate the
- <literal>freedesktop.org</literal> changes in its future
- releases.</para>
-
- <para>As of July 2004, in &os.current;,
- &xfree86; has been replaced with &xorg; as the default
- implementation. Since then the default X11 implementation
- in &os; is &xorg;.</para>
-
- <para>For further information, read the <ulink
- url="&url.books.handbook;/x11.html">X11</ulink> section of
- the &os; Handbook.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question id="xfree86-split">
- <para>Why did the X projects split, anyway?</para>
- </question>
-
- <answer>
- <para>The answer to this question is outside the scope of this
- FAQ. Note that there are voluminous postings in various
- mailing list archives on the Internet; please use your
- favorite search engine to investigate the history instead of
- asking this question on the &os; mailing lists. It may even
- be the case that only the participants will ever know for
- certain.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question id="why-choose-xorg">
- <para>Why did &os; choose to go with the &xorg; ports by
- default?</para>
- </question>
-
- <answer>
- <para>The &xorg; developers claimed that their goal is to
- release more often and incorporate new features more
- quickly. If they are able to do so, this will be very
- attractive. Also, their software still uses the traditional
- X license, while &xfree86; is using their modified
- one.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="running-X">
<para>I want to run X, how do I go about it?</para>
</question>
@@ -7226,7 +7122,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<qandaentry>
<question id="xfree86-root">
- <para>Before, I was able to run &xfree86; as a regular user.
+ <para>Before, I was able to run &xorg; as a regular user.
Why does it now say that I must be
<username>root</username>?</para>
</question>
@@ -7234,18 +7130,9 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<answer>
<para>All X servers need to be run as
<username>root</username> in order to get direct access to
- your video hardware. Older versions of &xfree86; (&lt;=
- 3.3.6) installed all bundled servers to be automatically run
- as <username>root</username> (setuid to
- <username>root</username>). This is obviously a security
- hazard because X servers are large, complicated programs.
- Newer versions of &xfree86; do not install the servers
- setuid to <username>root</username> for just this
- reason.</para>
-
- <para>Obviously, running an X server as the
- <username>root</username> user is not acceptable, nor a good
- idea security-wise. There are two ways to be able to use X
+ your video hardware.</para>
+
+ <para>There are two ways to be able to use &xorg;
as a regular user. The first is to use
<command>xdm</command> or another display manager (e.g.,
<command>kdm</command>); the second is to use the
@@ -7257,7 +7144,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
sessions; it is essentially the graphical counterpart of
&man.getty.8; and &man.login.1;. For more information on
<command>xdm</command> see <ulink
- url="http://www.xfree86.org/sos/resources.html">the &xfree86; documentation</ulink>,
+ url="http://www.x.org/wiki/UserDocumentation">the &xorg; documentation</ulink>,
and the <link
linkend="xdm-boot">the FAQ entry</link> on it.</para>
@@ -8159,37 +8046,6 @@ Key F15 A A Menu Workplace Nop</programlisting>
to <literal>0</literal>.</para>
</answer>
</qandaentry>
-
- <qandaentry>
- <question id="cvsup-missing-libs">
- <para>I have just installed <application>CVSup</application>
- but trying to execute it produces errors. What is
- wrong?</para>
- </question>
-
- <answer>
- <para>First, see if the error message you are receiving is
- like the one shown below.</para>
-
- <programlisting>/usr/libexec/ld-elf.so.1: Shared object "libXaw.so.6" not found</programlisting>
-
- <para>Errors like these are caused by installing the <filename
- role="package">net/cvsup</filename> port on a machine which
- does not have the <application>&xorg;</application> suite.
- If you want to use the <acronym>GUI</acronym> included with
- <application>CVSup</application> you will need to install
- <application>&xorg;</application> now. Alternatively if you
- just wish to use <application>CVSup</application> from a
- command line you should delete the package previously
- installed. Then install the <filename
- role="package">net/cvsup-without-gui</filename> or the
- <filename role="package">net/csup</filename> port. If you
- have a recent &os; release you may use &man.csup.1;. This
- is covered in more detail in the <ulink
- url="&url.books.handbook;/cvsup.html">CVSup section</ulink>
- of the Handbook.</para>
- </answer>
- </qandaentry>
</qandaset>
</chapter>