From 6b36aacb164d034b7cebdc0956b3e6ea0308009a Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 22:13:25 -0800 Subject: [PATCH 001/214] correcting several minor DocBook gripes jade:LDP/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml:443:11:E: value of attribute "id" invalid: "7" cannot start a name jade:LDP/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml:468:12:E: document type does not allow element "procedure" here; missing one of "caution", "important", "note", "tip", "warning", "blockquote" start-tag jade:LDP/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml:471:5:E: character data is not allowed here jade:LDP/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml:472:8:E: end tag for "step" which is not finished jade:LDP/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml:474:13:E: document type does not allow element "command" here; missing one of "remark", "title", "synopsis", "cmdsynopsis", "literallayout", "programlisting", "screen", "para", "simpara", "bridgehead" start-tag jade:LDP/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml:475:8:E: end tag for "step" which is not finished jade:LDP/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml:477:5:E: character data is not allowed here jade:LDP/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml:477:52:E: document type does not allow element "command" here; missing one of "remark", "title", "synopsis", "cmdsynopsis", "literallayout", "programlisting", "screen", "para", "simpara", "bridgehead" start-tag jade:LDP/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml:478:8:E: end tag for "step" which is not finished --- .../docbook/Athlon-Powersaving-HOWTO.xml | 34 ++++++++++++------- 1 file changed, 21 insertions(+), 13 deletions(-) diff --git a/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml b/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml index 14aac894..ff5afe11 100644 --- a/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml +++ b/LDP/howto/docbook/Athlon-Powersaving-HOWTO.xml @@ -440,7 +440,7 @@ - + AMD 760MP Powersaving @@ -465,18 +465,26 @@ If you have temperature controlled Fan on your CPU-Heatsink, you could check for the noise level of the Fan to see whether it works or not. After a few idle minutes you give the CPU somthing to do. - - I normaly do it like this: - - get superuser (root) - - - cd /usr/src/linux - - - and give the computer something to do: while true; do make clean; make bzImage; done - - + + + I normaly do it like this: + + + get superuser (root) + + + + + cd /usr/src/linux + + + + + and give the computer something to do: while true; do make clean; make bzImage; done + + + + After about 20 or 30 seconds you should notice that the noise of the fan is getting louder while the fan is getting faster. Don't forget to end the while-loop after some time ( a few minutes) with STRG-C. From a2b96e0f167294385124ee9139da6d274c36f7e2 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 22:15:38 -0800 Subject: [PATCH 002/214] stricter XML handling and a DocBook correction DocBook infraction: now wraps replacing an apostrophe with an ’ --- LDP/howto/docbook/XWindow-User-HOWTO.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/LDP/howto/docbook/XWindow-User-HOWTO.xml b/LDP/howto/docbook/XWindow-User-HOWTO.xml index 9f09eae6..1aecbe0b 100644 --- a/LDP/howto/docbook/XWindow-User-HOWTO.xml +++ b/LDP/howto/docbook/XWindow-User-HOWTO.xml @@ -73,7 +73,7 @@ - + - + @@ -2605,7 +2605,7 @@ Also, BIOS set up, or Linux set up before X starts. So the trick above is one way. There is also a utility available as either numlockx, or - setnumlock, that can be found on the ’Net, if + setnumlock, that can be found on the ’Net, if your distribution does not include one or the other. This can be put in a start up file to turn Numlock on automatically if you would prefer. From f21f00319258a8dce4650bf8a1e72ae3c2a1ea16 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 22:19:11 -0800 Subject: [PATCH 003/214] inserting required url attribute on ulink element --- LDP/howto/docbook/Accessibility-HOWTO.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/LDP/howto/docbook/Accessibility-HOWTO.xml b/LDP/howto/docbook/Accessibility-HOWTO.xml index b69c902a..577bea9f 100644 --- a/LDP/howto/docbook/Accessibility-HOWTO.xml +++ b/LDP/howto/docbook/Accessibility-HOWTO.xml @@ -585,7 +585,7 @@ operating system. More information is available at: and the Linux Accessibility Resource Site (LARS) . -W3C Web Accessibility initiative provides information and links on Web site accessibility. More information is available at: . +W3C Web Accessibility initiative provides information and links on Web site accessibility. More information is available at: their website. From 44b2209aa6cd02e621d057cf9f8346ceaff3b692 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 22:25:41 -0800 Subject: [PATCH 004/214] DocBook validation corrections cannot contain bare name, needs and must have some sort of child, selected --- LDP/howto/docbook/Autodir-HOWTO.xml | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/LDP/howto/docbook/Autodir-HOWTO.xml b/LDP/howto/docbook/Autodir-HOWTO.xml index aed36e43..172097a7 100644 --- a/LDP/howto/docbook/Autodir-HOWTO.xml +++ b/LDP/howto/docbook/Autodir-HOWTO.xml @@ -17,8 +17,14 @@
ramana <> intraperson dot com
- Rahul Sundaram - Machtelt Garrels + + Rahul + Sundaram + + + Machtelt + Garrels + 2004-09-23 @@ -401,7 +407,7 @@ This work is licensed under the Creative Commons Attribution License. To view a Autodir demands some extra requirements from the backup program being used: when the backup is working on the real directory, with corresponding expired virtual directory, and that virtual directory is requested again by an application while the backup is running, the backup process is killed. First a SIGTERM is sent to gracefully stop it. But if it does not shut down in time - and it has one second to do this - a SIGKILL will be sent, which is guaranteed to stop the backup. -Only when the backup has stopped the application is given access to the requested virtual directory. +Only when the backup has stopped the application is given access to the requested virtual directory. Whatever backup is used, it should be able to recover from this signal gracefully, not causing unrecoverable side effects. From 312627189897f8d20bf7c164fe53c1ad07bb9613 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 22:32:41 -0800 Subject: [PATCH 005/214] DocBook validation corrections A cannot contain bare text, but a of a can. --- .../docbook/Bash-Scripting-Introduction-HOWTO.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/LDP/howto/docbook/Bash-Scripting-Introduction-HOWTO.xml b/LDP/howto/docbook/Bash-Scripting-Introduction-HOWTO.xml index 947185d6..11f984f2 100644 --- a/LDP/howto/docbook/Bash-Scripting-Introduction-HOWTO.xml +++ b/LDP/howto/docbook/Bash-Scripting-Introduction-HOWTO.xml @@ -161,13 +161,13 @@ Maintainers: Francis Litterio , - - Nathan Hurst - Jon Abbott - Felix Hudson - Kees van den Broek - Andreas Beck - + + Nathan Hurst + Jon Abbott + Felix Hudson + Kees van den Broek + Andreas Beck + From 2b48e95364dfdc9bf7bf935f5549e1d4c2e7fdfa Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 22:35:44 -0800 Subject: [PATCH 006/214] DocBook validation corrections A cannot directly contain a , so wrapped the elements in --- LDP/howto/docbook/Cryptoloop-HOWTO.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/LDP/howto/docbook/Cryptoloop-HOWTO.xml b/LDP/howto/docbook/Cryptoloop-HOWTO.xml index 85d99bf1..7efb66e8 100644 --- a/LDP/howto/docbook/Cryptoloop-HOWTO.xml +++ b/LDP/howto/docbook/Cryptoloop-HOWTO.xml @@ -285,8 +285,8 @@ email address : cryptoloop@ralfhoelzer.com. and mounted. In order to use util-linux 2.12 with a 2.6 kernel at least the following two patches need to be applied: - Combined losetup patch - Util-linux 2.6 patch + Combined losetup patch + Util-linux 2.6 patch From 64d989718a4536c836bb7e7beb228cdf030af63b Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 22:48:13 -0800 Subject: [PATCH 007/214] DocBook validation corrections Any elements without got a new friend. Replaced two with Removed one spuriously hovering and extraneous '>' --- LDP/howto/docbook/DB2-HOWTO.xml | 116 ++++++++++++++++---------------- 1 file changed, 58 insertions(+), 58 deletions(-) diff --git a/LDP/howto/docbook/DB2-HOWTO.xml b/LDP/howto/docbook/DB2-HOWTO.xml index cbd40a92..7470cd6e 100644 --- a/LDP/howto/docbook/DB2-HOWTO.xml +++ b/LDP/howto/docbook/DB2-HOWTO.xml @@ -174,19 +174,19 @@ - Hardware requirements: + Hardware requirements: - Supported processors - Disk space requirements - Memory requirements + Supported processors + Disk space requirements + Memory requirements - Software requirements: + Software requirements: - Linux distributions - Kernel levels and libraries requirements - Additional software requirements + Linux distributions + Kernel levels and libraries requirements + Additional software requirements @@ -195,10 +195,10 @@ Supported processor architectures - x86 (32-bit processor) - x86–64 (64-bit processor) - POWER™ (any iSeries™ or pSeries® that - supports Linux) + x86 (32-bit processor) + x86–64 (64-bit processor) + POWER™ (any iSeries™ or pSeries® that + supports Linux) @@ -264,23 +264,23 @@ requirements, consider the following points: - Your SWAP space should be at least twice as much as your RAM. + Your SWAP space should be at least twice as much as your RAM. - Additional memory should be allocated for any non-DB2 software - that may be running on your system. + Additional memory should be allocated for any non-DB2 software + that may be running on your system. - Additional memory is necessary to support database clients and - database activity. + Additional memory is necessary to support database clients and + database activity. - These memory requirements will be affected by the size and + These memory requirements will be affected by the size and complexity of your database system, as well as specific performance - requirements. + requirements. - The maximum RAM allowed for a DB2 Express-C installation is 4 GB. + The maximum RAM allowed for a DB2 Express-C installation is 4 GB. @@ -392,18 +392,18 @@ of users and groups: - Installation choices: + Installation choices: - db2setup installation - db2_install installation - DB2 response file installation + db2setup installation + db2_install installation + DB2 response file installation - User and group setup: + User and group setup: - User and group requirements - Creating users + User and group requirements + Creating users @@ -741,32 +741,32 @@ tar zxf db2exc_912_LNX_x86.tar.gz "Next". - On the Select the installation type window, + On the Select the installation type window, select the type of installation you want to perform. You have three - installation options: + installation options: - Typical: 460–560 MB. This option installs and + Typical: 460–560 MB. This option installs and configures most of the DB2 components, using a typical configuration with default values. This option includes all of the core features, along with ODBC support, and commonly used tools such as the Control Center. You can select the "View Features" button to see what components get installed - with this option. + with this option. - Compact: 380–460 MB. This option installs and + Compact: 380–460 MB. This option installs and configures only the basic DB2 components, with minimal configuration performed on your computer. With this option you get the base server and client support, along with Java and SQL procedure support. Again, you can click the "View Features" button for more - information. + information. - Custom: 320–820 MB. This option allows you to install + Custom: 320–820 MB. This option allows you to install only those components that you select; and to create and customize - a basic DB2 instance. + a basic DB2 instance. Make your choice and click "Next". (The remainder @@ -907,10 +907,10 @@ tar zxf db2exc_912_LNX_x86.tar.gz step; DB2 will still record all administration notifications in the log files. Click "Next". - If you specified a new local list for contacts in the previous + If you specified a new local list for contacts in the previous step, then in the Specify a contact for health monitor notification, you can add a name and email address where DB2 Health Center messages will - be sent for any health alerts from DB2 databases. + be sent for any health alerts from DB2 databases. On the Start copying files window, review @@ -2145,12 +2145,12 @@ db2set DB2_DOCPORT=host_port by selecting any of the menu items in the "Help" menu. To invoke the DB2 Information Center from the command line, issue any of these commands: - - db2icdocs - db2help - db2ic - db2cc -ic - + + db2icdocs + db2help + db2ic + db2cc -ic + @@ -2263,12 +2263,12 @@ userdel -r db2fenc1(If you created different user names during Issue one of the launch commands: - - db2icdocs - db2help - db2ic - db2cc -ic - + + db2icdocs + db2help + db2ic + db2cc -ic + @@ -2402,17 +2402,17 @@ db2 => Open a terminal and run 'db2sampl' to create the SAMPLE database Test terminal based commands: - db2 connect to sample - db2 'select * from dept' + db2 connect to sample + db2 'select * from dept' Test DB2 Control Center: - Open the control center with 'db2cc' command - Select the "Advanced" view - Verify the SAMPLE database is present under the "All databases" tab - Look at the contents of one of the SAMPLE database tables and - views (e.g. vphone) + Open the control center with 'db2cc' command + Select the "Advanced" view + Verify the SAMPLE database is present under the "All databases" tab + Look at the contents of one of the SAMPLE database tables and + views (e.g. vphone) Create TOOLS database: @@ -2420,8 +2420,8 @@ db2 => Launch DB2 Task Center: - Create a task that issues a simple query like "connect to sample; select tabname from syscat.tables; connect reset;", schedule to run now - Click on "show results", no errors should exist> + Create a task that issues a simple query like "connect to sample; select tabname from syscat.tables; connect reset;", schedule to run now + Click on "show results", no errors should exist Launch DB2 Journal: You should be able to see the results of the From ff7867ec3afce2275b83dfdfe5b80b43330e9f5e Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 23:01:00 -0800 Subject: [PATCH 008/214] DocBook validation corrections Replace a multibyte endash with a simple hyphen (ASCII 0x2d). Put empty in a few incomplete elements. --- .../Implement-Sys-Call-Linux-2.6-i386.xml | 23 +++++++++++++++---- 1 file changed, 18 insertions(+), 5 deletions(-) diff --git a/LDP/howto/docbook/Implement-Sys-Call-Linux-2.6-i386.xml b/LDP/howto/docbook/Implement-Sys-Call-Linux-2.6-i386.xml index e47ac58f..419cfc6c 100644 --- a/LDP/howto/docbook/Implement-Sys-Call-Linux-2.6-i386.xml +++ b/LDP/howto/docbook/Implement-Sys-Call-Linux-2.6-i386.xml @@ -62,8 +62,12 @@ New user space files, to be created, to test our system call are listed below: -1. testmycall.c – Source file that will call our system call. -2. testmycall.h - Header file.Kernel files to be modifiedsyscall_table.S +1. testmycall.c - Source file that will call our system call. +2. testmycall.h - Header file. +Kernel files to be modified + + +syscall_table.S Full path of the file - /usr/src/linux/arch/i386/kernel/syscall_table.S This file contains system call names. @@ -105,7 +109,12 @@ Add mycall/ to core-y (Search for regex: core-y.*+=). You will be creating this directory. This directory will contain the source file, header file and the Makefile for our system call. -New kernel files/directories to be createdmycall + +New kernel files/directories to be created + + + +mycall Full path of the file - /usr/src/linux/mycall @@ -137,7 +146,12 @@ #####Makefile Start##### obj-y := mycall.o -#####Makefile End#######New user space files, to be created, to test our system calltestmycall.h (new user space header file to be created) +#####Makefile End####### +New user space files, to be created, to test our system call + + + +testmycall.h (new user space header file to be created) testmycall.h @@ -652,4 +666,3 @@ recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software. - From 14d5758d926b2b967328503c48a976b758e8948d Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 23:10:39 -0800 Subject: [PATCH 009/214] DocBook validation corrections cannot contain text directly; wrapping in switching a few elements to with old element has been renamed --- LDP/howto/docbook/Indic-Fonts-HOWTO.xml | 58 ++++++++++++------------- 1 file changed, 29 insertions(+), 29 deletions(-) diff --git a/LDP/howto/docbook/Indic-Fonts-HOWTO.xml b/LDP/howto/docbook/Indic-Fonts-HOWTO.xml index 76f4f51a..d779da47 100644 --- a/LDP/howto/docbook/Indic-Fonts-HOWTO.xml +++ b/LDP/howto/docbook/Indic-Fonts-HOWTO.xml @@ -81,9 +81,9 @@ NCST has written Simpm ( Simple Package Manager ) that takes care of the entire installation process on your system. Simpm carries out the following steps for a binary distribution of the IndiX system: - It reads the names of the files within the distribution by essentially running the command tar -tzpPf package.tgz > .package.list - It saves all these files and the file containing the list using the command tar -czpPf .old.package.tgz .package.list `cat .package.list` - Simpm then extracts the files from the package and installs them using tar -xzpPf package.tgz + It reads the names of the files within the distribution by essentially running the command tar -tzpPf package.tgz > .package.list + It saves all these files and the file containing the list using the command tar -czpPf .old.package.tgz .package.list `cat .package.list` + Simpm then extracts the files from the package and installs them using tar -xzpPf package.tgz Should you wish to go back to the old system state for any reason, you can easily do so using tar -xzpPf .old.package.tgz @@ -268,35 +268,35 @@ To setup Netscape so that it displays Hindi characters: - - Goto, Edit -> Preferences - Select category, Appearance -> Fonts - Select Language encoding "Unicode" - Set Variable-width and Fixed-width fonts to "raghu" - Check button "Always use my font settings, overriding web page font" - + + Goto, Edit -> Preferences + Select category, Appearance -> Fonts + Select Language encoding "Unicode" + Set Variable-width and Fixed-width fonts to "raghu" + Check button "Always use my font settings, overriding web page font" + Also, ensure that the character coding scheme is set to UTF-8 - - Goto, View -> Character Coding - Select "Unicode (UTF-8)" from the list - + + Goto, View -> Character Coding + Select "Unicode (UTF-8)" from the list + Konqueror Konqueror has good support for Unicode. To setup konqueror so that it displays Hindi characters: - - Goto, Settings -> Configure Konqueror - Select "Konqueror Bowser" from the left pan - Goto "Appearance" tab on the right pan - Select charset "iso106460-1" - Set all fonts to "raghu" for this encoding and also set Default encoding to "utf8" - + + Goto, Settings -> Configure Konqueror + Select "Konqueror Bowser" from the left pan + Goto "Appearance" tab on the right pan + Select charset "iso106460-1" + Set all fonts to "raghu" for this encoding and also set Default encoding to "utf8" + @@ -391,8 +391,8 @@ IndiX links - IndiX Homepage - IndiX Download + IndiX Homepage + IndiX Download @@ -401,8 +401,8 @@ The good guys at Centurion Linux have finished work on Exodus GNU/Linux, a 100% Free Software distribution featuring full Hindi language support for GNOME and KDE. The much awaited Exodus GNU/Linux (code named BitterCoffee) is expected to be released in the Indian market shortly. - Centurion Linux Homepage - The Official GNOME i18n Team - India (hindi) + Centurion Linux Homepage + The Official GNOME i18n Team - India (hindi) @@ -410,8 +410,8 @@ Unicode - The official Unicode website - UTF-8 and Unicode FAQ + The official Unicode website + UTF-8 and Unicode FAQ @@ -535,7 +535,7 @@ Last Modified: Nov 16, 2000 --> - + Version 1.1, March 2000 @@ -551,7 +551,7 @@ license document, but changing it is not allowed. - + GNU Free Documentation License From 72cac0c0577e44a74b50bbf2fab7872025b0eed8 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 23:20:57 -0800 Subject: [PATCH 010/214] DocBook validation corrections cannot contain text directly; wrapping in --- LDP/howto/docbook/Linux+Win9x+Grub-HOWTO.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/LDP/howto/docbook/Linux+Win9x+Grub-HOWTO.xml b/LDP/howto/docbook/Linux+Win9x+Grub-HOWTO.xml index f791481e..8be0bc7b 100644 --- a/LDP/howto/docbook/Linux+Win9x+Grub-HOWTO.xml +++ b/LDP/howto/docbook/Linux+Win9x+Grub-HOWTO.xml @@ -64,12 +64,12 @@ This is where GNU GRUB, the GRand Unified Bootloader comes in. It differs from You will need: - A computer with a working installation of Linux. - Enough free disk space for your new Windows partition. - A partition editor such as GNU Parted. - GRUB rpm or source. - A Windows/DOS boot disk with CDROM support and a CD with the Windows 9x install on it, or a bootable Windows 9x install CD. - (Recommended) A Linux boot disk. + A computer with a working installation of Linux. + Enough free disk space for your new Windows partition. + A partition editor such as GNU Parted. + GRUB rpm or source. + A Windows/DOS boot disk with CDROM support and a CD with the Windows 9x install on it, or a bootable Windows 9x install CD. + (Recommended) A Linux boot disk. From 4d4d611d882b097817b50b55478c7dd8428b1ac5 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 23:23:30 -0800 Subject: [PATCH 011/214] DocBook validation corrections becomes The following additional changes were made in DocBook V4.0: artheader was renamed articleinfo; comment was renamed remark; docinfo was broken into a set of other info elements; and bookbiblio, interfacedefinition, and seriesinfo were removed. http://www.docbook.org/tdg/en/html/ref-elements.html --- LDP/howto/docbook/Mail-User-HOWTO.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/LDP/howto/docbook/Mail-User-HOWTO.xml b/LDP/howto/docbook/Mail-User-HOWTO.xml index 2aff1833..69230106 100644 --- a/LDP/howto/docbook/Mail-User-HOWTO.xml +++ b/LDP/howto/docbook/Mail-User-HOWTO.xml @@ -674,7 +674,7 @@ a memory. Mail HOWTO" to avoid a collision with Guylhem Aznar's Mail HOWTO, which will become the Mail Administrator HOWTO. - + 3.4 @@ -716,7 +716,7 @@ which will become the Mail Administrator HOWTO. - + From 9fafdcd30afc59cd85a3d828fd3f005e109d4810 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 23:25:53 -0800 Subject: [PATCH 012/214] fixing probable input error -> ~ the URL http://www.chiark.greenend.org.uk/sgtatham/putty/ does not load and also does not make sense, however, at http://www.chiark.greenend.org.uk/~sgtatham/putty/ there is software --- LDP/howto/docbook/Mock-Mainframe.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/LDP/howto/docbook/Mock-Mainframe.xml b/LDP/howto/docbook/Mock-Mainframe.xml index 432cce55..231c6955 100644 --- a/LDP/howto/docbook/Mock-Mainframe.xml +++ b/LDP/howto/docbook/Mock-Mainframe.xml @@ -1533,7 +1533,7 @@ operation system: Any program that lets you log in via telnet closed networks) or ssh (everywhere else) will do. Microsoft Windows includes a telnet client that is best described as rudimentary; for serious work, try a free Win32 implementation such as Simon Tathamt's -PuTTY http://www.chiark.greenend.org.uk/sgtatham/putty/. Apple users with Mac +PuTTY http://www.chiark.greenend.org.uk/~sgtatham/putty/. Apple users with Mac OS X should have no problems with their clients. From d909acc45c3964b78ef5293c0ca2aae3dac8bfb2 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 23:32:47 -0800 Subject: [PATCH 013/214] DocBook validation corrections became before DocBook V4.1; not sure how this validated before --- LDP/howto/docbook/Partition-Rescue.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/LDP/howto/docbook/Partition-Rescue.xml b/LDP/howto/docbook/Partition-Rescue.xml index 76d48fb4..61baa63c 100644 --- a/LDP/howto/docbook/Partition-Rescue.xml +++ b/LDP/howto/docbook/Partition-Rescue.xml @@ -1,4 +1,4 @@ -
Partition-Rescue12008-11-24 09:27:50jddmainly title change in the wiki"Partition-Rescue HOWTO" - Jean-Daniel Dodin
Revision HistoryRevision V4.1 - 2008-11-24 - Revised by jdd Title fix (the wiki have to get the exact name of the HOWTO) Revision v4 - 2008-08-29 - Revised by: jdd Major update - First complete revised wiki version Revision v3.7 - 2008-05-30 - Revised by: rm Minor update - lots of little punctuation, spelling, usage, and grammar nits :-) Revision v3.6 - 2008-05-25 - Revised by: jdd Major update - LDP wiki - addition about logical partitions Revision v3.5 - 2003-10-31 - Revised by: jdd Major update - new licence - some fixes in addresses - vi use :-) Revision v3.4 - 2002-08-22 - Revised by: jdd Minor update related only with docbook Revision v3.3 - 2001-11-17 - Revised by: jdd Minor update - docbook & revision history - emacs use. Revision v3.2 - 2001-09-25 - Revised by: jdd Major update. Whow! My disk is empty! My Linux is gone! If you have or fear to have one day or another such a problem, read this...
Beginning
What's inThis HOWTO addresses only the "lost partition table" problem. This can be when: you have no more access to your computer, with the "no operating system" message; you have installed a new system (i.e., MS Windows) and you see no more Linux, and MS Windows takes up all the capacity of the disk; you have just partitioned the wrong drive with fdisk (for example, in the process of changing your hard drive). Here, you will learn that, if you know the right thing and do it, Linux comes usually safe from such things. MS Windows can, but it's luckier. We will first see what you can do before the problem to ease future recovery, and what you must do after to recover. There is little to do to prevent from erasing a disk; usually this is done by automatic MS Windows or Linux-install ill-behaved programs or users' mistakes - nothing can be done to prevent this, except care, but you are already careful, aren't you? It can also be done by the use of MS-DOS/Windows fdisk. Avoid it as most as you can, but you probably can't. I have done this many times, on my computer and on other guys' computers, and restored Linux most of the time and MS Windows sometimes. I wish you luck!
What to do right now?If you don't have any problem yet, if you read this by curiosity or are just seeking information, and you are on a running Linux system, do immediately the following : open a root terminal or xterm; key in /sbin/fdisk -l (that last character being l for Lima). Then do fdisk -u -l; You will be gratified to see a list of all current partitions, on all disks present on your computer. The second one gives the listing in units of sectors, in place of cylinders, and this is sometimes necessary. Write this back on paper (or do "/sbin/fdisk -l | lpr" and "/sbin/fdisk -u -l | lpr" to print it) and save it in a safe place for future use. If you are not the system administrator, you should not be concerned by the problem, and can stop reading this.
Legal stuffThis HOWTO is Copyright (c) 2000-2008 by Jean-Daniel Dodin. As of November 2003, the licence is LGPL. I am not responsible of any damage on any computer as a result of anyone reading this HOWTO. If you do any damage, it is YOUR fault, NOT MINE! Be careful when partitioning disks, and don't make any mistakes, because it can be fatal! Backup all your important data and check that everything you do is correct! What is described here worked on my computer, but it may or may not work on your computer. Although it should work for everyone, I can't guarantee anything. This is the last warning you get: BACKUP IMPORTANT DATA! Or, to put it concisely: Use at your own risk!
What do I need to know right now?You need to know that, in case of any major problem with your hard disk, you need to stop using it in write mode, at least until the time for you to understand what's happening. Information there is very volatile... If ever, one morning, awaking, your computer says "can't load, no system installed", you must not begin reinstalling all the stuff. If you have MS Windows installed, I can't promise you can recover your data, but it's likely you will recover all your Linux stuff, provided it's not located too low (near the beginning of the disk) in the disk structure. This is because some MS Windows viruses erase the very first disk cylinder, whatever is on. However I didn't ever experiment with such viruses, and can't say for sure. Try recovering, anyway. You must also know that I give you all this information only for this - information purposes. Neither I nor any other people but you can be held responsible for any problem your data can have using this info. There are too many different systems on the world for anybody being able to promise anything. I can only wish you luck and hope that you, like me, will be happy recovering data.
Technical info
DisksA hard disk is made of sectors numbered from 0 to the max. dmesg gives, for example: CHS means Cylinders, Heads, Sectors. 523*255*63=8401995 sectors of 512 bytes, thus the 4103 MB. This is only a logical map; it's not necessarily what is written on the disk cover (except for the total size). The true size of the sectors is of no interest for us, given that we don't want to modify anything, but merely wish to restore a previous state. For us, the default size given by fdisk is all right. The size seen by the system is directly dependent on the work of the BIOS (Basic Input/Output System - the PC's ROM). The mode of the hard disk indicated in the BIOS is essential. On a new disk, it's better to use BIOS automatic hard disk recognition and say "yes". Anyway, any modification at this level may destroy all the data of the disk, so don't play with this without essential reason. This is probably what your disk already uses, so don't be afraid.
PartitionsDisk are now huge -- 500 GB drives are not rare -- so it's not really handy to have all this stuff packed in only one part. Only MS Windows does so, and, if you use Linux, maybe it's because you are aware of how inefficient the other is. So a hard disk is usually cut in some pieces called "partitions" (see the Partition HOWTO for details, also read README.fdisk on the web or on your disk - location vary). Let's get a look at (part of) my own print of fdisk -l :
Partition-Rescue12008-11-24 09:27:50jddmainly title change in the wiki"Partition-Rescue HOWTO" - Jean-Daniel Dodin
Revision HistoryRevision V4.1 - 2008-11-24 - Revised by jdd Title fix (the wiki have to get the exact name of the HOWTO) Revision v4 - 2008-08-29 - Revised by: jdd Major update - First complete revised wiki version Revision v3.7 - 2008-05-30 - Revised by: rm Minor update - lots of little punctuation, spelling, usage, and grammar nits :-) Revision v3.6 - 2008-05-25 - Revised by: jdd Major update - LDP wiki - addition about logical partitions Revision v3.5 - 2003-10-31 - Revised by: jdd Major update - new licence - some fixes in addresses - vi use :-) Revision v3.4 - 2002-08-22 - Revised by: jdd Minor update related only with docbook Revision v3.3 - 2001-11-17 - Revised by: jdd Minor update - docbook & revision history - emacs use. Revision v3.2 - 2001-09-25 - Revised by: jdd Major update. Whow! My disk is empty! My Linux is gone! If you have or fear to have one day or another such a problem, read this...
Beginning
What's inThis HOWTO addresses only the "lost partition table" problem. This can be when: you have no more access to your computer, with the "no operating system" message; you have installed a new system (i.e., MS Windows) and you see no more Linux, and MS Windows takes up all the capacity of the disk; you have just partitioned the wrong drive with fdisk (for example, in the process of changing your hard drive). Here, you will learn that, if you know the right thing and do it, Linux comes usually safe from such things. MS Windows can, but it's luckier. We will first see what you can do before the problem to ease future recovery, and what you must do after to recover. There is little to do to prevent from erasing a disk; usually this is done by automatic MS Windows or Linux-install ill-behaved programs or users' mistakes - nothing can be done to prevent this, except care, but you are already careful, aren't you? It can also be done by the use of MS-DOS/Windows fdisk. Avoid it as most as you can, but you probably can't. I have done this many times, on my computer and on other guys' computers, and restored Linux most of the time and MS Windows sometimes. I wish you luck!
What to do right now?If you don't have any problem yet, if you read this by curiosity or are just seeking information, and you are on a running Linux system, do immediately the following : open a root terminal or xterm; key in /sbin/fdisk -l (that last character being l for Lima). Then do fdisk -u -l; You will be gratified to see a list of all current partitions, on all disks present on your computer. The second one gives the listing in units of sectors, in place of cylinders, and this is sometimes necessary. Write this back on paper (or do "/sbin/fdisk -l | lpr" and "/sbin/fdisk -u -l | lpr" to print it) and save it in a safe place for future use. If you are not the system administrator, you should not be concerned by the problem, and can stop reading this.
Legal stuffThis HOWTO is Copyright (c) 2000-2008 by Jean-Daniel Dodin. As of November 2003, the licence is LGPL. I am not responsible of any damage on any computer as a result of anyone reading this HOWTO. If you do any damage, it is YOUR fault, NOT MINE! Be careful when partitioning disks, and don't make any mistakes, because it can be fatal! Backup all your important data and check that everything you do is correct! What is described here worked on my computer, but it may or may not work on your computer. Although it should work for everyone, I can't guarantee anything. This is the last warning you get: BACKUP IMPORTANT DATA! Or, to put it concisely: Use at your own risk!
What do I need to know right now?You need to know that, in case of any major problem with your hard disk, you need to stop using it in write mode, at least until the time for you to understand what's happening. Information there is very volatile... If ever, one morning, awaking, your computer says "can't load, no system installed", you must not begin reinstalling all the stuff. If you have MS Windows installed, I can't promise you can recover your data, but it's likely you will recover all your Linux stuff, provided it's not located too low (near the beginning of the disk) in the disk structure. This is because some MS Windows viruses erase the very first disk cylinder, whatever is on. However I didn't ever experiment with such viruses, and can't say for sure. Try recovering, anyway. You must also know that I give you all this information only for this - information purposes. Neither I nor any other people but you can be held responsible for any problem your data can have using this info. There are too many different systems on the world for anybody being able to promise anything. I can only wish you luck and hope that you, like me, will be happy recovering data.
Technical info
DisksA hard disk is made of sectors numbered from 0 to the max. dmesg gives, for example: CHS means Cylinders, Heads, Sectors. 523*255*63=8401995 sectors of 512 bytes, thus the 4103 MB. This is only a logical map; it's not necessarily what is written on the disk cover (except for the total size). The true size of the sectors is of no interest for us, given that we don't want to modify anything, but merely wish to restore a previous state. For us, the default size given by fdisk is all right. The size seen by the system is directly dependent on the work of the BIOS (Basic Input/Output System - the PC's ROM). The mode of the hard disk indicated in the BIOS is essential. On a new disk, it's better to use BIOS automatic hard disk recognition and say "yes". Anyway, any modification at this level may destroy all the data of the disk, so don't play with this without essential reason. This is probably what your disk already uses, so don't be afraid.
PartitionsDisk are now huge -- 500 GB drives are not rare -- so it's not really handy to have all this stuff packed in only one part. Only MS Windows does so, and, if you use Linux, maybe it's because you are aware of how inefficient the other is. So a hard disk is usually cut in some pieces called "partitions" (see the Partition HOWTO for details, also read README.fdisk on the web or on your disk - location vary). Let's get a look at (part of) my own print of fdisk -l : This is my second hard disk, tied to guesses and tries. (The first is too simple to be interesting.) /dev/hdb is my second ide disk (slave on the primary interface), /dev/hdb1 is the first primary partition, running from the first (1) block to the block 153. There can be four such primary partitions. If one wants more than 4, one of them must be repurposed as an "extended" partition (not necessarily the fourth), and all other partitions are "logical" and are located inside the extended one. Notice that partition number 5 and partition number 4 have the same beginning. Number five is logical, number 4 extended. Logical partitions' numbering always begins at 5, even if there are only 2 primary partitions. Here's the fdisk -u -l listing of an other disk: This is my second hard disk, tied to guesses and tries. (The first is too simple to be interesting.) /dev/hdb is my second ide disk (slave on the primary interface), /dev/hdb1 is the first primary partition, running from the first (1) block to the block 153. There can be four such primary partitions. If one wants more than 4, one of them must be repurposed as an "extended" partition (not necessarily the fourth), and all other partitions are "logical" and are located inside the extended one. Notice that partition number 5 and partition number 4 have the same beginning. Number five is logical, number 4 extended. Logical partitions' numbering always begins at 5, even if there are only 2 primary partitions. Here's the fdisk -u -l listing of an other disk: Don't worry about the French part, I'm French ... look at your own disk listing. Of course, numbers are bigger.
Why is there a problem?The problem is that all installed operating systems must share the disks, and, since at start, the BIOS only scans the first one, there must be a so called "partition table" at the very beginning of this disk. This partition table is located in the Master Boot Record (MBR), side by side with the boot loader. Any misuse of the MBR by any of the OS's leads to problems. When trying to install any system, a "yes" answer at a question like "automatic partitioning?" is likely to give problems... This is specially true with MS Windows, and especially with custom MS Windows installations made by special makes' PCs (when no true "Windows" CD is included, as with many laptops). But it's also true with some "smart" (not so smart!) Linux installation programs included with some distributions (hopefully this is not more the case in 2008).
Solving the problemPlease, beware! Following the explanations given here will lead you to revert back to a previous system, losing all your recent changes, if any! You must choose...
The simpler caseAll is simple if you have at hand: A disk (floppy, usb key or CD) able to start Linux by itself with fdisk available - most rescue disks of any distribution can do that; A paper with the fdisk -l and fdisk -u -l content written down. It's enough to: Start Linux; Start fdisk /dev/hda (or whatever is the disk to rescue); Use fdisk to delete (d option) all the existing partitions on the damaged disk; Use fdisk to create all the primary (1 - 4) partitions mentioned on the paper; Give them the appropriate tag (t option) : 82 is for Linux swap, 83 for Linux main (L gives you the list), 5 is extended and must be done before creating logical partitions, c is MS Windows FAT32, and f is MS Windows extended when 6 is MS Windows FAT16. Create any logical partition. On my SUSE installation and any time I had to do this for other people, this has produced good results. However, I said that some fdisks may cut partitions on a sector basis, not cylinder. So the fdisk -u -l version of the paper. For using the fdisk -u -l listing one must start fdisk -u :-). In my opinion, using sector limit is a very bad idea, but it may have a real use I'm not aware of. The problem is that, with cylinder limit, it's easy to guess even if you don't have paper. With sector one, there are many more guesses... fdisk is a small and very smart programs. There are many other makes of fdisk, but I always prefer the bare bones one. (I speak of Linux ones, of course, not the others....) Be aware that fdisk doesn't write anything to disk before you hit w and return. If you fear a mistake, hit q (quit) or Ctrl C (^C) to quit safe without saving changes. When your new partition table is written, start your Linux. It's possible you might not be able to do that as usual: lilo/grub may have been damaged also, and you thus may need a boot floppy or CD. Choose the option "booting the installed partition". If you are accustomed to booting with lilo, as soon as you are logged in as root, key in "lilo" and hit return to reinstall your favourite boot loader. Right now, I'm not sure that the same thing is as easy with GRUB, but it should not be very difficult, either. Your Linux should be all here; test it. Try, also, to start MS Windows if applicable. If you can't, there is a (very small) chance you can read your data from Linux, maybe with a raw sector-by-sector read. If you can identify the disk sectors your data is on, using dd you can copy it to a file. This is wise for text only. This recovery is NOT in the scope of this mini-HOWTO.
A not-so-simple case
By handThis is when the previous case can't be used, for lack of fdisk paper, or if it won't work for use of an out-of-date one. Warning You can only try primary partitions with no fear. logical partition uses ordinary sectors of the disk to store their own housekeeping data, so, each time you write some logical partition with fdisk, you write some sectors, erasing the data content, if any. There is still a chance you don't have any data there or the data is unimportant, but, the less often you do such tries, the better. First, be aware that as soon as you don't write to the disk (except with fdisk), you don't erase your data, so that you can use a block-by-block try. That is you need to know the beginning of the partition to start it. If, say a 153 doesn't fit, try a 154, and so on. This can be tiresome, but, if you remember approximately the size of the Linux partition, there is a chance to win.
Linux's own info and other hacks
KernelIf you just destroyed your own partition table, but have not rebooted Linux: Don't reboot! You can still retrieve the partition information stored in the Kernel: cat /proc/partitions gives major minor #blocks name 3 0 19535040 hda 3 1 2096451 hda1 3 2 4980150 hda2 3 3 1 hda3 <--- this marks an extended partition 3 5 4980118 hda5 3 6 4972086 hda6
hdparmhdparm -g /dev/hda1/dev/hda1 : geometry = 2432/255/63, sectors = 4192902, start = 63 You'll need to do a few unit conversions. "blocks" are usually 1K in length. "Sectors" are disk sectors, often 512 bytes. But usually the disk partitioning tools work in units of cylinders. (Here, 255*63=16065 sectors.) Using this information, you can build a new partition table.
I know the start of the partition, but not the end.If you know the start of a Linux partition, but not the end, you can still mount it, and learn about the structure. Set the partition table start correctly, and set the end to something very large. See if you guessed correctly with: You can even mount the partition and check the size: Don't worry about the French part, I'm French ... look at your own disk listing. Of course, numbers are bigger.
Why is there a problem?The problem is that all installed operating systems must share the disks, and, since at start, the BIOS only scans the first one, there must be a so called "partition table" at the very beginning of this disk. This partition table is located in the Master Boot Record (MBR), side by side with the boot loader. Any misuse of the MBR by any of the OS's leads to problems. When trying to install any system, a "yes" answer at a question like "automatic partitioning?" is likely to give problems... This is specially true with MS Windows, and especially with custom MS Windows installations made by special makes' PCs (when no true "Windows" CD is included, as with many laptops). But it's also true with some "smart" (not so smart!) Linux installation programs included with some distributions (hopefully this is not more the case in 2008).
Solving the problemPlease, beware! Following the explanations given here will lead you to revert back to a previous system, losing all your recent changes, if any! You must choose...
The simpler caseAll is simple if you have at hand: A disk (floppy, usb key or CD) able to start Linux by itself with fdisk available - most rescue disks of any distribution can do that; A paper with the fdisk -l and fdisk -u -l content written down. It's enough to: Start Linux; Start fdisk /dev/hda (or whatever is the disk to rescue); Use fdisk to delete (d option) all the existing partitions on the damaged disk; Use fdisk to create all the primary (1 - 4) partitions mentioned on the paper; Give them the appropriate tag (t option) : 82 is for Linux swap, 83 for Linux main (L gives you the list), 5 is extended and must be done before creating logical partitions, c is MS Windows FAT32, and f is MS Windows extended when 6 is MS Windows FAT16. Create any logical partition. On my SUSE installation and any time I had to do this for other people, this has produced good results. However, I said that some fdisks may cut partitions on a sector basis, not cylinder. So the fdisk -u -l version of the paper. For using the fdisk -u -l listing one must start fdisk -u :-). In my opinion, using sector limit is a very bad idea, but it may have a real use I'm not aware of. The problem is that, with cylinder limit, it's easy to guess even if you don't have paper. With sector one, there are many more guesses... fdisk is a small and very smart programs. There are many other makes of fdisk, but I always prefer the bare bones one. (I speak of Linux ones, of course, not the others....) Be aware that fdisk doesn't write anything to disk before you hit w and return. If you fear a mistake, hit q (quit) or Ctrl C (^C) to quit safe without saving changes. When your new partition table is written, start your Linux. It's possible you might not be able to do that as usual: lilo/grub may have been damaged also, and you thus may need a boot floppy or CD. Choose the option "booting the installed partition". If you are accustomed to booting with lilo, as soon as you are logged in as root, key in "lilo" and hit return to reinstall your favourite boot loader. Right now, I'm not sure that the same thing is as easy with GRUB, but it should not be very difficult, either. Your Linux should be all here; test it. Try, also, to start MS Windows if applicable. If you can't, there is a (very small) chance you can read your data from Linux, maybe with a raw sector-by-sector read. If you can identify the disk sectors your data is on, using dd you can copy it to a file. This is wise for text only. This recovery is NOT in the scope of this mini-HOWTO.
A not-so-simple case
By handThis is when the previous case can't be used, for lack of fdisk paper, or if it won't work for use of an out-of-date one. Warning You can only try primary partitions with no fear. logical partition uses ordinary sectors of the disk to store their own housekeeping data, so, each time you write some logical partition with fdisk, you write some sectors, erasing the data content, if any. There is still a chance you don't have any data there or the data is unimportant, but, the less often you do such tries, the better. First, be aware that as soon as you don't write to the disk (except with fdisk), you don't erase your data, so that you can use a block-by-block try. That is you need to know the beginning of the partition to start it. If, say a 153 doesn't fit, try a 154, and so on. This can be tiresome, but, if you remember approximately the size of the Linux partition, there is a chance to win.
Linux's own info and other hacks
KernelIf you just destroyed your own partition table, but have not rebooted Linux: Don't reboot! You can still retrieve the partition information stored in the Kernel: cat /proc/partitions gives major minor #blocks name 3 0 19535040 hda 3 1 2096451 hda1 3 2 4980150 hda2 3 3 1 hda3 <--- this marks an extended partition 3 5 4980118 hda5 3 6 4972086 hda6
hdparmhdparm -g /dev/hda1/dev/hda1 : geometry = 2432/255/63, sectors = 4192902, start = 63 You'll need to do a few unit conversions. "blocks" are usually 1K in length. "Sectors" are disk sectors, often 512 bytes. But usually the disk partitioning tools work in units of cylinders. (Here, 255*63=16065 sectors.) Using this information, you can build a new partition table.
I know the start of the partition, but not the end.If you know the start of a Linux partition, but not the end, you can still mount it, and learn about the structure. Set the partition table start correctly, and set the end to something very large. See if you guessed correctly with: You can even mount the partition and check the size: This won't directly tell you where the next partition starts, because of rounding issues. But it can help you get close. Be sure to use the "-n" and "-r" flags, to treat the system as read-only!!!
Other places partition information is storedSome distributions record partition information in a file. Of course, you probably won't be able to get to this file when you need it. But, just in case: (if you are aware of others, please e-mail the maintainer of this document)
gpartBut there is a better way if you can still access the Net or have "gpart" on hand. gpart is available in most distribution, at or directly from . Please note that gpart is not gparted - the GNOME partition editor. "gpart - guess PC-type hard disk partitions" as the first line of the it's man page states (man gpart). And goes on to say: "gpart tries to guess which partitions are on a hard disk. If the primary partition table has been lost, overwritten, or destroyed, the partitions still exist on the disk, but the operating system cannot access them." This is exactly what we need. gpart is a very useful tool. The problem is the following: the first block of any partition is marked. But it's never "unmarked" if not overwritten. So, many "first partition block" exist on an old disk, and gpart tries to do its best guessing what is the good one. In fact, it's not too difficult to try; nothing is written on the disk by gpart. Here is the result of gpart on the previously seen disk, hdb: gpart /dev/hdb Begin scan... Possible partition(Linux ext2), size(1200Mb), offset(0Mb) @@ -45,4 +45,4 @@ type: 131(0x83)(Linux ext2 filesystem) size: 1004mb #s(2056256) s(4919781-6976036) chs: (306/61/49)-(434/60/47)d (306/61/49)-(434/60/47)r Primary partition(4) -type: 000(0x00)(unused) size: 0mb #s(0) s(0-0) chs: (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r]]>As you see, primary partition can be recovered, but, for extended ones, it's still to be done. DOS partitions are labelled "Windows NTFS" because they were created while trying to install MS Windows 2000 (a very awful experience in year 2000!). The "invalid" one is, in fact the extended partition. With this, one can use fdisk and try re-creating the partition table. (Remember, this is risk-free given the original one is already lost.) gpart is updated on a weekly basis :-) and so new versions may be more powerful than I know.
Recovering partitions inside an extended partitionExtended partition information is scattered on the disk, not stored with the primary partition. To recover these often requires more work. The process is: Scan for the start of the first partition (using gpart's -k option); Create a temporary primary partition entry with the true start position and a fake end position. (This may drive you to delete an actual primary partition if no one is available - this is risk free if you don't reuse the sectors of the deleted partition); Use "e2fsk -n", "mount -r", and "df" to determine the true end point. Write this value down (warning: read the man page for each program mentioned, and use the read-only options; you do not want to write to your disk until all partitions are in the correct place); Repeat this process for each partition to be recovered; Build a complete new correct partition table.
If your hard drive has errorsIf your hard drive has errors, you may have real trouble mounting, checking, or using data. (The drive read errors get in the way.) Gpart may not even find it. But if you know the start of the partition, you can easily copy the data to a temporary file stored on a different drive. Sectors with read errors will usually be set to zero by this process: Copy the partition data to a file. You must know the start block of the partition; XXX is the sector start and YYY the sector count (can be guessed). Mount the file as a loop file system. Use dd_rescue if the disk is really badly damaged.
The rich man's casePartition Magic is a commercial (and proprietary) software product, not so cheap given the little use one can have (approx a hundred bucks in France), but with a very high reputation all around there. However, I never use it and will not rate it. It's said to be able to do anything with partitions, including restoring them. Ralf's original partition-rescue mini HOWTO was essentially based around the use of Partition Magic, so I assume it's a very good solution, if you have valuable data on your Linux partition and little Linux capability. However, there are now much more recent releases of Partition Magic and I think it's better for you to read the manual.
PMagicPartedMagic if the tool of choice for any partition work, including recovery. Extremely good product (and open, of course). Read the HOWTO anyway, because you may need it to prevent disasters, but all the tools are on pmagic, this is the best recovery cd ever...
References
AuthorsThe author of this HOWTO is Jean-Daniel Dodin. I can be joined at My masqued e-mail or simply searching "Jean-Daniel Dodin" on Google :-). My Web site is at []. I want to thank Rolf Klausen, who wrote the previous partition-rescue mini HOWTO. Even if I rewrote it almost entirely, he had first the good idea. Every other member of the Linux community, and everybody who supports Linux and writes documentation and programs for Linux, and all the authors of the LDP, and virtually any person involved in anything which has to do with Linux. Particularly Linus B. Torvalds - he is The King !!! I want also to thank Michail Brzitwa (see Web site in the text) for writing gpart ! Bryce Nesbitt <bryce at obviously dot com> did a very good job, "Linux's own info" is from him as are some minor enhancements.
Most recent versionThe most recent version of this HOWTO will be found on the tldp wiki
\ No newline at end of file +type: 000(0x00)(unused) size: 0mb #s(0) s(0-0) chs: (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r]]>As you see, primary partition can be recovered, but, for extended ones, it's still to be done. DOS partitions are labelled "Windows NTFS" because they were created while trying to install MS Windows 2000 (a very awful experience in year 2000!). The "invalid" one is, in fact the extended partition. With this, one can use fdisk and try re-creating the partition table. (Remember, this is risk-free given the original one is already lost.) gpart is updated on a weekly basis :-) and so new versions may be more powerful than I know.
Recovering partitions inside an extended partitionExtended partition information is scattered on the disk, not stored with the primary partition. To recover these often requires more work. The process is: Scan for the start of the first partition (using gpart's -k option); Create a temporary primary partition entry with the true start position and a fake end position. (This may drive you to delete an actual primary partition if no one is available - this is risk free if you don't reuse the sectors of the deleted partition); Use "e2fsk -n", "mount -r", and "df" to determine the true end point. Write this value down (warning: read the man page for each program mentioned, and use the read-only options; you do not want to write to your disk until all partitions are in the correct place); Repeat this process for each partition to be recovered; Build a complete new correct partition table.
If your hard drive has errorsIf your hard drive has errors, you may have real trouble mounting, checking, or using data. (The drive read errors get in the way.) Gpart may not even find it. But if you know the start of the partition, you can easily copy the data to a temporary file stored on a different drive. Sectors with read errors will usually be set to zero by this process: Copy the partition data to a file. You must know the start block of the partition; XXX is the sector start and YYY the sector count (can be guessed). Mount the file as a loop file system. Use dd_rescue if the disk is really badly damaged.
The rich man's casePartition Magic is a commercial (and proprietary) software product, not so cheap given the little use one can have (approx a hundred bucks in France), but with a very high reputation all around there. However, I never use it and will not rate it. It's said to be able to do anything with partitions, including restoring them. Ralf's original partition-rescue mini HOWTO was essentially based around the use of Partition Magic, so I assume it's a very good solution, if you have valuable data on your Linux partition and little Linux capability. However, there are now much more recent releases of Partition Magic and I think it's better for you to read the manual.
PMagicPartedMagic if the tool of choice for any partition work, including recovery. Extremely good product (and open, of course). Read the HOWTO anyway, because you may need it to prevent disasters, but all the tools are on pmagic, this is the best recovery cd ever...
References
AuthorsThe author of this HOWTO is Jean-Daniel Dodin. I can be joined at My masqued e-mail or simply searching "Jean-Daniel Dodin" on Google :-). My Web site is at []. I want to thank Rolf Klausen, who wrote the previous partition-rescue mini HOWTO. Even if I rewrote it almost entirely, he had first the good idea. Every other member of the Linux community, and everybody who supports Linux and writes documentation and programs for Linux, and all the authors of the LDP, and virtually any person involved in anything which has to do with Linux. Particularly Linus B. Torvalds - he is The King !!! I want also to thank Michail Brzitwa (see Web site in the text) for writing gpart ! Bryce Nesbitt <bryce at obviously dot com> did a very good job, "Linux's own info" is from him as are some minor enhancements.
Most recent versionThe most recent version of this HOWTO will be found on the tldp wiki
From a80c80cf84c6e95bd60a6920b8d94e4dcfd868cc Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 23:39:11 -0800 Subject: [PATCH 014/214] DocBook validation corrections corrected placement of one which was foiling validation (and also aligned some text visually) became because they could not descend directly from --- LDP/howto/docbook/Partition.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/LDP/howto/docbook/Partition.xml b/LDP/howto/docbook/Partition.xml index dad2e0c7..1e3ab2dc 100644 --- a/LDP/howto/docbook/Partition.xml +++ b/LDP/howto/docbook/Partition.xml @@ -1266,13 +1266,14 @@ partitions can be sub-divided. p print the partition table + n create a new partition - d - delete a partition + d + delete a partition q @@ -1283,7 +1284,6 @@ partitions can be sub-divided. write the new partition table and exit - Changes you make to the partition table do not take effect until you issue the write (w) command. Here is a sample partition table: @@ -1807,7 +1807,7 @@ LABEL=/usr /usr ext3 defaults 1 2 options to mke2fs. -Simple Invocation +Simple Invocation mke2fs /dev/hdb1 @@ -1829,10 +1829,10 @@ LABEL=/usr /usr ext3 defaults 1 2 - + -Reserved blocks +Reserved blocks The -m option is probably the one of most use to non-experts. If the file system becomes filled and there is no more space to write, it @@ -1858,7 +1858,7 @@ LABEL=/usr /usr ext3 defaults 1 2 - + From 26c82bfcf95e2f0e0aeff670802229c71aa33350 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 23:42:00 -0800 Subject: [PATCH 015/214] DocBook validation corrections corrected placement of one tag which was foiling validation --- LDP/howto/docbook/Reliance-HOWTO.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/LDP/howto/docbook/Reliance-HOWTO.xml b/LDP/howto/docbook/Reliance-HOWTO.xml index 2542bce8..482355fc 100644 --- a/LDP/howto/docbook/Reliance-HOWTO.xml +++ b/LDP/howto/docbook/Reliance-HOWTO.xml @@ -264,12 +264,12 @@ start KPPP. Testing using KPPP: - Click on the Configure button. Go to the Modem tab. + Click on the Configure button. Go to the Modem tab. There add a new modem on /dev/ttyS1 and click OK. Now select the newly created modem and click the EDIT button. In the new box which appears, select Modem and then click Query modem. If the modem is properly set then you will get the proper status of the - modem. It will first say something like Finding Modem, then some more messages. + modem. It will first say something like Finding Modem, then some more messages. Lock file BE SURE TO UNCHECK THE USE LOCK FILE CHECKBOX in the modem properties, else From b5687c50f666f40de6265cbfb496b25bc7195e18 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 23:43:27 -0800 Subject: [PATCH 016/214] DocBook validation corrections correcting one which lacked the required url attribute value --- LDP/howto/docbook/Valgrind-HOWTO.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/LDP/howto/docbook/Valgrind-HOWTO.xml b/LDP/howto/docbook/Valgrind-HOWTO.xml index 3a3e1ecd..d2269b59 100644 --- a/LDP/howto/docbook/Valgrind-HOWTO.xml +++ b/LDP/howto/docbook/Valgrind-HOWTO.xml @@ -883,7 +883,7 @@ please let us know. References - http://developer.kde.org/~sewardj/docs/ + The most valuable source of information is the source code itself. From 00d7a4ea8046b16e7f497ba9f5a8de97c0614e69 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sat, 16 Jan 2016 23:45:35 -0800 Subject: [PATCH 017/214] DocBook validation corrections correcting nonexistent &qt; entity with " --- LDP/howto/docbook/Windows-Newsreaders-under-Linux-HOWTO.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/LDP/howto/docbook/Windows-Newsreaders-under-Linux-HOWTO.xml b/LDP/howto/docbook/Windows-Newsreaders-under-Linux-HOWTO.xml index 367a3aa3..9f5421f3 100644 --- a/LDP/howto/docbook/Windows-Newsreaders-under-Linux-HOWTO.xml +++ b/LDP/howto/docbook/Windows-Newsreaders-under-Linux-HOWTO.xml @@ -931,7 +931,7 @@ Fixed" will work. -To change the font, go into Settings -&qt; General Settings -&qt; +To change the font, go into Settings -" General Settings -" Fonts/Colors. Change the "Bodies (monospaced)" font to "Misc Fixed." From 6f7f33141aa6620b14d877a3b4722ee2af20f4f2 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 00:19:52 -0800 Subject: [PATCH 018/214] DocBook validation corrections A crapton of corrections; parser seems a bit more cantankerous, is requiring closing entries; so I added them. Also, corrected a few misplaced or missing elements. N.B. The canonical content seems to be hosted at git://repo.or.cz/lartc.git --- LDP/howto/docbook/Adv-Routing-HOWTO.sgml | 171 ++++++++++++++++++++++- 1 file changed, 168 insertions(+), 3 deletions(-) diff --git a/LDP/howto/docbook/Adv-Routing-HOWTO.sgml b/LDP/howto/docbook/Adv-Routing-HOWTO.sgml index 568946bd..d07b263a 100644 --- a/LDP/howto/docbook/Adv-Routing-HOWTO.sgml +++ b/LDP/howto/docbook/Adv-Routing-HOWTO.sgml @@ -915,7 +915,7 @@ that connect a local network (or even a single machine) to the big Internet. There are usually two questions given this setup. - + Split access The first is how to route answers to packets coming in over a @@ -986,6 +986,7 @@ There are usually two questions given this setup. or you are going to want to masquerade to one of the two providers. In both cases you will want to add rules selecting which provider to route out from based on the IP address of the machine in the local network. + Load balancing @@ -1980,6 +1981,7 @@ ICMP + txqueuelen @@ -1993,6 +1995,7 @@ execute: ifconfig eth0 txqueuelen 10 You can't set this parameter with tc! + @@ -2100,6 +2103,7 @@ latency parameter, which specifies the maximum amount of time a packet can sit in the TBF. The latter calculation takes into account the size of the bucket, the rate and possibly the peakrate (if set). + burst/buffer/maxburst @@ -2115,6 +2119,7 @@ rates require a larger buffer. For 10mbit/s on Intel, you need at least If your buffer is too small, packets may be dropped because more tokens arrive per timer tick than fit in your bucket. + mpu @@ -2124,6 +2129,7 @@ A zero-sized packet does not use zero bandwidth. For ethernet, no packet uses less than 64 bytes. The Minimum Packet Unit determines the minimal token usage for a packet. + rate @@ -2131,6 +2137,7 @@ token usage for a packet. The speedknob. See remarks above about limits! + @@ -2163,6 +2170,7 @@ our waits so we send just at peakrate. However, due to de default 10ms timer resolution of Unix, with 10.000 bits average packets, we are limited to 1mbit/s of peakrate! + mtu/minburst @@ -2182,6 +2190,7 @@ all. To calculate the maximum possible peakrate, multiply the configured mtu by 100 (or more correctly, HZ, which is 100 on Intel, 1024 on Alpha). + @@ -2287,6 +2296,7 @@ The SFQ is pretty much self tuning: Reconfigure hashing once this many seconds. If unset, hash will never be reconfigured. Not recommended. 10 seconds is probably a good value. + quantum @@ -2296,6 +2306,7 @@ Amount of bytes a stream is allowed to dequeue before the next queue gets a turn. Defaults to 1 maximum sized packet (MTU-sized). Do not set below the MTU! + @@ -2434,6 +2445,7 @@ Read it for the strict definitions of the terms used. An algorithm that manages the queue of a device, either incoming (ingress) or outgoing (egress). + Classless qdisc @@ -2441,6 +2453,7 @@ or outgoing (egress). A qdisc with no configurable internal subdivisions. + Classful qdisc @@ -2453,6 +2466,7 @@ bands which are, in fact, classes. However, from the user's configuration perspective, it is classless as the classes can't be touched with the tc tool. + Classes @@ -2461,6 +2475,7 @@ tool. A classful qdisc may have many classes, which each are internal to the qdisc. Each of these classes may contain a real qdisc. + Classifier @@ -2469,6 +2484,7 @@ qdisc. Each of these classes may contain a real qdisc. Each classful qdisc needs to determine to which class it needs to send a packet. This is done using the classifier. + Filter @@ -2477,6 +2493,7 @@ packet. This is done using the classifier. Classification can be performed using filters. A filter contains a number of conditions which if matched, make the filter match. + Scheduling @@ -2487,6 +2504,7 @@ go out earlier than others. This process is called Scheduling, and is performed for example by the pfifo_fast qdisc mentioned earlier. Scheduling is also called 'reordering', but this is confusing. + Shaping @@ -2496,6 +2514,7 @@ The process of delaying packets before they go out to make traffic confirm to a configured maximum rate. Shaping is performed on egress. Colloquially, dropping packets to slow traffic down is also often called Shaping. + Policing @@ -2505,6 +2524,7 @@ Delaying or dropping packets in order to make traffic stay below a configured bandwidth. In Linux, policing can only drop a packet and not delay it - there is no 'ingress queue'. + Work-Conserving @@ -2514,6 +2534,7 @@ A work-conserving qdisc always delivers a packet if one is available. In other words, it never delays a packet if the network adaptor is ready to send one (in the case of an egress qdisc). + non-Work-Conserving @@ -2524,6 +2545,7 @@ to a packet for a certain time in order to limit the bandwidth. This means that they sometimes refuse to give up a packet, even though they have one available. + @@ -2811,6 +2833,7 @@ The following parameters are recognized by tc: Number of bands to create. Each band is in fact a class. If you change this number, you must also change: + priomap @@ -2824,6 +2847,7 @@ at the TC_PRIO priority to decide how to enqueue traffic. This works just like with the pfifo_fast qdisc mentioned earlier, see there for lots of detail. + The bands are classes, and are called major:1 to major:3 by default, so if @@ -3051,6 +3075,7 @@ These are parameters you can specify in order to configure shaping: Average size of a packet, measured in bytes. Needed for calculating maxidle, which is derived from maxburst, which is specified in packets. + bandwidth @@ -3059,6 +3084,7 @@ which is derived from maxburst, which is specified in packets. The physical bandwidth of your device, needed for idle time calculations. + cell @@ -3069,6 +3095,7 @@ based on the packet size. An 800 and an 806 size packet may take just as long to send, for example - this sets the granularity. Most often set to '8'. Must be an integral power of two. + maxburst @@ -3079,6 +3106,7 @@ at maxidle, this number of average packets can be burst before avgidle drops to 0. Set it higher to be more tolerant of bursts. You can't set maxidle directly, only via this parameter. + minburst @@ -3096,6 +3124,7 @@ The time to wait is called the offtime. Higher values of minburst lead to more accurate shaping in the long term, but to bigger bursts at millisecond timescales. + minidle @@ -3111,6 +3140,7 @@ it gets too low. Minidle is specified in negative microseconds, so 10 means that avgidle is capped at -10us. + mpu @@ -3120,6 +3150,7 @@ Minimum packet size - needed because even a zero size packet is padded to 64 bytes on ethernet, and so takes a certain time to transmit. CBQ needs to know this to accurately calculate the idle time. + rate @@ -3127,6 +3158,7 @@ to know this to accurately calculate the idle time. Desired rate of traffic leaving this qdisc - this is the 'speed knob'! + @@ -3176,6 +3208,7 @@ the 'priority' parameter. Each time a class gets its turn, it can only send out a limited amount of data. 'Allot' is the base unit of this amount. See the 'weight' parameter for more information. + prio @@ -3185,6 +3218,7 @@ The CBQ can also act like the PRIO device. Inner classes with lower priority are tried first and as long as they have traffic, other classes are not polled for traffic. + weight @@ -3203,6 +3237,7 @@ using 'rate/10' as a rule of thumb and it appears to work well. The renormalized weight is multiplied by the 'allot' parameter to determine how much data can be sent in one round. + @@ -3239,6 +3274,7 @@ agencies on your link who do want to give each other freebies. The control program tc also knows about 'sharing', which is the reverse of 'isolated'. + bounded/borrow @@ -3248,6 +3284,7 @@ A class can also be 'bounded', which means that it will not try to borrow bandwidth from sibling classes. tc also knows about 'borrow', which is the reverse of 'bounded'. + A typical situation might be where you have two agencies on your link which @@ -3750,6 +3787,7 @@ packet. Source mask 'match ip src 1.2.3.0/24', destination mask 'match ip dst 4.3.2.0/24'. To match a single host, use /32, or omit the mask. + On source/destination port, all IP protocols @@ -3757,6 +3795,7 @@ Source mask 'match ip src 1.2.3.0/24', destination mask 'match ip dst Source: 'match ip sport 80 0xffff', 'match ip dport 0xffff' + On ip protocol (tcp, udp, icmp, gre, ipsec) @@ -3765,6 +3804,7 @@ Source: 'match ip sport 80 0xffff', 'match ip dport 0xffff' Use the numbers from /etc/protocols, for example, icmp is 1: 'match ip protocol 1 0xff'. + On fwmark @@ -3791,6 +3831,7 @@ The number 6 is arbitrary. If you don't want to understand the full tc filter syntax, just use iptables, and only learn to select on fwmark. + On the TOS field @@ -3806,6 +3847,7 @@ To select interactive, minimum delay traffic: Use 0x08 0xff for bulk traffic. + @@ -4240,6 +4282,7 @@ Bases the decision on how the firewall has marked the packet. This can be the easy way out if you don't want to learn tc filter syntax. See the Queueing chapter for details. + u32 @@ -4247,6 +4290,7 @@ Queueing chapter for details. Bases the decision on fields within the packet (i.e. source IP address, etc) + route @@ -4254,6 +4298,7 @@ Bases the decision on fields within the packet (i.e. source IP address, etc) Bases the decision on which route the packet will be routed by + rsvp, rsvp6 @@ -4265,6 +4310,7 @@ URL="http://www.isi.edu/div7/rsvp/overview.html" >. Only useful on networks you control - the Internet does not respect RSVP. + tcindex @@ -4272,6 +4318,7 @@ on networks you control - the Internet does not respect RSVP. Used in the DSMARK qdisc, see the relevant section. + @@ -4297,6 +4344,7 @@ here for convenience: The protocol this classifier will accept. Generally you will only be accepting only IP traffic. Required. + parent @@ -4305,6 +4353,7 @@ accepting only IP traffic. Required. The handle this classifier is to be attached to. This handle must be an already existing class. Required. + prio @@ -4312,6 +4361,7 @@ an already existing class. Required. The priority of this classifier. Lower numbers get tested first. + handle @@ -4319,6 +4369,7 @@ The priority of this classifier. Lower numbers get tested first. This handle means different things to different filters. + @@ -4828,6 +4879,7 @@ Currently, three actions are available: Causes this filter not to match, but perhaps other filters will. + drop @@ -4839,6 +4891,7 @@ For example, you may have a name server that falls over if offered more than 5mbit/s of packets, in which case an ingress filter could be used to make sure no more is ever offered. + Pass/OK @@ -4847,6 +4900,7 @@ sure no more is ever offered. Pass on traffic ok. Might be used to disable a complicated filter, but leave it in place. + reclassify @@ -4855,6 +4909,7 @@ it in place. Most often comes down to reclassification to Best Effort. This is the default action. + @@ -5158,6 +5213,7 @@ Kuznetsov <kuznet@ms2.inr.ac.ru> and Andi Kleen <ak@muc.de> If the kernel decides that it can't deliver a packet, it will drop it, and send the source of the packet an ICMP notice to this effect. + /proc/sys/net/ipv4/icmp_echo_ignore_all @@ -5166,6 +5222,7 @@ send the source of the packet an ICMP notice to this effect. Don't act on echo packets at all. Please don't set this by default, but if you are used as a relay in a DoS attack, it may be useful. + /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts [Useful] @@ -5175,6 +5232,7 @@ If you ping the broadcast address of a network, all hosts are supposed to respond. This makes for a dandy denial-of-service tool. Set this to 1 to ignore these broadcast messages. + /proc/sys/net/ipv4/icmp_echoreply_rate @@ -5182,6 +5240,7 @@ ignore these broadcast messages. The rate at which echo replies are sent to any one destination. + /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses @@ -5190,6 +5249,7 @@ The rate at which echo replies are sent to any one destination. Set this to ignore ICMP errors caused by hosts in the network reacting badly to frames sent to what they perceive to be the broadcast address. + /proc/sys/net/ipv4/icmp_paramprob_rate @@ -5199,6 +5259,7 @@ A relatively unknown ICMP message, which is sent in response to incorrect packets with broken IP or TCP headers. With this file you can control the rate at which it is sent. + /proc/sys/net/ipv4/icmp_timeexceed_rate @@ -5207,6 +5268,7 @@ rate at which it is sent. This the famous cause of the 'Solaris middle star' in traceroutes. Limits number of ICMP Time Exceeded messages sent. + /proc/sys/net/ipv4/igmp_max_memberships @@ -5215,6 +5277,7 @@ number of ICMP Time Exceeded messages sent. Maximum number of listening igmp (multicast) sockets on the host. FIXME: Is this true? + /proc/sys/net/ipv4/inet_peer_gc_maxtime @@ -5226,6 +5289,7 @@ Minimum interval between garbage collection passes. This interval is in effect under low (or absent) memory pressure on the pool. Measured in jiffies. + /proc/sys/net/ipv4/inet_peer_gc_mintime @@ -5234,6 +5298,7 @@ jiffies. Minimum interval between garbage collection passes. This interval is in effect under high memory pressure on the pool. Measured in jiffies. + /proc/sys/net/ipv4/inet_peer_maxttl @@ -5243,6 +5308,7 @@ Maximum time-to-live of entries. Unused entries will expire after this period of time if there is no memory pressure on the pool (i.e. when the number of entries in the pool is very small). Measured in jiffies. + /proc/sys/net/ipv4/inet_peer_minttl @@ -5253,6 +5319,7 @@ time-to-live on the reassembling side. This minimum time-to-live is guaranteed if the pool size is less than inet_peer_threshold. Measured in jiffies. + /proc/sys/net/ipv4/inet_peer_threshold @@ -5263,6 +5330,7 @@ entries will be thrown aggressively. This threshold also determines entries' time-to-live and time intervals between garbage collection passes. More entries, less time-to-live, less GC interval. + /proc/sys/net/ipv4/ip_autoconfig @@ -5271,6 +5339,7 @@ More entries, less time-to-live, less GC interval. This file contains the number one if the host received its IP configuration by RARP, BOOTP, DHCP or a similar mechanism. Otherwise it is zero. + /proc/sys/net/ipv4/ip_default_ttl @@ -5280,6 +5349,7 @@ Time To Live of packets. Set to a safe 64. Raise it if you have a huge network. Don't do so for fun - routing loops cause much more damage that way. You might even consider lowering it in some circumstances. + /proc/sys/net/ipv4/ip_dynaddr @@ -5290,6 +5360,7 @@ address. Once your demand interface comes up, any local TCP sockets which haven' connection that brings up your interface itself does not work, but the second try does. + /proc/sys/net/ipv4/ip_forward @@ -5297,6 +5368,7 @@ second try does. If the kernel should attempt to forward packets. Off by default. + /proc/sys/net/ipv4/ip_local_port_range @@ -5305,6 +5377,7 @@ If the kernel should attempt to forward packets. Off by default. Range of local ports for outgoing connections. Actually quite small by default, 1024 to 4999. + /proc/sys/net/ipv4/ip_no_pmtu_disc @@ -5315,6 +5388,7 @@ determine the largest Maximum Transfer Unit possible on your path. See also the section on Path MTU discovery in the chapter. + /proc/sys/net/ipv4/ipfrag_high_thresh @@ -5325,6 +5399,7 @@ ipfrag_high_thresh bytes of memory is allocated for this purpose, the fragment handler will toss packets until ipfrag_low_thresh is reached. + /proc/sys/net/ipv4/ip_nonlocal_bind @@ -5335,6 +5410,7 @@ which doesn't belong to a device on your system. This can be useful when your machine is on a non-permanent (or even dynamic) link, so your services are able to start up and bind to a specific address when your link is down. + /proc/sys/net/ipv4/ipfrag_low_thresh @@ -5342,6 +5418,7 @@ are able to start up and bind to a specific address when your link is down. Minimum memory used to reassemble IP fragments. + /proc/sys/net/ipv4/ipfrag_time @@ -5349,6 +5426,7 @@ Minimum memory used to reassemble IP fragments. Time in seconds to keep an IP fragment in memory. + /proc/sys/net/ipv4/tcp_abort_on_overflow @@ -5358,6 +5436,7 @@ A boolean flag controlling the behaviour under lots of incoming connections. When enabled, this causes the kernel to actively send RST packets when a service is overloaded. + /proc/sys/net/ipv4/tcp_fin_timeout @@ -5371,6 +5450,7 @@ to overflow memory with kilotons of dead sockets, FIN-WAIT-2 sockets are less dangerous than FIN-WAIT-1, because they eat maximum 1.5K of memory, but they tend to live longer. Cf. tcp_max_orphans. + /proc/sys/net/ipv4/tcp_keepalive_time @@ -5380,6 +5460,7 @@ How often TCP sends out keepalive messages when keepalive is enabled. Default: 2hours. + /proc/sys/net/ipv4/tcp_keepalive_intvl @@ -5389,6 +5470,7 @@ How frequent probes are retransmitted, when a probe isn't acknowledged. Default: 75 seconds. + /proc/sys/net/ipv4/tcp_keepalive_probes @@ -5402,6 +5484,7 @@ Default value: 9. Multiplied with tcp_keepalive_intvl, this gives the time a link can be non-responsive after a keepalive has been sent. + /proc/sys/net/ipv4/tcp_max_orphans @@ -5416,6 +5499,7 @@ network conditions require more than default value, and tune network services to linger and kill such states more aggressively. Let me remind you again: each orphan eats up to  64K of unswappable memory. + /proc/sys/net/ipv4/tcp_orphan_retries @@ -5426,6 +5510,7 @@ Default value 7 corresponds to  50sec-16min depending on RTO. If your machi is a loaded WEB server, you should think about lowering this value, such sockets may consume significant resources. Cf. tcp_max_orphans. + /proc/sys/net/ipv4/tcp_max_syn_backlog @@ -5439,6 +5524,7 @@ make it greater than 1024, it would be better to change TCP_SYNQ_HSIZE in include/net/tcp.h to keep TCP_SYNQ_HSIZE*16<=tcp_max_syn_backlog and to recompile kernel. + /proc/sys/net/ipv4/tcp_max_tw_buckets @@ -5451,6 +5537,7 @@ not lower the limit artificially, but rather increase it (probably, after increasing installed memory), if network conditions require more than default value. + /proc/sys/net/ipv4/tcp_retrans_collapse @@ -5460,6 +5547,7 @@ Bug-to-bug compatibility with some broken printers. On retransmit try to send bigger packets to work around bugs in certain TCP stacks. + /proc/sys/net/ipv4/tcp_retries1 @@ -5470,6 +5558,7 @@ and it is necessary to report this suspicion to network layer. Minimal RFC value is 3, it is default, which corresponds to  3sec-8min depending on RTO. + /proc/sys/net/ipv4/tcp_retries2 @@ -5484,6 +5573,7 @@ says that the limit should be longer than 100 sec. It is too small number. Default value 15 corresponds to  13-30min depending on RTO. + /proc/sys/net/ipv4/tcp_rfc1337 @@ -5495,6 +5585,7 @@ sockets in the time-wait state. Default: 0 + /proc/sys/net/ipv4/tcp_sack @@ -5503,6 +5594,7 @@ Default: 0 Use Selective ACK which can be used to signify that specific packets are missing - therefore helping fast recovery. + /proc/sys/net/ipv4/tcp_stdurg @@ -5516,6 +5608,7 @@ Linux might not communicate correctly with them. Default: FALSE + /proc/sys/net/ipv4/tcp_syn_retries @@ -5524,6 +5617,7 @@ Default: FALSE Number of SYN packets the kernel will send before giving up on the new connection. + /proc/sys/net/ipv4/tcp_synack_retries @@ -5534,6 +5628,7 @@ piggybacked ACK on it, to acknowledge the earlier received SYN. This is part 2 of the threeway handshake. This setting determines the number of SYN+ACK packets sent before the kernel gives up on the connection. + /proc/sys/net/ipv4/tcp_timestamps @@ -5544,6 +5639,7 @@ sequence numbers. A 1 gigabit link might conceivably re-encounter a previous sequence number with an out-of-line value, because it was of a previous generation. The timestamp will let it recognize this 'ancient packet'. + /proc/sys/net/ipv4/tcp_tw_recycle @@ -5552,6 +5648,7 @@ generation. The timestamp will let it recognize this 'ancient packet'. Enable fast recycling TIME-WAIT sockets. Default value is 1. It should not be changed without advice/request of technical experts. + /proc/sys/net/ipv4/tcp_window_scaling @@ -5561,6 +5658,7 @@ TCP/IP normally allows windows up to 65535 bytes big. For really fast networks, this may not be enough. The window scaling options allows for almost gigabyte windows, which is good for high bandwidth*delay products. + @@ -5584,6 +5682,7 @@ to resend your packet on the same interface), it will send us a ICMP Redirect. This is a slight security risk however, so you may want to turn it off, or use secure redirects. + /proc/sys/net/ipv4/conf/DEV/accept_source_route @@ -5593,6 +5692,7 @@ Not used very much anymore. You used to be able to give a packet a list of IP addresses it should visit on its way. Linux can be made to honor this IP option. + /proc/sys/net/ipv4/conf/DEV/bootp_relay @@ -5607,6 +5707,7 @@ such packets. The default is 0, since this feature is not implemented yet (kernel version 2.2.12). + /proc/sys/net/ipv4/conf/DEV/forwarding @@ -5614,6 +5715,7 @@ The default is 0, since this feature is not implemented yet (kernel version Enable or disable IP forwarding on this interface. + /proc/sys/net/ipv4/conf/DEV/log_martians @@ -5622,6 +5724,7 @@ Enable or disable IP forwarding on this interface. See the section on . + /proc/sys/net/ipv4/conf/DEV/mc_forwarding @@ -5629,6 +5732,7 @@ See the section on If we do multicast forwarding on this interface + /proc/sys/net/ipv4/conf/DEV/proxy_arp @@ -5640,6 +5744,7 @@ pseudo bridges'. Do take care that your netmasks are very correct before enabling this! Also be aware that the rp_filter, mentioned elsewhere, also operates on ARP queries! + /proc/sys/net/ipv4/conf/DEV/rp_filter @@ -5648,6 +5753,7 @@ operates on ARP queries! See the section on . + /proc/sys/net/ipv4/conf/DEV/secure_redirects @@ -5656,6 +5762,7 @@ See the section on Accept ICMP redirect messages only for gateways, listed in default gateway list. Enabled by default. + /proc/sys/net/ipv4/conf/DEV/send_redirects @@ -5663,6 +5770,7 @@ list. Enabled by default. If we send the above mentioned redirects. + /proc/sys/net/ipv4/conf/DEV/shared_media @@ -5671,6 +5779,7 @@ If we send the above mentioned redirects. If it is not set the kernel does not assume that different subnets on this device can communicate directly. Default setting is 'yes'. + /proc/sys/net/ipv4/conf/DEV/tag @@ -5678,6 +5787,7 @@ device can communicate directly. Default setting is 'yes'. FIXME: fill this in + @@ -5700,6 +5810,7 @@ Maximum for random delay of answers to neighbor solicitation messages in jiffies (1/100 sec). Not yet implemented (Linux does not have anycast support yet). + /proc/sys/net/ipv4/neigh/DEV/app_solicit @@ -5708,6 +5819,7 @@ yet). Determines the number of requests to send to the user level ARP daemon. Use 0 to turn off. + /proc/sys/net/ipv4/neigh/DEV/base_reachable_time @@ -5716,6 +5828,7 @@ to turn off. A base value used for computing the random reachable time value as specified in RFC2461. + /proc/sys/net/ipv4/neigh/DEV/delay_first_probe_time @@ -5724,6 +5837,7 @@ in RFC2461. Delay for the first time probe if the neighbor is reachable. (see gc_stale_time) + /proc/sys/net/ipv4/neigh/DEV/gc_stale_time @@ -5735,6 +5849,7 @@ to another machine). When ucast_solicit is greater than 0 it first tries to send an ARP packet directly to the known host When that fails and mcast_solicit is greater than 0, an ARP request is broadcast. + /proc/sys/net/ipv4/neigh/DEV/locktime @@ -5743,6 +5858,7 @@ mcast_solicit is greater than 0, an ARP request is broadcast. An ARP/neighbor entry is only replaced with a new one if the old is at least locktime old. This prevents ARP cache thrashing. + /proc/sys/net/ipv4/neigh/DEV/mcast_solicit @@ -5750,6 +5866,7 @@ locktime old. This prevents ARP cache thrashing. Maximum number of retries for multicast solicitation. + /proc/sys/net/ipv4/neigh/DEV/proxy_delay @@ -5759,6 +5876,7 @@ Maximum time (real time is random [0..proxytime]) before answering to an request for which we have an proxy ARP entry. In some cases, this is used to prevent network flooding. + /proc/sys/net/ipv4/neigh/DEV/proxy_qlen @@ -5766,6 +5884,7 @@ prevent network flooding. Maximum queue length of the delayed proxy arp timer. (see proxy_delay). + /proc/sys/net/ipv4/neigh/DEV/retrans_time @@ -5775,6 +5894,7 @@ The time, expressed in jiffies (1/100 sec), between retransmitted Neighbor Solicitation messages. Used for address resolution and to determine if a neighbor is unreachable. + /proc/sys/net/ipv4/neigh/DEV/ucast_solicit @@ -5782,6 +5902,7 @@ neighbor is unreachable. Maximum number of retries for unicast solicitation. + /proc/sys/net/ipv4/neigh/DEV/unres_qlen @@ -5790,6 +5911,7 @@ Maximum number of retries for unicast solicitation. Maximum queue length for a pending arp request - the number of packets which are accepted from other layers while the ARP address is still resolved. + Internet QoS: Architectures and Mechanisms for Quality of Service, @@ -5799,6 +5921,7 @@ Zheng Wang, ISBN 1-55860-608-4 Hardcover textbook covering topics related to Quality of Service. Good for understanding basic concepts. + @@ -5820,6 +5943,7 @@ log from the routing code. The higher the error_cost factor is, the fewer messages will be written. Error_burst controls when messages will be dropped. The default settings limit warning messages to one every five seconds. + /proc/sys/net/ipv4/route/error_cost @@ -5830,6 +5954,7 @@ log from the routing code. The higher the error_cost factor is, the fewer messages will be written. Error_burst controls when messages will be dropped. The default settings limit warning messages to one every five seconds. + /proc/sys/net/ipv4/route/flush @@ -5837,6 +5962,7 @@ The default settings limit warning messages to one every five seconds. Writing to this file results in a flush of the routing cache. + /proc/sys/net/ipv4/route/gc_elasticity @@ -5855,6 +5981,7 @@ URL="http://mailman.ds9a.nl/pipermail/lartc/2002q1/002667.html" >this post by Ard van Breemen. + /proc/sys/net/ipv4/route/gc_interval @@ -5862,6 +5989,7 @@ URL="http://mailman.ds9a.nl/pipermail/lartc/2002q1/002667.html" See /proc/sys/net/ipv4/route/gc_elasticity. + /proc/sys/net/ipv4/route/gc_min_interval @@ -5869,6 +5997,7 @@ See /proc/sys/net/ipv4/route/gc_elasticity. See /proc/sys/net/ipv4/route/gc_elasticity. + /proc/sys/net/ipv4/route/gc_thresh @@ -5876,6 +6005,7 @@ See /proc/sys/net/ipv4/route/gc_elasticity. See /proc/sys/net/ipv4/route/gc_elasticity. + /proc/sys/net/ipv4/route/gc_timeout @@ -5883,6 +6013,7 @@ See /proc/sys/net/ipv4/route/gc_elasticity. See /proc/sys/net/ipv4/route/gc_elasticity. + /proc/sys/net/ipv4/route/max_delay @@ -5890,6 +6021,7 @@ See /proc/sys/net/ipv4/route/gc_elasticity. Delays for flushing the routing cache. + /proc/sys/net/ipv4/route/max_size @@ -5898,6 +6030,7 @@ Delays for flushing the routing cache. Maximum size of the routing cache. Old entries will be purged once the cache reached has this size. + /proc/sys/net/ipv4/route/min_adv_mss @@ -5905,6 +6038,7 @@ reached has this size. FIXME: fill this in + /proc/sys/net/ipv4/route/min_delay @@ -5912,6 +6046,7 @@ FIXME: fill this in Delays for flushing the routing cache. + /proc/sys/net/ipv4/route/min_pmtu @@ -5919,6 +6054,7 @@ Delays for flushing the routing cache. FIXME: fill this in + /proc/sys/net/ipv4/route/mtu_expires @@ -5926,6 +6062,7 @@ FIXME: fill this in FIXME: fill this in + /proc/sys/net/ipv4/route/redirect_load @@ -5935,6 +6072,7 @@ Factors which determine if more ICMP redirects should be sent to a specific host. No redirects will be sent once the load limit or the maximum number of redirects has been reached. + /proc/sys/net/ipv4/route/redirect_number @@ -5942,6 +6080,7 @@ redirects has been reached. See /proc/sys/net/ipv4/route/redirect_load. + /proc/sys/net/ipv4/route/redirect_silence @@ -5950,6 +6089,7 @@ See /proc/sys/net/ipv4/route/redirect_load. Timeout for redirects. After this period redirects will be sent again, even if this has been stopped, because the load or number limit has been reached. + @@ -5997,6 +6137,7 @@ Specifies the length of the queue. Measured in bytes for bfifo, in packets for pfifo. Defaults to the interface txqueuelen (see pfifo_fast chapter) packets long or txqueuelen*mtu bytes for bfifo. + @@ -6650,8 +6791,7 @@ URL="http://linux-atm.sourceforge.net/" This qdisc is not included in the standard kernels but can be downloaded from �. +/>. Currently the qdisc is only tested with Linux 2.2 kernels but it will probably work with 2.4/2.5 kernels too. @@ -7070,6 +7210,7 @@ BUT This would put additional load on the router and some commercial routers might not even support this. + Using a Layer 4 switch. @@ -7087,6 +7228,7 @@ The cost for this equipment is usually very high. Typical layer 4 switch would normally cost more than a typical router+good linux server. + Using cache server as network's gateway. @@ -7107,6 +7249,7 @@ or the server itself might crash and no one on the network will be able to access the Internet if that occurs. + Linux+NetFilter router. @@ -7117,6 +7260,7 @@ which is using NetFilter for "mark"ing the packets with destination port 80 and using iproute2 to route the "mark"ed packets to the Squid server. + @@ -7255,6 +7399,7 @@ naret# ip route add default via 10.0.0.2 dev eth0 table www.out naret# ip route flush cache + @@ -7581,6 +7726,7 @@ This means that downloading or uploading files should not disturb SSH or even telnet. These are the most important things, even 200ms latency is sluggish to work over. + Allow 'surfing' at reasonable speeds while up or downloading @@ -7589,6 +7735,7 @@ sluggish to work over. Even though http is 'bulk' traffic, other traffic should not drown it out too much. + Make sure uploads don't harm downloads, and the other way around @@ -7597,6 +7744,7 @@ too much. This is a much observed phenomenon where upstream traffic simply destroys download speed. + It turns out that all this is possible, at the cost of a tiny bit of @@ -7652,6 +7800,7 @@ eliminated, and moved to your Linux router. Luckily this is possible. By limiting our upload speed to slightly less than the truly available rate, no queues are built up in our modem. The queue is now moved to Linux. + Limit download speed @@ -7663,6 +7812,7 @@ which causes TCP/IP to slow down to just the rate we want. Because we don't want to drop traffic unnecessarily, we configure a 'burst' size we allow at higher speed. + @@ -8348,6 +8498,7 @@ URL="http://scry.wanfear.com/~greear/vlan/cisco_howto.html" Update: has been included in the kernel as of 2.4.14 (perhaps 13). + Alternate 802.1Q VLAN Implementation for Linux + Linux Virtual Server + CBQ.init + Chronox easy shaping scripts + Virtual Router @@ -8523,6 +8678,7 @@ Not *one* ping packet was lost! Just after packet 4, I disconnected my P200 from the network, and my 486 took over, which you can see from the higher latency. + @@ -8544,6 +8700,7 @@ URL="http://snafu.freedom.org/linux2.2/iproute-notes.html" Contains lots of technical information, comments from the kernel + Slides by Jamal Hadi Salim, one of the authors of Linux traffic control + + + Differentiated Services on Linux @@ -8590,6 +8750,7 @@ URL="ftp://icaftp.epfl.ch/pub/linux/diffserv/misc/dsid-01.txt.gz" Kuznetsov describes DiffServ facilities in the Linux kernel, amongst which are TBF, GRED, the DSMARK qdisc and the tcindex classifier. + + + Docum experimental site + TCP/IP Illustrated, volume 1, W. Richard Stevens, ISBN 0-201-63346-9 @@ -8636,6 +8800,7 @@ of practical information, examples, tests and also points out some CBQ/tc bugs. Required reading if you truly want to understand TCP/IP. Entertaining as well. + From 4fa28296a380be20b135ac0239883e718b61a803 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 00:29:12 -0800 Subject: [PATCH 019/214] DocBook validation corrections adding a few closing tags: , and a --- LDP/howto/docbook/XDM-Xterm.sgml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/LDP/howto/docbook/XDM-Xterm.sgml b/LDP/howto/docbook/XDM-Xterm.sgml index b9750d11..fe7bbbaa 100644 --- a/LDP/howto/docbook/XDM-Xterm.sgml +++ b/LDP/howto/docbook/XDM-Xterm.sgml @@ -474,7 +474,8 @@ of functionality, ranging from completely diskless terminals to full X workstations. - + + @@ -1049,6 +1050,7 @@ id:5:initdefault: + @@ -1570,6 +1572,7 @@ + From 8642facb9af32e6f4f7dabad50e4cb8a8511aa5a Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 00:31:46 -0800 Subject: [PATCH 020/214] DocBook validation correction removing one extraneous --- LDP/howto/docbook/XDMCP-HOWTO.sgml | 3 --- 1 file changed, 3 deletions(-) diff --git a/LDP/howto/docbook/XDMCP-HOWTO.sgml b/LDP/howto/docbook/XDMCP-HOWTO.sgml index 98a17f0c..4cd821d7 100644 --- a/LDP/howto/docbook/XDMCP-HOWTO.sgml +++ b/LDP/howto/docbook/XDMCP-HOWTO.sgml @@ -1,4 +1,3 @@ -
@@ -962,8 +961,6 @@ for more information. Using and Managing GDM - - Configuring XDM (from Linux Journal) From 1f4ea7ccad5c5509e35dc767dd02383f120f1efb Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 00:34:49 -0800 Subject: [PATCH 021/214] DocBook validation correction getting rid of one extraneous --- LDP/howto/docbook/Wireless-Link-sys-WPC11.sgml | 2 -- 1 file changed, 2 deletions(-) diff --git a/LDP/howto/docbook/Wireless-Link-sys-WPC11.sgml b/LDP/howto/docbook/Wireless-Link-sys-WPC11.sgml index fe9196f6..20898a36 100644 --- a/LDP/howto/docbook/Wireless-Link-sys-WPC11.sgml +++ b/LDP/howto/docbook/Wireless-Link-sys-WPC11.sgml @@ -212,8 +212,6 @@ Uncomment line 8 and set the ssid2scan to your network's SSID. Uncomment line 9 and set the networktype to infra (unless you really are using adhoc). Save your changes. - - Now eject the card cardctl eject and plug it in again. From the directory where you unpacked the drivers, type insmod -f rtl8180_24x.o From e5287bc81eb72e105fa83874490316637c7b9ab9 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 00:51:09 -0800 Subject: [PATCH 022/214] DocBook validation correction Adding tons of closing , , and elements. --- LDP/howto/docbook/Webcam-HOWTO.sgml | 62 +++++++++++++++++++++++------ 1 file changed, 49 insertions(+), 13 deletions(-) diff --git a/LDP/howto/docbook/Webcam-HOWTO.sgml b/LDP/howto/docbook/Webcam-HOWTO.sgml index 72019a64..636afd26 100644 --- a/LDP/howto/docbook/Webcam-HOWTO.sgml +++ b/LDP/howto/docbook/Webcam-HOWTO.sgml @@ -290,7 +290,7 @@ An easy way to tell if the driver is enabled is to use the dmesg -If you don't see it, the particular driver may exist as a loadable module. If you know what that module is named, try using find; in this example we are looking for the 'ibmcam' module: +If you don't see it, the particular driver may exist as a loadable module. If you know what that module is named, try using find; in this example we are looking for the 'ibmcam' module: $ find /lib/modules -name ibmcam.o @@ -353,12 +353,14 @@ Drivers for specific webcam models, or links to project pages hosting code for d If you are unfamiliar with the prerequisites and procedure of compiling your own kernel, I direct you to the Kernel HOWTO for more information. - + Patching, Source-Only or Precompiled Binary? -You may find that your webcam is supported by only a kernel patch, by a source-only driver not requiring a kernel recompile, or you may even be lucky enough to have a distribution that makes a pre-compiled and packaged binary driver available for your computer's architecture. The procedure involved in the former is largely beyond the scope of this document and is probably best outlined in the documentation available on the web page of your particular model's driver found in . Some further more general documentation on these processes are, however, addressed in +You may find that your webcam is supported by only a kernel patch, by a source-only driver not requiring a kernel recompile, or you may even be lucky enough to have a distribution that makes a pre-compiled and packaged binary driver available for your computer's architecture. The procedure involved in the former is largely beyond the scope of this document and is probably best outlined in the documentation available on the web page of your particular model's driver found in . Some further more general documentation on these processes are, however, addressed in + + @@ -366,6 +368,7 @@ You may find that your webcam is supported by only a kernel patch, by a source-o Supporting the Connection Type + USB Webcams @@ -426,6 +429,8 @@ can only use one at at time. .tgz or .deb format from your Linux distribution. + + Linux Kernel USB Support @@ -434,7 +439,7 @@ Linux distribution. libusb (outlined above). For 2.2 and 2.4 series kernels, your USB webcam may require the module usbvideo -to function. This is not required in the 2.6+ series. +to function. This is not required in the 2.6+ series. For generic USB bus support in Linux, you will need USB subsystem support in your kernel, whether usb-ohci, usb-ehci, or whatever flavor @@ -447,7 +452,7 @@ For a more in-depth discussion of USB support in general, I direct you to the Linux-usb project site. If you want to find out which modules are loaded, at the command line -or in an xterm, type the following: +or in an xterm, type the following: @@ -498,7 +503,9 @@ should see an entry such as the following: Oct 18 12:43:12 K7 kernel: ibmcam.c: IBM PC Camera USB camera found (model 2, rev. 0x030a) Oct 18 12:43:12 K7 kernel: usbvideo.c: ibmcam on /dev/video1: canvas=352x240 videosize=352x240 - + + + @@ -531,6 +538,7 @@ url="http://www.tele.ucl.ac.be/PEOPLE/DOUXCHAMPS/ieee1394/cameras/">IEEE1394 Digital Camera List, by Damien Douxchamps, offers an outstanding summary of the capabilities of IEEE 1394 cameras as well as the current status of support for individual models. + @@ -590,7 +598,9 @@ mode, or alternatively ECP/EPP. Unidirectional mode is unsuitable for scanning. The above setting can usually be accessed through your BIOS menu, at -least on x86 systems. +least on x86 systems. + + @@ -637,6 +647,7 @@ project web page. It may require a kernel recompile after patching depending on your kernel version. + CPiA based Webcams @@ -707,6 +718,7 @@ port webcams including the following: + @@ -769,6 +781,7 @@ The driver supports the following: + @@ -862,6 +875,7 @@ Supported models include: + Logitech (formerly Connectix) Quickcam Support @@ -916,6 +930,7 @@ url="http://www.ee.oulu.fi/~tuukkat/quickcam/FAQ">here. Some Logitech camera models are supported by the Philips driver in . + ICM532 Based Webcams @@ -971,6 +986,7 @@ in . + NW802 Based Webcams @@ -992,6 +1008,7 @@ The models supported include the following: + @@ -1001,7 +1018,7 @@ The models supported include the following: Philips USB Webcams -Because of the expiration of the Non-Disclosure-Agreement between Philips Corporation and the former maintainer of the pwc driver, the previous kernel support for Philips PWC-chip-based webcams has been removed. Luckily a new, still experimental driver that does not require a proprietary module is under development. The old site, with a discussion of the change, can be seen at http://www.smcc.demon.nl/webcam/; the new driver is maintained at saillard.org with more information at the PWC Documentation Project. +Because of the expiration of the Non-Disclosure-Agreement between Philips Corporation and the former maintainer of the pwc driver, the previous kernel support for Philips PWC-chip-based webcams has been removed. Luckily a new, still experimental driver that does not require a proprietary module is under development. The old site, with a discussion of the change, can be seen at http://www.smcc.demon.nl/webcam/; the new driver is maintained at saillard.org with more information at the PWC Documentation Project. Philips models supported by the above include the following. @@ -1050,6 +1067,7 @@ Because of the expiration of the Non-Disclosure-Agreement between Philips Corpor + SPCA50X USB Camera Linux Driver @@ -1142,6 +1160,7 @@ Kodak DVC-325 and EZ200 Sigma-Apo Petcam + @@ -1159,6 +1178,7 @@ Quickpix 2. If you have a serial version, the main one of which is the Scan e-Studio, you should go here. + Winbond w9966cf @@ -1168,7 +1188,8 @@ SUPRA webcam. It is included in the late 2.4 kernel series and later under the heading 'video4linux' support. The homepage for this project is here. +url="http://hem.fyristorg.com/mogul/w9966.html">here. + Xirlink <trademark>C-it</trademark> HDCS-1000 based Webcams @@ -1341,6 +1362,7 @@ See the documentation for chmod (man chmod or Framegrabbing Applications + Command Line Programs @@ -1352,7 +1374,7 @@ See the documentation for chmod (man chmod or Streamer is a versatile program that allows a capture from a webcam or video device using only the command line. -It may be offered in your Linux distribution's Xawtv package, or may need to be fetched separately as in Debian. You can find it and more information at Gerd Knorr's Xawtv homepage. +It may be offered in your Linux distribution's Xawtv package, or may need to be fetched separately as in Debian. You can find it and more information at Gerd Knorr's Xawtv homepage. To take a standard JPEG picture from the command line where the camera is accessed through /dev/video0: @@ -1385,6 +1407,7 @@ Streamer can capture raw and Quicktime (non-Sorensen) formats and can capture audio as well. See streamer --help for more information. + camE @@ -1397,6 +1420,7 @@ text all by altering the appropriate line in the configuration file. See the camE homepage for more information. + Motion @@ -1419,12 +1443,14 @@ configuration file options nicely. The motion homepage can be found here. + Webcam Webcam is an automated command line tool for operating a webcam that is also available from the Xawtv homepage. It is excellent for automated operation such as from a cron job, as it requires no command line options, only a previously edited configuration file (usually ~/.webcamrc). It is similar to camE above in that one can captures images and upload them to a Web-Server via ftp or ssh. + SANE @@ -1438,6 +1464,7 @@ See the relevant sections of the Scanner-HOWTO here. + GUI(Grapical User Interface)-Based Programs @@ -1449,7 +1476,7 @@ url="http://tldp.org/HOWTO/Scanner-HOWTO/sane.html#getting-SANE">here. in Linux including TV tuning devices and webcams. The home page is at http://bytesex.org/xawtv. +url="http://bytesex.org/xawtv">http://bytesex.org/xawtv. When you first try out your webcam, and you think things are configured right, use the -hwscan option: @@ -1486,6 +1513,7 @@ from your window manager's menu next time. You can read about more xawtv options with man xawtv. + Gqcam @@ -1500,10 +1528,12 @@ and configuring webcam settings blissfully easy. It is highly recommended for those who only want to take a picture here and there without editing a configuration file or using the command line. + Camorama Camorama is a graphical GTK+2.0-based application very similar to gqcam written for the Gnome2 desktop. The home page is here. + GnomeMeeting @@ -1563,16 +1593,19 @@ device is attached to. The P: indicates (obviously) the vendor and product ID, which are catalogued at the linux USB Project homepage. + Help, I can't find the camera device in <filename>/dev</filename>! Assuming your connection type is supported, and your camera is working, see . + Help, I can see the camera device (both in person and as a device node in <filename>/dev</filename>), but I can't access it! See . + Help, my camera has a driver that is source-only, i.e., has to be built by me! Where do I start? First, check @@ -1625,7 +1658,8 @@ Assuming it compiles correctly, you can simply load the new module with modprobe. If you have any problems, see . - + + I am using Debian GNU/Linux. Is there an easier way to go through all this kernel compiling stuff and building of source modules? @@ -1663,6 +1697,7 @@ source driver using apt. So, in the case of the Quickcam Ex # tar -xvzf qc-usb-modules.tar.gz + This will uncompress the source into the /usr/src/modules directory. The final step, while still in /usr/src/linux is to make the modules with kernel-package: @@ -1715,7 +1750,8 @@ program you use to recompile, enabling the appropriate support. If any of the hunks failed, or you run into any problems in addition to the link referenced above you, should consult man patch -and . +and . + From b3d83f6861242d47e1caa88457da4d1741777f1c Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 01:10:40 -0800 Subject: [PATCH 023/214] DocBook validation correction lots of nits because &65533; is not SGML friendly (?) several substitutions for inline and a very strange addition of just to allow the nesting of
--- LDP/howto/docbook/VMS-to-Linux-HOWTO.sgml | 72 +++++++++++------------ 1 file changed, 33 insertions(+), 39 deletions(-) diff --git a/LDP/howto/docbook/VMS-to-Linux-HOWTO.sgml b/LDP/howto/docbook/VMS-to-Linux-HOWTO.sgml index 7719724c..12e9beab 100644 --- a/LDP/howto/docbook/VMS-to-Linux-HOWTO.sgml +++ b/LDP/howto/docbook/VMS-to-Linux-HOWTO.sgml @@ -5,18 +5,22 @@ From VMS to Linux HOWTO - -By Guido Gonzato, �, -and Mike Miller, � - + + + Guido + Gonzato + +
guido ``at'' ibogeo.df.unibo.it
+ + + + Mike + Miller + +
miller5@uiuc.edu
+ + + v1.1.4, 22 September 2004 @@ -147,9 +151,8 @@ equivalent of the command HELP. The Linux Documentation Project documents, available on �, are an important source of +URL="ftp://sunsite.unc.edu:/pub/Linux/docs/LDP">ftp://sunsite.unc.edu:/pub/Linux/docs/LDP +are an important source of information. I suggest that you read Larry Greenfield's ``Linux User Guide''---it's invaluable for the novice user. @@ -1878,10 +1881,9 @@ to the marked position. Alas, Linux doesn't still support file version numbers, but you overcome this limitation in two ways. The first is to use RCS, the Revision Control System, which allows you to keep previous versions of a file. RCS is -covered in ``The RCS MINI-HOWTO'' (�). +covered in ``The RCS MINI-HOWTO'' ( + +http://sunsite.unc.edu/mdw/HOWTO/mini/RCS.html). @@ -1904,10 +1906,11 @@ these lines in your .emacs: In jed, make sure you have version 0.98.7 or newer; the patch for -numbered backups is available on � . +numbered backups is available on +http://ibogeo.df.unibo.it/guido/slang/backups.sl + +. @@ -2536,10 +2539,7 @@ particular flavor of *nix. -(Thanks to Wojtek Skulski (�) +(Thanks to Wojtek Skulski (skulski@nsrlc6.nsrl.rochester.edu) for pointing out setblk.) @@ -2580,10 +2580,8 @@ the HOWTOs. If you have questions, please contact Tim Bynum, the Linux HOWTO -coordinator, at � via email. +coordinator, at linux-howto@sunsite.unc.edu +via email. @@ -2599,14 +2597,10 @@ are VMS users, and some of them have switched to Linux. -``From VMS to Linux HOWTO'' was written by Guido Gonzato, �, and Mike Miller, -� who contributed the section on reading VMS tapes. +``From VMS to Linux HOWTO'' was written by Guido Gonzato, guido ``at'' ibogeo.df.unibo.it and Mike Miller, +miller5@uiuc.edu +who contributed the section on reading VMS tapes. Many thanks to my colleagues and friends who helped me define the needs and habits of the average VMS user, especially to Dr. Warner Marzocchi. From 6f2690da82b2fd307765129babe6a14abc2d3d18 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 01:16:16 -0800 Subject: [PATCH 024/214] DocBook validation correction just some tag balancing; plenty more closing tags for and a --- LDP/howto/docbook/User-Authentication-HOWTO.sgml | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/LDP/howto/docbook/User-Authentication-HOWTO.sgml b/LDP/howto/docbook/User-Authentication-HOWTO.sgml index 299cd757..4016db3e 100644 --- a/LDP/howto/docbook/User-Authentication-HOWTO.sgml +++ b/LDP/howto/docbook/User-Authentication-HOWTO.sgml @@ -272,7 +272,9 @@ Installing PAM from scratch is long process, beyond the scope of this HOWTO. If PAM isn't installed on your system, you're probably running such an old version of your distribution that there are many other reasons to upgrade. If you really want to do it yourself, then you're certainly not the sort of person who needs any help from me. For all these reasons, I'm going to assume that you already have PAM installed. - + + How @@ -374,7 +376,7 @@ <varlistentry><term>requisite</term> <listitem><para> Failure to authenticate via this module results in immediate denial of authentication. - </para> + </para></listitem> </varlistentry> <varlistentry><term>required</term> <listitem><para> @@ -537,6 +539,7 @@ <para> As our example, we'll install and configure mod_auth_pam, an Apache module that allows you to authenticate users of your webserver using PAM. For the purpose of this example, I'll assume you have apache installed. If it's not installed already you should be able find installation packages from your distributor. </para> + </sect2> <sect2> <title>Our example @@ -605,11 +608,13 @@ Before we test our setup, I'll take a moment to explain the Apache configuration you just entered. The <Directory> directive is used to encapsulate configuration data for this directory. Inside this directive, we've enabled PAM authentication ("AuthPAM_enabled on"), turned off any overriding of this configuration ("AllowOverride none"), named this authentication zone "Family Secrets" ("AuthName "Family Secrets""), set the http authentication (not the PAM authentication) type to the default ("AuthType "basic""), and required the user group family ("require group family"). + Testing our setup Now that we've got everything setup up properly, it's time to revel in our success. Fire up your favorite web browser and head over to http://your-domain/family/ (replacing your-domain with, well, your domain). You are now an uber-authenticator! + @@ -675,5 +680,6 @@ Conclusion - I hope you found this HOWTO helpful. If you have any questions, comments, or suggestions, I'd love to hear from you. You can email me at petehern@yahoo.com. + I hope you found this HOWTO helpful. If you have any questions, comments, or suggestions, I'd love to hear from you. You can email me at petehern@yahoo.com. +
From bf247c6a6c013df3c55d51071136caa60754e506 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 01:20:05 -0800 Subject: [PATCH 025/214] DocBook validation correction adding a bunch of closing to allow validation --- LDP/howto/docbook/Token-Ring.sgml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/LDP/howto/docbook/Token-Ring.sgml b/LDP/howto/docbook/Token-Ring.sgml index bb63e0e1..e552ac19 100644 --- a/LDP/howto/docbook/Token-Ring.sgml +++ b/LDP/howto/docbook/Token-Ring.sgml @@ -230,7 +230,7 @@ - + @@ -857,6 +857,7 @@ cards) can have their io regions located anywhere permitted by the PnP specification. This location is found using the new turbo detection code and no parameters are required. + @@ -869,6 +870,7 @@ + @@ -952,6 +954,7 @@ + Multi-card @@ -1049,6 +1052,7 @@ + Network Monitor @@ -1179,6 +1183,7 @@ + Multi-card From 93752f8b0940c58dbef8d31e4b34b577096b68de Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 01:21:49 -0800 Subject: [PATCH 026/214] DocBook validation correction adding a single closing --- LDP/howto/docbook/Sybase-PHP-Apache.sgml | 1 + 1 file changed, 1 insertion(+) diff --git a/LDP/howto/docbook/Sybase-PHP-Apache.sgml b/LDP/howto/docbook/Sybase-PHP-Apache.sgml index e53a70bf..47bffef5 100644 --- a/LDP/howto/docbook/Sybase-PHP-Apache.sgml +++ b/LDP/howto/docbook/Sybase-PHP-Apache.sgml @@ -224,6 +224,7 @@ try to guess the Sybase directory. If you see the following error: errorerwerqwerqwerwerwer + when trying to run sybinstall.sh or rc.sybase, then you need to change From 82101ac3a9186ac0f6aa0df65b095f3dc9f933de Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 01:27:34 -0800 Subject: [PATCH 027/214] DocBook validation correction New style replacing the no-longer validating which held mailto: URLs. --- LDP/howto/docbook/SRM-HOWTO.sgml | 27 ++++++++++++++++----------- 1 file changed, 16 insertions(+), 11 deletions(-) diff --git a/LDP/howto/docbook/SRM-HOWTO.sgml b/LDP/howto/docbook/SRM-HOWTO.sgml index e1adb61c..87de27bd 100644 --- a/LDP/howto/docbook/SRM-HOWTO.sgml +++ b/LDP/howto/docbook/SRM-HOWTO.sgml @@ -5,18 +5,23 @@ SRM Firmware Howto - + + + Rich + Payne - -Rich Payne, -and David Huggins-Daines - + +
rdp@alphalinux.org
+ + + + David + Huggins-Daines + +
dhuggins@linuxcare.com
+ + + v0.8, 09 November 2000 From 2fbe6fee468d8a7191de6e91f3d57cf9275d1883 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 01:30:35 -0800 Subject: [PATCH 028/214] DocBook validation correction removing one stray to allow validation --- LDP/howto/docbook/Software-Proj-Mgmt-HOWTO.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/LDP/howto/docbook/Software-Proj-Mgmt-HOWTO.sgml b/LDP/howto/docbook/Software-Proj-Mgmt-HOWTO.sgml index 7510809a..b1a0b37a 100644 --- a/LDP/howto/docbook/Software-Proj-Mgmt-HOWTO.sgml +++ b/LDP/howto/docbook/Software-Proj-Mgmt-HOWTO.sgml @@ -3270,7 +3270,7 @@ pages for more information and options. </author> <title><ulink url="http://www.advogato.org/article/72.html">Importance of - Non-Developer Supporters in Free Software</ulink><title> + Non-Developer Supporters in Free Software Advogato @@ -3980,4 +3980,4 @@ sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: ---> \ No newline at end of file +--> From 691bb85e155938fab86f86bf0dc47a20158c70d2 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 01:39:57 -0800 Subject: [PATCH 029/214] DocBook validation correction upgrading entire document to DocBook V3.1 (from V3.0): because the authors were using elements (e.g. and ) that were not available in the earlier DocBook release --- LDP/howto/docbook/RPM-HOWTO.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/LDP/howto/docbook/RPM-HOWTO.sgml b/LDP/howto/docbook/RPM-HOWTO.sgml index 4a9a4637..ac05df88 100644 --- a/LDP/howto/docbook/RPM-HOWTO.sgml +++ b/LDP/howto/docbook/RPM-HOWTO.sgml @@ -1,4 +1,4 @@ - +
From 8afd6d7e1e07d4f273d628c79d76954b131dc630 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 01:44:32 -0800 Subject: [PATCH 030/214] DocBook validation correction adding one missing --- LDP/howto/docbook/Bridge.sgml | 1 + 1 file changed, 1 insertion(+) diff --git a/LDP/howto/docbook/Bridge.sgml b/LDP/howto/docbook/Bridge.sgml index 823e3e45..1ad36745 100644 --- a/LDP/howto/docbook/Bridge.sgml +++ b/LDP/howto/docbook/Bridge.sgml @@ -312,6 +312,7 @@ brcfg -deb Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. + PREAMBLE From a52bf88f4fc5381cf2e002b3546391a1e7c9211c Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 01:51:27 -0800 Subject: [PATCH 031/214] DocBook validation correction adding a bunch of terminating and a handful of other tags --- LDP/howto/docbook/BTTV.sgml | 33 +++++++++++++++++++++++++-------- 1 file changed, 25 insertions(+), 8 deletions(-) diff --git a/LDP/howto/docbook/BTTV.sgml b/LDP/howto/docbook/BTTV.sgml index 5233ae33..937163a0 100644 --- a/LDP/howto/docbook/BTTV.sgml +++ b/LDP/howto/docbook/BTTV.sgml @@ -85,6 +85,7 @@ no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found in . + @@ -112,6 +113,7 @@ validity of any trademark or service mark. Naming of particular products or brands should not be seen as endorsements. + @@ -129,6 +131,7 @@ endorsements. url="http://www.tldp.org/HOWTO/BTTV.html">here. + @@ -143,6 +146,7 @@ use of the script in Also, I would like to thank Marla, without whose encouragement this project would not have been possible. + Feedback Please send any information you may feel important to the following email address: hshane[AT]austin.rr.com, whether you have a @@ -213,7 +217,7 @@ outlined with screen output in their own paragraph or heading: The BTTV Hardware - + Bttv Basics @@ -251,7 +255,7 @@ TV cards known NOT to work include the following: Pinnacle DC10+ Linux Media Labs LML33 - Cards with a Philips SAA7130/7134 controller + Cards with a Philips SAA7130/7134 controller Multimedia eXtension Board cards, manufactured by Siemens-Nixdorf Hexium HV-PCI6, Orion or Gemini framegrabber cards Any ISA-based TV card @@ -259,7 +263,7 @@ TV cards known NOT to work include the following: If you are uncertain which chipset your TV card has, use the lspci command. -An example of such output for a Bt8x8 card might look similar to the following: +An example of such output for a Bt8x8 card might look similar to the following: 0000:02:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 02) @@ -267,6 +271,7 @@ An example of such output for a Bt8x8 card might look similar to the following: (rev 02) A list of hardware (mostly PCI cards) compatible with the Bttv driver is found in + The Sound Output @@ -279,6 +284,8 @@ will be able to control the input with your mixer from your primary sound card a well as record (see for more information on recording). Alternatively you can use external speakers connected to the line out of your Bt8x8 card. + + @@ -348,7 +355,7 @@ chipset features and kernel version (in this case, 2.6): If you don't see it, the particular driver module you are interested in may be available but not necessarily loaded at that time. If you know what the module is named, -try using find; in this example we are looking for the 'bttv' module: +try using find; in this example we are looking for the 'bttv' module: $ find /lib/modules -name bttv.o @@ -417,6 +424,7 @@ following example (using the bttv module): + @@ -450,6 +458,7 @@ in the OSS "Sound" category is optional if you want to use external speakers attached to the the card's audio out jack, and either (or both) OSS or ALSA sound system btaudio drivers in the 2.6+ series. + Configuration Requirements for Use of your Bttv Hardware @@ -550,6 +559,7 @@ save it as MAKEDEV or whatever name you like, make it executable # ./MAKEDEV + @@ -660,6 +670,7 @@ to remove the module, you can use rmmod: $ rmmod bttv You can then reload the module with the appropriate options. + The Tuner Module @@ -743,11 +754,13 @@ the following list: tuner=45 Microtune 4049 FM5 + Other Modules Don't forget to load any other modules you may need, including btaudio if you plan on recording or capturing audio to another application. + Automating the Module Loading Process @@ -764,14 +777,13 @@ automatically with the appropriate options. The following is an example entry: options tuner type=2 + + Television Applications Now that your kernel is configured, your devices have been configured, and your modules are inserted, you will also need an application to actually view or capture the images from your card. - - - Console-Based Applications FbTV @@ -782,12 +794,15 @@ a framebuffer is you can read the . Fbtv is available from the Bttv homepage with Xawtv. + AATV AATV is a simple program to watch TV on a text console under Linux using aalib and a Bt8x8 card. While the graphics are enabled in ascii graphics only, the advantage is that you (or anyone) can watch television from anywhere over the internet using your -local Bt8x8 hardware. +local Bt8x8 hardware. + + GUI-based Applications The following applications require a graphical user interface such as GNOME, KDE etc. @@ -828,10 +843,12 @@ Now that you know your Bt8x8 device is available, try starting Xawtv: Note that some Nvidia cards may confuse xawtv, so if you have one of these be sure to use the -device switch as above. + Motv Motv is a Motif-based rewrite of Xawtv. Other than a more attractive interface, and is also found at the Xawtv homepage. It is otherwise identical to Xawtv. + TVtime TVtime is the ultimate application for those who want to watch TV using an application that doesn't get in the way and requires little or no From 8ceb8a930bb847c75f336b018aaf7afd775f25a9 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 01:57:38 -0800 Subject: [PATCH 032/214] DocBook validation correction adding a bunch of terminating and tags --- LDP/howto/docbook/Cable-Modem.sgml | 26 +++++++++++++++++++++----- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/LDP/howto/docbook/Cable-Modem.sgml b/LDP/howto/docbook/Cable-Modem.sgml index c5e9628c..c2c6d288 100644 --- a/LDP/howto/docbook/Cable-Modem.sgml +++ b/LDP/howto/docbook/Cable-Modem.sgml @@ -90,7 +90,7 @@ confidently even when the outlook was dimmest and others unforgiving. I'm yours Feedback Please send any additions or comments pertaining to this document to the following email address: -hshane[AT]austin.rr.com. +hshane[AT]austin.rr.com. Conventions Used in this Document The following conventions are used in this document and are outlined here for those who may not yet have a complete understanding of how to access and control the underlying operating system in Linux, @@ -122,6 +122,7 @@ Most cable modems have two possible interfaces for connection to your computer: Ethernet or USB. If your version of Linux is like most, there is very little you will need to do to to get your cable modem working with an Ethernet interface as long as you have support for networking and the driver for your specific networking hardware installed. + Ethernet Support @@ -144,6 +145,7 @@ using whatever kernel configuration front-end application (whether make xconfig) prior to compiling a custom kernel. For 2.4.x and earlier kernels under the heading 'Networking options' you will require 'TCP/IP Networking' along with 'Network Device Support,' go to 'Ethernet (10 or 100Mbit) Support' and enable your specific NIC driver. If you use the 2.6.x series, the heading 'Drivers' has a sub-heading 'Networking Support,' where you should enable 'Network Device Support' and 'Ethernet Connection Support/Ethernet (10 or 100Mbit), as well as your specific NIC hardware driver. If you are interested in how to configure the USB interface go to ; otherwise you can go to . + USB Interface Support @@ -167,6 +169,7 @@ For kernel 2.6.x you will need See for instructions on how to load modules when time to test the modem. + The Modem Device First, plug in and turn on the cable modem. Connect your Ethernet card to the modem with 10BaseT/100BaseT cable @@ -202,7 +205,7 @@ url="http://www.tldp.org/HOWTO/mini/DHCP/x74.html">DHCP mini-HOWTO.

- Configuration + Configuration Ready to Start With an Ethernet-Modem connection Once you are plugged into the system, your modem is on and your dhcp server is running as outlined in , you should be provided your own IP address that @@ -226,6 +229,7 @@ successfully acquired an IP address (the 'inet addr') provided by our cable inte service provider. A simple Ethernet-based configuration should be complete at this step. If you have more than one Ethernet interface available and want to select a specific one for the cable service, go on to . + Grabbing A Specific Interface Let's say @@ -261,6 +265,7 @@ hardware or for just plain testing. Use ifconfig: You can check if it worked by calling ifconfig without options after your next reboot. See man ifconfig for more options. + Automatic Configuration of Devices The method for automatically assigning a particular interface name ethX, @@ -284,6 +289,7 @@ eth1 it won't work. The easy way to do this at boot up is to make an i script to load the dhcp address to the correct interface, which should be placed in /etc/init.d. Then run update-rc.d as root with the correct arguments (see man update-rc.d). + Red Hat The file to edit will of the form ifcfg-ethX, located in @@ -303,10 +309,12 @@ save it. If the file doesn't exist for the interface you need you can create it, for example ifcfg-eth1. You can then use ifconfig eth1 up from the command line to use it immediately. Upon reboot the correct hardware settings should be loaded automatically. + Slackware Slackware has a configuration utility named 'netconfig' that you can use at the command line as root to modify your network settings and configure interfaces by static IP addresses or dhcp. You can rerun it at any time to reconfigure things once you have installed your modem. + @@ -316,6 +324,7 @@ distribution-specific information to add; see . Consult distribution documentation where appropriate. + Using the USB interface instead of an Ethernet card @@ -338,7 +347,7 @@ There are two ways your kernel may support a device driver: either by being stat 0.98.6 7 Jan 2002 Brad Hards and another Mar 2 11:00:52 K7 kernel: usb.c: registered new driver CDCEther -in the case of a statically compiled driver or a module loaded at boot. +in the case of a statically compiled driver or a module loaded at boot. If you don't see it, to find out if your kernel has already loaded the CDCEther (Communications Device Class Ethernet) driver as a module, on the command line issue lsmod as root. You should see the module CDCEther listed for 2.4.x kernels, or alternatively usbnet for 2.6.x kernels. @@ -357,7 +366,7 @@ or at the end of dmesg | less from the command line: Mar 2 11:00:52 K7 kernel: usb.c: registered new driver CDCEther If all goes well you should see something like the following in your system log -files or at the end of dmesg: +files or at the end of dmesg: Mar 2 11:00:52 K7 kernel: CDCEther.c: 0.98.6 7 Jan 2002 Brad Hards and another @@ -379,16 +388,23 @@ device have been addressed in . configuring a cable modem and cable internet service providers in Israel on Jess' webpage for those that live there. I have personally subscribed to two large cable ISPs in the U.S. without any trouble using the instructions outlined above. The previous incarnation of this document had a large catalogue of ISPs listed by geography, but as a rule the identity of the upstream provider should not affect configuration. If your cable ISP claims not to support linux, it is not because of any technical difficulties related to the operating system. Just don't expect them to configure if for you on your end like they do for most other users (that's why you're reading this document, right?). Ambit ModemsSupported by Ethernet and CDCEther. + Broadcom Cable ModemsSupported by Ethernet and CDCEther. + Ericson PipeRider ModemsSupported by Ethernet and CDCEther. + Motorola SurfBoard Modems This model has enjoyed widespread use by cable providers. There is a separate HOWTO, written by your humble author. Supported by both Ethernet and USB CDCEther. Refer to that document for any hardware specific questions. The generic instructions above generally work. -RCA (Tompson) ModemsSupported with Ethernet, CDCEther untested. + +RCA (Tompson) ModemsSupported with Ethernet, CDCEther untested. + Terayon ModemsAt minimum the tj715 is known to be supported using Ethernet and CDCEther. + Toshiba PCX-XXXX Cable Modems The four X's in the name indicate model number. Works with Ethernet, CDCEther untested. 'out-of-the-box' with the above instructions. + Webstar ModemsSupported with Ethernet, CDCEther untested. From ef3222af2738007aaaad74dffc0e05a278c200e2 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 02:25:14 -0800 Subject: [PATCH 033/214] DocBook validation correction adding a few and closing tags to allow for validation --- LDP/howto/docbook/Debian-Jigdo.sgml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/LDP/howto/docbook/Debian-Jigdo.sgml b/LDP/howto/docbook/Debian-Jigdo.sgml index 7f9b2fc9..817c28d4 100644 --- a/LDP/howto/docbook/Debian-Jigdo.sgml +++ b/LDP/howto/docbook/Debian-Jigdo.sgml @@ -206,8 +206,8 @@ were two ways of creating Debian CDs: - Downloading the entire ISO - Using the pseudo-image kit (PIK) + Downloading the entire ISO + Using the pseudo-image kit (PIK) This document is about the newer and better way of obtaining Debian ISO images, using a @@ -1030,6 +1030,7 @@ url="http://www.daemon-tools.cc">Daemon tools and Nero Image Drive are both very popular. See also http://tinyurl.com/c39zr for more options. + @@ -1219,13 +1220,13 @@ You might find that under MS Windows, jigdo-lite will download some files but then fail to read their contents, which will produce a "No such file or directory" - error message. + error message. It seems that this occurs if the length of the filenames that jigdo processes exceeds a certain limit. The solution is to move the half-finished download up in the directory hierarchy, closer to the top-level directory of the drive. - + On MS Windows, why won't my image grow larger than 2GB? @@ -1297,7 +1298,7 @@ More About Scan Sources By now you know that when jigdo-lite asks for files to scan, - you can use 3 sources: + you can use 3 sources: From 6a44dd5e5e657295f00a04e3a80671917a1a2dae Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 02:28:50 -0800 Subject: [PATCH 034/214] DocBook validation correction adding a few and closing tags to allow for validation --- LDP/howto/docbook/Handspring-Visor.sgml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/LDP/howto/docbook/Handspring-Visor.sgml b/LDP/howto/docbook/Handspring-Visor.sgml index 07ef48a1..0635df32 100644 --- a/LDP/howto/docbook/Handspring-Visor.sgml +++ b/LDP/howto/docbook/Handspring-Visor.sgml @@ -164,7 +164,7 @@ need to configure linux to know how to do the low-level communication with your device, and then a a user-space program to do the actual communication with the device. - + @@ -326,6 +326,8 @@ Memory at ..... The preliminary USB Device Filesystem (CONFIG_USB_DEVICEFS) + + The appropriate controller - UHCI, or OHCI @@ -539,6 +541,7 @@ none /proc/bus/usb usbdevfs defaults 0 0 coldsync can be found at http://coldsync.org/. + pilot-link @@ -672,6 +675,7 @@ pilot-xfer -p /dev/ttyUSB1 -b visorbackup cp -r hotplug-2002_08_26/etc/hotplug /etc + Configure the Visor Driver @@ -759,6 +763,7 @@ pilot-xfer -p /dev/ttyUSB1 -b visorbackup + @@ -800,6 +805,7 @@ pilot-xfer -p /dev/ttyUSB1 -b visorbackup Hotplug info: http://linux-hotplug.sourceforge.net/. + Documentation to figure out type type of controller From d9ef8bfe6d2669497633af0cc78828c4aa57a60e Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 02:30:24 -0800 Subject: [PATCH 035/214] DocBook validation correction First line must include the definition. --- LDP/howto/docbook/Hard-Disk-Upgrade.sgml | 2 -- 1 file changed, 2 deletions(-) diff --git a/LDP/howto/docbook/Hard-Disk-Upgrade.sgml b/LDP/howto/docbook/Hard-Disk-Upgrade.sgml index eb5511a8..812a4908 100644 --- a/LDP/howto/docbook/Hard-Disk-Upgrade.sgml +++ b/LDP/howto/docbook/Hard-Disk-Upgrade.sgml @@ -1,5 +1,3 @@ - - - + + + The Server Side From fea669531f9520b00edab7c0a8e7a3ce645d812c Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 09:58:02 -0800 Subject: [PATCH 048/214] DocBook validation correction DocBook XML is picky about capitalization of the name of the document type. --- LDP/howto/docbook/rpmupgrade.sgml/rpmupgrade.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/LDP/howto/docbook/rpmupgrade.sgml/rpmupgrade.xml b/LDP/howto/docbook/rpmupgrade.sgml/rpmupgrade.xml index ff5da044..844185a5 100644 --- a/LDP/howto/docbook/rpmupgrade.sgml/rpmupgrade.xml +++ b/LDP/howto/docbook/rpmupgrade.sgml/rpmupgrade.xml @@ -1,5 +1,5 @@ - ]> From 8be30ab5540ba4692dadb98d92365d3af64b7bf4 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 10:32:44 -0800 Subject: [PATCH 049/214] DocBook validation correction Wrapping a in a , wrapping a bunch of elements in
and correcting a bad xreflinkend attribute to xreflabel, all to allow for validation. --- LDP/howto/docbook/ACPI-HOWTO.xml | 32 +++++++++++++++++++++++++++++--- 1 file changed, 29 insertions(+), 3 deletions(-) diff --git a/LDP/howto/docbook/ACPI-HOWTO.xml b/LDP/howto/docbook/ACPI-HOWTO.xml index 78b8bdae..f1d9f46d 100644 --- a/LDP/howto/docbook/ACPI-HOWTO.xml +++ b/LDP/howto/docbook/ACPI-HOWTO.xml @@ -453,7 +453,7 @@ directory for the newly patched kernel. You should create a backup of all import /usr/src/System.map -It is possible the location of these files differs on your system. Use locate as follows if the files are not in the locations specified above: locate <file> +It is possible the location of these files differs on your system. Use locate as follows if the files are not in the locations specified above: locate <file> @@ -476,8 +476,10 @@ directory for the newly patched kernel. You should create a backup of all import debian packages: binutils, e2fsprogs, gcc, make, module-init-tools, procps, util-linux (see also the list from 2.4) + Learn more about the 2.6 kernel before you upgrade This HOWTO does not include information on how to migrate from a 2.4 series kernel to a 2.6 series kernel. Please read the resources listed in before attempting a kernel upgrade. + 2.4.x series kernels @@ -509,11 +511,13 @@ site to find the kernel you would like. Download the kernel and patch +
- wget http://kernel.org/pub/linux/kernel/v2.4/linux-&kernel-version;.tar.bz2 + wget http://kernel.org/pub/linux/kernel/v2.4/linux-&kernel-version;.tar.bz2 Download the latest patch for your kernel. This may or may not be the newest patch available. Please look carefully. For example: if you are using the 2.4.20 kernel you would get acpi-20021212-2.4.20.diff.gz. The patches can be downloaded from: . Note the revision date. In this example above the date is 20021212 (December 12, 2002), but it will almost certainly be different for your kernel. You will need to know this number when you check to make sure the patch worked. +
 @@ -525,6 +529,7 @@ to your current kernel. This link must point to the new kernel, you will update Unpacking your kernel source files +
@@ -549,6 +554,7 @@ to your current kernel. This link must point to the new kernel, you will update +
 If your kernel needs to be patched, do so now. @@ -577,6 +583,7 @@ different ACPI related options that you will need to select. Please also read the list of . +
cd @@ -610,6 +617,7 @@ different ACPI related options that you will need to select. +
@@ -629,11 +637,13 @@ kernel. I still need this option even in the 2.6.6 kernel due to my nVidia graph Each of these steps should be performed as the root user. +
cd /usr/src/linux make-kpkg clean make-kpkg kernel_image modules_image +
I no longer use .date to distinguish kernel builds. It was too frustrating to have 030627a, 032627b (etc) as I tried to figure things out. I now use names, in alphabetical order, starting with the kernel build alien. My current kernel build is Ulairi. (The machine itself is Smeagol--a name it has earned.) @@ -646,6 +656,7 @@ kernel builds. It was too frustrating to have 030627a, 032627b (etc) as I tried Each of these steps should be performed as the root user. +
cd /usr/src dpkg kernel-image-&kernel-version;.&kernel-name;_10.00.Custom_i386.deb @@ -680,6 +691,7 @@ read-only .deb files. +
@@ -697,28 +709,36 @@ system), you will need to check that you are running the new kernel with the cor First you need to make sure you are running the correct kernel. This can be done with the command line tool uname. The revision is the date the patch was released and will be different for each kernel release. + &prompt; uname + Assuming you are indeed running the new kernel, you can now check the ACPI's revision date with the following command. + &prompt; cat /proc/acpi/info + This may give you only a version number, or a more detailed list. You are looking for the line that starts with version:. If for some reason that gives you no information, you can also check the message printed when ACPI was first loaded as the system was booting. This information can be printed to a terminal window with the application dmesg. + &prompt; dmesg | grep ACPI.*Subsystem\ revision + It should give the output: ACPI: Subsystem revision 20040326. The revision number is the date the patch was originally released by the development team. If you patched your kernel according to this number will match the patch that you installed in . To read all the ACPI-related information, you can expand the pattern that grep matches and selectively print all ACPI messages: + &prompt; dmesg | grep ACPI + @@ -908,6 +928,7 @@ look for the absence of errors.) Patching your kernel These steps should be performed as the root user. +
cd @@ -936,6 +957,7 @@ look for the absence of errors.) (this is the actual patching part) +
 Once you have finished patching your kernel, continue reading at The normal way of compiling a kernel does not use make-kpkg. Instead, it uses the following steps: - + Compile the kernel +
cd @@ -982,6 +1005,7 @@ generic way. In fact it is probably only 10 or so lines of difference. (remember to unpack your modules first) +
 @@ -994,6 +1018,7 @@ lilo. If you are not doing things The Debian Way your Install the new kernel +
cd @@ -1025,6 +1050,7 @@ lilo. If you are not doing things The Debian Way your +
 From baa86853312ff4222d1b285502e45cb24d19a40b Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 10:47:50 -0800 Subject: [PATCH 050/214] DocBook validation correction OK, this one is just weird--order matters (!?); The child of needed to precede the
child. The document would not validate without this change. Seems very strange. --- LDP/howto/docbook/Apache-WebDAV-LDAP-HOWTO.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/LDP/howto/docbook/Apache-WebDAV-LDAP-HOWTO.xml b/LDP/howto/docbook/Apache-WebDAV-LDAP-HOWTO.xml index d89064ae..9c7a5c83 100644 --- a/LDP/howto/docbook/Apache-WebDAV-LDAP-HOWTO.xml +++ b/LDP/howto/docbook/Apache-WebDAV-LDAP-HOWTO.xml @@ -12,10 +12,10 @@ Saqib Ali -
- saqib@seagate.com -
Offshore XML/XHTML Development +
+ saqib@seagate.com +
From 6801a8d915e53109f456cfc981facc0c1a116173 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 11:12:07 -0800 Subject: [PATCH 051/214] DocBook validation correction Persnickety about the placement of elements in both the <appendix/>, where it must come after the <appendixinfo/> and in the <sect1/>, which requires a <title/>. Changes made to allow document validation. --- .../Conexant+Rockwell-modem-HOWTO.sgml | 23 +++++++++++-------- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git a/LDP/howto/docbook/Conexant+Rockwell-modem-HOWTO.sgml b/LDP/howto/docbook/Conexant+Rockwell-modem-HOWTO.sgml index 8e479cf1..0d1e9a15 100644 --- a/LDP/howto/docbook/Conexant+Rockwell-modem-HOWTO.sgml +++ b/LDP/howto/docbook/Conexant+Rockwell-modem-HOWTO.sgml @@ -211,7 +211,7 @@ Remember when asking for help to include your modems Device ID, Vendor ID and an <title>Quick Start guide This section tries to get you up and running as soon as possible, if you can follow the steps given in this section and they work for you, you can ignore the rest of this howto. This section is updated more often then the rest of the HOWTO so will contain the most up to date information. -First you need to find out if your modem is an HSF or HCF modem. You can find out from your modem by looking at it's Windows drivers or looking at the label on it's chipset, or alternatively you can download the ListModem utility and run it to get the information. Drivers are available for both types, but the HSF driver is further into development then the HCF driver so is likely to be more advanced for now. Expect the HCF driver to come out of beta sometime mid-year(2002). @@ -234,7 +234,6 @@ Download the driver from ht Load up a terminal (or go to a console), change to the root user and enter the directory you downloaded the driver to and use the command "rpm -i" followed by the name of the driver. For instance if it is called hsflinmodem-4.06.06.02mbsibeta02012000-1.i586.rpm you would enter, &pt;rpm -i hsflinmodem-4.06.06.02mbsibeta02012000-1.i586.rpm - Run the program hsfconfig and just follow the on-screen instructions and it should automatically detect your modem and install the driver. If you have any problems consult the documentation that comes with the driver. @@ -264,7 +263,6 @@ Download the driver from ht Load up a terminal (or go to a console), change to the root user and enter the directory you downloaded the driver to and use the command "rpm -i" followed by the name of the driver. For instance if it is called hcflinmodem-0.9mbsibeta02030801-1.i586.rpm you would enter, &pt;rpm -i hcflinmodem-0.9mbsibeta02030801-1.i586.rpm - @@ -808,7 +806,7 @@ When trying to dial my ISP I get "No Carrier" error ? It has been reported that making the following changes to your configuration will work: - + @@ -821,7 +819,6 @@ Replace the command ATDT with ATX3DT - @@ -832,7 +829,9 @@ When running ./ins_alI get the error "No matching INF file is found for SoftK56 + This occurs when the driver can't find the correct %HSFModem% line in the lin_hsf.inf line, go back through the instructions and make sure that you didn't make a mistake when making or entering the the %HSFModem% line. + @@ -856,11 +855,9 @@ This is often caused by the modem's device number clashing with that of PCMCIA, -License + - - - + Version 1.1, March 2000 @@ -880,7 +877,12 @@ This is often caused by the modem's device number clashing with that of PCMCIA, document, but changing it is not allowed. - + +License + +GNU Free Documentation License + + GNU Free Documentation License Copyright 2000 Free Software Foundation, Inc. @@ -1526,6 +1528,7 @@ This is often caused by the modem's device number clashing with that of PCMCIA, +
From 5b385e13e1a8acf22766d07096cb8119709d7b93 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Sun, 17 Jan 2016 11:34:57 -0800 Subject: [PATCH 052/214] DocBook validation correction Adding lots of closing as well as a few and elements to allow validation of the document. --- LDP/howto/docbook/Apache-Compile-HOWTO.sgml | 56 +++++++++++++-------- 1 file changed, 34 insertions(+), 22 deletions(-) diff --git a/LDP/howto/docbook/Apache-Compile-HOWTO.sgml b/LDP/howto/docbook/Apache-Compile-HOWTO.sgml index 72400494..1cc450fb 100644 --- a/LDP/howto/docbook/Apache-Compile-HOWTO.sgml +++ b/LDP/howto/docbook/Apache-Compile-HOWTO.sgml @@ -467,13 +467,14 @@ desk (yes, its funny and he loves it!) freetype2-devel This RPM contains the header files needed for php re2c Only needed if PHP is being built from the CVS tree - + To be continued All major distributions should include this general prerequisites. + @@ -534,7 +535,7 @@ Search for and replace it i.e with