May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

Installing endpoints



Recommended Links Reference Tarball-based Installation Brandon Mitchell's  scripts


How to install or configure endpoints in a DMZ Tivoli Gateway Proxy   Troubleshooting endpoints Gateway Troubleshooting
Old but useful Redbook Using Log Files to Troubleshoot Tivoli Environment Tivoli lcfd daemon last.cfg Etc

Tivoli endpoint can be installed in many different ways. First of all you can create a tar file of installed files and use it.


For UNIX remote installation is preferable and Perl script winstlcf is the standard way to install LCF. A file containing a list of targets can be passed to winstlcf if multiple endpoints need to be installed. 

It uses rsh or ssh protocols on target host (rsh is default, ssh requires -j option)

winstlcf requires either rsh or ssh communication with the target host. You need to check connectivity via selected protocol (for example SSH) before using it.

You need manually connect via selected protocol (for example SSH) to the host before running winstlcf

Again, due to the age of the script rsh-based communication is default. To specify ssh communication you should use -j option. In addition it requires a Bourne-compatible shell, and standard UNIX utilities such as grep on the target system but this is given for Unix installs.

For example, if can create a simple one line shell script to install the endpoint of any of the supported flavors of UNIX:

winstlcf -Y -j -d /opt/tivoli/lcf -L"-Dlcs.login_interfaces=nti5001 -Dbcast_disable=1 -Dlcs.machine_name=$1-ep" $1

If you name the script, then to install endpoint on the server RHEL273 you need to run the command: rhel273

You can also install multiple endpoints on set of UNIX servers by creating a list file containing a list (one system per line) of all target endpoints. Let's assume that  you want to use ssh. Then the command:

# winstlcf -j -f endpoints.txt -P
will install the LCF Endpoint modules on each system in the list. The -f argument specifies an input file and the the -P argument enables you to enter a global password for use on all of the machines being installed.
# ksh susesrv

Trying susesrv...
password for root:

locating files in /opt/TMF/bin/lcf_bundle.41100...
locating files in /opt/TMF/bin/lcf_bundle...

Ready to copy files to host susesrv:
  destination: susesrv:/opt/tivoli/lcf
       source: tmrserv:/opt/TMF/bin/lcf_bundle
       source: tmrserv:/opt/TMF/bin/lcf_bundle.41100
Tivoli Light Client Framework starting on susesrv
Nov 05 15:11:22 1 lcfd Command line argv[0]='/opt/tivoli/lcf/bin/linux-ix86/mrt/lcfd'
Nov 05 15:11:22 1 lcfd Command line argv[1]='-Dlcs.login_interfaces=tmrserv'
Nov 05 15:11:22 1 lcfd Command line argv[2]='-Dbcast_disable=1'
Nov 05 15:11:22 1 lcfd Command line argv[3]='-Dlcs.machine_name=susesrv-ep'
Nov 05 15:11:22 1 lcfd Command line argv[4]='-Dlib_dir=/opt/tivoli/lcf/lib/linux-ix86'
Nov 05 15:11:22 1 lcfd Command line argv[5]='-Dload_dir=/opt/tivoli/lcf/bin/linux-ix86/mrt'
Nov 05 15:11:22 1 lcfd Command line argv[6]='-C/opt/tivoli/lcf/dat/2'
Nov 05 15:11:22 1 lcfd Command line argv[7]='-Dlcs.machine_name=susesrv-2'
Nov 05 15:11:22 1 lcfd Command line argv[8]='-Dlcs.login_interfaces=tmrserv'
Nov 05 15:11:22 1 lcfd Command line argv[9]='-Dbcast_disable=1'
Nov 05 15:11:22 1 lcfd Command line argv[10]='-Dlcs.machine_name=susesrv-ep'
Nov 05 15:11:22 1 lcfd Starting Unix daemon
Performing auto start configuration
Tivoli LCF daemon master autostart file is /etc/init.d/Tivoli_lcfd2.

After that you need to subscribe the new endpoint. To do that you need to run the “” script. This subscribes all new endpoints. To check if the endpoint alive and well you can use:

# ./
Subscribing susesrv-ep (linux-ix86) to and

After that you can check if the endpoint is alive and well:

# wep ls | grep susesrv
1034227612.506.522+#TMF_Endpoint::Endpoint# susesrv-ep
Other useful command for checking status of endpoint after installation is:

wepstatus endpoint name

Tarball-based Installation

You need to create tar of the following three directotiries

After untarring those files you must first modify the file /opt/tivoli/lcf/dat/1/last.cfg.

First, change the lcs.machine_name to identify the new system’s endpoint name, then add the “lcs.login_interfaces=your_tmr_server” line.

Another issue is when an endpoint is connected but the lcf is unreachable or distribution shows as unavailable. Could be that the wrong gateway is cached. If we deal with existing endpoint, try to delete cache on endpoint if it exists.

Brandon Mitchell's scripts

See   Brandon Michell creased set of script for the  creation of a tarballs for endpoint installation. They can be used for installing endpoint on DMZ but also can be used for all other types of installation instead of standard procedure.

tar tvf FWK-ep.tar
-rwxr--r-- bmitch/bmitch  2017 2006-08-17 10:57
-rwxr--r-- bmitch/bmitch  2815 2006-08-17 10:57
-rwxr--r-- bmitch/bmitch  3782 2006-08-17 10:57
-rwxr--r-- bmitch/bmitch  2986 2006-08-17 10:56
-rwxr--r-- bmitch/bmitch  1110 2006-08-17 10:58 readme.txt

Please note that tar on AIX and tar on Linux are not fully compatible so you ned to move installation files first to linux if you TMR is running on AIX (which is actually much worse for running Tivoli then Solaris).

After creation of the tar file move is and script to the target server and run it.

Top Visited
Past week
Past month


Old news ;-)

IBM - Endpoint install error

Problem(Abstract)"...could not rexec on host (name of the host)..." error message occurs when attempting to install an Endpoint on a Solaris i-86 version 2.5.1 using the "winstlcf" command.

Resolving the problem "...could not rexec on host (name of the host)..." error message occurs when attempting to install an Endpoint on a Solaris i-86 version 2.5.1 using the "winstlcf" command.

The complete error message is as follows:

trying (name of EP)
connect:bad file number
could not rexec on host (name of the host)
lcf installed failed for the following machine (name of the EP)

If the "...could not rexec on host (name of the host)..." error occurs, perform the following steps:

1. Install Tier 2 support for Endpoint support for Solaris ix-86
2. Turn on the rexec daemon.

In the "/etc/services" file and the "/etc/inetd.conf" file, make sure that the exec line is not commented out. If this needs to be changed, re-boot the system.

[Beowulf] passwordless rsh login

Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.

Tyler Simon tasimon at Wed Jul 7 23:22:32 PDT 2004


To set up a RedHat 8.0 cluster using a "passwordless" rsh I
always check the that I have the following.

For each child:

1.)In the users home directory make sure there exists a
'.rhosts' file containg a listing of child nodes and the
master node, set the permissions to 644.


2.) Type 'setup' and from the 'System Services' menu make
sure that rsh, rlogin, and rexec are selected.

3.) Add the following lines to the end of the /etc/securetty


4.) Change directory to /etc/pam.d and modify the rsh,
rlogin, and rexec files as follows. The order is very

rsh file
# For root login to succeed here with pam_securetty, "rsh"
must be
# listed in /etc/securetty.
auth       required     /lib/security/
auth       required     /lib/security/
auth       required     /lib/security/
auth       required     /lib/security/
account    required     /lib/security/
session    required     /lib/security/

rlogin file
# For root login to succeed here with pam_securetty,
"rlogin" must be
# listed in /etc/securetty.
auth       sufficient   /lib/security/
auth       required     /lib/security/
auth       required     /lib/security/
auth       required     /lib/security/
auth       required     /lib/security/
account    required     /lib/security/
password   required     /lib/security/
session    required     /lib/security/
rexec file
# For root login to succeed here with pam_securetty, "rexec"
must be
# listed in /etc/securetty.
auth       required     /lib/security/
auth       required     /lib/security/
auth       required     /lib/security/
auth       required     /lib/security/
account    required     /lib/security/
session    required     /lib/security/

5.) Make sure to have an updated /etc/passwd,/etc/shadow and
/etc/group file on each node.

This should do it, and feel free to contact me if you have
any trouble.

-Tyler Simon

> Hi,
> I have a cluster set up with redhat 8.0 in which Fluent is
> being used. The /home of the master is being shared by all
> the nodes on the cluster. For running parallel
> applications with Fluent it requires passwordless "rsh"
> login to all the nodes. As a local user (non root) I am
> able to login from the master to all the nodes with rsh
> without password. But from one node to another it keeps
> asking for the password.
> Is there a solution to it?
> Thanks in advance.
> Sandy.
> Sandeep Krishnan
> Graduate Student
> Oklahoma State University
> ---------------------------------
> Do you Yahoo!?
> New and Improved Yahoo! Mail - Send 10MB messages!
> _______________________________________________
> Beowulf mailing list, Beowulf at
> To change your subscription (digest mode or unsubscribe)
> visit

TMF - Installing endpoint on Red Hat Enterprise Linux 3.0


Try the following that was created and tested under RH7.2 and I assume that will work under RHE3.0:

Endpoint installation procedure.

This procedure will create a Tivoli endpoint called tivolinux.ep that will be used for the rest of this workshop.

First, we need to configure RSH service to be used by Tivoli at endpoint installation time. To accomplish that, some files must be updated.

In file /etc/xinetd.d/rsh
Change the line that contains 'disable=yes' to 'disable=no'
Add a line in the file /etc/securetty with rsh
Add the file /root/.rhosts that must contain the line:
Service xinetd restart
The command that creates the endpoint can be executed now. From a terminal
emulation session
execute the following commands:
. /etc/Tivoli/
winstlcf –e –g tivolinux+9494 –n tivolinux.ep tivolinux

Lic. Javier R. Barabas
Certified Senior IT Specialist
Tivoli Software - Software Group
IBM Argentina S.A.
Phone: 54-11-4319-6129 - T/L 840-6129
E-Mail: barabas@xxxxxxxxxx

RE: [ITM] winstlcf could not determine INTERP

RE: [ITM] winstlcf could not determine INTERP

Have you checked if the Linux has rsh service active in the inetd.conf ? In general Linux distros does not make it active by default, and winstlcf is based on remote commands.

Good luck!

Gerson Koji Saito - Certified IT Specialist
IBM Software Group
Phone : +55-11-2132-3309 Fax: +55-11-2132-5534
Email : saito-xuelUoVDAHHQT0dZR+AlfA@xxxxxxxxxxxxxxxx

"Silvis, Jasper E. (MBS)" <Jasper.Silvis-UUSGX2jyPCJpFjMZrrdVc9BPR1lH4CV8@xxxxxxxxxxxxxxxx>
Sent by: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx

I have had the best luck with Linux endpoint installations using the Brandon
Mitchell approach of tarballing the endpoint image for the linux-ix86 interp
and installing that from the Linux server. I am using LCF v41100 with no

Let me know if you need guidance. You may already use this solution for DMZ
installations (pre-TMF411, that is).

Best of luck,

Jasper Silvis
Cendant Mortgage

-----Original Message-----
From: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
[mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx]On Behalf Of
Sent: Tuesday, April 13, 2004 3:05 PM
To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
Subject: Re: [tme10] [ITM] winstlcf could not determine INTERP

Now, at the endpoint we dropped the line inserted before to solve TMR name
and a new entry on the endpoint DNS was made so the TMR name could be
resolved by DNS and not by /etc/hosts at the endpoint.

But the problem was not solved and winstlcf still complaining.

> Can you resolve both hostnames and the ip addresses using nslookup on both
> servers (TMR and Endpoint) ?
> John F. Mostler
> Certified Tivoli Consultant
> New York Life
> john_mostler-H66Kdd6cy6IQQYfiE9goCw@xxxxxxxxxxxxxxxx
> (908) 236-3262


winstlcf37 source code of the Perl script

winstlcf (Tivoli Management Framework, Reference Manual)

Installs an endpoint on all operating systems except AS/400, and OS/2.


winstlcf [-a] [-C locale_name] [-D] [-d dir_name] [-e] [-f file_name] [-g machine[+port][:machine[+port]] [-i] [-j] [-L config_options] [-l endpoint_port] [-N endpoint] [-n endpoint_label] [-P] [-R] [-r policy_region] [-S share_name] [-s dir_name] [-T account] [-v] [-x TCPIP | IPX] [-Y] host [user_account password]...


The winstlcf command installs and starts the endpoint service (lcfd) on one or more workstations. This command can be used to install an endpoint on all operating systems except AS/400 and OS/2 operating systems. For AS/400 operating systems, use the command or Tivoli Software Installation Service. For OS/2 operating systems, use the provided InstallShield program or Tivoli Software Installation Service.


By default, the endpoint service starts after installation. You can install endpoints to multiple workstations by listing the machine names on the command line or using the -f option to specify a file that contains a list of machine names.

If you run the winstlcf command on a machine more than once, you have more than one instance of lcfd service running on that machine.

After you specify an installation password with the winstlcf command, that password becomes the default for all subsequent installations. To change the password, follow these steps:

  1. Explicitly specify another password.
  2. Attempt an installation on an unsupported operating system, which erases the global variable containing the password.
  3. Specify the -P option.


Specifies that endpoints be installed asynchronously. Without this option,the command waits for the endpoint to log in to its gateway before installing the next endpoint.
-C locale_name
For Linux and UNIX operating systems only, specifies the language locale for the target endpoint. If the -C option is not specified, the language is inherited from the lcfd environment.
-d dir_name
Specifies the target directory in which to install the endpoint software. The default location is the /opt/Tivoli/lcf directory for UNIX operating systems and the c:\Program Files\Tivoli\lcf directory for Windows operating systems. When installing a Windows endpoint from a Linux or UNIX Tivoli server, forward slashes in path names are also supported.
For Windows operating systems, indicates that the lcfep program is not installed. When installing in a Windows Terminal Server environment, this is the default behavior and cannot be overridden. In other words, the lcfep program cannot be installed in this environment.
For UNIX operating systems only, specifies to use trusted host access instead of exec.
-f file_name
Specifies the name of a file that contains a list of machine where an endpoint needs to be installed. The file must contain one machine name per line. Each line can contain the machine name, the user ID, the password, the policy region, and the label that is used to install the endpoint. The following is the format of a line:
host_name user_ID password policy_region endpoint_label


The host name of the machine where the endpoint is to be installed.
The user ID of the system administrator performing the installation.
The password associated with the user_ID.
Optional. The name of the policy region where the endpoint is moved.


If you specify endpoint_label and you do not want the endpoint moved to a policy region, you must specify policy_region as a null string ("").
Optional. The label of the endpoint.

For example, the following could be three lines in a file:

red root mstr_Key
orange chris d1n0mite "" orange-ep
yellow root mstr_Key NYC_PR yellow-ep
-g machine[+port][:machine[+port]]...
Specifies the Internet Protocol (IP) address or host name and, optionally, the port number of the gateway to which the endpoint logs in. Multiple gateway entries must be separated by colons (:). You must specify the port number if it is other than 9494, the default. If the -g option is omitted, the endpoint broadcasts to all gateways.


In a network address translation (NAT) environment, gateways must be specified as fully qualified domain names and not as IP addresses. Direct specification of gateway IP addresses fails in a NAT environment.
Turns off auto-start configuration for a Linux or UNIX endpoint after installation. By default, Windows endpoints always start automatically after installation.
Causes the command to use an encrypted secure shell (SSH) connection when connecting to the machine to install the endpoint.


  1. You cannot use SSH to perform installations on Windows targets.
  2. When you use this option to install an endpoint from a Windows system, you must use a trusted host access method. Because trusted host access methods do not use passwords, you cannot use the -j option with winstlcf options that require a password.
  3. To install an endpoint from a Windows system using the winstlcf command and -j option, you must launch a Cygwin command prompt and then run the winstlcf command from the version of Perl provided by Cygwin, as shown in the following example:
    /usr/bin/perl -S winstlcf -j options
    For more information, see the chapter about SSH in the Tivoli Enterprise Installation Guide.
-l endpoint_port
Specifies the port number for the endpoint. The default port number is 9495.
-L config_options
Passes configuration options to the lcfd command for starting the endpoint. If you specify multiple options or have spaces in a single option, you must enclose the text in double quotation marks ("). See the lcfd command for a list of valid options.
-n endpoint_label
Specifies an endpoint label provided by a user.


If you omit the -n option, the endpoint label is generated automatically. If you do not specify the endpoint port number, the label is the host name of the endpoint. If you specify the endpoint port number (for example, using the -l option), the endpoint label is generated as follows:
  • On Windows operating systems, the label has the format host-port.
  • On Linux and UNIX operating systems, the label has the format host-instance, if the instance number is greater than 1. The value of instance matches the instance number used in the $LCFROOT/dat/instance directory.
-N endpoint
Specifies an existing Windows endpoint in the domain or trust to be used as a proxy to remotely install all other Windows endpoints.


To install Windows endpoints using the winstlcf command, you must first install one Windows endpoint in the domain or trust manually using the InstallShield image. This endpoint is used as a proxy to remotely install all additional Windows endpoints in the domain or trust. After you have installed the proxy endpoint, install all additional Windows endpoints in that domain or trust using the winstlcf command and -N option. When you use this option, all endpoints to be installed are assumed to be Windows clients. Installing the Tivoli Remote Execution Service is not necessary.
Prompts for a password for each machine. This option is useful only when installing on remote hosts with different passwords. If each machine has the same password or if you do not use this option, the command prompts for a global password to use for each machine.
-r policy_region
Specifies a policy region to install the endpoint to.
Requires the Windows endpoint to restart after installation without prompting the user. This option is only needed if the Tivoli Authentication Package, TivoliAP.dll, was not previously installed on the endpoint or an older version of the Tivoli Authentication Package is being replaced.
-s dir_name
Specifies the source directory containing the endpoint installation image.
-S share_name
Specifies a destination share name (default = C$).
-T account
Specifies the Tivoli remote access account fn class="pk">-v
Lists verbose installation information and error messages.
-x [TCPIP | IPX]
For Internetwork Packet Exchange (IPX) endpoints only. Specifies the protocol used by the endpoint. If you do not specify this option, the endpoint uses TCP/IP. Supported protocols are TCP/IP and IPX. To specify both TCP/IP and IPX, specify the option as -x=TCPIP,IPX. You cannot turn off the TCP/IP protocol for a gateway.
Installs the endpoint without confirmation. performs the installation without requesting confirmation.
host [user_account password]
Specifies the name of the machine on which the endpoint is installed. If you specify only the host name, the root or Administrator account is used. You are prompted for the password. You can specify a different user account and password by enclosing the three entries in single quotation marks. For example, you might enter the following:
winstlcf 'vernon DOMAIN-NT\chris d1n0mite'

If the Windows domain and the local computer use the same user_account name (such as Administrator), you must specify the fully qualified name for the account, as in the preceding example. Quotation marks are necessary when specifying fully qualified user accounts.


No Tivoli authorization role is required except when the -N option is specified. To use the winstlcf command and -N option, you must have the super, senior, or admin role.


  1. The following example installs the endpoint software on a UNIX workstation vernon, sets the locale to French, and starts the endpoint daemon (lcfd). The winstlcf command uses the root account and prompts for the root password on vernon. The installation image is placed in the default directory. The endpoint starts with the default configuration.
    winstlcf -C fr vernon
  2. The following example installs the endpoint software on a Windows workstation olympus and starts the endpoint service. The winstlcf command uses the Administrator account and prompts for the Administrator password on olympus. The installation image is taken from a Windows proxy fuji (a previously installed endpoint in the Windows domain). The software is installed in the default directory on olympus. The endpoint starts with the default configuration.
    winstlcf -N fuji olympus
  3. The following example installs the endpoint on a Windows workstation in a directory other than the default directory. In this example, the endpoint is installed on workstation bonnell on drive D with the share name steve. For instances where the share name of the destination drive is not the default name (D:\ = D$), use the -d to specify the directory (D:\tivoli\lcf), and use the -S to specify the share name (steve).
    winstlcf -N pctmp107 -d D:\tivoli\lcf -S steve bonnell
  4. The following example installs the endpoint software on workstation myoung. The endpoint performs its initial login through IP address
    winstlcf -g myoung
  5. The following example installs the endpoint on workstation bbunny and passes configuration options to the lcfd command to use when it starts the endpoint. In the example, -g cedar+1616 specifies the gateway and port that the endpoint contacts for initial login, and -Dlcs.machine_name=bbunny-ep assigns a specific name to the endpoint.
    winstlcf -L "-g cedar+1616 -Dlcs.machine_name=bbunny-ep" bbunny
  6. The following example installs machines cedar and mahogany as endpoints. The installation process prompts for a global root password, but does not prompt for confirmation before installing.
    winstlcf -P -Y cedar mahogany
  7. The following example installs multiple endpoints from the endpt.txt file. The installation process does not prompt for password or installation confirmation. The software is installed in the /usr/lcf directory.
    winstlcf -f endpt.txt -Y -d /usr/lcf
  8. The following example installs the Windows endpoint antonella on the computer system agodino using IPX to connect to the NetWare gateway lux using the endpoint vernon as a proxy.
    winstlcf -x IPX -N vernon -g LUX+7787 -n antonella agodino
  9. The following example installs an endpoint on machine oak using an encrypted SSH connection from a Windows managed node .
    /usr/bin/perl -S winstlcf -j oak

    To install an endpoint from a Windows managed node using the winstlcf command and -j option, you must launch a Cygwin command prompt and then run the winstlcf command from the version of Perl provided by Cygwin.

See Also, wdelep



Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy


War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes


Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law


Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

Copyright © 1996-2021 by Softpanorama Society. was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to to buy a cup of coffee for authors of this site


The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019