Softpanorama

May the source be with you, but remember the KISS principle ;-)
Contents Bulletin Scripting in shell and Perl Network troubleshooting History Humor

Prev Contents Next

The Historical Dimension of "Solaris vs. Linux" Debate

Long before UNIX and PDP-11 there were mainframes with OSes in assembler where kernel was compiled for each installation, with customer-developed patches and enhancements, and tools tapes put together by customers and vendors. One of the earliest user groups (if not the very first) was the user group of IBM mainframes users called SHARE -- it's not an acronym, it's what the members did. They did shared the code. 

In late 80th and early 90th DOS user community flourished on Usenet  creating huge archives of source code and free binaries such as SimTel, Garbo, etc. Here is a quote from comp.os.msdos.programmer FAQ (19-July-1992):

====================

QA01. What is garbo?  What is wustl?

    These are alternative archive sites.  Please try to use the site for
    your continent; see next Q.

QA02. What are Simtel and "mirror sites"?  What good are they?

    The U.S. Government maintains a massive archive of useful software
    and info files at the SIMTEL20 site.  This includes scads of
    utilities, plus source code from {PC Magazine}, {Dr Dobbs Journal},
    and others.  You can use Simtel by ftp (wsmr-simtel20.army.mil =
    192.88.110.20) or (if necessary) email.  To find out how, look for
    these monthly articles in comp.binaries.ibm.pc.archives :

        How to find files in the SIMTEL20 msdos collection
        SIMTEL20 archive info for Internet FTP users
        How to order SIMTEL20 files via e-mail

    Another important archive site is garbo (at the University of Vaasa,
    Finland).  garbo is set up differently from Simtel but contains many
    of the same useful files.

BBS of DOS era were first social sites for computer enthusiasts (here is one announcement Google Groups comp.archives.msdos.announce). They have had their own community of testers (see Frequently asked question list for comp.sources.testers).  Most classic Unix utilities such as csh, awk, perl, sed, vi, ed, lex, yacc, find, grep, tr, wc, tar, diff, man, troff,  nroff  etc were freely available with the source code. NSF, ftp, telnet client were also freely available.   There was complete Unix environment for DOS with GNU c compiler called djgpg which also has its own Usenet group (comp.os.msdos.djgpp). It has several thousands strong user community (full listing of Usenet groups):

comp.os.msdos.djgpp

  DOS GNU C/C++ applications and programming environment.

  Readers: 5400 (0.1%) {22%}         Mesgs per month/day: 648/22     {54%}
  Crossposting: 1% {12%}             Megs  per month/day: 0.9/0.030  {53%}
  Sites reciving this Group: 42%     Cost ratio ($US/month/rdr): 0.06

Linux is just a part (and far from being the most important part) of open source movement, which became prominent with the advent of Internet. Open source movement is not something new. People in local communities, political parties, religious organizations, public television audiences, and ethnic groups do in fact often succeed in getting themselves organized and mobilized in pursuit of a public good for the group. Often the level of productivity is below the level that would be possible in for-profit enterprise; often there is some level of free-riding involved; but history alike are replete with examples of long-term and successful voluntary collective action. Programming is no exception.

It is important to understand that Linux is the second free Unix-like OS. The first was BSD Unix. The Orwellian level of rewriting of history that exists in pro-linux camp and that also poisoned much of mainstream press (not without gentle IBM help) can be nicely illustrated by the fact that Linus Torvalds often considered to be a revolutionary despite the fact that Linux kernel is a straightforward (even somewhat backward) clone of Unix kernel, a 30 years old OS. Often this misinformation is coupled with another: that Linux was the first open source OS.

Generally programming is not a place for blind devotion. As John Stuart Mill aptly put it long before computers were available:

There must be discussion, to show how experience is to be interpreted. Wrong opinions and practices gradually yield to fact and argument: but facts and arguments, to produce any effect on the mind, must be brought before it. Very few facts are able to tell their own story, without comments to bring out their meaning. The whole strength and value, then, of human judgment, depending on the one property, that it can be set right when it is wrong, reliance can be placed on it only when the means of setting it right are kept constantly at hand. In the case of any person whose judgment is really deserving of confidence, how has it become so? Because he has kept his mind open to criticism of his opinions and conduct. Because it has been his practice to listen to all that could be said against him; to profit by as much of it as was just, and expound to himself, and upon occasion to others, the fallacy of what was fallacious. Because he has felt, that the only way in which a human being can make some approach to knowing the whole of a subject, is by hearing what can be said about it by persons of every variety of opinion, and studying all modes in which it can be looked at by every character of mind.

It is very important to understand that before 1991, the year when Linus started his project, several books with in-depth coverage of Unix internals were published. Source code was also widely available:

Sun shipped its first UNIX-based Sun-1 workstation in 1982: almost ten years before Linus Torvalds decided to replicate Unix kernel as a "hobby/vanity fair" project. In 1986 Sun (for a short period of time) produced Intel 386 based Unix workstation [Sparcproductdirectory2004]:

If, like me, you were looking for a well integrated Unix platform on Intel Architecture in 1986 you could do a lot worse than choose Sun's 386i. It ran SunOS and some DOS applications in a of Intel development. compatible window, and it had slots for PC-AT disks. There the similarity to a PC ended. Instead of low resolution PC graphics it had high resolution Sun graphics. Instead of low performance disk drives it came with high performance SCSI disks - and a lot more RAM than the PCs of that vintage. Although the 386i was rubbish as a graphics workstation (the graphics was too slow) and despite the fact that the DOS emulation was too slow and useless to run most DOS applications - the 386i was a low cost entry level database server which could outperform Sun-3's and low end VAXes for a fraction of the cost. When I first signed up as a Sun VAR in the 1980s - it was the 386i which I used as the Trojan horse to replace our aged Zilog boxes and eventually displace the HP and DEC minis. We were using Motorola's VMEbus SBCs as our main real-time platform - but needed a Unix with a future to coexist with our multiprocessor applications. Although the first SPARC systems had come out - the original Sun-4's didn't inspire any more confidence in me than the myriad of other RISC based Unix servers which were hitting the market at the time. Sun was supporting 3 hardware platforms with its SunOS at the time:- Motorola, SPARC and Intel. My guess was that Sun's long term strategy would be to run with Intel. I was right - but there was to be an 18 year discontinuity before that became a firm reality.

When we compare Solaris with linux it is important to understand that historically Sun has a very impressive record of making contributions to the community. Among the most notable contributions we can mention:

  1. The idea "the network is the computer" - many pieces of hardware, some of them mutually incompatible, accessible as one system via common protocol (TCP/IP). The acronym "SUN" means "Stanford University Network". Please remember that this idea was introduced in 1981 with SunOS, long before WWW revolution that from 1994 gradually make TCP/IP available to everybody. 

  2. Virtual filesystem interface. Sun OS 2.0 offered a filesystem independent interface to concurrently support several different filesystems within an OS instance. This interface, today know as the vnode/VFS interface was created first of all to accommodate NFS. UFS was modified to accommodate this new vnode/VFS interface framework.

  3. Tmpfs filesystem that uses virtual memory subsystem (VM) for storing files. It was invented in Sun OS 4.0 in 1987 and migrated to Solaris. See Peter Snyder, ‘‘tmpfs: A Virtual Memory File System,’’ Proceedings of the Autumn 1990 EUUG Conference, pp. 241-248. EUUG, Nice France, October 1990. The Solaris /tmp directory was made a tmpfs file system by default starting with Solaris 2.1, released in November 1994. Later (around 2001) in was re-implemented in linux kernel 2.4. Tmpfs was is designed primarily as a performance enhancement to allow short lived files to be written and accessed without generating disk or network I/O. By using RAM it maximizes file manipulation speed. It was pretty  brilliant idea, that was somewhat reminiscent of Multics:  to use  virtual memory system facilities for file storage and access. Tmpfs files are not differentiated from other uses of physical memory. This means tmpfs file data can be ‘‘swapped’’ or paged to disk, freeing VM resources for other needs. VM system  performs many low level tmpfs file system operations. This reduces the amount of code needed to maintain the file system, and ensures that tmpfs resource demands may coexist with other VM resource users with no adverse effects. As such it is more advanced then ramdisk (which originated ion Ms DOS), and is more dynamic. In addition to /tmp many Sun based webservers use tmpfs for storing WebPages (now it is perfectly possible with linux too but such practice is rare). The same is true for mail servers, especially Sendmail-based.   Tmps was also added to NetBSD and FreeBSD.
     

  4. /proc virtual filesystem (which originated in Plan 9 but was introduced into Unix by Solaris). The idea of using filesystem interface to expose and manipulate system blocks now is standard part of any Unix. So called "proc" utilities introduced by Solaris also proved to be incredibly useful. Both pgrep and pkill are real time savers for system administrators. Less known but still interesting utilities include pstack to show you a process' stack (for each thread), psig to see the signal handlers for a process, ptree to draw an ASCII chart of a process' parents and children. The latter you need only occasionally, but when you need them, there is no substitute.

  5. Loadable kernel modules (SunOS 4.x was the first Unix to offer them). This was one of the reasons that Solaris typically was shipped without a C compiler.

  6. RPC -- which is a revolutionary way to distribute computation in Unix, the infrastructure that made such important Unix achievements as rsh, NSF, NIS, ssh and many other protocols possible.

  7. PAM -- this is standard way to implement complex authentication schemes in all modern Unixes and linux. PAM was first proposed by Sun Microsystems in an RFC 86.0 dated October 1995 (see The original PAM RFC). As authors of PAM - InstallationWiki state:

    The history of PAM goes back to 1995 when developers from Sun Microsystems implemented a generic framework for Solaris. When Solaris 2.6 was released in August 1997, PAM was an integrated component of the operating system. Ever since then, Solaris has been using PAM for authentication. In February 1997, the Linux-PAM project began, and most GNU/Linux distributions today are using PAM.

  8. Packages for binary software distribution. In 1992 Solaris adopted a SVR4 mechanism for "standardizing" the installation of optional software called SVR4 packages. Very quickly all Sun software was packaged with this format. Most vendors switched to this format in Solaris 2.3. Packages can be installed/deinstalled with pkgadd/pkgrm utilities. Note that the "pkg" system introduced a lot of new concepts which later were adopted in linux packaging schemes, for example the concept of packages database (in /var/sadm/install), the concept of checking of installed package for integrity and many others. A database was also used for clean removal of packages. Here how the "pkg" concept was described in early version of Solaris FAQ dated 16 Jun 93:

    • What are "packages"?

      A SVR4 mechanism for "standardizing" the installation of optional software. Most vendors are expected to use this format for distributing add-on software for Solaris 2.x.

      Packages can be installed/deinstalled with pkgadd/pkgrm which are standard SVR4 items, or with swm (CRT) or swmtool (GUI-based) which are provided only in Solaris 2.

      Note that the "pkg" system keeps lots of files in /var/sadm/install, and in particular the file "contents", which is hundreds of KB, and that there are two copies of it while pkgadd is running, so you needs lots of free space where /var is, typically the root. This file must be kept around if you want, for example, to use pkgrm to remove a package, or pkgchk to verify months later that all of a package's files are still intact.

    RPM packaging format was created in 1995 by Marc Ewing and Erik Troan for Red Hat distribution. RPM was in turn based on several earlier linux packaging systems but soon it became the most common way of packaging software for linux and until apt was created dominated among linux distributions. It replicated the basic functionality of SVR4 packages with some extensions. Its rapid adoption in linux distributions as well as the creation of alternative formats like apt can be considered to be the testament of success of Solaris-pioneered approach to binary software packaging for Unix. Some information about history of RPM is available from Maximum RPM

  9. Open Office (if this can be considered an innovation). While it was not developed by Sun, the product was bought and later released as open source by Sun. Due to the fact that Sun released the codebase under an open source license Open Office instantly became the only credible free Office environment available for both Unix and linux and the only Unix/Linux Office suit  that in some respects is competitive with Microsoft Office. Some cities (like Munich) even experimented with switching to Open Office to save money.
     

  10. Wabi (the precursor of Wine) -- wine is the most popular windows emulator for Linux. Bob Amstadt, the initial project leader, and Eric Youngdale started the Wine project in 1993 as a way to run Windows applications on Linux. It was inspired by two Sun Microsystems' products, the Wabi for the Solaris operating system, and the Public Windows Initiative,[17] which was an attempt to get the Windows API fully reimplemented in the public domain as an ISO standard but rejected due to pressure from Microsoft in 1996.[18] Wine originally targeted 16-bit applications for Windows 3.x, but as of 2010 focuses on 32-bit and 64-bit versions which have become the standard on newer operating systems. The project originated in discussions on Usenet in comp.os.linux in June 1993.[19] Alexandre Julliard has led the project since 1994.
     

  11. Virtual Box virtual machine (now exists as Oracle VM VirtualBox )

    VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU General Public License (GPL) version 2. See "About VirtualBox" for an introduction.

    Presently, VirtualBox runs on Windows, Linux, Macintosh, and Solaris hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, Windows 7, Windows 8, Windows 10), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x and 4.x), Solaris and OpenSolaris, OS/2, and OpenBSD.

  12. The ides of a uniform scripting language for Unix environment. While this idea of universal scripting language for Unix was killed by Sun brass which, unfortunately, fell in love with Java. But historically the company supported the development of TCL and the funded the conversion of TCL from a one man university-based project into full-fledged production strength scripting environment. This was a very sad story of innovation killed by a corporation in a way similar to the history of treatment of VM/CMS by IBM brass. Javascript has also origin in Sun research.

    It's really unfortunate that both Solaris and linux remains extremely archaic in this respect and that no Unix flavor provides standard, universal for most applications scripting language like REXX in OS/2 or VBA in Windows. In this respect it is honest to state that both Solaris and linux should be considered backward, not revolutionary environments (actually linux can be considered a backward, outdated OS in more then one respect as we will discover later).

  13. The first successful commercial implementation of light-weight virtual machines (zones) pioneered by FreeBSD. Sun significantly extended this concept in Solaris based on initial FreeBSD implementation called jails and due to this Solaris 10 be called the first XXI century Unix. Solaris zones cleanly solved  important for large enterprise environment problem of "root hell" when root access is shared between multiple "application owners" and system administration group (which in turn can consist of a dozen of people). As a result left hand often does not know what right hand is doing. The main problem in UNIX security is not that root is too powerful, but that a regular user account as not powerful enough and that for many tasks application owners need to be able to switch to root. Giving application owners a separate zone with full root privileges creates much nicer, development friendly environment, the environment currently which gradually is replicated in other Unix flavors much like NFS and /proc subsystem (AIX 6 was the second OS after Solaris to implement this approach ).  Only after 2015 Linux achieved quality of implementation that allows using light weight machines in production env.
     

  14. Coming from Stanford experience Sun was the first vendor committed to shipping servers with "no proprietary network" - all networking was TCP/IP-based networking and was available in Solaris from day one.  Actually Solaris was the first OS in which detaching and re-attaching networking cable on a working server was a trivial exercise. Sun servers have high interoperability and due to this they have been all over the Web in 2000 just before dot-com crash. Linux TCP-networking was added as an after-thought and initially was an add-on optional package.  That's another sign that Linux kernel and linux in general was, from a technical standpoint,  a conservative project.
     

  15. Sun Grid engine. Very powerful and flexible cluster scheduler. One of the most popular open source products for Linux clusters
     

  16. Hadoop-SGE integration  with HDFS as cluster filesystem  as one of the most popular implementation of Hadoop concept:

    Nov 30, 2009 In case you haven't heard yet, the upcoming release of Sun Grid Engine will include an integration with Apache Hadoop that will allow Map/Reduce jobs to be submitted to a Sun Grid Engine cluster while minding HDFS data locality. The 6.2u5 release will be out by the end of the year, but it's currently in the beta testing phase. And that's where you come in.

    ... ... ...

    In a nutshell, the integration consists of two components. The first is the hadoop parallel environment that allows Map/Reduce jobs to be started as parallel jobs in a Sun Grid Engine cluster. The second is the integration with HDFS, called Herd, that makes the Sun Grid Engine scheduler aware of the locations of the HDFS data blocks. Herd has two parts. One part is a load sensor that runs on every execution machine and reports the HDFS blocks on that machine. The other part is a JSV that translates HDFS data paths included in the job submission into a list of HDFS blocks needed by the job.

  17. Lustre filesystem. The Lustre filesystem development was as a research project in 1999 by Peter J. Braam who worked at  Carnegie Mellon University (CMU) at the time. Braam went on to found his own company Cluster File Systems in 2001, starting from work on the InterMezzo file system in the Coda project at CMU. Lustre was developed under the Accelerated Strategic Computing Initiative Path Forward project funded by the United States Department of Energy, which included Hewlett-Packard and Intel.[16] In September 2007, Sun Microsystems acquired the assets of Cluster File Systems Inc. including its intellectual property. Sun included Lustre with its high-performance computing hardware offerings
     

  18. ZFS filesystem. Pioneered in Solaris 10 and later open sourced. Now along with Solaris is used by FreeBSD.
     

  19. Openindiana  -- a derivative of Open Solaris with ZFS as a filesystem
     

  20. Environment modules  The Modules package is designed to abstract environment information from the user. It was created by John L. Furlani in early 1990th when he was the system administrator for Sun’s Research Triangle Park Facility in North Carolina.

This list definitely can be continued but the statement that I want to make is that rumors about linux being an innovative Unix implementation are greatly exaggerated :-). Moreover Linux track record in innovation looks pale even in comparison with other major branches of commercial Unixes each of which also introduced important parts of modern Unix infrastructure that linux re-implemented.

For example AIX introduced concept of volume manager (licensed from Veritas but actually pretty native for all IBM Operating systems products with idiosyncratic distinction between physical and logical drives which comes from the days of OS/360) and one of the first really successful in production implementations on Unix of para-virtualization (Lpars in AIX).

I put this example to show that the level of distortions of history typical in many publications devoted to linux is such that for a reasonable computer science literate reader it should immediately produce an allergic reaction similar to the reaction many native English speakers get reading a paper with just too many grammar and spelling errors (this one is a nice example of the genre ;-).

For those who got their education of Unix history from various attempts to rewrite it in best Bolsheviks traditions it is important to remember that linux actually belongs to the dozen of Unixes created for Intel with previous major implementation being Microsoft Xenix, which actually created all the necessary for Unix on PC logical infrastructure including partitioning schemes, boot managers for dual boot and console switching (idea of multiple virtual consoles, switchable via Alt-F1, Alt-F2 and so on belongs to Xenix). It also stimulated writing of over a hundred books on the topic. In other words Xenix was not only dominant Unix implementation on PC, it was the most popular Unix in existence. Microsoft voluntarily abandoned its leadership position to concentrate on OS/2 and then NT and the void was filled by Linux.

I would like to stress it again that it was Microsoft XENIX not linux, which created most of the infrastructure for Unix on Intel including the critical mass of books. Whether we like it on not, linux owes much of its success to Microsoft: it was XENIX which provided all (yes, all) the major technical solutions and infrastructure used by each and every subsequent Intel Unix implementation.

Moreover even later after abandoning Unix in favor of OS/2 Microsoft indirectly subsidized all Unixes on Intel as the de-facto owner of PC standard: hardware that any Intel based Unix is running on is created by OEMs using the standards that Microsoft license for free to all PC manufactures and the cost of this hardware is mainly determined by the size of the market created by Microsoft OSes. Plug and play hardware specification is a nice example of Microsoft contribution to linux success here. Whether we like Microsoft or not, the simplest and reasonably precise definition of PC always was "Microsoft compatible computer". As the most recent example it was actually Microsoft who politely and firmly explained to Intel that it should provide hardware compatibility with Opteron and not to reinvent the 64-bit extensions wheel. For Intel breach of relations with Microsoft was too serious threat to ignore. That's just one example of how Microsoft provides and defends unification and standardization of hardware platform often mistakenly called Intel-platform, but which properly should be called Microsoft-Intel platform, the platform that linux uses for free without any investments. In this respect one can state that linux is just a side effect of Microsoft success in hardware. The undeniable fact is that linux is critically dependent on Microsoft-subsidized hardware and without Microsoft success there would never be any linux as mass, supported by such companies as IBM and HP, operating system. I think that Linux Towards should seriously consider adding Microsoft to the list of kernel contributors ;-).

Sun fought Microsoft-Intel alliance on his own UltraSparc ground. That was a difficult uphill battle that left many scars and Sun did not succeed. But it did it fought Microsoft-Intel dominance straight on and until recently, if we allow somewhat politically incorrect word, did not tried to co-habilitate Microsoft subsidized hardware. That was a completely different game, much more complex and dangerous but if we like to use high words it was real fight for the freedom (unlike Intel CPUs UltraSparc was/is an open sourced CPU). In a way, typical linux advocates rumblings (including some Linux Torvalds and Richard Stallman's interviews) are completely hypocritical -- it you love freedom so much why on the Earth you use closed proprietary CPU when a free open-sourced CPU is readily available and even does not cost that much.

BSD branch also get further development and eventually  was represented by three major flavors: FreeBSD, OpenBSD and NetBSD. Each of them make important contributions. For FreeBSD it was jail (a brilliant light-weight VM implementation that serves as a prototype for sun containers), for OpenBSD was it was SSH daemon and unmatched attention to security. For NetBSD it was portability. 

Please also do not forget that linux is now twenty years old OS that has a lot of baggage and the development is no longer as nimble and fast as it used to be. Most core developers became middle-aged, tired and disillusioned "old guard". By all computer science standards, twenty year is an old age for any OS. Actually very few OSes survived that long. Inevitably the key developers who participated in it from day one approach the age when some sclerosis and arthritis should be expected :-). And change of the guard in free/open source development is a very complex and painful process as BSD experience (which is an even older OS which remains the trailblazer for all newcomers into free OS arena and as patriarch of the field experienced signs of sclerosis both in architecture and key developers minds before it hit linux) can attest. Days when Linus Torvalds will be just another retired multi-millionaire with his own (smaller then Larry Edison's :-) yacht might be closer then many linux fans think...

Actually the reason for Unix survival are not trivial and are often missed. I think it is because Linux as not just an operating system—it's has dual personality of OS and development platform. I think it is the latter that  ensured its immortality. Unix as a platform enables accelerated experimentation and development of software prototypes due to availability of scripting languages and the massive array of open source components.

Unix was the first viable component architecture with shell serving as a glue to the utilities which were simultaneously components. The connection between components was mainly via pipes and environment variables. And unfortunately in this area Linux contributed nothing. Linus Torvalds by training and by inclination is just a brilliant C programmer with strong DOS background. He never understood the area of scripting languages and never paid attention to the development of the platform aspect of Linux.  And Microsoft by implementing .Net produced a knockdown for Linux as a development platform despite inferiority of many Windows NT line architectural decision (and first of all OS API) and the baggage of DOS mentality. Actually Solaris also has dismal record in this area. It is true that Sun brass understood this issue better and at one time played with the possibility of using TCL as a new component glue into Solaris. But Java wave washed out those inclinations and those ideas never materialized.

Historically Sun's assault of IBM's mainframe business was one of the major reasons why IBM became so interested in Linux and tried to save his mainframe franchise from extinction by implementing VM/Linux project. For IBM Linux was a brilliant counterplay of Sun encroaching into its mainframe turf. Idea of running Linux via tried and true VM instantly gave a new lease of life to the dying, but still very good technology. And that's why the major push in IBM adoption of Linux was initially directed toward VM/Linux -- a bold and reasonably successful attempt to stop sliding of the market share of the oldest IBM platform into oblivion. That essentially saved such an amazing (and underappreciated by almost everybody, including old IBM brass) OS as VM. Later VM virtualization technology was also ported to AIX. Currently IBM tries to emphasize Linux on Power ...

The last but not least historical distortion of linux history is that linux development is often presented as a work of volunteers. This is hypothesis open to review for all but the earliest years of linux development. A recent report from the Linux Foundation reveals the extent to which linux development looks like a corporate cooperative initiative:

Report states: "It is worth noting that, even if one assumes that all of the 'unknown' contributors were working on their own time, over 70% of all kernel development is demonstrably done by developers who are being paid for their work."

That brings us to the ideological dimension of Solaris vs. linux debate.

Prev Contents Next



Etc

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 in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes.   If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. 

ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.  

Society

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

Quotes

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

Bulletin:

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

History:

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


Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.

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.

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 make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info

Disclaimer:

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 author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

Created Jan 2, 2005. Last modified: April 06, 2017