[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: documentation bugs to fix

On Thu, Oct 18, 2001 at 01:38:12AM -0400, Adam Di Carlo wrote:
> Chris, can you get documentation bugs 106218 and and 81029 please?

Enclosed please check out a fix for 81029. The bug is pretty old, and the
documentation it asks to incorporate is even older ;-) so these changes
really need someone knowledgeable to comment on their currency and
relevance. I'll wait to commit until peple have a chance to comment.

|  .''`.  |   Debian GNU/Linux: <http://www.debian.org>          |
| : :'  : |   debian-imac: <http://debian-imac.sourceforge.net>  |
| `. `'`  |      Chris Tillman        tillman@azstarnet.com      |
|   `-    |            May the Source be with you                |
Index: documentation/en/appendix.sgml
RCS file: /cvs/debian-boot/boot-floppies/documentation/en/appendix.sgml,v
retrieving revision 1.11
diff -u -r1.11 appendix.sgml
--- documentation/en/appendix.sgml	2001/10/02 06:40:42	1.11
+++ documentation/en/appendix.sgml	2001/10/19 03:48:28
@@ -342,9 +342,40 @@
 null	everything pointed to this device will disappear
 zero	one can endlessly read zeros out of this device
-  </sect>
+<sect1>Setting Up Your Mouse
+The mouse can be used in both the Linux console (gpm) and X windows.
+The preferred configuration / signal flow are:
+mouse => /dev/psaux  => gpm => /dev/gpmdata -> /dev/mouse => X
+         /dev/ttyS0             (repeater)        (symlink)
+         /dev/ttyS1
+Currently, by default the repeater protocol of gpm is set to be ms3 in
+/etc/gpm.conf (which matches with intellimouse for X in
+/etc/X11/XF86Config). An alternative method is to set the repeater
+protocol to be raw while setting X to the original mouse protocol.
+This approach to use gpm even in X has advantages when the mouse is
+unplugged inadvertantly.  Simply restarting gpm with
+user@debian:# /etc/init.d/gpm restart
+will re-connect the mouse in software without restarting X.
+If gpm is disabled or not installed with some reason, make sure to
+set X to read directly from the mouse device such as /dev/psaux.
+For details, refer to the 3-Button Mouse mini-Howto at
+<![ %powerpc [
+For PowerPC, in <file>/etc/X11/XF86Config</file>, set the mouse
+device to "/dev/input/mice". 
 <!-- Keep this comment at the end of the file
 Local variables:
 mode: sgml
Index: documentation/en/post-install.sgml
RCS file: /cvs/debian-boot/boot-floppies/documentation/en/post-install.sgml,v
retrieving revision 1.16
diff -u -r1.16 post-install.sgml
--- documentation/en/post-install.sgml	2001/08/16 23:57:53	1.16
+++ documentation/en/post-install.sgml	2001/10/19 03:48:28
@@ -30,7 +30,9 @@
 clean state.  This chapter contains material to help you get oriented;
 it is not intended to be a tutorial for how to use Debian, but just a
 very brief glimpse of the system for the very rushed.
-    <p>
+ <sect1>Debian Packaging System
 The most important concept to grasp is the Debian packaging system.
 In essence, large parts of your system should be considered under the
 control of the packaging system.  These include:
@@ -50,6 +52,61 @@
 work, but then if you upgrade your <package>perl</package> package,
 the file you put there will be replaced.  Experts can get
 around this by putting packages on ``hold'' in <prgn>dselect</prgn>.
+       One of the best installation methods is apt. You can use it as a
+       method from dselect, or you can use the command line version
+       (info apt-get).  Note apt will also let you merge non-us, main,
+       contrib, and non-free so you can have export-restricted
+       packages as well as standard versions.
+ <sect1>Application Version Management
+       Alternative versions of applications are managed by
+       update-alternatives. You can set your preferred vi by modifying
+       the symlinks in /etc/alternatives/. For example, /usr/bin/vi ->
+       /etc/alternatives/vi -> {nvi, vim, whatever you like}.
+ <sect1>Kernel Image Management
+       The debian way of building a kernel is also somewhat different.
+       Get the kernel-package package, get the kernel source tree
+       (either debian version or standard linux archive kernel will
+       work), install in <file>/usr/src/linux</file> (or symlink to
+       that), and for any non-std modules (i.e., pcmcia) get that
+       source too (debian module sources will install to
+       <file>/usr/src/modules</file>).  Then read
+       <file>/usr/doc/kernel-packages/README.gz</file>.  This method
+       will make a .deb of your kernel source, and, if you have
+       non-standard modules, make a synchronized dependent .deb of
+       those too. It's a better way to manage kernel images;
+       <file>/boot</file> will hold the kernel, the System.map, and a
+       log of the active config file for the build.
+ <sect1>Cron Job Management
+       Only personal cron jobs should be in
+       <file>/var/spool/cron/crontabs</file> on a debian server. Any
+       jobs under the purview of the system administrator should be in
+       <file>/etc</file>, since they are configuration files.  If you
+       have a root cron job for daily, weekly, or nightly runs, put
+       them in <file>/etc/cron.{daily,weekly,monthly}</file>.  These
+       are invoked from <file>/etc/crontab</file>, and will run in
+       alphabetic order, which serializes them.
+       On the other hand, if you have a cron job that (a) needs to run
+       as a special user, or (b) needs to run at a special time or
+       frequency, you can use either <file>/etc/crontab</file>, or,
+       better yet, <file>/etc/cron.d/whatever</file>.  These
+       particular files also have an extra field that allows you to
+       stipulate the user under which the cron job runs.
+       In either case, you just edit the files and cron will notice
+       them automatically. There is no need to run a special command.
+       For more information see cron(8), crontab(5), and
+       <file>/usr/doc/cron/README.Debian</file>.
 <![ %i386 [
   <sect id="reactivating-win">Reactivating DOS and Windows
@@ -112,7 +169,10 @@
 There is lots of useful documentation in <file>/usr/doc</file> as
 well.  In particular, <file>/usr/doc/HOWTO</file> and
-<file>/usr/doc/FAQ</file> contain lots of interesting information.
+<file>/usr/doc/FAQ</file> contain lots of interesting information.  To
+submit bugs, look at <file>/usr/doc/debian/bug*</file>.  To read about
+Debian-specific issues for particular programs, look at
 The <url id="http://&www-debian-org;/"; name="Debian web
 site"> contains a large quantity of documentation about Debian.  In
Index: documentation/en/rescue-boot.sgml
RCS file: /cvs/debian-boot/boot-floppies/documentation/en/rescue-boot.sgml,v
retrieving revision 1.64
diff -u -r1.64 rescue-boot.sgml
--- documentation/en/rescue-boot.sgml	2001/10/14 23:03:34	1.64
+++ documentation/en/rescue-boot.sgml	2001/10/19 03:48:30
@@ -465,7 +465,7 @@
 Open Firmware prompt:
-O >
+0 >
 At the prompt, type
Index: scripts/rootdisk/messages/C/release_notes
RCS file: /cvs/debian-boot/boot-floppies/scripts/rootdisk/messages/C/release_notes,v
retrieving revision 1.8
diff -u -r1.8 release_notes
--- scripts/rootdisk/messages/C/release_notes	2001/10/15 06:52:18	1.8
+++ scripts/rootdisk/messages/C/release_notes	2001/10/19 03:48:31
@@ -18,3 +18,4 @@
 developing the free software concept and the GNU project.
 Please be sure to visit the Debian WWW site: http://www.debian.org/
+You will find an Installation Instructions link on the home page.

Reply to: