aldev updates

This commit is contained in:
alavoor 2003-08-18 20:31:37 +00:00
parent 02a9d75420
commit 4e3ab9b66c
2 changed files with 270 additions and 87 deletions

View File

@ -1,8 +1,43 @@
<?xml version="1.0"?>
<!--
** The syntax of DOCTYPE is described in
http://www.freebsd.cz/doc/en_US.ISO8859-1/books/fdp-primer/sgml-primer-doctype-declaration.html
**
<DOCTYPE first-element-in-doc formal-public-identifier-FPI>
** FPI is Owner//Keyword and Description//Language, -//Owner indicates
unregisterd and +//Owner indicates registered owner. ** Keyword can be
DTD,ELEMENT,ENTITIES or TEXT ** Description can be anything like "DocBook XML
my version V4.2" ** Language is 2 letter like EN for english -->
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"/usr/share/sgml/docbook/xml-dtd-4.2-1.0-19/docbookx.dtd" [
<!ENTITY version "0.01">
] >
<!--
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
[
<!ENTITY version "0.01">
] >
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://docbook.org/xml/4.2/docbookx.dtd" [
<!ENTITY version "0.01">
] > ********** *** For some reason file:/usr/share/... does not work, remove
file: and change to '/usr/share/...' then it works
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"/usr/share/sgml/docbook/xml-dtd-4.2-1.0-19/docbookx.dtd" [
<!ENTITY version "0.01">
] >
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"file:/usr/share/sgml/docbook/xml-dtd-4.2-1.0-19/docbookx.dtd" [
<!ENTITY version "0.01">
] >
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://docbook.org/xml/4.2/docbookx.dtd" [
<!ENTITY version "0.01">
] >
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY version "0.01">
]>
] > -->
<article>
<articleinfo>
<title>
@ -28,7 +63,7 @@
</affiliation>
</author>
<pubdate>
v6.5, 27 July 2003
v6.7, 15 Aug 2003
</pubdate>
<abstract>
<para>
@ -133,10 +168,11 @@
<para>
It is Illegal, Unlawful, Felony and Fraud to use a computer
without compiling the OS Kernel with your VERY OWN hands! There is
a 6 months imprionment and US$50,000 fine if you use a computer
without compiling the the OS Kernel source code. Some
states/countries have stringent laws which prohibit using any
computer without compiling the kernel source code.
a punishment of 3 months jail (imprionment) and US$50,000 fine if
you use a computer without compiling the the OS Kernel source
code. Some states/countries/governments have stringent laws which
prohibit using any computer without compiling the kernel source
code.
</para>
</listitem>
<listitem>
@ -257,6 +293,33 @@
After this, look in the next section to do make and install.
</para>
</sect2>
<sect2 id="Documentation">
<title>
New Release Changes: Documentation
</title>
<para>
If you downloaded the new kernel sources, then make sure you read the
following files in /usr/src/linux/Documentation
<itemizedlist>
<listitem>
<para>
Changes: This file lists the minimum requirements and some notes
</para>
</listitem>
<listitem>
<para>
kernel.txt: This file has 'Understanding the Linux Kernel'
</para>
</listitem>
<listitem>
<para>
Read all *.txt files in /usr/src/linux/Documentation but most
important ones are kernel*.txt files.
</para>
</listitem>
</itemizedlist>
</para>
</sect2>
<sect2 id="impatient">
<title>
For the Impatient
@ -1947,6 +2010,18 @@
<para>
Check the following books on "The Linux Kernel" at
<itemizedlist>
<listitem>
<para>
Understanding the Linux Kernel : In your computer at
/usr/src/linux/Documentation, see the file kernel-docs.txt which
is also online at
<ulink url="http://www.dit.upm.es/~jmseyas/linux/kernel/hackers-docs.html">
"http://www.dit.upm.es/~jmseyas/linux/kernel/hackers-docs.html"
</ulink>
This lists several important links on Linux Kernel Textbooks and
kernel documentation. Must visit this website.
</para>
</listitem>
<listitem>
<para>
Kernel book
@ -2892,16 +2967,16 @@
<listitem>
<para>
Linuxconf
<ulink url="http://www.solucorp.qc.ca/linuxconf">
http://www.solucorp.qc.ca/linuxconf
<ulink url="http://www.solucorp.qc.ca/linuxconf">
http://www.solucorp.qc.ca/linuxconf
</ulink>
Linuxconf is a extremely large project. It is tremendously
powerful and has large number of features. Linuxconf is the BEST
KNOWN system admin tool for Linux!! It is available in all distros
like Redhat, Debian, Suse, and others. The Linuxconf is the
equivalent of SAM of HPUX and SMITTY of AIX. It runs on console
window and as well as in GUI in X-Window.
On Debian Linux to download and install just do 'apt-get linuxconf'.
window and as well as in GUI in X-Window. On Debian Linux to
download and install just do 'apt-get linuxconf'.
</para>
</listitem>
<listitem>
@ -2951,8 +3026,8 @@
/usr/sbin/redhat-config-network-druid /usr/sbin/redhat-config-services
To start the progam -
# /usr/sbin/redhat-config-bind &
# /usr/sbin/redhat-config-network &
# /usr/sbin/redhat-config-bind &amp;
# /usr/sbin/redhat-config-network &amp;
And try other commands.
</programlisting>
@ -4215,13 +4290,13 @@ Initializing RT netlink socket
</table>
</para>
<para>
2 short beeps : POST not correct. Error in a Harware test. 1 short & 2
long beeps : video error. 1) Video ROM BIOS, parity error. 2) Problem
with the horizontal retour from the video adapter. 1 long & 3 short
beeps: video error. 1) videocard defect. 2) wrong detection from used
monitor. 3) Video RAM error. 1 long beep : POST was correct If there
is a posterror, there is a hardwareproblem. Check the extentioncards
for a bad contact
2 short beeps : POST not correct. Error in a Harware test. 1 short
&amp; 2 long beeps : video error. 1) Video ROM BIOS, parity error. 2)
Problem with the horizontal retour from the video adapter. 1 long
&amp; 3 short beeps: video error. 1) videocard defect. 2) wrong
detection from used monitor. 3) Video RAM error. 1 long beep : POST
was correct If there is a posterror, there is a hardwareproblem. Check
the extentioncards for a bad contact
</para>
<para>
See also
@ -4813,7 +4888,7 @@ bash# cp /usr/src/kernelconfigs/.config.save .config # In case you want to reus
gives compile problems. You should give 'make mrproper' before doing
make.
<programlisting format="linespecific">
bash# make clean && make mrproper # "MUST DO THIS mrproper", otherwise you will face hell lot of problems !!
bash# make clean &amp;&amp; make mrproper # "MUST DO THIS mrproper", otherwise you will face hell lot of problems !!
</programlisting>
If this problem persists, then try menuconfig instead of xconfig.
Sometimes GUI version xconfig causes some problems:

View File

@ -1,8 +1,42 @@
<?xml version="1.0"?>
<!--
** The syntax of DOCTYPE is described in
http://www.freebsd.cz/doc/en_US.ISO8859-1/books/fdp-primer/sgml-primer-doctype-declaration.html
** and described at http://xmlwriter.net/xml_guide/entity_declaration.shtml **
<DOCTYPE first-element-in-doc formal-public-identifier-FPI>
** FPI is Owner//Keyword and Description//Language, -//Owner indicates
unregisterd and +//Owner indicates registered owner. ** Keyword can be
DTD,ELEMENT,ENTITIES or TEXT ** Description can be anything like "DocBook XML
my version V4.2" ** Language is 2 letter like EN for english -->
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"/usr/share/sgml/docbook/xml-dtd-4.2-1.0-19/docbookx.dtd" [
<!ENTITY version "0.01">
] >
<!--
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
[
<!ENTITY version "0.01">
] >
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://docbook.org/xml/4.2/docbookx.dtd" [
<!ENTITY version "0.01">
] > ********* **** For some reason file:// does not work. But why???
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"/usr/share/sgml/docbook/xml-dtd-4.2-1.0-19/docbookx.dtd" [
<!ENTITY version "0.01">
] >
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"file:/usr/share/sgml/docbook/xml-dtd-4.2-1.0-19/docbookx.dtd" [
<!ENTITY version "0.01">
] >
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://docbook.org/xml/4.2/docbookx.dtd" [
<!ENTITY version "0.01">
] >
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY version "0.01">
]>
] > -->
<article>
<articleinfo>
<title>
@ -28,7 +62,7 @@
</affiliation>
</author>
<pubdate>
v18.8, 14 May 2003
v19.2, 15 Aug 2003
</pubdate>
<abstract>
<para>
@ -847,9 +881,8 @@ set autoindent
<emphasis remap="it">
shiftwidth
</emphasis>
is the number of spaces the lines will be shifted with "> > " or "
<
<" vi commands. Refer to Vi tutorials
is the number of spaces the lines will be shifted with "&gt; &gt; " or "
&lt; &lt; " vi commands. Refer to Vi tutorials
<xref linkend="vim-tutorial"/>
for more details.
</para>
@ -1490,9 +1523,7 @@ OR plain vanilla mode
</para>
<para>
Inside the Vim editor, you can jump to a function by typing : (colon)
tag
< function name >
as below -
tag &lt; function name &gt; as below -
<programlisting format="linespecific">
:tag sample_function</programlisting>
This will place the cursor on first line of sample_function()
@ -1813,44 +1844,25 @@ sort $tmp_tag &gt; tags
</para>
<para>
<screen format="linespecific">
VIM - main help file
Move around: Use the cursor keys, or "h" to go left,
"j" to go down, "k" to go up, "l" to go right.
":1" takes you to 1st line of page
":n" takes you to nth line of page
"&lt;SHIFT&gt;g" takes you to bottom of page
":/someword/ will search for "someword" in doc
Close this window: Use ":q&lt;Enter&gt;".
Jump to a subject: Position the cursor on a tag between |bars| and hit CTRL-].
With the mouse: ":set mouse=a" to enable the mouse (in xterm or GUI).
Double-click the left mouse button on a tag between |bars|.
jump back: Type CTRL-T or CTRL-O.
Get specific help: It is possible to go directly to whatever you want help
on, by giving an argument to the ":help" command |:help|.
It is possible to further specify the context:
WHAT PREPEND EXAMPLE ~
Normal mode commands (nothing) :help x
Visual mode commands v_ :help v_u
Insert mode commands i_ :help i_&lt;Esc&gt;
command-line commands : :help :quit
command-line editing c_ :help c_&lt;Del&gt;
Vim command arguments - :help -r
options ' :help 'textwidth'
list of documentation files:
|howto.txt| how to do the most common things
|intro.txt| introduction to Vim
|index.txt| alphabetical index for each mode
|autocmd.txt| automatically executing commands on an event
|change.txt| delete and replace text
VIM - main help file Move around: Use the cursor keys, or "h" to go
left, "j" to go down, "k" to go up, "l" to go right. ":1" takes you to
1st line of page ":n" takes you to nth line of page "&lt;SHIFT&gt;g"
takes you to bottom of page ":/someword/ will search for "someword" in
doc Close this window: Use ":q&lt;Enter&gt;". Jump to a subject:
Position the cursor on a tag between |bars| and hit CTRL-]. With the
mouse: ":set mouse=a" to enable the mouse (in xterm or GUI).
Double-click the left mouse button on a tag between |bars|. jump back:
Type CTRL-T or CTRL-O. Get specific help: It is possible to go
directly to whatever you want help on, by giving an argument to the
":help" command |:help|. It is possible to further specify the
context: WHAT PREPEND EXAMPLE ~ Normal mode commands (nothing) :help x
Visual mode commands v_ :help v_u Insert mode commands i_ :help
i_&lt;Esc&gt; command-line commands : :help :quit command-line editing
c_ :help c_&lt;Del&gt; Vim command arguments - :help -r options '
:help 'textwidth' list of documentation files: |howto.txt| how to do
the most common things |intro.txt| introduction to Vim |index.txt|
alphabetical index for each mode |autocmd.txt| automatically executing
commands on an event |change.txt| delete and replace text
</screen>
</para>
</sect1>
@ -3039,17 +3051,12 @@ list of documentation files:
characters or words.
</para>
<para>
Some other filter commands (here,
< CR >
means press Return):
Some other filter commands (here, &lt; CR &gt; means press Return):
<itemizedlist>
<listitem>
<para>
<emphasis remap="bf">
!/the
< CR >
sort
< CR >
!/the &lt; CR &gt; sort &lt; CR &gt;
</emphasis>
: Sort from the current line up to and including the next line
containing the
@ -3058,8 +3065,7 @@ list of documentation files:
<listitem>
<para>
<emphasis remap="bf">
!1Ggrep the
< CR >
!1Ggrep the &lt; CR &gt;
</emphasis>
: Replace from the current line to and including Line 1 with
just the lines that contain the
@ -3068,8 +3074,7 @@ list of documentation files:
<listitem>
<para>
<emphasis remap="bf">
!Gawk '{print $1}'
< CR >
!Gawk '{print $1}' &lt; CR &gt;
</emphasis>
: From the current line to the end of file, replace every line
with just its first word.
@ -3496,8 +3501,7 @@ list of documentation files:
</para>
<para>
<emphasis remap="bf">
/the
< CR >
/the &lt; CR &gt;
</emphasis>
</para>
<para>
@ -3514,8 +3518,7 @@ list of documentation files:
</para>
<para>
<emphasis remap="bf">
:n
< CR >
:n &lt; CR &gt;
</emphasis>
</para>
<para>
@ -3548,8 +3551,7 @@ list of documentation files:
</para>
<para>
<emphasis remap="bf">
:w
< CR >
:w &lt; CR &gt;
</emphasis>
</para>
<para>
@ -3557,8 +3559,7 @@ list of documentation files:
</para>
<para>
<emphasis remap="bf">
:rew
< CR >
:rew &lt; CR &gt;
</emphasis>
</para>
<para>
@ -5569,6 +5570,113 @@ list of documentation files:
</para>
</sect2>
</sect1>
<sect1 id="xml_editor">
<title>
Vim as XML Editor
</title>
<para>
If you do lot of XML editing with Vim, refer to this mini-howto on Vim
as XML Editor at
<ulink url="http://www.pinkjuice.com/howto/vimxml">
http://www.pinkjuice.com/howto/vimxml
</ulink>
. See also
<ulink url="http://www.protocol7.com/svg-wiki/?VimXml">
Vim XML Wiki page
</ulink>
,
<ulink url="http://vim.sourceforge.net/scripts/script.php?script_id=301">
Devin Weaver "Script Karma" - xmledit
</ulink>
a filetype plugin to help edit XML, HTML, and SGML documents,
<ulink url="http://www.vim.org/scripts/script_search_results.php?keywords=xml">
Vim.org XML scripts
</ulink>
,
<ulink url="http://www.vim.org/tips/tip_search_results.php?keywords=xml">
Vim.org XML tips
</ulink>
,
<ulink url="http://www.w3.org/TR/REC-xml.html#sec-well-formed">
w3.org - Well formed XML doc
</ulink>
.
</para>
<sect2 id="matchit">
<title>
Matchit.vim &amp; Xmledit.vim
</title>
<para>
Jump around the buffer with %, eg between opening and closing angle
brackets of XML tags and between opening and closing tags when XML
syntax recognition is turned on. home
<ulink url="www.vim.org/scripts/script.php?script_id=39">
http://www.vim.org/scripts/script.php?script_id=39
</ulink>
For installation instructions enter:
<programlisting format="linespecific">
vim somefile.txt
:help add-local-help
rpm -qa | grep -i vim
rpm -ql vim-minimal | less
rpm -ql vim-common | less
ls /usr/share/vim/vim61/macros/matchit.*
mkdir -p ~/.vim/plugin
cp /usr/share/vim/vim61/macros/matchit.vim ~/.vim/plugin/
mkdir ~/.vim/doc
cp /usr/share/vim/vim61/macros/matchit.txt ~/.vim/doc/
vim some-xml-file.xml # And test out the % key to match the tags
</programlisting>
For xmledit.vim download the tar ball from
<ulink url="http://www.vim.org/scripts/script.php?script_id=301">
http://www.vim.org/scripts/script.php?script_id=301
</ulink>
and unpack this into ~/.vim for Unix and into $VIM/vimfiles folder for
MS DOS or MS Windows.
<programlisting format="linespecific">
cd ~/.vim
tar xvf xmledit.tar.gz
ln ftplugin/*.xml ~/.vim/plugin
vim some-xml-file.xml # And test out the autocreation of tags in insert mode
</programlisting>
</para>
</sect2>
<sect2 id="vim_docbook">
<title>
Vim and Docbook - Useful key mappings
</title>
<para>
This is from
<ulink url="http://supportweb.cs.bham.ac.uk/documentation/tutorials/docsystem/build/tutorials/gvim/gvim.html#gVim-DocBook">
Ashley - gVim and Docbook
</ulink>
. One can write DocBook documents at an incredably faster rate if one
maps element entry to key bindings. A directory called xml was created
in the ftplugins directory of the gVim installation. Into this was
placed a vim file that contained macros to map key combinations to
element insertions. Comma preceeds each mapping, this is convenient
because if the user types comma followed by space, nothing happens,
but if the user types comma followed by one of the mapped key
combinations an element is inserted. Most of the mappings are
intuitive, for example, ulink is mapped onto ,-u-l. The mappings are
very easy to customise and the improvement in document creation speed
is amazing.
</para>
</sect2>
<sect2 id="XML_Validation">
<title>
XML Validation
</title>
<para>
To check for well-formedness of your XML document just do
<programlisting format="linespecific">
:!xmllint --valid --noout %
</programlisting>
And the --dtdvalid dtd allows validation of the document(s) against a
given DTD.
</para>
</sect2>
</sect1>
<sect1 id="wysiwyg">
<title>
Build Your "WYSIWYG" HTML Editor With Vi &amp; Netscape
@ -5980,8 +6088,8 @@ sub atchange { # if $file has changed, do $cmd{$file}
Emacs - Old Habits Die Hard !
</title>
<para>
If you were using Emacs before and now started using Vim & vi, then this
mistake is commited very often and will be quite annoying to you.
If you were using Emacs before and now started using Vim &amp; vi, then
this mistake is commited very often and will be quite annoying to you.
</para>
<para>
You hit "control x" "control s" to save the file and Vim stops dead. How