Linus Torvalds Releases Linux 1.2.0
Tuesday, March 7, 1995, Linus Torvalds released Linux 1.2.0, also called “Linux '95”, little less than a year after his release of the ground-breaking Linux 1.0. In his announcement, Linus pointed out an important difference—the license—between the two operating systems, with an elaborate spoof on Microsoft's license explanation. Here's a short sample from Linus's spoof:
Linux '95 has several types of licenses, including, but not limited to:
End-User License Agreement—Applications:This is an application-specific license, which is intended for a single application running on your Linux '95-authorized computer. The license agreement rules differ depending on the application. See appendix `H'.
End-User License Agreement—Systems:This agreement is intended for single system product use, such as the Linux '95 kernel license. It's important to note that the Systems product licenses do not permit concurrent, or second copies. There is a special Multi-License upgrade program for those that want to start out with a single license but later expand their setup.
Multi-License Pak:This agreement is intended for sites with multiple systems, which want to run multiple copies of the Linux '95 system concurrently and/or on several machines. This license is available as a 10, 50 or 100-unit license depending on the size of your installation.
[...]
The “I've got too much money” License: Contact us for details on this exclusive licensing deal, we'll work something out. Please contact “ivemoney@linux.Helsinki.FI” directly.
Large institutions that want to possibly combine several licenses can do so with a standard licensing fee reduction. Please contact our licensing department for further details.
[...]
We thank you for using Linux '95,
Linus
Of course, Linux 1.2 is still freely available under the GNU public license, just as Linux 1.0 was, and just as future versions will continue to be, and so all the licensing fees mentioned above are $0 per copy...except maybe the “I've got too much money” license.

Figure
Here is a list of a few of the new features that version 1.2 has, compared to version 1.0:
Highly improved networking.
Faster disk I/O.
EIDE, multiple-IDE controllers, and ATA-CD-ROM support.
Supports more kinds of floppies, including 2.88 MB.
More CD-ROM devices supported.
Improved SCSI support, support for new SCSI adapter drivers.
Support for more network adapters.
New, improved memory management.
Multi-platform support underway.
UMSDOS filesystem: install Linux on DOS filesystem.
New sound driver supports Linux DOOM
Much, much more.
Most Linux vendors are expected to release new versions of their distributions containing Linux 1.2 soon.
If you have Internet access, you can download the source code for the new kernel via ftp from ftp.funet.fi, in the directory /pub/OS/Linux/PEOPLE/Linus/v1.2/. Version 1.2.0 is in the file linux-1.2.0.tar.gz; by the time you read this, it is likely that a few bug fixes will have been released, so look for the newest version there. If you do not have internet access, a local BBS may have the source code, and any one of the vendors advertising in Linux Journal will be happy to sell you a CD-ROM with the source included as soon as they have them available.
Linus has indicated that further testing, and bug fixing as necessary, will be done for approximately another month, leading to an even more stable Linux 1.2.x release. He has indicated that he will probably begin work on a new development series, Linux 1.3.x, sometime in early April.
Some utilities will need to be upgraded if you upgrade from Linux 1.0 to Linux 1.2, including networking utilities like ifconfig. The update program and the module utilities will also need to be updated. An article in the next issue of Linux Journal will cover the process of updating from 1.0 to 1.2 in detail.
Since Linux version 1.0 was released, the version number has been used to distinguish between “production” or “stable” releases of Linux and “experimental” or “development” versions. Each version number has three parts: the major release number, the minor release number, and the patchlevel. Version 1.1.95, is major version 1, minor version 1, patchlevel 95. Version 1.2.0 is major version 1, minor version 2, patchlevel 0. All version numbers with even minor version numbers are considered production versions, and official patches to production versions only include bug fixes, so for instance, between version 1.0.0 and 1.0.9 there were only bug fixes. All version numbers with odd minor version numbers are development versions, which (although they usually work fine) are not expected to be stable—all sorts of changes might have happened during their development.
Linux 1.2 is the second production release of Linux, and follows the first production release, Linux 1.0, by just under a year.
Phil Hughes
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Designing Electronics with Linux
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?




9 hours 13 min ago
13 hours 40 min ago
17 hours 15 min ago
17 hours 48 min ago
20 hours 11 min ago
20 hours 14 min ago
20 hours 16 min ago
1 day 41 min ago
1 day 2 hours ago
1 day 7 hours ago