Since I get so many requests for URLs that I mention and some people had
problems accessing my infrastructures URL page
(http://www.sistema.it/twiki/bin/view/Main/infrastructures) on the web, I
attach it as an html doc to this message.  The most up-to-date version can
always be found at the above URL;  if you didn't look at it you can use the
diffs to see what is new...

--bud
<HTML>
<HEAD>
    <TITLE> TWiki . Main . infrastructures  </TITLE>
    
</HEAD>
<BODY bgcolor="#ffffff">
<BASE href="http://www.sistema.it/twiki/bin/view/Main/infrastructures";>
<TABLE width="100%" border="0" cellpadding="3" cellspacing="0">
<FORM name="main" action="http://www.sistema.it/twiki/bin/view/Main/";>
  <TR>
    <TD BGCOLOR="#FFFFC0" rowspan="2" valign="top" width="1%">
      <A href="http://apple1.sistema.it/twiki/";><IMG 
src="http://apple1.sistema.it/twiki/pub/wikiHome.gif"; border="0"></A>
    </TD>
    <TD>
      <B>TWiki . Main . </B><FONT size="+2"><B>infrastructures</B> </FONT>
    </TD><TD ALIGN="right">
      <!-- included HTML text -->
        <A href="http://apple1.sistema.it/twiki/";>TWiki</A> . {
            <A 
href="http://www.sistema.it/twiki/bin/view/Main/WebHome";>Main</A> 
          | <A 
href="http://www.sistema.it/twiki/bin/view/Know/WebHome";>Know</A> 
          | <A href="http://www.sistema.it/twiki/bin/view/Sdf/WebHome";>Sdf</A> 
          | <A href="http://www.sistema.it/twiki/bin/view/Tad/WebHome";>Tad</A> 
        }

    </TD>
  </TR>
  <TR BGCOLOR="#FFFFC0">
    <TD COLSPAN="2">
      <!-- included HTML text -->
        Main . {
            <A href="WebHome">Home</A> 
          | <A href="WelcomeGuest">Welcome</A>
          | <A href="TWikiUsers">Users</A>
          | <A href="http://www.sistema.it/twiki/bin/changes/Main";>Changes</A>
          | <A 
href="http://www.sistema.it/twiki/bin/search/Main/?scope=topic&amp;regex=on&amp;search=.*";>Index</A>
          | <A href="WebSearch">Search</A>
          | Go <INPUT type="text" name="topic" size="16">
        }

    </TD>
  </TR>
</FORM>
</TABLE>
<BR>


<DIV CLASS="header">
<DIV CLASS="navigate">
</DIV>
</DIV>
<DIV CLASS="main">
<H1><A NAME="Anotated Infrastructure Links">Anotated Infrastructure 
Links</A></H1>
<H2><A NAME="Collaborative Web Page">Collaborative Web Page</A></H2>
<P><HR WIDTH="80%" ALIGN="Left">
<STRONG>Note: </STRONG>Anyone can write on this page in the simple SDF markup 
language (see <A 
HREF="http://www.mincom.com/mtr/sdf/";>http://www.mincom.com/mtr/sdf/</A>).  
This Page is powered by SDFwiki (<A 
HREF="http://www.sistema.it/software.html";>http://www.sistema.it/software.html</A>).
<HR WIDTH="80%" ALIGN="Left"></P>
<P>Welcome,</P>
<P>Please add your URLs below.</P>
<UL>
<LI><B>FAI</B>:  a debian specific automatic installer <A 
HREF="http://www.informatik.uni-koeln.de/fai/";>http://www.informatik.uni-koeln.de/fai/</A>
<LI><B>EPM</B>: Package Manager that can create different package formats from 
a single source <A 
HREF="http://www.easysw.com/epm/";>http://www.easysw.com/epm/</A>
<LI><B>debconf</B>: Configuration Management for Debian <A 
HREF="http://www.de.debian.org/Lists-Archives/debian-devel-9909/msg01500.html";>http://www.de.debian.org/Lists-Archives/debian-devel-9909/msg01500.html</A>
<LI><B>Alien</B>:  binary-level package format translator <A 
HREF="http://kitenet.net/programs/alien/";>http://kitenet.net/programs/alien/</A>
<LI><B>Comparision of package formats</B>:  from Alien page <A 
HREF="http://www.de.debian.org/Lists-Archives/debian-devel-9909/msg01500.html";>http://www.de.debian.org/Lists-Archives/debian-devel-9909/msg01500.html</A>
<LI><B>epkg</B> is a free, open-source package manager which uses the Encap 
Package Management System. The Encap Package Management System is a method for 
flexibly handling installation and management of third-party software on a Unix 
system. Encap places each package in its own subdirectory, then automatically 
manages symlinks to their appropriate places in /usr/local. epkg supports the 
Encap 2.0 package format, which includes postinstall scripts and prerequisite 
checking. Other features include builtin tar/gzip extraction, transaction 
logging, and the ability to automatically upgrade a package to the latest 
version. <A 
HREF="http://freshmeat.net/appindex/1999/04/03/923187812.html";>http://freshmeat.net/appindex/1999/04/03/923187812.html</A>
<LI><B>CMU depot</B>: Package management system (?) <A 
HREF="http://andrew2.andrew.cmu.edu/ANDREWII/depot.html";>http://andrew2.andrew.cmu.edu/ANDREWII/depot.html</A>
<LI><B>pkglink</B> <A 
HREF="http://www.cs.unm.edu/~ssg/SSG_SysAdmin/SSG_Pkglink.shtml";>http://www.cs.unm.edu/~ssg/SSG_SysAdmin/SSG_Pkglink.shtml</A>
<LI><B>Slink</B> <A 
HREF="http://www.cs.tufts.edu/~couch/systems.html";>http://www.cs.tufts.edu/~couch/systems.html</A>
<LI><B>GNU stow</B>: <A 
HREF="http://www.gnu.org/software/stow/";>http://www.gnu.org/software/stow/</A>
<LI><B>LUDE</B>: <A 
HREF="http://www.iro.umontreal.ca/lude2/";>http://www.iro.umontreal.ca/lude2/</A>
<LI><B>SEPP</B>: <A 
HREF="http://www.sepp.ee.ethz.ch/";>http://www.sepp.ee.ethz.ch/</A>
<LI><B>GNU Queue</B>: Can this be used to tranparently run user jobs on the 
most idle machine in the cluster? <A 
HREF="http://bioinfo.mbb.yale.edu/~wkrebs/queue.html";>http://bioinfo.mbb.yale.edu/~wkrebs/queue.html</A>
<LI><B>auto RPM</B>: AutoRPM is a program for keeping RPMs consistent in a 
number of situations. For Beowulfs it is particularly useful for keeping the 
installed RPMs consistent across the cluster. <A 
HREF="http://www.kaybee.org/~kirk/html/linux.html";>http://www.kaybee.org/~kirk/html/linux.html</A>
<LI><B>SCMS:</B> is an extensible management tool for beowulf cluster developed 
to simplify the magement task for large� beowulf cluster.� SCMS provides a 
reich set of tools and support system that help system administrator monitor, 
submit command, query system status, maintain system configuration and more. <A 
HREF="http://smile.cpe.ku.ac.th/software/scms/";>http://smile.cpe.ku.ac.th/software/scms/</A>
<LI><B>swim:</B> A RPM-like command-line package manager for Debian. The_* 
Software has created software which makes it easy to find and download 
GNU/Linux or GNU/Hurd software. Our software gives you access to over 5,000 
high quality software packages which belong to the distribution the very 
successful Corel LINUX OS choose to develop from. You can run our software from 
whatever distribution you are using which means you can download and setup 
packages on distributions like Mandrake, Suse, Red Hat or Slackware. <A 
HREF="http://the.netpedia.net/the-software.html";>http://the.netpedia.net/the-software.html</A>
<LI><B>cfpasswd:</B> by Eric Sorenson &lt;[EMAIL PROTECTED]&gt;. The cfpasswd 
program itself might come in handy too. I modified a Perl module from CPAN 
called AcctInfo so that it fully supports arbitrary passwd/shadow files.  
Cfpasswd is a wrapper to break out and manage a master passwd file into smaller 
subsets for distribution to target machines, to help keep UID's in control.  
This is helpful if you need NIS netrgroup-style functionality but don't like 
network dependencies.  These files and instructions for cvs'ing them are at <A 
HREF="http://explosive.net/opensource/";>http://explosive.net/opensource/</A>.
<LI><B>Aegis</B>: Software Configuration Management System that supports change 
sets, review, automatic testing, and flexible transport (e-mail, rsync, etc.). 
<A 
HREF="http://www.canb.auug.org.au/~millerp/aegis/aegis.html";>http://www.canb.auug.org.au/~millerp/aegis/aegis.html</A><UL>
<LI>Aegis can be configured to use different &quot;history tools&quot; 
including Fhist and RCS.
<LI>Aegis configured to use RCS makes it possible to use CVSup!</UL>
<LI><B>CVSup</B> is a software package for transferring and updating 
collections of files across a network. It consists of a server called cvsupd 
and a client called cvsup. CVSup is faster (often by an order of magnitude) and 
more flexible than traditional network packages such as rdist and sup. In 
addition, CVSup has special knowledge of RCS files (as used by CVS). Software 
projects using CVSup to distribute their CVS repositories include FreeBSD, KDE, 
and (shortly) Postgres. <A 
HREF="http://www.polstra.com/projects/freeware/CVSup/";>http://www.polstra.com/projects/freeware/CVSup/</A>
<LI><B>htmlsysinfo:</B> writes information about your system to an HTML, LaTeX, 
or ASCII text document. It is able to read system information such as IDE/SCSI 
devices, network, CPU, RAM, kernel, etc. <A 
HREF="http://www.geocities.com/sebastianude/";>http://www.geocities.com/sebastianude/</A>
<LI><B>mrtg:</B> The Multi Router Traffic Grapher (MRTG) is a tool to monitor 
the traffic load on network-links. MRTG generates HTML pages containing GIF/PNG 
images which provide a live visual representation of this traffic. <A 
HREF="http://ee-staff.ethz.ch/~oetiker/webtools/mrtg/mrtg.html";>http://ee-staff.ethz.ch/~oetiker/webtools/mrtg/mrtg.html</A>
<LI><B>Bronc:</B> when combined with RRDtool, is a replacement for MRTG. Bronc 
provides on-the-fly graph generation, automated  SNMP data collection, and 
Mason-based templating. It's designed to be fast and to use very little of your 
system's  resources. Bronc is not limited to collecting data from routers--if 
you have a data source, Bronc can graph it. <A 
HREF="http://bronc.blueaspen.com/";>http://bronc.blueaspen.com/</A>
<LI><B>SMT:</B> (Service Monitoring Tool) is a daemon used to monitor various 
system services. It includes pre-built tests for DNS, HTTP, IMAP, POP3, and 
SMTP servers, and uses a command-line interface for both testing services and 
notifying users of results. <A 
HREF="http://www.doodlabs.com/smt/";>http://www.doodlabs.com/smt/</A>
<LI><B>syslog-ng:</B> as the name shows is a syslogd replacement, but with new 
functionality for the new generation. The original syslogd allows messages only 
to be sorted based on priority/facility pair, syslog-ng adds the possibility to 
filter based on message contents using regular expressions. The new 
configuration scheme is intuitive and powerful. <A 
HREF="http://www.balabit.hu/products/syslog-ng/";>http://www.balabit.hu/products/syslog-ng/</A>
<LI><B>Secure Syslog:</B> is a cryptographically secure system logging tool for 
UNIX systems. Designed to replace the syslog daemon, ssyslog implements a 
cryptographic protocol called PEO-1 that allows the remote auditing of system 
logs. Auditing remains possible even if an intruder gains superuser privileges 
in the system, the protocol guarantees that the information logged before and 
during the intrusion process cannot be modified without the auditor (on a 
remote, trusted host) noticing. <A 
HREF="http://www.core-sdi.com/english/slogging/ssyslog.html";>http://www.core-sdi.com/english/slogging/ssyslog.html</A>
<LI><B>eEMU:</B> (license is free but restricted!) eEMU is a complete 
enterprise event management and monitoring system. It is one of the simplest 
yet most powerful frameworks for writing agents thanks to its time-to-live 
concept. eEMU has been used for some time in large datacenter environments and 
is very popular among system administrators due to its simplicity and ability 
to re-use any existing  code/scripts as monitoring agents. eEMU offers a simple 
messaging &quot;language&quot; to encompass a variety of event management 
scenarios. It comes with a GUI browser and basic agents (scripts). <A 
HREF="http://www.jarrix.com.au/";>http://www.jarrix.com.au/</A>
<LI><B>Linux Terminal Server Project:</B> Linux makes a great platform for 
deploying diskless workstations that boot from a network server. The LTSP is an 
open source project to create the administration tools that will make setting 
up a diskless Linux workstation easier. <A 
HREF="http://www.ltsp.org/";>http://www.ltsp.org/</A>
<LI><B>SGI's Performance Co-Pilot:</B> (PCP) is a framework and set of services 
for supporting system-level performance monitoring and performance management. 
It provides a unifying abstraction for all of the interesting performance data 
in a system, and allows client applications to easily retrieve and process any 
subset of that data using a single API. A client-server architecture allows 
multiple clients to monitor the same host, and a single client to monitor 
multiple hosts. Archive logging and replay are integrated so that a client 
application can use the same API to process real-time data from a host or 
historical data from an archive. <A 
HREF="http://oss.sgi.com/projects/pcp/";>http://oss.sgi.com/projects/pcp/</A>
<LI><B>NetSaint</B> is a program that will monitor hosts and services on your 
network. It has the ability to email or page you when a problem arises and when 
a problem is resolved. Several CGI programs are included in order to allow you 
to view the current service status, problem history, notification history, and 
log file via the web. <A 
HREF="http://www.netsaint.org/";>http://www.netsaint.org/</A>
<LI><B>GNU cfengine:</B>  is a tool for setting up and maintaining BSD and 
System-5-like operating system optionally attached to a TCP/IP network. You can 
think of cfengine as a very high level language, much higher level than Perl or 
shell: a single statement can result in many hundreds of operations being 
performed on multiple hosts. Cfengine is good at performing a lot of common 
system administration tasks, and allows you to build on its strengths with your 
own scripts. You can also use it as a netwide front-end for `cron'. <A 
HREF="http://www.iu.hioslo.no/cfengine/";>http://www.iu.hioslo.no/cfengine/</A>.
<LI><B>cfengine experiences</B>:<UL>
<LI>NASA: <A 
HREF="http://www.google.com/search?q=cache:in.nas.nasa.gov/Groups/LAN/Software/cfengine/docs/infrastructure.html";>http://www.google.com/search?q=cache:in.nas.nasa.gov/Groups/LAN/Software/cfengine/docs/infrastructure.html</A>
<LI>Eric Sorenson: Description of his use of cfengine with his cfpassword <A 
HREF="http://explosive.net/opensource/cfpasswd/doc/cfengine.html";>http://explosive.net/opensource/cfpasswd/doc/cfengine.html</A>.
  Eric's post to infrastructures.org <A 
HREF="http://infrastructure.skylab.org/200001/msg00005.html";>http://infrastructure.skylab.org/200001/msg00005.html</A></UL>
<LI><B>Debian tools on other platforms:</B><UL>
<LI>debian-scala HOWTO: Debian on non-Linux systems: <A 
HREF="http://www.debian.org/Lists-Archives/debian-dpkg-0001/msg00002.html";>http://www.debian.org/Lists-Archives/debian-dpkg-0001/msg00002.html</A>
<LI>possible port of dpkg to AIX: <A 
HREF="http://www.debian.org/Lists-Archives/debian-dpkg-0001/msg00012.html";>http://www.debian.org/Lists-Archives/debian-dpkg-0001/msg00012.html</A>
<LI>I also saw mention of ports to Solaris in the Debian list archives</UL>
<LI><B>Debian packages for Diskless Workstations:</B><UL>
<LI>diskless
<LI>netboot: this has a nice utility to get al Ethernet MAC numbers from a 
LAN...</UL>
<LI><B>pre-processors</B> that could be used for config file management:<UL>
<LI><B>chpp</B> is a general purpose preprocessor. It was designed originally 
for the purpose of preprocessing HTML code but can be used successfully in 
other fields of application as well. Highlights are, beside powerful language 
constructs, CGI-scripting support and an SQL database interface. <A 
HREF="http://www.unix.cslab.tuwien.ac.at/~chpp/";>http://www.unix.cslab.tuwien.ac.at/~chpp/</A>
<LI><B>HTML::EP</B> is a server-side embedded HTML system in the style of PHP3, 
that allows you to combine the full power of Perl with your HTML pages. 
HTML::EP runs as a separate CGI binary or (for full speed) as a mod_perl 
package. It includes  database access via DBI, the Perl Database Interface, 
session support and allows quite easy extension via a modular, OO interface.  
<A 
HREF="http://freshmeat.net/appindex/1999/09/26/938369482.html";>http://freshmeat.net/appindex/1999/09/26/938369482.html</A>
<LI><B>Perlfect::Template</B> is a no-thrills, general-purpose Text template 
processing module. It is mainly geared towards rendering generating HTML 
dynamically in CGI programs. <A 
HREF="http://www.perlfect.com/articles/templates.shtml";>http://www.perlfect.com/articles/templates.shtml</A>
<LI><B>Jamal</B> <A 
HREF="http://peter.verhas.com/progs/perl/jamal/index.html";>http://peter.verhas.com/progs/perl/jamal/index.html</A></UL>
<LI><B>Debian-Beowulf discussion on &quot;Large scale installations of 
debian&quot;</B> with issues directly relevant to infrastructures <A 
HREF="http://www.debian.org/Lists-Archives/debian-beowulf-9907/threads.html";>http://www.debian.org/Lists-Archives/debian-beowulf-9907/threads.html</A>
<LI><B>syssumm:</B> (AKA &quot;System Summaries&quot;) is a  collaborative open 
source project developing a set of Perl scripts that generate a profile of a  
computer's hardware, software, and network configuration that can then be 
viewed with a browser. <A 
HREF="http://syssumm.saic.com/";>http://syssumm.saic.com/</A>
<LI><B>Lhinv 1.1</B> is a version of IRIX hinv for linux systems, providing a 
standardized inventory of configured hardware through the proc filesystem. This 
version supports most of the IRIX flags, plus includes options for mailing the 
output via SMTP and a CGI wrapper. Lhinv can be used as a test for the 
existance of specific hardware subsystems and is useful for supporting large 
numbers of workstations. <A 
HREF="http://lhinv.sourceforge.net/";>http://lhinv.sourceforge.net/</A></UL>
</DIV>
<DIV CLASS="footer">
<DIV CLASS="navigate">
</DIV>
</DIV>


<BR clear=all><P>
<TABLE width="100%" border="0" cellpadding="3" cellspacing="0">
  <TR BGCOLOR="#FFFFC0">
    <TD valign="top">
      Topic <B>infrastructures</B> . {
        <A 
href="http://www.sistema.it/twiki/bin/edit/Main/infrastructures";><B>Edit</B></A>
      | <A 
href="http://www.sistema.it/twiki/bin/search/Main/?scope=text&regex=on&search=infrastructures%5B%5EA-Za-z%5D";>Ref-By</A>
      | <A 
href="http://www.sistema.it/twiki/bin/attach/Main/infrastructures";>Attach</A>
      | <A 
href="http://www.sistema.it/twiki/bin/rdiff/Main/infrastructures";>Diffs</A>
         | r1.37 | <A 
href="../../rdiff/Main/infrastructures?rev1=1.37&rev2=1.36">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.36">r1.36</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.36&rev2=1.35">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.35">r1.35</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.35&rev2=1.34">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.34">r1.34</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.34&rev2=1.33">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.33">r1.33</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.33&rev2=1.32">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.32">r1.32</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.32&rev2=1.31">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.31">r1.31</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.31&rev2=1.30">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.30">r1.30</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.30&rev2=1.29">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.29">r1.29</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.29&rev2=1.28">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.28">r1.28</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.28&rev2=1.27">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.27">r1.27</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.27&rev2=1.26">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.26">r1.26</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.26&rev2=1.25">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.25">r1.25</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.25&rev2=1.24">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.24">r1.24</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.24&rev2=1.23">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.23">r1.23</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.23&rev2=1.22">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.22">r1.22</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.22&rev2=1.21">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.21">r1.21</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.21&rev2=1.20">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.20">r1.20</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.20&rev2=1.19">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.19">r1.19</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.19&rev2=1.18">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.18">r1.18</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.18&rev2=1.17">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.17">r1.17</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.17&rev2=1.16">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.16">r1.16</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.16&rev2=1.15">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.15">r1.15</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.15&rev2=1.14">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.14">r1.14</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.14&rev2=1.13">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.13">r1.13</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.13&rev2=1.12">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.12">r1.12</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.12&rev2=1.11">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.11">r1.11</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.11&rev2=1.10">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.10">r1.10</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.10&rev2=1.9">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.9">r1.9</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.9&rev2=1.8">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.8">r1.8</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.8&rev2=1.7">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.7">r1.7</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.7&rev2=1.6">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.6">r1.6</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.6&rev2=1.5">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.5">r1.5</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.5&rev2=1.4">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.4">r1.4</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.4&rev2=1.3">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.3">r1.3</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.3&rev2=1.2">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.2">r1.2</A> | <A 
href="../../rdiff/Main/infrastructures?rev1=1.2&rev2=1.1">&gt;</A> | <A 
href="../../view/Main/infrastructures?rev=1.1">r1.1</A> }
    </TD>
  </TR>
</TABLE>
<TABLE width="100%" border="0" cellpadding="3" cellspacing="0">
  <TR>
    <TD valign="top">
      Revision r1.37 - 07 Feb 2000 - 13:40 by <A 
href="http://www.sistema.it/twiki/bin/view/Main/BudBruegger";>BudBruegger</A>

    </TD>
    <TD width="50%" valign="top">
      <FONT SIZE=-2>Copyright &copy; 1999 by the contributing authors.  
All material on this Intranet is property of {yourCompany}. <br>
Ideas, requests, problems regarding TWiki? Send 
<A href="mailto:[EMAIL PROTECTED] Feedback">
feedback</A>. </FONT>

    </TD>
  </TR>
</TABLE>
</BODY></HTML>
/------------------------------------------------------------------------\
| Bud P. Bruegger, Ph.D.  |  mailto:[EMAIL PROTECTED]                       |
| Sistema                 |  http://www.sistema.it                       |
| Information Systems     |  voice general: +39-0564-418667              |
| Via U. Bassi, 54        |  voice direct:  +39-0564-418667 (internal 41)|
| 58100 Grosseto          |  fax:           +39-0564-426104              |
| Italy                   |  P.Iva:         01116600535                  |
\------------------------------------------------------------------------/

Reply via email to