docs/166273: remove outdated FAQ questions

Eitan Adler eadler at
Tue Mar 20 03:30:13 UTC 2012

>Number:         166273
>Category:       docs
>Synopsis:       remove outdated FAQ questions
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 20 03:30:13 UTC 2012
>Originator:     Eitan Adler
The FAQ currently has a number of outdated and incorrect information. This is step one of fixing that. My goal with this patch is to remove questions which are no longer relevant in either the question or the answer. When I get my next batch of free time I attempt to fix up some of the answers that need changing.
Read the FAQ
Index: book.sgml
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/faq/book.sgml,v
retrieving revision 1.1144
diff -u -r1.1144 book.sgml
--- book.sgml	19 Feb 2012 02:11:53 -0000	1.1144
+++ book.sgml	20 Mar 2012 03:21:10 -0000
@@ -77,7 +77,6 @@
-      &tm-attrib.xfree86;
@@ -4400,7 +4399,7 @@
 	  <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 @@
-	      <term>ReiserFS</term>
-	      <listitem>
-		<para>&os; includes a read-only ReiserFS driver.  For
-		  more information, see &man.mount.reiserfs.8;.</para>
-	      </listitem>
-	    </varlistentry>
-	    <varlistentry>
@@ -6313,7 +6303,7 @@
-	  <para>Use &man.killall.1;.</para>
+	  <para>Use &man.pkill.1;.</para>
@@ -6356,21 +6346,6 @@
-      <qandaentry>
-	<question id="where-is-makedev">
-	  <para>What happened to
-	    <filename>/dev/MAKEDEV</filename>?</para>
-	</question>
-	<answer>
-	  <para>&os; 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>
 	<question id="add-pty">
 	  <para>How do I add pseudoterminals to the system?</para>
@@ -6765,85 +6740,6 @@
-	<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="">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</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=""></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></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>
@@ -7226,7 +7122,7 @@
 	<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
@@ -7234,18 +7130,9 @@
 	  <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; (<=
-	    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 @@
 	    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="">the &xfree86; documentation</ulink>,
+	      url="">the &xorg; documentation</ulink>,
 	    and the <link
 	      linkend="xdm-boot">the FAQ entry</link> on it.</para>
@@ -8159,37 +8046,6 @@
 	    to <literal>0</literal>.</para>
-      <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/ Shared object "" 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>


More information about the freebsd-doc mailing list