svn commit: r40371 - in projects/entities/en_US.ISO8859-1: articles/committers-guide articles/contributors articles/portbuild books books/arch-handbook/driverbasics books/arch-handbook/sound books/...
Glen Barber
gjb at FreeBSD.org
Wed Dec 12 23:38:20 UTC 2012
Author: gjb
Date: Wed Dec 12 23:38:18 2012
New Revision: 40371
URL: http://svnweb.freebsd.org/changeset/doc/40371
Log:
Merged /head/en_US.ISO8859-1:r40180-40370
to projects/entities/en_US.ISO8859-1
Added:
projects/entities/en_US.ISO8859-1/htdocs/google6bb24ed0b804d5e9.html
- copied unchanged from r40370, head/en_US.ISO8859-1/htdocs/google6bb24ed0b804d5e9.html
Deleted:
projects/entities/en_US.ISO8859-1/books/corp-net-guide/
Modified:
projects/entities/en_US.ISO8859-1/articles/committers-guide/article.xml
projects/entities/en_US.ISO8859-1/articles/contributors/contrib.corealumni.xml
projects/entities/en_US.ISO8859-1/articles/portbuild/article.xml
projects/entities/en_US.ISO8859-1/books/Makefile
projects/entities/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
projects/entities/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml
projects/entities/en_US.ISO8859-1/books/faq/book.xml
projects/entities/en_US.ISO8859-1/books/handbook/eresources/chapter.xml
projects/entities/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml
projects/entities/en_US.ISO8859-1/books/handbook/mac/chapter.xml
projects/entities/en_US.ISO8859-1/books/handbook/mail/chapter.xml
projects/entities/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml
projects/entities/en_US.ISO8859-1/books/porters-handbook/book.xml
projects/entities/en_US.ISO8859-1/htdocs/Makefile
projects/entities/en_US.ISO8859-1/htdocs/administration.xml
projects/entities/en_US.ISO8859-1/htdocs/docs/books.xml
projects/entities/en_US.ISO8859-1/htdocs/donations/index.xml
projects/entities/en_US.ISO8859-1/htdocs/index.xsl
projects/entities/en_US.ISO8859-1/htdocs/internal/i18n.xml
projects/entities/en_US.ISO8859-1/htdocs/layout/css/layout.css
projects/entities/en_US.ISO8859-1/htdocs/layout/js/google.js
projects/entities/en_US.ISO8859-1/htdocs/news/status/report-2001-08.xml
projects/entities/en_US.ISO8859-1/htdocs/news/status/report-2002-05-2002-06.xml
projects/entities/en_US.ISO8859-1/htdocs/platforms/arm.xml
projects/entities/en_US.ISO8859-1/htdocs/releng/charter.xml
projects/entities/en_US.ISO8859-1/htdocs/releng/index.xml
projects/entities/en_US.ISO8859-1/htdocs/where.xml
Directory Properties:
projects/entities/en_US.ISO8859-1/ (props changed)
Modified: projects/entities/en_US.ISO8859-1/articles/committers-guide/article.xml
==============================================================================
--- projects/entities/en_US.ISO8859-1/articles/committers-guide/article.xml Wed Dec 12 22:41:25 2012 (r40370)
+++ projects/entities/en_US.ISO8859-1/articles/committers-guide/article.xml Wed Dec 12 23:38:18 2012 (r40371)
@@ -1883,37 +1883,20 @@ U stable/9/share/man/man4/netmap.4
<para>Don't remove and re-add the same file in a single commit
as this will break the CVS exporter.</para>
- <para>Speeding up checkouts and minimising network traffic is
- possible with the following recipe:</para>
+ <para>Speeding up svn is
+ possible by adding the following to <filename>~/.ssh/config</filename>:</para>
- <screen>&prompt.user; <userinput>svn co --depth=empty svn+ssh://svn.freebsd.org/base fbsvn</userinput>
-&prompt.user; <userinput>cd fbsvn</userinput>
-&prompt.user; <userinput>svn up --depth=empty stable</userinput>
-&prompt.user; <userinput>svn up head</userinput>
-&prompt.user; <userinput>cd stable</userinput>
-&prompt.user; <userinput>cp -r ../head/ 7</userinput>
-&prompt.user; <userinput>cd 7</userinput>
-&prompt.user; <userinput>svn switch svn+ssh://svn.freebsd.org/base/stable/7</userinput>
-&prompt.user; <userinput>cd ..</userinput>
-&prompt.user; <userinput>cp -r 7/ 6</userinput>
-&prompt.user; <userinput>cd 6</userinput>
-&prompt.user; <userinput>svn switch svn+ssh://svn.freebsd.org/base/stable/6</userinput></screen>
-
- <para>What this bit of evil does is check out head, stable/7 and
- stable/6. We create the empty checkout directories under
- <acronym>SVN</acronym>'s control. In <acronym>SVN</acronym>,
- subtrees are self identifying, like in <acronym>CVS</acronym>.
- We check out head and clone it as stable/7. Except we don't
- want the head version so we <quote>switch</quote> it to the
- 7.x tree location. <acronym>SVN</acronym> downloads diffs to
- convert the <quote>head</quote> files to
- <quote>stable/7</quote> instead of doing a fresh checkout.
- The same goes for stable/6. This does, however, definitely
- count as abuse of the working copy client code!</para>
+ <screen>Host *
+ControlPath ~/.ssh/sockets/master-%l-%r@%h:%p
+ControlMaster auto
+ControlPersist yes</screen>
+
+ <para>and then typing</para>
+ <screen><userinput>mkdir ~/.ssh/sockets</userinput></screen>
<para>Checking out a working copy with a stock Subversion client
without &os;-specific patches
- (<makevar>WITH_FREEBSD_TEMPLATE</makevar>) will mean that
+ (<makevar>OPTIONS_SET=FREEBSD_TEMPLATE</makevar>) will mean that
<literal>$FreeBSD$</literal> tags will not be
expanded. Once the correct version has been installed, trick
Subversion into expanding them like so:</para>
@@ -1921,8 +1904,7 @@ U stable/9/share/man/man4/netmap.4
<screen>&prompt.user; <userinput>svn propdel -R svn:keywords .</userinput>
&prompt.user; <userinput>svn revert -R .</userinput></screen>
- <para>This is not a good idea if uncommitted patches exist,
- however.</para>
+ <para>This will wipe out uncommitted patches.</para>
</sect2>
</sect1>
@@ -2458,14 +2440,13 @@ U stable/9/share/man/man4/netmap.4
<term>&a.committers;</term>
<listitem>
- <para>cvs-committers is the entity that the version control system uses to send you all your
- commit messages. You should <emphasis>never</emphasis> send email
- directly to this list. You should only send replies to this list
- when they are short and are directly related to a commit.</para>
-
- <para>There is a similar list, svn-committers, which has a
- similar purpose but is a normal list, i.e., you are free to
- send any suitable message to this list.</para>
+ <para>&a.svn-src-all.name;, &a.svn-ports-all.name; and
+ &a.svn-doc-all.name; are the mailing lists that the
+ version control system uses to send commit messages to.
+ You should <emphasis>never</emphasis> send email directly
+ to these lists. You should only send replies to this list
+ when they are short and are directly related to a
+ commit.</para>
</listitem>
</varlistentry>
Modified: projects/entities/en_US.ISO8859-1/articles/contributors/contrib.corealumni.xml
==============================================================================
--- projects/entities/en_US.ISO8859-1/articles/contributors/contrib.corealumni.xml Wed Dec 12 22:41:25 2012 (r40370)
+++ projects/entities/en_US.ISO8859-1/articles/contributors/contrib.corealumni.xml Wed Dec 12 23:38:18 2012 (r40371)
@@ -3,6 +3,10 @@
<itemizedlist>
<listitem>
+ <para>&a.attilio.email; (2012)</para>
+ </listitem>
+
+ <listitem>
<para>&a.wilko.email; (2006 - 2012)</para>
</listitem>
Modified: projects/entities/en_US.ISO8859-1/articles/portbuild/article.xml
==============================================================================
--- projects/entities/en_US.ISO8859-1/articles/portbuild/article.xml Wed Dec 12 22:41:25 2012 (r40370)
+++ projects/entities/en_US.ISO8859-1/articles/portbuild/article.xml Wed Dec 12 23:38:18 2012 (r40371)
@@ -1977,13 +1977,11 @@ touch /tmp/.boot_finished</screen>
</listitem>
<listitem>
- <para>Modify
- <filename>usr/local/etc/sudoers</filename>:<screen>
-38a39,42
->
-> # local changes for package building
-> %wheel ALL=(ALL) ALL
-> ports-<replaceable>${arch}</replaceable> ALL=(ALL) NOPASSWD: ALL</screen>
+ <para>Create
+ <filename>usr/local/etc/sudoers/sudoers.d/portbuild</filename>:<programlisting>
+# local changes for package building
+%wheel ALL=(ALL) ALL
+ports-<replaceable>${arch}</replaceable> ALL=(ALL) NOPASSWD: ALL</programlisting>
</para>
</listitem>
</itemizedlist>
@@ -2866,6 +2864,7 @@ rpc_lockd_enable="NO"
rpc_statd_enable="YES"
sendmail_enable="NONE"
smartd_enable="YES"
+zfs_enable="YES"
</screen>
</step>
@@ -2921,7 +2920,7 @@ devel/subversion
net/nc
net/rsync
sysutils/ganglia-monitor-core (with GMETAD off)
-sysutils/ganglia-webfrontend (WITHOUT_X11)
+sysutils/ganglia-webfrontend (compile with -DWITHOUT_X11)
www/apache22 (with EXT_FILTER)</screen>
</para>
@@ -2948,7 +2947,8 @@ sysutils/screen</screen>
benchmarks/bonnie++
ports-mgmt/pkg_tree
sysutils/dmidecode
-sysutils/smartmontools</screen>
+sysutils/smartmontools
+sysutils/zfs-stats</screen>
</para>
</step>
@@ -2962,6 +2962,10 @@ sysutils/smartmontools</screen>
<procedure>
<step>
+ <para>Create <filename>/a</filename>.</para>
+ </step>
+
+ <step>
<para>Create a <application>zfs</application> volume named
<filename>a</filename> and mount it on
<filename>/a</filename>.</para>
@@ -3123,7 +3127,7 @@ sysutils/smartmontools</screen>
<step>
<para>Copy the following files from
- <filename>/var/portbuild/conf/etc/rc.d/</filename> to
+ <filename>/var/portbuild/etc/rc.d/</filename> to
<filename>/usr/local/etc/rc.d/</filename>:<screen>
buildproxy.sh
pollmachine.sh
@@ -3209,12 +3213,11 @@ qmanager.sh</screen>
</step>
<step>
- <para>If not already created, add the following users:<screen>
-squid:*:100:100::0:0:User &:/usr/local/squid:/bin/sh
+ <para>If not already created, add the following user:<screen>
ganglia:*:102:102::0:0:User &:/usr/local/ganglia:/bin/sh</screen>
</para>
- <para>Add them to <filename>/etc/group</filename> as well.</para>
+ <para>Add it to <filename>/etc/group</filename> as well.</para>
</step>
<step>
Modified: projects/entities/en_US.ISO8859-1/books/Makefile
==============================================================================
--- projects/entities/en_US.ISO8859-1/books/Makefile Wed Dec 12 22:41:25 2012 (r40370)
+++ projects/entities/en_US.ISO8859-1/books/Makefile Wed Dec 12 23:38:18 2012 (r40371)
@@ -1,7 +1,6 @@
# $FreeBSD$
SUBDIR = arch-handbook
-SUBDIR+= corp-net-guide
SUBDIR+= design-44bsd
SUBDIR+= dev-model
SUBDIR+= developers-handbook
Modified: projects/entities/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
==============================================================================
--- projects/entities/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Wed Dec 12 22:41:25 2012 (r40370)
+++ projects/entities/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Wed Dec 12 23:38:18 2012 (r40371)
@@ -327,9 +327,9 @@ echo_read(struct cdev *dev __unused, str
* or as big as the remaining data
*/
- amt = MIN(uio-<uio_resid, echomsg-<len - uio-<uio_offset);
- uio-<uio_offset += amt;
- if ((error = uiomove(echomsg-<msg, amt, uio)) != 0)
+ amt = MIN(uio->uio_resid, echomsg->len - uio->uio_offset);
+ uio->uio_offset += amt;
+ if ((error = uiomove(echomsg->msg, amt, uio)) != 0)
uprintf("uiomove failed!\n");
return (error);
@@ -348,31 +348,31 @@ echo_write(struct cdev *dev __unused, st
/* Copy the string in from user memory to kernel memory */
/*
- * We either write from the beginning or are appending - do
- * not allow ranom access.
+ * We either write from the beginning or are appending -- do
+ * not allow random access.
*/
- if (uio-<uio_offset != 0 && (uio-<uio_offset != echomsg-<len))
+ if (uio->uio_offset != 0 && (uio->uio_offset != echomsg->len))
return (EINVAL);
/*
* This is new message, reset length
*/
- if (uio-<uio_offset == 0)
- echomsg-<len = 0;
+ if (uio->uio_offset == 0)
+ echomsg->len = 0;
/* NULL charcter should be overriden */
- if (echomsg-<len != 0)
- echomsg-<len--;
+ if (echomsg->len != 0)
+ echomsg->len--;
/* Copy the string in from user memory to kernel memory */
- amt = MIN(uio-<uio_resid, (BUFFERSIZE - echomsg-<len));
+ amt = MIN(uio->uio_resid, (BUFFERSIZE - echomsg->len));
- error = uiomove(echomsg-<msg + uio-<uio_offset, amt, uio);
+ error = uiomove(echomsg->msg + uio->uio_offset, amt, uio);
/* Now we need to null terminate, then record the length */
- echomsg-<len += amt + 1;
- uio-<uio_offset += amt + 1;
- echomsg-<msg[echomsg-<len - 1] = 0;
+ echomsg->len += amt + 1;
+ uio->uio_offset += amt + 1;
+ echomsg->msg[echomsg->len - 1] = 0;
if (error != 0)
uprintf("Write failed: bad address!\n");
Modified: projects/entities/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml
==============================================================================
--- projects/entities/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml Wed Dec 12 22:41:25 2012 (r40370)
+++ projects/entities/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml Wed Dec 12 23:38:18 2012 (r40371)
@@ -82,16 +82,16 @@
<sect1 id="oss-files">
<title>Files</title>
- <para>All the relevant code currently (FreeBSD 4.4) lives in
+ <para>All the relevant code lives in
<filename>/usr/src/sys/dev/sound/</filename>, except for the
public ioctl interface definitions, found in
<filename>/usr/src/sys/sys/soundcard.h</filename></para>
<para>Under <filename>/usr/src/sys/dev/sound/</filename>, the
<filename>pcm/</filename> directory holds the central code,
- while the <filename>isa/</filename> and
- <filename>pci/</filename> directories have the drivers for ISA
- and PCI boards.</para>
+ while the <filename>pci/</filename>, <filename>isa/</filename>
+ and <filename>usb/</filename> directories have the drivers
+ for PCI and ISA boards, and for USB audio devices.</para>
</sect1>
@@ -527,7 +527,7 @@
<function>channel_resetdone()</function>, and
<function>channel_notify()</function> are for special purposes
and should not be implemented in a driver without discussing
- it with the authorities (&a.cg.email;).</para>
+ it on the &a.multimedia;.</para>
<para><function>channel_setdir()</function> is deprecated.</para>
</sect3>
Modified: projects/entities/en_US.ISO8859-1/books/faq/book.xml
==============================================================================
--- projects/entities/en_US.ISO8859-1/books/faq/book.xml Wed Dec 12 22:41:25 2012 (r40370)
+++ projects/entities/en_US.ISO8859-1/books/faq/book.xml Wed Dec 12 23:38:18 2012 (r40371)
@@ -64,7 +64,6 @@
&tm-attrib.ibm;
&tm-attrib.ieee;
&tm-attrib.intel;
- &tm-attrib.iomega;
&tm-attrib.linux;
&tm-attrib.microsoft;
&tm-attrib.mips;
@@ -87,14 +86,13 @@
unless otherwise noted. If you are interested in helping with
this project, send email to the &a.doc;. The latest version of
this document is always available from the <ulink
- url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html">&os; World Wide Web server</ulink>.
+ url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html">&os; website</ulink>.
It may also be downloaded as one large <ulink
- url="book.html">HTML</ulink> file with HTTP or as plain text,
- &postscript;, PDF, etc. from the <ulink
+ url="book.html">HTML</ulink> file with HTTP or as a variety
+ of other formats from the <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">&os; FTP
server</ulink>. You may also want to <ulink
- url="&url.base;/search/index.html">Search the FAQ</ulink>.
- </para>
+ url="&url.base;/search/index.html">Search the FAQ</ulink>.</para>
</abstract>
</bookinfo>
@@ -123,17 +121,18 @@
</question>
<answer>
- <para>Briefly, &os; is a &unix; like operating system for
- AMD64 and &intel; EM64T, &i386; PC-98, IA-64, &arm;,
- &powerpc; and &ultrasparc; platforms based on U.C.
+ <para>&os; is a modern operating system for desktops,
+ laptops, servers, and embedded systems with
+ support for a large number of <ulink
+ url="http://www.FreeBSD.org/platforms/">platforms</ulink>.</para>
+
+ <para>It is based on U.C.
Berkeley's <quote>4.4BSD-Lite</quote> release, with some
<quote>4.4BSD-Lite2</quote> enhancements. It is also based
indirectly on William Jolitz's port of U.C. Berkeley's
<quote>Net/2</quote> to the &i386;, known as
<quote>386BSD</quote>, though very little of the 386BSD code
- remains. A fuller description of what &os; is and how it
- can work for you may be found on the <ulink
- url="&url.base;/index.html">&os; home page</ulink>.</para>
+ remains.</para>
<para>&os; is used by companies, Internet Service Providers,
researchers, computer professionals, students and home users
@@ -315,11 +314,6 @@
<para>What is the latest version of &os;?</para>
</question>
-<!--
- This answer is a hack to deal with the fact that for now there are
- multiple "latest" versions of FreeBSD.
--->
-
<answer>
<para>At any point in the development of &os;, there can be
multiple parallel branches. &rel.relx; releases are
@@ -389,17 +383,12 @@
url="&url.books.handbook;/index.html">Handbook</ulink> for
details on running <emphasis>-CURRENT</emphasis>.</para>
- <para>If you are not familiar with the operating system or are
- not capable of identifying the difference between a real
- problem and a temporary problem, you should not use
+ <para>If you are not familiar with &os;
+ you should not use
&os.current;. This branch sometimes evolves quite quickly
- and can be un-buildable sometimes.
+ and due to mistake can be un-buildable at times.
People that use &os.current; are expected to be able to
- analyze any problems and only report them if they are deemed
- to be mistakes rather than <quote>glitches</quote>.
- Questions such as <quote>make world produces some error
- about groups</quote> on the &a.current; may be treated with
- contempt.</para>
+ analyze, debug, and report problems.</para>
<para>Every month, <ulink
url="&url.base;/snapshots/">snapshot</ulink>
@@ -613,19 +602,6 @@
an article on how to write good problem reports.</para>
</answer>
</qandaentry>
-
- <qandaentry>
- <question id="other-info-sources">
- <para>What other sources of information are there?</para>
- </question>
-
- <answer>
- <para>Please check the <ulink
- url="http://www.FreeBSD.org/docs.html">Documentation</ulink>
- list on the main <ulink
- url="http://www.FreeBSD.org">&os;</ulink> web site.</para>
- </answer>
- </qandaentry>
</qandaset>
</chapter>
@@ -1146,8 +1122,8 @@
<answer>
<para>On the
- <ulink url="http://www.freebsd.org/where.html">Get &os; page</ulink>
- select <literal>[iso]</literal> next to the
+ <ulink url="http://www.freebsd.org/where.html">Getting &os;</ulink>
+ page select <literal>[iso]</literal> next to the
architecture you want to use.</para>
<para>Any of the following can be used:</para>
@@ -1171,11 +1147,11 @@
<row>
<entry><filename>dvd1.iso</filename></entry>
<entry>Similar to <filename>disc1.iso</filename>
- but with addtional packages.</entry>
+ but with additional packages.</entry>
</row>
<row>
- <entry><filename>memstick.iso</filename></entry>
+ <entry><filename>memstick.img</filename></entry>
<entry>A bootable image sufficient for copying to a
USB stick.</entry>
</row>
@@ -1262,8 +1238,11 @@
</question>
<answer>
- <para>Installation instructions can be found in the <ulink
- url="&url.books.handbook;/install.html">Handbook entry on installing &os;</ulink>.</para>
+ <para>Installation instructions for versions since
+ &os; 9.0 can be found at <ulink
+ url="&url.books.handbook;/bsdinstall.html">Handbook entry on installing &os;</ulink>.
+ Older instructions can be found in the <ulink
+ url="&url.books.handbook;/install.html">legacy entry on installing &os;</ulink>.</para>
</answer>
</qandaentry>
@@ -1283,7 +1262,7 @@
<qandaentry>
<question id="custom-boot-floppy">
- <para>How can I make my own custom install disk?</para>
+ <para>How can I make my own custom release or install disk?</para>
</question>
<answer>
@@ -1390,41 +1369,19 @@
<qandaentry>
<question id="boot-floppy-strangeness">
- <para>Strange things happen when I boot the install floppy!
+ <para>Strange things happen when I boot the install disk!
What is happening?</para>
</question>
<answer>
<para>If you are seeing things like the machine grinding to a
halt or spontaneously rebooting when you try to boot the
- install floppy, here are three questions to ask
- yourself:</para>
-
- <orderedlist>
- <listitem>
- <para>Did you use a new, freshly-formatted, error-free
- floppy (preferably a brand-new one straight out of the
- box, as opposed to the magazine cover disk that has been
- lying under the bed for the last three years)?</para>
- </listitem>
-
- <listitem>
- <para>Did you download the floppy image in binary (or
- image) mode? (do not be embarrassed, even the best of us
- have accidentally downloaded a binary file in ASCII mode
- at least once!)</para>
- </listitem>
-
- <listitem>
- <para>If you are using &windows; 95 or
- &windows; 98 did you run <command>fdimage</command>
- or <command>rawrite</command> in pure DOS mode? These
- operating systems can interfere with programs that write
- directly to hardware, which the disk creation program
- does; even running it inside a DOS shell in the GUI can
- cause this problem.</para>
- </listitem>
- </orderedlist>
+ &os; installer, make sure that the SHA256 hash of
+ the image matches the one on the website. If you
+ accidently downloaded the disk image in binary (or
+ image) mode the will be corrupted. (Do not be embarrassed,
+ even the best of us have accidentally downloaded a binary
+ file in ASCII mode at least once!)</para>
</answer>
</qandaentry>
@@ -1483,22 +1440,6 @@
</qandaentry>
<qandaentry>
- <question id="stop-at-boot-manager">
- <para>Why can I not get past the boot manager's
- <prompt>F?</prompt> prompt?</para>
- </question>
-
- <answer>
- <para>This is another symptom of the problem described in the
- preceding question. Your BIOS geometry and &os; geometry
- settings do not agree! If your controller or BIOS supports
- cylinder translation (often marked as <quote>>1GB drive
- support</quote>), try toggling its setting and reinstalling
- &os;.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="need-complete-sources">
<para>Do I need to install the source?</para>
</question>
@@ -1561,21 +1502,6 @@
</qandaentry>
<qandaentry>
- <question id="boot-floppy-hangs">
- <para>Why does the boot floppy start, but hang at the
- <literal>Probing Devices...</literal> screen?</para>
- </question>
-
- <answer>
- <para>If you have a IDE &iomegazip; or &jaz; drive installed,
- remove it and try again. The boot floppy can get confused by
- the drives. After the system is installed you can reconnect
- the drive. Hopefully this will be fixed in a later
- release.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="panic-on-install-reboot">
<para>Why do I get a <errorname>panic: can't mount
root</errorname> error when rebooting the system after
@@ -2074,118 +2000,6 @@
<qandaset>
<qandaentry>
- <question id="usbkbd">
- <para>Does &os; support my USB keyboard?</para>
- </question>
-
- <answer>
- <para>&os; supports USB keyboards out-of-the-box. Once you
- have USB keyboard support enabled on your system, the AT
- keyboard becomes <devicename>/dev/kbd0</devicename> and
- the USB keyboard becomes
- <devicename>/dev/kbd1</devicename>, if both are connected
- to the system. If there is the USB keyboard only, it will
- be <devicename>/dev/ukbd0</devicename>.</para>
-
- <para>If you want to use the USB keyboard in the console,
- you have to explicitly tell the console driver to use the
- existing USB keyboard. This can be done by running the
- following command as a part of system
- initialization.</para>
-
- <screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd1 < /dev/console > /dev/null</userinput></screen>
-
- <para>Note that if the USB keyboard is the only keyboard, it
- is accessed as <devicename>/dev/ukbd0</devicename>, thus,
- the command should look like:</para>
-
- <screen>&prompt.root; <userinput>kbdcontrol -k /dev/ukbd0 < /dev/console > /dev/null</userinput></screen>
-
- <note>
- <para>To make this change permanent across reboots, add
- <literal>keyboard="/dev/ukbd0"</literal> to
- <filename>/etc/rc.conf</filename>.</para>
- </note>
-
- <para>Once this is done, the USB keyboard should work in the
- X environment as well without any special settings.</para>
-
- <para>If you want to switch back to the default keyboard,
- use this command:</para>
-
- <screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd0 > /dev/null</userinput></screen>
-
- <para>To allow using both the second USB keyboard and the
- first AT keyboard at the same time on a console via
- &man.kbdmux.4; driver type the following commands:</para>
-
- <screen>&prompt.root; <userinput>kbdcontrol -K < /dev/console > /dev/null</userinput>
-&prompt.root; <userinput>kbdcontrol -a atkbd0 < /dev/kbdmux0 > /dev/null</userinput>
-&prompt.root; <userinput>kbdcontrol -a ukbd1 < /dev/kbdmux0 > /dev/null</userinput>
-&prompt.root; <userinput>kbdcontrol -k /dev/kbdmux0 < /dev/console > /dev/null</userinput></screen>
-
- <para>See the &man.ukbd.4;, &man.kbdcontrol.1; and
- &man.kbdmux.4; manual pages for more information.</para>
-
- <note>
- <para>Hot-plugging and unplugging of the USB keyboard may
- not work quite right yet. We recommend connecting the
- keyboard before starting the system and leaving it
- connected until the system is shutdown to avoid
- issues.</para>
- </note>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question id="busmouse">
- <para>I have an unusual bus mouse. How do I set it
- up?</para>
- </question>
-
- <answer>
- <para>&os; supports the bus mouse and the InPort bus mouse
- from such manufacturers as Microsoft, Logitech and ATI. The
- <filename>GENERIC</filename> kernel does not include the
- device driver. To build a custom kernel with the bus mouse
- driver, add the following line to the kernel config
- file:</para>
-
- <programlisting>device mse0 at isa? port 0x23c irq5</programlisting>
-
- <para>Bus mice usually come with dedicated interface cards.
- These cards may allow you to set the port address and the
- IRQ number other than shown above. Refer to the manual of
- your mouse and the &man.mse.4; manual page for more
- information.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question id="ps2mouse">
- <para>How do I use my PS/2 (<quote>mouse port</quote> or
- <quote>keyboard</quote>) mouse?</para>
- </question>
-
- <answer>
- <para>The PS/2 mouse is supported out-of-the-box. The
- necessary device driver, <devicename>psm</devicename>, is
- included in the kernel.</para>
-
- <para>If your custom kernel does not have this, add the
- following line to your kernel configuration and compile a
- new kernel.</para>
-
- <programlisting>device psm0 at atkbdc? irq 12</programlisting>
-
- <para>Once the kernel detects <devicename>psm0</devicename>
- correctly at boot time, a device node
- <devicename>psm0</devicename> will be created
- automatically.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="moused">
<para>Is it possible to use a mouse in any way outside the X
Window system?</para>
@@ -2235,10 +2049,14 @@
</question>
<answer>
- <para>Once you get the mouse daemon running (see the <link
- linkend="moused">previous section</link>), hold down the
+ <para>It is not possible to remove data using the mouse.
+ However, it is possible to <quote>copy and
+ paste</quote>.
+ Once you get the mouse daemon running (see the
+ <link linkend="moused">previous question</link>)
+ hold down
button 1 (left button) and move the mouse to select a region
- of text. Then, press the button 2 (middle button) to paste
+ of text. Then, press button 2 (middle button) to paste
it at the text cursor. Pressing button 3 (right button)
will <quote>extend</quote> the selected region of
text.</para>
@@ -2271,18 +2089,6 @@
</qandaentry>
<qandaentry>
- <question id="laptop-mouse-trackball">
- <para>How do I use the mouse/trackball/touchpad on my
- laptop?</para>
- </question>
-
- <answer>
- <para>Please refer to <link linkend="ps2mouse">the answer to
- the previous question</link>.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="keyboard-delete-key">
<para>How do I use my delete key in <command>sh</command>
and <command>csh</command>?</para>
@@ -2311,7 +2117,7 @@ bindkey ^[[3~ delete-char # for xterm</p
</sect1>
<sect1 id="compatibility-networking">
- <title>Networking and Serial Devices</title>
+ <title>Networking</title>
<qandaset>
<qandaentry>
@@ -2336,37 +2142,6 @@ bindkey ^[[3~ delete-char # for xterm</p
&man.bwn.4; and &man.bwi.4; drivers.</para>
</answer>
</qandaentry>
-
- <qandaentry>
- <question id="multiport-serial-support">
- <para>Which multi-port serial cards are supported by
- &os;?</para>
- </question>
-
- <answer>
- <para>There is a list of these in the <ulink
- url="&url.books.handbook;/serial.html">Serial Communications</ulink>
- chapter of the handbook.</para>
-
- <para>Some unnamed clone cards have also been known to work,
- especially those that claim to be AST compatible.</para>
-
- <para>Check the &man.sio.4; manual page to get more
- information on configuring such cards.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question id="serial-console-prompt">
- <para>How do I get the boot: prompt to show on the serial
- console?</para>
- </question>
-
- <answer>
- <para>See <ulink
- url="&url.books.handbook;/serialconsole-setup.html">this section of the handbook</ulink>.</para>
- </answer>
- </qandaentry>
</qandaset>
</sect1>
@@ -2426,17 +2201,9 @@ bindkey ^[[3~ delete-char # for xterm</p
</question>
<answer>
- <para>&os; supports <acronym>APM</acronym> on certain
- machines. Further information can be found in
- &man.apm.4;.</para>
-
- <para>&os; also supports the <acronym>ACPI</acronym>
- features found in most modern hardware. Further
- information can be found in &man.acpi.4;. If a system
- supports both <acronym>APM</acronym> and
- <acronym>ACPI</acronym>, either can be used. We suggest
- you try both and choose the one that best fits your
- needs.</para>
+ <para>&os; supports the <acronym>ACPI</acronym>
+ features found in modern hardware. Further
+ information can be found in &man.acpi.4;.</para>
</answer>
</qandaentry>
</qandaset>
@@ -2492,52 +2259,6 @@ bindkey ^[[3~ delete-char # for xterm</p
</qandaentry>
<qandaentry>
- <question id="hpnetserver-scsi-failure">
- <para>Why does &os; not detect my HP Netserver's SCSI
- controller?</para>
- </question>
-
- <answer>
- <para>This is basically a known problem. The EISA on-board
- SCSI controller in the HP Netserver machines occupies EISA
- slot number 11, so all the <quote>true</quote> EISA slots
- are in front of it. Alas, the address space for EISA slots
- >= 10 collides with the address space assigned to PCI,
- and &os;'s auto-configuration currently cannot handle this
- situation very well.</para>
-
- <para>So now, the best you can do is to pretend there is no
- address range clash :), by bumping the kernel option
- <literal>EISA_SLOTS</literal> to a value of 12. Configure
- and compile a kernel, as described in the <ulink
- url="&url.books.handbook;/kernelconfig.html">Handbook entry on configuring the kernel</ulink>.</para>
-
- <para>Of course, this does present you with a chicken-and-egg
- problem when installing on such a machine. In order to work
- around this problem, a special hack is available inside
- <emphasis>UserConfig</emphasis>. Do not use the
- <quote>visual</quote> interface, but the plain command-line
- interface there. Simply type the following command at the
- prompt and install your system as usual:</para>
-
- <programlisting>eisa 12
-quit</programlisting>
-
- <para>While it is recommended you compile and install a custom
- kernel anyway.</para>
-
- <para>Hopefully, future versions will have a proper fix for
- this problem.</para>
-
- <note>
- <para>You cannot use a <literal>dangerously
- dedicated</literal> disk with an HP Netserver. See <link
- linkend="dedicate">this note</link> for more info.</para>
- </note>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="ed1-timeout">
<para>I keep seeing messages like <errorname>ed1:
timeout</errorname>. What do these messages mean?</para>
@@ -2710,58 +2431,6 @@ quit</programlisting>
</qandaentry>
<qandaentry>
- <question id="screen-loses-sync">
- <para>Why does the screen go black and lose sync when I
- boot?</para>
- </question>
-
- <answer>
- <para>This is a known problem with the ATI Mach64 video
- card. The problem is that this card uses address
- <literal>2e8</literal>, and the fourth serial port does too.
- Due to a bug (feature?) in the &man.sio.4; driver it will
- touch this port even if you do not have the fourth serial
- port, and <emphasis>even</emphasis> if you disable
- <devicename>sio3</devicename> (the fourth port) which
- normally uses this address.</para>
-
- <para>Until the bug has been fixed, you can use this
- workaround:</para>
-
- <orderedlist>
- <listitem>
- <para>Enter <option>-c</option> at the boot prompt.
- (This will put the kernel into configuration
- mode).</para>
- </listitem>
-
- <listitem>
- <para>Disable <devicename>sio0</devicename>,
- <devicename>sio1</devicename>,
- <devicename>sio2</devicename> and
- <devicename>sio3</devicename> (all of them). This way
- the &man.sio.4; driver does not get activated — no
- problems.</para>
- </listitem>
-
- <listitem>
- <para>Type exit to continue booting.</para>
- </listitem>
- </orderedlist>
-
- <para>If you want to be able to use your serial ports, you
- will have to build a new kernel with the following
- modification: in
- <filename>/usr/src/sys/dev/sio/sio.c</filename> (or in
- <filename>/usr/src/sys/pc98/cbus/sio.c</filename> for pc98)
- find the one occurrence of the string
- <literal>0x2e8</literal> and remove that string and the
- preceding comma (keep the trailing comma). Now follow the
- normal procedure of building a new kernel.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="kmem-map-too-small">
<para>My system has more than 1 GB of RAM, and I'm
getting panics with <errorname>kmem_map too small</errorname>
@@ -2873,22 +2542,6 @@ quit</programlisting>
</qandaentry>
<qandaentry>
- <question id="brkadrint-illegal-host-access">
- <para>What does the message <errorname>ahc0: brkadrint,
- Illegal Host Access at seqaddr 0x0</errorname> mean?</para>
- </question>
-
- <answer>
- <para>This is a conflict with an Ultrastor SCSI Host
- Adapter.</para>
-
- <para>During the boot process enter the kernel configuration
- menu and disable <devicename>uha0</devicename>, which is
- causing the problem.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="aci0-illegal-cable">
<para>When I boot my system, I get the error <errorname>ahc0:
illegal cable configuration</errorname>. My cabling is
@@ -3380,37 +3033,6 @@ kern.timecounter.hardware: TSC -> i82
</qandaentry>
<qandaentry>
- <question id="boot-read-error">
- <para>Why does &os;'s boot loader display <errorname>Read
- error</errorname> and stop after the BIOS screen?</para>
- </question>
-
- <answer>
- <para>&os;'s boot loader is incorrectly recognizing the hard
- drive's geometry. This must be manually set within
- &man.fdisk.8; when creating or modifying &os;'s
- slice.</para>
-
- <para>The correct drive geometry values can be found within
- the machine's BIOS. Look for the number of cylinders, heads
- and sectors for the particular drive.</para>
-
- <para>Within &man.sysinstall.8;'s fdisk, hit
- <keycap>G</keycap> to set the drive geometry.</para>
-
- <para>A dialog will pop up requesting the number of cylinders,
- heads and sectors. Type the numbers found from the BIOS
- separated by forward slashes. For example, values of 5000
- cylinders, 250 heads, and 60 sectors would be entered as
- <userinput>5000/250/60</userinput>.</para>
-
- <para>Press <keycap>Enter</keycap> to set the values, and hit
- <keycap>W</keycap> to write the new partition table to the
- drive.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="bootmanager-restore">
<para>Another operating system destroyed my Boot Manager. How
do I get it back?</para>
@@ -3524,6 +3146,9 @@ kern.timecounter.hardware: TSC -> i82
unfortunate timing they could cause undesirable effects
ranging from a minor blip in the system's responsiveness to
a complete system lockup.</para>
+
+ <para>For additional information about locking in &os; see
+ &man.locking.9;.</para>
</answer>
</qandaentry>
@@ -3570,7 +3195,7 @@ kern.timecounter.hardware: TSC -> i82
<answer>
<para>The open-source <application><ulink
- url="http://www.openoffice.org">OpenOffice.org</ulink></application>
+ url="http://www.openoffice.org">Apache OpenOffice</ulink></application>
and <application><ulink
url="http://www.libreoffice.org">LibreOffice</ulink></application>
office suites work natively on &os;.</para>
@@ -3975,36 +3600,35 @@ kern.timecounter.hardware: TSC -> i82
<qandaentry>
<question id="minimal-sh">
- <para>Why is <command>/bin/sh</command> so minimal? Why does
- &os; not use <command>bash</command> or another
+ <para>Why is <command>/bin/sh</command> so minimal? Why
+ does &os; not use <command>bash</command> or another
shell?</para>
</question>
<answer>
- <para>Because &posix; says that there shall be such a
- shell.</para>
-
- <para>The more complicated answer: many people need to write
- shell scripts which will be portable across many systems.
- That is why &posix; specifies the shell and utility commands
- in great detail. Most scripts are written in Bourne shell,
- and because several important programming interfaces
- (&man.make.1;, &man.system.3;, &man.popen.3;, and analogues
- in higher-level scripting languages like Perl and Tcl) are
- specified to use the Bourne shell to interpret commands.
- Because the Bourne shell is so often and widely used, it is
- important for it to be quick to start, be deterministic in
- its behavior, and have a small memory footprint.</para>
+ <para>Many people need to write shell scripts which will be
+ portable across many systems. That is why &posix;
+ specifies the shell and utility commands in great detail.
+ Most scripts are written in Bourne shell (&man.sh.1;), and
+ because several important programming interfaces
+ (&man.make.1;, &man.system.3;, &man.popen.3;, and
+ analogues in higher-level scripting languages like Perl
+ and Tcl) are specified to use the Bourne shell to
+ interpret commands. Because the Bourne shell is so often
+ and widely used, it is important for it to be quick to
+ start, be deterministic in its behavior, and have a small
+ memory footprint.</para>
<para>The existing implementation is our best effort at
meeting as many of these requirements simultaneously as we
- can. In order to keep <command>/bin/sh</command> small, we
- have not provided many of the convenience features that
- other shells have. That is why the Ports Collection
- includes more featureful shells like
+ can. In order to keep <command>/bin/sh</command> small,
+ we have not provided many of the convenience features that
+ other shells have. That is why other more
+ featureful shells like
<command>bash</command>, <command>scsh</command>,
- <command>tcsh</command>, and <command>zsh</command>. (You
- can compare for yourself the memory utilization of all these
+ &man.tcsh.1;, and <command>zsh</command> are available.
+ (You can
+ compare for yourself the memory utilization of all these
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-projects
mailing list