renaming lynx to cougar ....

alliance/src/lynx/man1/Makefile.am

@@ -1,2 +1,2 @@
-man_MANS  = lynx.1
+man_MANS  = cougar.1
 EXTRA_DIST = $(man_MANS)

alliance/src/lynx/man1/cougar.1

@@ -1,10 +1,10 @@
-.\"   $Id: lynx.1,v 1.1 2002/03/29 17:43:39 ludo Exp $
+.\"   $Id: cougar.1,v 1.1 2002/05/21 06:52:00 xtof Exp $
 .\" @(#)lynx 1.09 94/10/10 UPMC/ASIM/LIP6/CAO-VLSI " Ludovic Jacomme, Frederic Petrot
-.TH LYNX 1 "October 1, 1997" "ASIM/LIP6" "ALLIANCE USER COMMANDS"
+.TH COUGAR 1 "October 1, 1997" "ASIM/LIP6" "ALLIANCE USER COMMANDS"
 .SH NAME
-lynx \- Hierarchical netlist extractor
+cougar \- Hierarchical netlist extractor
 .SH SYNOPSIS
-.B lynx
+.B cougar
 [
 .I \-v
 ]
@@ -30,7 +30,8 @@ lynx \- Hierarchical netlist extractor
 .br
 .so man1/alc_origin.1
 .SH DESCRIPTION
-\fBLynx\fP is a hierarchical layout extractor.
+\fBLynx\fP changed its name to \fBCougar\fP during May 2002 in order to avoid name conflict with the famous text-mode Web browser.
+\fBCougar\fP is a hierarchical layout extractor.
 It builds a netlist of interconnections from a symbolic layout view.
 The \fIinput\fP argument is the name of the symbolic layout cell to
 be extracted, using as input format the one selected by the
@@ -40,7 +41,7 @@ If no \fIoutput\fP is given, then \fIinput\fP will also be the generated
 netlist name.
 The output format is specified by the \fBMBK_OUT_LO\fP(1) environment variable.
 .br
-As most of the Alliance cad tools, \fBlynx\fP uses \fBmbk\fP(1) environment
+As most of the Alliance cad tools, \fBcougar\fP uses \fBmbk\fP(1) environment
 variables.
 .BR MBK_CATA_LIB (1),
 .BR MBK_WORK_LIB (1),
@@ -48,7 +49,7 @@ variables.
 .BR MBK_OUT_LO (1),
 .BR RDS_TECHNO_NAME (1).
 .PP
-\fBLynx\fP computes capacitances attached to the signals if 
+\fBCougar\fP computes capacitances attached to the signals if 
 the -ac option is set. At the moment,
 the value of these capacitances is computed for a typical one micron
 technology, and cannot be changed by the user through a technology file.
@@ -65,7 +66,7 @@ ALU1
 ALU2
 25
 .SH OPTIONS
-\fBLynx\fP checks the two basic \fBALLIANCE\fP rules regarding connector names:
+\fBCougar\fP checks the two basic \fBALLIANCE\fP rules regarding connector names:
 .br
 .RS
 If two physical connectors are connected to the same net, they must have
@@ -82,7 +83,7 @@ and ground connectors )
 When no options are specified, the current hierarchical level is extracted.
 The resulting netlist is the list of interconnections of the current
 layout hierarchy level.
-Three options are available to change \fBlynx\fP behaviour :
+Three options are available to change \fBcougar\fP behaviour :
 .TP
 \-t
 Notifies a transistor level extraction, the symbolic layout cell is flattened to
@@ -102,7 +103,7 @@ along  with some statistics.
 .TP
 \-c
 Generates a \fBcore\fP file representing the conflictuel net, when 
-\fBlynx\fP detects two external connectors with different names on
+\fBcougar\fP detects two external connectors with different names on
 the same signal, or when it finds two external connectors having 
 the same name but not internally connected to the same net, or when 
 it cannot correctly extract an L shaped transistor.
@@ -117,7 +118,7 @@ resistance foreach layer can be changed in the RDS file.
 .ie t  \{\
 .ft CR \}
 .el \fB
-prompt> lynx -v amd2901
+prompt> cougar -v amd2901
 .ft R
 .RS
 Gives a logical netlist of the chip amd2901, for one hierarchical
@@ -135,7 +136,7 @@ a2_y
 a2p_y
  .
  .
-prompt> lynx -f amd2901
+prompt> cougar -f amd2901
 .fi
 .ft R
 .RS
@@ -146,7 +147,7 @@ on the cells specified in the catalog ( the standard cell library in our case ).
 .ft CR \}
 .el \fB
 .nf
-prompt> lynx -t amd2901
+prompt> cougar -t amd2901
 .fi
 .ft R
 .RS