Language Selection

English French German Italian Portuguese Spanish

Your First Kernel

1.X
27% (428 votes)
2.0.x
11% (176 votes)
2.2.x
16% (250 votes)
2.4.x
26% (411 votes)
2.6.x
20% (324 votes)
Total votes: 1589

Another interesting poll

Do you compile your own Linux kernels?

2.4.22 was THE kernel

atang1 wrote:
It has posix and mosix and USB2.0 emulation from scsi.

It has kudzu and bios drivers and others in /dev.

It has KDE and Gnome and Cups.

IIt has DHCP, dhcpcd.

It has Mozilla 1.2 And sylpheed.

2.6.x is for servers of local distributed data priority and ambiguous drivers for devices made of DSPs. Now added realtime threads in 2.6.21.


I second this.
2.4.22 was really THE perfectly working kernel on my computer years ago.

Wink

My first kernel?

0.97 Yaggdrasil. (Can't spell it any more.) This was 92 Stuck it on my desktop in Newmarket and am remembering it from location. Bought the CD's at U of Toronto Bookstores. Put it up against AIX, SCO and Solaris then got the slack diskette set from Walnut Creek.

But in 86 I was trained on System V Berkley 4.2 and wrote code for it. We had a 200meg hard drive. It was about 6 rack units high x 19" wide on a Modcomp then graduated to a VAX 750 with a DEC VT240.

Asta la Vista

My first kernel?

I had to look up Red Hat 5 on Distrowatch. I'm glad someone keeps track of this stuff. I don't even think I knew what a kernel was back then.

I didn't know DW had that info!

My first version of Linux was a boxed publisher's version of Red Hat 5.2 that was on sale at Costco, of all places. (Only time I've ever seen anything Linux-related there.) Kernel 2.0.36.

More in Tux Machines

Red Hat News

  • An Open Source Load Balancer for OpenShift
    A highly-available deployment of OpenShift needs at least two load balancers: One to load balance the control plane (the master API endpoints) and one for the data plane (the application routers). In most on-premise deployments, we use appliance-based load balancers (such as F5 or Netscaler).
  • Red Hat Beefs Up Platform as a Service Suite
    Red Hat has begun shipping Red Hat Fuse 7, the next major release of its distributed, cloud-native integration solution, and introduced a new fully hosted low-code integration platform as a service (iPaaS) offering, Fuse Online. With Fuse 7, the vendor says expanding its integration capabilities natively to Red Hat OpenShift Container Platform, an enterprise Kubernetes platform. Fuse gives customers a unified solution for creating, extending and deploying containerized integration services across hybrid cloud environments.
  • Red Hat ‘Fuses’ Low Code Development and Data Integration
    Red Hat, a provider of open source solutions, has announced Red Hat Fuse 7, the next major release of its distributed, cloud-native integration solution, and introduced a new fully hosted low-code integration platform as a service offering, Fuse Online. With Fuse 7, Red Hat is expanding its integration capabilities natively to Red Hat OpenShift Container Platform, a comprehensive enterprise Kubernetes platform. Fuse gives customers a unified solution for creating, extending and deploying containerized integration services across hybrid cloud environments.
  • The GPL cooperation commitment and Red Hat projects
    As of today, all new Red Hat-initiated open source projects that opt to use GPLv2 or LGPLv2.1 will be expected to supplement the license with the cure commitment language of GPLv3. The cure language will live in a file in the project source tree and will function as an additional permission extended to users from the start. This is the latest development in an ongoing initiative within the open source community to promote predictability and stability in enforcement of GPL-family licenses. The “automatic termination” provision in GPLv2 and LGPLv2.x is often interpreted as terminating the license upon noncompliance without a grace period or other opportunity to correct the error in compliance. When the Free Software Foundation released GPLv2 in 1991, it held nearly all GPL-licensed copyrights, in part a consequence of the copyright assignment policy then in place for GNU project contributions. Long after the Linux kernel and many other non-GNU projects began to adopt the GPL and LGPL, the FSF was still the only copyright holder regularly engaged in license enforcement. Under those conditions, the automatic termination feature of GPLv2 section 4 may have seemed an appropriate means of encouraging license compliance.
  • Monness Believes Red Hat (NYSE: RHT) Still Has Room to Grow
  • Comparing Red Hat (RHT) & Autoweb (AUTO)
  • As Red Hat (RHT) Share Value Rose, Calamos Advisors Upped Its Position by $300,831; Chilton Capital Management Increases Stake in Equinix (EQIX)
  • Blair William & Co. IL Buys 23,279 Shares of Red Hat Inc (RHT)

Total War: WARHAMMER

Red Hat changes its open-source licensing rules

From outside programming circles, software licensing may not seem important. In open-source, though, licensing is all important. So, when leading Linux company Red Hat announces that -- from here on out -- all new Red Hat-initiated open-source projects that use the GNU General Public License(GPLv2) or GNU Lesser General Public License (LGPL)v2.1 licenses will be expected to supplement the license with GPL version 3 (GPLv3)'s cure commitment language, it's a big deal. Read more

Android Leftovers