From ea149806782a7b8c9f0cf20da99d090884a260da Mon Sep 17 00:00:00 2001
From: gferg <>
Date: Sun, 25 Feb 2001 22:37:07 +0000
Subject: [PATCH] updated
---
LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml | 4 +-
LDP/howto/docbook/HOWTO-INDEX/hwSect.sgml | 2 +-
.../docbook/HOWTO-INDEX/networkingSect.sgml | 2 +-
LDP/howto/linuxdoc/Chroot-BIND-HOWTO.sgml | 118 +++++--
LDP/howto/linuxdoc/Linmodem-HOWTO.sgml | 296 ++++++++----------
5 files changed, 218 insertions(+), 204 deletions(-)
diff --git a/LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml b/LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml
index 1189a757..62b6182e 100644
--- a/LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml
+++ b/LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml
@@ -378,7 +378,7 @@ Chinese software.
Chroot-BIND-HOWTO,
The ideal solution to this dilemma requires a reasonably recent version of
-syslogd> which supports the -a> switch introduced by OpenBSD. Check the
-manpage for your syslogd(8)> to see if you have such a version.
+syslogd> which supports the -a> switch introduced by OpenBSD.
+Check the manpage for your syslogd(8)> to see if you have such a
+version.
If you do, all you have to do is add the switch ``-a
-/chroot/named/dev/log>'' to the command line when you launch syslogd>. On
-systems which use a full SysV-init (which includes most Linux distributions),
+/chroot/named/dev/log>'' to the command line when you launch syslogd>.
+On systems which use a full SysV-init (which includes most Linux distributions),
this is typically done in the file /etc/rc.d/init.d/syslog>. For example,
on my Red Hat Linux system, I changed the line
@@ -475,14 +499,22 @@ You will also have to add or change a few options in your named.conf> to
keep the various directories straight. In particular, you should add (or
change, if you already have them) the following directives in the options>
section:
-
You can go take a nap now ;-).
+ So, you had BIND 8.2.2_P7 all nicely chrooted and tweaked to your taste...
+and then you hear this nasty rumour that there's a remotely-exploitable root
+hole in that version too, and you need to upgrade to 8.2.3 right away. Do
+you have to go through this whole long process to install this new version?
+
+Nope. In fact, you really just need the section on and the first two parts of the section on (installing the binaries outside and
+inside the jail, respectively).
+
+The rest of the HOWTO deals with setting up the jail and other things like
+that, which shouldn't need to be altered between versions of BIND. You can
+just dump the new binaries in over top of the old ones, and you're good to go.
+But don't forget to kill and restart BIND afterwards, or the old, vulnerable
+version will still be running!
+
@@ -514,13 +564,15 @@ I'd like to thank Lonny Selinger <lonny at abyss.za.org>> for
"testing" this HOWTO and making sure that I didn't miss any steps. I'd also
like to thank Chirik <chirik at CastleFur.COM>>, Dwayne Litzenberger
<dlitz at cheerful.com>>, Phil Bambridge <phil.b at
-cableinet.co.uk>>, and others for pointing out errors, omissions, and other
-useful advice to make this HOWTO even better.
+cableinet.co.uk>>, Robert Cole <rcole at metrum-datatape.com>>,
+Colin MacDonald <colinm at telus.net>>, and others for pointing out
+errors, omissions, and providing other useful advice to make this HOWTO even
+better.
-Copyright © Scott Wunsch, 2000. This document may be distributed only
+Copyright © Scott Wunsch, 2000-2001. This document may be distributed only
subject to the terms set forth in the LDP licence at
To emphasize: your best bet under Linux is certainly to get
a true hardware modem. However, if you're stuck with a winmodem, perhaps
@@ -77,8 +76,10 @@ this document can help.
For the most up-to-date information about available Linmodem drivers,
visit
-
-Copyright (c) 2000 by Sean Walbran, Marvin Stodolsky
+Copyright (c) 2000,2001 by Sean Walbran, Marvin Stodolsky
Please freely copy and distribute (sell or give away) this document in
any format. It's requested that corrections and/or comments be fowarded
@@ -172,9 +173,9 @@ Most individual credits are given in the body of the text where appropriate.
A large amount of information contained in this document comes a variety
of great sources such as
-
Special thanks to Mark Spieth (mark(at)digivation.com.au) for
@@ -225,10 +226,11 @@ run on one's preferred operating system.
-At the time of this writing, only a few winmodems will work under
+An ever-growing number of winmodems will work under
Linux. Each chipset for which a driver is known to exist has a
section in this document, below, describing its installation.
-Any other chipset has no known support under Linux.
+Any other chipset has no known support under Linux
+(at least, not known to us).
If you know the precise name of your modem, you can try searching
the large Linux Modem Compatibility
-
-All of the drivers listed here are released as kernel modules; therefore,
+All of the kernel drivers listed here are released as kernel modules; therefore,
you must be sure to have a kernel which supports modules. In addition,
"module version" support should be enabled to aid the use of
kernels and modules which are not version matched, as described further below.
-If you use a kernel from a reasonably recent Linux distribution, module support
+If you use a kernel from a reasonably recent Linux distribution, such module support
is most likely already enabled. If you're compiling the kernel yourself, then you
should already be aware of how to enable modules, via the
-
-This is a newly recognized factor as of October, 2000, and
-should be considered anecdotal until information on further
-hardware/software combinations is gathered. Marv Stodolsky has
-observed that with the binary-only Lucent driver (v5.68), sound
-support must be enabled
-in the kernel (support via sound modules is OK), or else a
-dail-in session utilizing the ltmodem.o driver aborts/hangs
-when the ppp protocol is initiated.
-The combination of OSS software providing all audio support (with a
-kernel without sound compiled in) failed to support the ppp
-protocol through the ltmodem.o driver. How broadly valid these
-"sound" factors for other Linmodems/Audio_cards remains to be clarified.
-
-
If you have an ISA Plug-n-Play modem, you will most likely
@@ -398,6 +384,7 @@ at this point.)
If you wish to know more about your PCI modem
than cat /proc/pci gives, utilities within the software package
pciutils are useful, such as scanpci and lspci.
+In particular, lspci -vv gives lots of nice, useful information.
-
-A version-matched kernel module is inserted using the command
-insmod module_name. If
-the module were compiled under a different kernel than the current one,
+A version-matched kernel module should usually be inserted using the command
+modprobe module_name; modprobe will try to
+insert any other modules on which your module depends (as determined
+by depmod, described below).
+
+A single module can be inserted (without those modules on which it depends)
+using the command insmod module_name.
+If the module were compiled under a different kernel than the current one,
insmod would report the version mismatch and refuse load the module.
One can, however, pass a flag to force the module to load despite the mismatch:
insmod -f module_name. If the kernel interface the
@@ -421,15 +413,8 @@ This is the case with, for example, the ESS modem module esscom.o
which, while compiled under 2.2.12, can be forcibly inserted with later kernels
and will function to a greater or lesser extent up through kernel version 2.2.14
without further changes; beyond 2.2.15, the patch to tty.h described
-below is required. However, even forcing insertion fails for kernels compiled
-from the rapidly maturning 2.4.0-testX sources.
-
-
-
-The command modprobe modulename will insert a module and
-all of the modules required by that module (as determined by depmod,
-described below).
+below is required. However, even forcing insertion fails for kernels
+from the 2.4 series.
-The depmod commands analyses module dependencies.
-The compatility of precompiled modules
-with a running kernel
+The depmod commands analyzes module dependencies.
+The compatility of precompiled modules with a running kernel
can be checked with a command like:
-As of the writing of this document, source code is only available for the Ambient Technology
-driver, with partial source available for the Lucent LT modem. Generally, modules/binaries
+Many of the linmodem drivers are only available as precompiled, binary kernel modules.
+Generally, modules/binaries
transparently function only with the kernel against which they were co-compiled. Therefore,
-getting the precompiled linmodem drivers to work with your particular kernel can be a challenge.
+getting a precompiled linmodem driver to work with your particular kernel could be a challenge.
-Since the
-Linux kernel is a dynamically changing beast, it is very unfortunate that most
+Since the Linux kernel is a dynamically changing beast, it is very unfortunate that many
modem/chip vendors have not yet chosen to release source-code versions of their
-drivers, which would ensure the ability to modify these drivers appropriately as
+drivers, which would ensure your and our ability to modify these drivers appropriately as
kernel source code evolves. Some of the binary modules have been coaxed to function
under some later kernel versions using various tricks, as described below; however,
-even though a module may functional, it is advisable to use them minimally.
+even though a module may be rendered functional, it is advisable to use them minimally.
Quoting an email from Mark Spieth,
"A driver can never work properly if there are unresolved symbols, as it means
@@ -482,7 +465,7 @@ something is not going to work. Furthermore, it means that that something
that would have been called will call something else in the kernel
and this could be anything. This is very bad."
-Therefore, you should be very careful in using binary modules with a kernel
+Therefore, you should be careful in using binary modules with a kernel
of a different version; proceed at your own risk. If you require above all
that your modem function, consider downgrading your kernel to match the
module - this is by no means a ridiculous prospect. Despite these warnings,
@@ -490,11 +473,10 @@ however, many others have used mismatched binary modules and kernels with only m
annoyances ( such as the occasional kernel panic ) using tricks and tools such as
the following.
-
-Mark Spieth has contributed a progressively improved series of "fixscripts",
-a script which edits a binary module so that the version mismatch warning is eliminated.
+Mark Spieth has contributed a progressively improved series of "fixscripts"
+for editing a binary module so that version mismatch warnings are eliminated.
Insertion of the "fixed" module then proceeds without the forcing flag, i.e. simply
insmod module_name. Later versions also rename module symbols
to match those exported by the kernel, so that "Unresolved symbols" errors
@@ -502,7 +484,7 @@ are not returned by the test depmod -e. It must be emphasized that thi
change is almost entirely cosmetic - it is still recommended that the module be used
minimally.
-To use the fixscript on, for example, the binary Lucent module ltmodem.o,
+To use the fixscript on, for example, the (now-deprecated) binary Lucent module ltmodem.o,
make a working directory such as /root/modem.
Obtain the latest fixscript from
+
+IBM has a completely open-source (GPL'ed) driver for the software modem
+in their Thinkpad 600E's available
+
+
This modem enjoys the most support under Linux, in that there exist three different
-driver packages.
+driver packages:
-
+You should obtain the most recent package for your kernel from
+
-The source portion of the installation will depend on which version
-kernel with which you will be using the module. The original code is designed
-for use with Red Hat 6.2's kernel 2.2.14-5.0.
-
-This driver is superseded by version 5.78; however, it may still be of some use in
-special cases.
+This driver is superseded by version 5.78, described above; however,
+it may still be of some use in special cases.
-
Binary drivers can be found at
-
-A Debian-style installation package for kernel 2.2.16 is available
-from Corel at
-
@@ -753,50 +733,26 @@ With the modules in hand, proceed to install as follows:
-There exists a driver at
-
-It will, however, probably not
-work for you - very few people have been successful with this one.
-
-Some things already known about the driver include:
-
-A binary-only, beta driver for the Intel Creatix V.90 HaM
-compiled under kernel 2.2.16 was released to the Linmodems.org
-mailing list in late November, 2000, and is mirrored at
-
-
-
+
+An rpm package with a driver for the 3Com MDP3900V-U modem
+(apparently found in the Dell Dimension L733r) was
+posted to the Linmodems.org mailing list
+(
+
A request for comments was posted by a 3Com official
about the possible demand for a binary-only driver for their miniPCI combination
NIC/winmodem
+
+Ian Stewart
+
@@ -947,9 +903,16 @@ Linux system is below.
Probably not. Please see the section "Which Linmodem hardware is supported?" above,
and check the Linux Modem Compatibility
-
+
+Try setting your BIOS option from "PNP OS" to "non-PNP OS", from "Windows"
+to "Other OS", or the equivalent.
+
+Conexant users: See the Conexant section, above.
@@ -1024,8 +987,8 @@ like kppp will give this error, while an alternative like wvdial
-Lastly, there is the potential relationship with sound support
-mentioned above. Comparing functionality of ltmodem.o with/without sound
+Lastly, there is the potential relationship with sound support.
+Comparing functionality of ltmodem.o with/without sound
support in the kernels, dial-in is OK, but ppp is NOT achieved for the kernel
without sound support.
@@ -1174,4 +1137,3 @@ country_code country_name
-
+