LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2001-03-12 00:00:19 +00:00
parent 7637855f61
commit e97dcbc053
3 changed files with 297 additions and 154 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
LDP/howto/linuxdoc/C-C++Beautifier-HOWTO.sgml
View File

@ -42,7 +42,7 @@ C-C++ Beautifier HOW-TO
<author>Al Dev (Alavoor Vasudevan)
<htmlurl url="mailto:alavoor@yahoo.com"
name="alavoor@yahoo.com">
<date>v10.0, 30 Jan 2001
<date>v12.0, 08 Mar 2001
<abstract>
This document will help you to format (beautify) the C/C++ programs so
that it is more readable and confirms to your site C/C++ coding standards.
@ -79,16 +79,24 @@ the <bf>productivity</bf> of programmers by <bf>2 times</bf>!!
On Linux/Unixes there is a command called <bf>"indent"</bf> and <bf>"cb"</bf>
. Refer to 'man indent' and 'man cb'. Note that <bf>indent</bf> and
<bf>cb</bf> work for only "C" programs. For "C++" programs use
<bf>"bcpp"</bf>. Download the beautifier program from one of the following
<bf>"bcpp"</bf>.
<bf>Important NOTE:</bf> <it>To compile bcpp under unix, unpack bcpp.tar.gz and
you <bf>MUST</bf> change directory to "code" and give a make. Do not change
to "unix" directory and give a make. That will give lots of errors.</it>
Download the beautifier program from one of the following
<itemize>
<item>If you are having trouble downloading software from any of the sites below,
then download from my site at <url url="http://www.aldev.8m.com/cppbeautifier">
<p>
<item>C++ : BCPP site is at
<url url="http://dickey.his.com/bcpp/bcpp.html">
or at
<url url="http://www.clark.net/pub/dickey">
<item>C++ : BCPP ftp site is at
<url url="ftp://dickey.his.com/bcpp/bcpp.tar.gz">
or at <url url="http://www.clark.net/pub/dickey">.
BCPP ftp site is at <url url="ftp://dickey.his.com/bcpp/bcpp.tar.gz">
<item>C++ : <url url="http://www.consultix-inc.com/c++b.html">
<item>C : <url url="http://www.chips.navy.mil/oasys/c/">
and mirror at <url name="Oasys" url="http://oasys.nctamslant.navy.mil/oasys/c">
<item>C++ : <url url="http://www.semdesigns.com/Products/DMS/DMSToolkit.html">
<item> C++, C, Java and Oracle Pro-C Beautifier <url url="http://www.geocities.com/~starkville/main.html">
<item> C++, C beautifier <url url="http://users.erols.com/astronaut/vim/ccb-1.07.tar.gz">
@ -219,14 +227,12 @@ HTML, SQL, Java, Perl, Fortran.
<p>
<item>C++ : BCPP site is at
<url url="http://dickey.his.com/bcpp/bcpp.html">
or at
<url url="http://www.clark.net/pub/dickey">
<item>C++ : BCPP ftp site is at
<url url="ftp://dickey.his.com/bcpp/bcpp.tar.gz">
or at <url url="http://www.clark.net/pub/dickey">.
BCPP ftp site is at <url url="ftp://dickey.his.com/bcpp/bcpp.tar.gz">
<item>C++ : <url url="http://www.consultix-inc.com/c++b.html">
<item>C : <url url="http://www.chips.navy.mil/oasys/c/">
and mirror at <url name="Oasys" url="http://oasys.nctamslant.navy.mil/oasys/c">
<item> C++, C, Java, Oracle Pro-C Beautifier <url url="http://www.geocities.com/~starkville/main.html">
<item> C++, C beautifier <url url="http://users.erols.com/astronaut/vim/ccb-1.07.tar.gz">

404
LDP/howto/linuxdoc/Diskless-HOWTO.sgml
View File

@ -52,7 +52,7 @@ DISKLESS NODES HOW-TO for Linux
<htmlurl url="mailto:gero@gkminix.han.de"
name="gero@gkminix.han.de">
<date>v18.0, 25 Jan 2001
<date>v19.0, 07 Mar 2001
<abstract>
This document describes how to set up a diskless Linux box.
As technology is advancing rapidly, network-cards are becoming cheaper and much
@ -279,6 +279,9 @@ hardware or software upgrades.
<item> Eliminates cost of cdrom, floppy, tape drive, modem, UPS battery, Printer
parallel ports, serial ports etc..
<p>
<item> Prevents pilferage of hardware components as diskless node has very little
RAM and low-cost CPU. The server has lots of memory and many powerful CPUs.
<p>
<item> Can operate in places like factory floor where a hard disk might be too fragile.
</itemize>
@ -329,6 +332,8 @@ Visit the LTSP and related sites at :-
<item> <url url="http://www.ltsp.org">
<item> <url url="http://www.disklessworkstations.com">
<item> <url url="http://www.slug.org.au/etherboot">
and at <url name="mirror-site" url="http://etherboot.sourceforge.net">
and at <url name="google-site" url="http://www.google.com/search?q=Etherboot">
<item> <url url="http://metalab.unc.edu/Linux/HOWTO/XFree86-Video-Timings-HOWTO.html">
</itemize>
Related topics worth seeing -
@ -355,36 +360,87 @@ Related topics worth seeing -
-->
<sect1> What is this ?
<p>
This chapter is written by Abhijit Dasgupta and is reproduced here from
<url url="http://www.nnaf.net/~abhijit/eep">.
Abhijit's email :
(<bf>Note</bf>: This chapter is written by Abhijit Dasgupta. Abhijit's email:
<htmlurl url="mailto:
abhijit@ans.net
takdoom@yahoo.com
" name="
abhijit@ans.net
takdoom@yahoo.com
">
A photo of the burner is at -
<url url="http://www.nnaf.net/~abhijit/pictures/eeprom-burner.jpg">
The name of this project is EEP and it can be obtained from:
<itemize>
<item> Primary site (download tarball only):
<url url="http://metalab.unc.edu/pub/Linux/apps/circuits/">
<item> Browse and/or download:
<url url="http://homepages.go.com/~abhijit_dasgupta/eep/index.html">
<item> Browse and/or download:
<url url="http://members.nbci.com/abhijit_dasgupta/eep/index.html">
</itemize>
Please do not use the old URL for EEP anymore.)
This is an eeprom burner for the 2816/2864 type of eeproms.
There are various designs available, but the main goal was to
EEP is an open hardware design (you are free to copy, use, and modify
the hardware design) EEPROM burner for 24-pin and 28-pin 5-volt EEPROMs.
There are various designs available, but my main goal was to
have something which
<itemize>
<item> is cheap (less than $35)
<item> is easy to build and uses only commonly available parts
<item> works with linux
<item> is easy to build and uses only the most commonly available parts,
<item> is cheap, and
<item> is controlled by Linux.
</itemize>
The latest version is EEP-0.2.
This one uses a handful of 74HCTxx logic chips all available
at the local Radio Shack store! It uses the PC parallel port
interface, and Abhijit wrote the driver code for Linux only, but it
should be easy to modify it for other PC operating systems.
The ICs in EEP are all common 74HCT series logic chips, and
it uses the PC parallel port interface. I wrote the driver code
for Linux only, but it is GPL code, and it should be easy to modify
it for other PC operating systems.
This was used to burn netboot PROMs for ethernet cards, which
were used to make diskless linux boxes. See the netboot/etherboot
I use EEP to burn netboot PROMs for ethernet cards, which
are used to make diskless linux boxes. See the netboot/etherboot
packages for details of how to do that. You can also use it
for building microcontroller systems with external ROM (e.g. 8031).
for microcontroller systems with external ROM (e.g. 8031).
A photo of the burner is at
<url url="http://homepages.go.com/~abhijit_dasgupta/eep/eeprom-burner.jpg">
and a PostScript schematic diagram is at
<url url="http://homepages.go.com/~abhijit_dasgupta/eep/schematic.ps">.
<!--
*******************************************
************ End of Section ***************
*******************************************
-->
<sect1> Supported EEPROMs
<p>
Most 5-volt-programmable 24-pin and 28-pin EEPROMs should work with
EEP-0.2. Here is a partial list of common EEPROMS that are known to work:
<itemize>
<item> 24-pin 2816/28C16, 2048 bytes (16 kilobits)
<item> 28-pin 2817/28C17, 2048 bytes (16 kilobits)
<item> 28-pin 2864/28C64, 8192 bytes (64 kilobits)
<item> 28-pin 28256/28C256, 32768 bytes (256 kilobits)
</itemize>
Various vendors manufacture these EEPROMs. Some are: Microchip,
Atmel, Xicor, Catalyst, and STM.
<!--
*******************************************
************ End of Section ***************
*******************************************
-->
<sect1> Schematics and pinouts
<p>
The schematic is in PostScript (schematic.ps), but a GIF image
(schematic.gif) is also included. The ascii version is older.
In the schematic diagram, pin numbers are shown outside each
IC diagram. Pin numbers for the big box on the right side are
for the 28-pin ZIF socket.
The file pinouts.txt has pinout information for the ICs used.
For the 74HCT ICs used in the circuit, Vcc and Ground connections
are not shown in the schematic. Of course, these pins must be
properly connected. Please refer to the pinouts.txt file for
full pinouts (in particular Vcc/Ground connections).
<!--
*******************************************
************ End of Section ***************
@ -393,19 +449,53 @@ for building microcontroller systems with external ROM (e.g. 8031).
-->
<sect1> Construction
<p>
WARNING: It is easy to destroy the parallel port of your PC by
<bf>WARNING</bf>: It is easy to destroy the parallel port of your PC by
connecting things to it. It is also possible to damage or destroy
the whole PC, its attachments, peripherals, and people near it
by improper connections and electrical accidents. USE EXTREME
CAUTION.
by improper connections and electrical accidents. <bf>USE EXTREME
CAUTION</bf>.
Disclaimer: Use at your own risk. There is absolutely
no warranty of any kind here.
<bf>Disclaimer</bf>: Use at your own risk. There is absolutely
no warranty of any kind here, see COPYING/LICENSE below.
The programmer can be built on a breadboard, but use a protoboard
for a more permanent version. Use 0.1uF power-bus bypass capacitors
generously. The 5V power source can be obtained from the PC itself,
but be careful here.
but be careful here. The 28-pin ZIF socket is perhaps the most
expensive component. If you are building on a breadboard, you
may be able to get by without it (not recommended).
The 180 ohms resistor connecting pin 10 (Y6) of the upper 74HCT259
to pin 1 of the ZIF socket is a current limiting resistor to protect
the 74HCT259 IC in cases where a 28-pin EEPROM with RDY/BSY pin
is used. When using 32 kilobytes (256 kilobits) EEPROMs like the
28256, it is recommended that this resistor be shorted for more
reliable operation.
<!--
*******************************************
************ End of Section ***************
*******************************************
-->
<sect1> Jumper setup
<p>
J1 and J2 are single-row 3-pin headers for jumpers. When using
28-pin EEPROMs, jumper the right two pins on both J1 and J2.
For 24-pin EEPROMs, jumper the left two pins on both J1 and J2.
<!--
*******************************************
************ End of Section ***************
*******************************************
-->
<sect1> Low-justification of 24-pin EEPROM devices
<p>
When plugging in a 24-pin EEPROM device (like 2816) into the
28-pin ZIF socket, make sure the 24-pin device is low-justified
in the ZIF socket. This means that pins 1, 2, 27, and 28 of the
ZIF socket will remain unused, and the ground pin of the devices
match up (i.e. pin 12 of the 24-pin device should sit in to
pin 14 of the ZIF socket).
<!--
*******************************************
************ End of Section ***************
@ -417,70 +507,96 @@ but be careful here.
<itemize>
<item> <bf>ICs:</bf> 74HCT123, 74HCT132, 74HCT138, 74HCT157, 74HCT574 (1 ea),
and 2 74HCT259s.
<item> <bf>Resistors:</bf> 100K, 10K, 1K, and 390 ohms (1 ea).
<item> <bf>Resistors:</bf> 100K, 10K, 1K, 180 ohms, and 390 ohms (1 ea).
<item> <bf>Capacitors:</bf> 100pF, 1uF, (1 ea) and 3 0.1uF power-bus bypass capacitors.
<item> <bf>Misc:</bf> 1 LED, 1 SPST switch, 25-conductor ribbon cable with DB25
male connector, 28 pin ZIF socket (small breadboard can be
used instead), jumper pins.
used instead), header pins for jumpering.
</itemize>
<!--
*******************************************
************ End of Section ***************
*******************************************
-->
<sect1> If you have already built EEP-0.1
<p>
If you have already built the EEP-0.1 burner, you can make the following
modificatons to make the EEP-0.2 burner:
<enum>
<item> remove the connection from 74HCT157 pin 1 (SEL) to the upper
74HCT259 pin 11 (Y6)
<item> remove the 1K resistor that is connected from pin 1 of ZIF-socket to Vcc
<item> add a new connection from pin 1 (SEL) of the 74HCT157 to pin 9 of
of the DB-25 parallel port
<item> add a new connection from pin 10 of the upper 74HCT259 to the unused
pin of J1
<item> add a 180 ohms resistor from pin 11 of the upper 74HCT259 to
pin 1 of the ZIF-socket
</enum>
<!--
*******************************************
************ End of Section ***************
*******************************************
-->
<sect1> How to build the software
<p>
Download the software <url url="http://metalab.unc.edu/pub/Linux/apps/circuits/EEP-0.2.tar.gz"> and unpack it. Then cd to the src directory and type
`make'.
<!--
*******************************************
************ End of Section ***************
*******************************************
-->
<sect1> Usage
<p>
Download the software from <url url="http://www.nnaf.net/~abhijit/eep/eeprom.tar.gz">.
To build the software, just cd to the src directory and type `make';
The progran eep is used for burning and reading an eeprom. It reads
data from stdin and writes it to the eeprom. The data needs to be in
binary (raw) format. None of the usual hex and/or ascii formats (Intel,
Motorola srecord, etc) are supported, so if your assembler ouputs in only
a hex/ascii format, you will need to convert it to binary (see, e.g.,
the Hex2bin and srecord, available from the metalab.unc.edu/pub/Linux
archive). When reading, the output is also raw binary to stdout (unless
the -t option is given).
<code>
readrom
-------
readrom will read a specified number of bytes from a 2816/2864 eeprom
starting at a given offset, and send it to the standard output in
either binary (raw) or ascii-hex listing format.
Usage:
readrom -b|-t offset size
eep -0|-1|-2 -r|-w -b|-t offset size
where
where:
-b output binary (raw) bytes
-t output text (ascii-hex) listing
offset start address of eeprom, 0..8191
size number of bytes to output, 0..8192
-0|-1|-2 -0 chooses port lp0, -1 port lp1, and -2 port lp2,
-r|-w -r reads the eeprom to stdout, and -w burns it from stdin,
-b|-t -b is normal (binary) mode, and -t is debugging (ascii hex),
offset is the start address within the eeprom, 0..32767, and,
size is the number of bytes to read/write, 0..32768.
Examples:
The offset and size can be specified as a string of digits in decimal
notation, but will be taken as hexadecimal when there is a ``0x'' prefix,
and octal when preceded by ``0''.
# read the contents of a 2864 in binary (raw) form and save it in a file:
readrom -b 0 8192 > contents.bin
# list 80 bytes starting at offset 32:
readrom -t 32 80
writerom
Examples
--------
writerom will read a given number of bytes from the standard input and
write them into a 2816/2864 eeprom starting at a specified offset.
writerom verifies the eeprom byte-by-byte as it writes into it.
# Read the contents of a 2864 in binary (raw) form and save it in a file
eep -1 -r -b 0 8192 > contents.bin
# Same as:
eep -1 -r -b 0 0x2000 > contents.bin
Usage:
writerom offset size
# List 16 bytes starting at offset 128
eep -1 -r -t 128 16
# Same as:
eep -1 -r -t 0x80 0x10
where
offset start address of eeprom, 0..8191
size number of bytes to output, 0..8192
# Write 16384 bytes from the file nepci.lzrom into the first-half of
# a 28C256 eeprom, through lp0:
cat nepci.lzrom | eep -0 -w -b 0 16384
Example:
# Write 8192 bytes from the file ne.lzrom into the eeprom:
writerom 0 8192 < ne.lzrom
</code>
<!--
*******************************************
@ -488,90 +604,91 @@ writerom 0 8192 < ne.lzrom
*******************************************
-->
<sect1> Schematic Diagram
<sect1> Schematic Diagram in ASCII
<p>
The schematic is in ascii, but a PostScript version
which looks better is available from
<url url="http://www.nnaf.net/~abhijit/eep/eeprom/schematic.ps">
<code>
+-------+
+5-------|RST | +5---o o o J1 +-----------+
+5--o----|/CLR1 | 10K | | |
| | |-----o--/VVV\-- +5 +----------|26 +5(NC) |
+------+ | |1/2 123| | +----------->|27 NC(/WE) |
16 o-|/CS2 | | | |--||-+ | +--------->|23 /WE(A11)|
| CS1|----o----|B1 | 100pF | | | |
| | | /Q1|---------->---------o o o J2 | ZIF28 |
| Y1|---------|/A1 | | | socket |
| 138 | +-------+ _ 1/2 74HCT132 | | for |
| | +5 --| \ __ | | 2816(2864)|
| Y2|--------------------------| O--| \ | | |
8 o-|A2 | +-------+ |_/ | O-------------->|/OE |
7 o-|A1 Y4|--------------->|EN Y7|-----o-|_/ | | |
6 o-|A0 Y3|----+ +5-----|RST | | | | |
| Y0|-+ | | Y6|--+ | | | |
| /CS3| | | | 259 | | | | | |
+------+ | | | Y4|--|--|-----------|------->|2 NC(A12) |
| | | | Y3|--|--|-----------+ | |
5 o--->---|--|--|--------o--|D Y2|--|--|------------------->|A10 |
4 o--->---|--|--|------o-|--|A2 Y1|--|--|------------------->|A9 |
3 o--->---|--|--|----o-|-|--|A1 Y0|--|--|------------------->|A8 |
2 o--->---|--|--|--o-|-|-|--|A0 | | | | |
| | | | | | | +-------+ | | +5------------|28 NC(+5) |
| | | | | | | | | +5----/VVV\---|1 NC(RDY) |
| | | | | | | +-------+ | | 1K | |
| | | | | | | | Y7|--|--|------------o------>|A7 |
| | +---------->|EN |--|--|-----------o|------>| |
| | | | | | | |--|--|----------o||------>| |
| | | | | | | 259 |--|--|---------o|||------>| |
| | | | | | | |--|--|--------o||||------>| |
| | | | | | | |--|--|-------o|||||------>| |
| | | | | +--|D |--|--|------o||||||------>| |
| | | | +----|A2 Y0|--|--|-----o|||||||------>|A0 |
| | | +------|A1 | | | |||||||| | |
| | +--------|A0 RST| | | |||||||| | ZIF28 |
| | +-------+ | | +------------+ | for |
| | | | | | data in | | 2816/64 |
| | +5 | +-->|/OE | | |
| | | | 574 | | |
+-------+ J1
+5-------|RST | +5---o o o----+ +-----------+
+5--o----|/CLR1 | 10K | | | |
| | |-----o--/VVV\-- +5 +------|---|26 A13(+5V)|
+------+ | |1/2 123| | +--------|-->|27 /WE(NC) |
16 o-|/CS2 | | | |--||-+ | +------|-->|23 A11(/WE)|
| CS1|----o----|B1 | 100pF | | J2 | | |
| | | /Q1|---------->---------o o o | | ZIF28 |
| Y1|---------|/A1 | | | | socket |
| 138 | +-------+ _ 1/2 74HCT132 | | | for |
| | +5 --| \ __ | | | EEPROM |
| Y2|--------------------------| O--| \ | | | |
8 o-|A2 | +-------+ |_/ | O-----------|-->|22 /OE |
7 o-|A1 Y4|--------------->|EN Y7|-----o-|_/ | | | |
6 o-|A0 Y3|----+ +5-----|RST | | 180 ohm | | | |
| Y0|-+ | | Y6|-----|---/VVV\---|----|---|1 A14(NC) |
| /CS3| | | | 259 Y5|-----|-----------|----+ | |
+------+ | | | Y4|-----|-----------|------->|2 A12(NC) |
| | | | Y3|-----|-----------+ | |
5 o--->---|--|--|--------o--|D Y2|-----|------------------->|21 A10 |
4 o--->---|--|--|------o-|--|A2 Y1|-----|------------------->|24 A9 |
3 o--->---|--|--|----o-|-|--|A1 Y0|-----|------------------->|25 A8 |
2 o--->---|--|--|--o-|-|-|--|A0 | | | |
| | | | | | | +-------+ | +5------------|28 +5V(NC) |
| | | | | | | | | |
| | | | | | | +-------+ | | |
| | | | | | | | Y7|-----|------------o------>|3 A7 |
| | +---------->|EN |-----|-----------o|------>|4 A6 |
| | | | | | | |-----|----------o||------>|5 A5 |
| | | | | | | 259 |-----|---------o|||------>|6 A4 |
| | | | | | | |-----|--------o||||------>|7 A3 |
| | | | | | | |-----|-------o|||||------>|8 A2 |
| | | | | +--|D |-----|------o||||||------>|9 A1 |
| | | | +----|A2 Y0|-----|-----o|||||||------>|10 A0 |
| | | +------|A1 | | |||||||| | |
| | +--------|A0 RST| | |||||||| | ZIF28 |
| | +-------+ | +------------+ | socket |
| | | | | data in | | for |
| | +5 +-->|/OE | | EEPROM |
| | | 574 | | |
| +------------------------------->|CLK | | |
| | | data out | | |
| V +------------+ | |
+----+ +------------+ |||||||| | |
| | SEL | |||||||| | |
| | B3|<----|||||||o------|D7 |
11 o---<-----------------------|Y3 B2|<----||||||o-------| |
12 o---<-----------------------|Y2 B1|<----|||||o--------| |
13 o---<-----------------------|Y1 157 B0|<----||||o---------| |
15 o---<-----------------------|Y0 A3|<----|||o----------| |
| | A2|<----||o--- data---| |
| | A1|<----|o---- bus ---| |
| GND----|/OE A0|<----o-------------|D0 |
+----+ | data out | | |
| +------------+ | |
| +------------+ |||||||| | |
9 o-------------------------->| SEL | |||||||| | |
| | B3|<----|||||||o------|19 D7 |
11 o---<-----------------------|Y3 B2|<----||||||o-------|18 D6 |
12 o---<-----------------------|Y2 B1|<----|||||o--------|17 D5 |
13 o---<-----------------------|Y1 157 B0|<----||||o---------|16 D4 |
15 o---<-----------------------|Y0 A3|<----|||o----------|15 D3 |
| | A2|<----||o--- data---|13 D2 |
| | A1|<----|o---- bus ---|12 D1 |
| GND----|/OE A0|<----o-------------|11 D0 |
+5--o--+ | +------------+ | |
| | __ o---------------------------------------------->|/CE |
100K +-| \ | __ +-----------+
sw1 | | O-o-| \ 1/2 74HCT132
o-->o----|__/ | O---390ohm--+
| | +-|__/ |
| | __ o---------------------------------------------->|20 /CE 14|
100K +-| \ | __ +---------+-+
sw1 | | O-o-| \ 1/2 74HCT132 |
o-->o----|__/ | O---390ohm--+ |
| | +-|__/ | GND -+
| --- 1uF | LED
| --- +5--+ |
| | |
+---o----------------------------o- GND
</code>
Notes:
<enum>
<item> Pin numbers on the left margin are for DB25 parallel port.
<item> Pin numbers in the right box are for the _ZIF28 socket_, not the IC.
<item> A 2816 should be low-justified in the ZIF28 socket.
<item> J1 and J2 are single-row 3-pin jumpers. For both jumpers, the left two
pins should be jumpered for a 2816, the right two for a 2864.
<item> The signal labels for a 2864 (if different from 2816) in the ZIF28
socket box are given in parentheses. E.g. pin 23 of the ZIF 28
is labeled "23 /WE(A11)", so it is /WE for a 2816, and A11 for a 2864.
<item> Sw1 needs to be open to enable operation of the programmer.
</enum>
1. Pin numbers on the left margin are for DB25 parallel port.
3. A 24-pin chip (e.g. 2816) must be low-justified in the 28-pin ZIF socket.
2. Pin numbers in the right box are for the ZIF-28 socket, not the IC.
7. The signal labels inside the ZIF-28 socket box are for 28-pin EEPROMs
(they are given in parentheses for 24-pin EEPROMs).
4. J1 and J2 are single-row 3-pin headers for jumpers (or use a DPDT switch).
5. For 28-pin EEPROMs, jumper the right two pins of both J1 and J2.
6. For 24-pin EEPROMs, jumper the left two pins of both J1 and J2.
8. The SPST switch sw1 needs to be open to enable operation of the programmer.
9. Please refer to the file pinouts.txt for full pinouts of the ICs used.
Abhijit Dasgupta
takdoom@yahoo.com
</code>
<!--
*******************************************
************ End of Section ***************
@ -813,6 +930,8 @@ Besides commercial boot ROMs, there are <bf>TWO</bf> sources for free packages f
Free implementations of TCP/IP net loaders are -
<enum>
<item> <bf>ETHERBOOT</bf> <url url="http://www.slug.org.au/etherboot/"> and
and at <url name="mirror-site" url="http://etherboot.sourceforge.net">
and at <url name="google-site" url="http://www.google.com/search?q=Etherboot">
<item> <bf>NETBOOT</bf> <url url="http://www.han.de/~gero/netboot.html">
</enum>
@ -1046,6 +1165,8 @@ X-terminals are one natural use of network booting. The lack of a disk in the te
<p>
Your first stop should be the Etherboot home page:
<url url="http://www.slug.org.au/etherboot/">
and at <url name="mirror-site" url="http://etherboot.sourceforge.net">
and at <url name="google-site" url="http://www.google.com/search?q=Etherboot">
There you will find links to other resources, including a mailing list you can subscribe to, where problems and solutions are discussed.
@ -1260,7 +1381,9 @@ over the network to be executed on an x86 computer. Typically the
computer is diskless and the code is Linux, but these are not the only
possibilities.
This document is at <url url="http://www.slug.org.au/etherboot/" name="the Etherboot Home Page">.
This document is at <url url="http://www.slug.org.au/etherboot/" name="the Etherboot Home Page">
and at <url name="mirror-site" url="http://etherboot.sourceforge.net">
and at <url name="google-site" url="http://www.google.com/search?q=Etherboot">
This document explains how to install, configure and use the Etherboot package.
<!--
*******************************************
@ -1347,7 +1470,10 @@ Netboot mailing list archive is at
<itemize>
<item> <url url="http://www.sandybay.com/pc-web/network_interface_card_NIC.htm" name="Webopaedia page"> on network cards
<item> Jargon's <url url="http://www.evitech.fi/~jarnomn/files/drivers/net_d.html" name="driver page"> with many drivers for older network cards.
<item> <url url="http://www.slug.org.au/etherboot/" name="Etherboot"> This is a project similar to Netbot but based on the BSD bootrom code.
<item> <url url="http://www.slug.org.au/etherboot/" name="Etherboot">
and at <url name="mirror-site" url="http://etherboot.sourceforge.net">
and at <url name="google-site" url="http://www.google.com/search?q=Etherboot">
This is a project similar to Netbot but based on the BSD bootrom code.
<item> How to make an <url url="http://www.menet.umn.edu/~kaszeta/unix/xterminal/index.html" name="X Window Terminal"> out of your old or outdated PC.
<item> List of <url url="http://www.slug.org.au/NIC/index.html" name="jumper settings"> for various network cards. This page also contains many other good links.
<item> <url url="http://sites.inka.de/lina/freefire-l/tools.html" name="Freefire"> is the home page of the Freefire project, which lists many resources for network security issues.

19
LDP/howto/linuxdoc/Process-Monitor-HOWTO.sgml
View File

@ -39,7 +39,8 @@ Process Monitor HOW-TO for Linux
<author> Al Dev (Alavoor Vasudevan)
<htmlurl url="mailto:alavoor@yahoo.com"
name="alavoor@yahoo.com">
<date>v7.0, 10 Jan 2001
<date>v8.0, 07 Mar 2001
<abstract>
This document describes how to monitor Linux/Unix processes and to re-start them automatically
if they die without any manual intervention. This document also has URLs for "Unix Processes" FAQs.
@ -90,7 +91,7 @@ See also the following related topics on Linux/Unix processes.
Use the program <bf>procautostart</bf> (say "Prok-Auto-Start" or Process AutoStart) to
monitor and automatically re-start
any Unix/Linux process if they die. This tiny program is very powerful and is
comparable to big commercial products which costs about $80,000US.
comparable to big commercial products which <bf>costs about $80,000US</bf>.
Procautostart can be used for controlling following applications:
<itemize>
<item> For real-time control of process industries like chemical, manufacturing, power
@ -118,7 +119,7 @@ and is negligible since the program size is small and is highly optimized with -
For example -
<code>
procautostart -n 12 -c "monitor_test -d $HOME -a dummy_arg " nohup &amp
procautostart -n 12 -c "monitor_test -d $HOME -a dummy_arg " nohup &
</code>
Here <bf>procautostart</bf> will be checking the process monitor_test <bf>every</bf> 12 seconds.
@ -806,7 +807,7 @@ From your browser save this file as <bf>text-file</bf> named as 'monitor_test'.
Use this program for testing the 'procautostart' program. For example -
<code>
procautostart -n 12 -c "monitor_test -d $HOME -a dummy_arg "
procautostart -n 12 -c "monitor_test -d $HOME -a dummy_arg " nohup &
</code>
Here <bf>procautostart</bf> will be checking the process monitor_test <bf>every</bf> 12 seconds.
<p>
@ -823,6 +824,16 @@ do
sleep 2
done
</code>
Then do a tail command to monitor the output. And simulate the failures of monitor_test
programs.
<code>
bash$ tail -f monitor_test.log
bash$ ps -ef | grep monitor_test
See the PID of monitor_test and kill it..
bash$ kill -9 &lt PID of monitor_test >
</code>
Once you kill the process, you will notice that it immediately comes alive
due to procautostart !
<!--
*******************************************
************ End of Section ***************