add directory kernel

kernel/Historic/old-versions/README

@@ -0,0 +1,55 @@
+To: Linux-Activists@BLOOM-PICAYUNE.MIT.EDU
+From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
+Crossposted-To: alt.os.linux
+Subject: Second 0.95a alpha-patch, part 1/2
+Date: 4 Apr 92 14:42:10 GMT
+
+This is the promised patch to 0.95a, which hopefully corrects some of
+the problems encountered.  This is /not/ an offical new release: it's
+just a set of patches to get the same kernel I am currently running.
+
+Bugfixes:
+
+- extended partitions should finally work correctly (this release also
+  contains code for the hd-ioctl call, needed for fdisk).  Code mostly
+  by hedrick.
+
+- I corrected my original ptrace-fix (writing a long word to another
+  process' data space could fail with my original patches)
+
+- 387-emulation bug with the instructions "fcom[p] %st(x)" which
+  resulted in bad results on non-387 machines with newer versions of
+  gcc.  The emulation is still ugly, but it seems to work.
+
+- the cooked mode deletion/linekill bugs should be fixed.
+
+- various error-returns were wrong: I correted some of them (thanks to
+  bruce evans who pointed them out).  The bad error-values resulted in
+  incorrect or spurious error-messages from 'rm' etc. 
+
+- various minor fixes (including some in the hd-driver: this might help
+  persons with unexpected-interrupt and/or timeout errors)
+
+Additionally this version contains VFS-code from entropy, and a
+readdir() system call needed for the VFS.  The latter was inspired by
+patches sent by Remy Card, who did it with a getdirents sys-call.  My
+version is slightly simpler, but is probably slower.  Things might yet
+change. 
+
+The installation has also changed slightly: the keyboard type and
+math-emulation are specified in the main Makefile.  That one also
+contains the -fcombine-regs flag needed for 1.40.  The other makefiles
+should no longer need editing. 
+
+I've also incorporated the ps095 kernel patches: to get the actual
+user-level stuff you still have to get the ps-distribution.  Printer
+ports /still/ aren't in there, but this time I positively /promise/ to
+put it in next week.  Really. 
+
+People who have been patching their kernel might have problems getting
+this patch to work: it was made against a clean 0.95a kernel.  I'll
+consider a patched-up kernel version 0.95c - and I'd appreciate if
+future patches to me would be sent against this version.  I'll still
+accept older patches, or course. 
+
+                Linus

kernel/Historic/old-versions/RELNOTES-0.01

@@ -0,0 +1,254 @@
+
+
+
+		Notes for linux release 0.01
+
+
+		0. Contents of this directory
+
+linux-0.01.tar.Z	- sources to the kernel
+bash.Z			- compressed bash binary if you want to test it
+update.Z		- compressed update binary
+RELNOTES-0.01		- this file
+
+
+		1. Short intro
+
+
+This is a free minix-like kernel for i386(+) based AT-machines.  Full
+source is included, and this source has been used to produce a running
+kernel on two different machines.  Currently there are no kernel
+binaries for public viewing, as they have to be recompiled for different
+machines.  You need to compile it with gcc (I use 1.40, don't know if
+1.37.1 will handle all __asm__-directives), after having changed the
+relevant configuration file(s). 
+
+As the version number (0.01) suggests this is not a mature product. 
+Currently only a subset of AT-hardware is supported (hard-disk, screen,
+keyboard and serial lines), and some of the system calls are not yet
+fully implemented (notably mount/umount aren't even implemented).  See
+comments or readme's in the code.
+
+This version is also meant mostly for reading - ie if you are interested
+in how the system looks like currently.  It will compile and produce a
+working kernel, and though I will help in any way I can to get it
+working on your machine (mail me), it isn't really supported.  Changes
+are frequent, and the first "production" version will probably differ
+wildly from this pre-alpha-release. 
+
+Hardware needed for running linux:
+	- 386 AT
+	- VGA/EGA screen
+	- AT-type harddisk controller (IDE is fine)
+	- Finnish keyboard (oh, you can use a US keyboard, but not
+	  without some practise :-)
+
+The Finnish keyboard is hard-wired, and as I don't have a US one I
+cannot change it without major problems. See kernel/keyboard.s for
+details. If anybody is willing to make an even partial port, I'd be
+grateful. Shouldn't be too hard, as it's tabledriven (it's assembler
+though, so ...)
+
+Although linux is a complete kernel, and uses no code from minix or
+other sources, almost none of the support routines have yet been coded.
+Thus you currently need minix to bootstrap the system. It might be
+possible to use the free minix demo-disk to make a filesystem and run
+linux without having minix, but I don't know...
+
+
+		2. Copyrights etc
+
+
+This kernel is (C) 1991 Linus Torvalds, but all or part of it may be
+redistributed provided you do the following:
+
+	- Full source must be available (and free), if not with the
+	  distribution then at least on asking for it.
+
+	- Copyright notices must be intact. (In fact, if you distribute
+	  only parts of it you may have to add copyrights, as there aren't
+	  (C)'s in all files.) Small partial excerpts may be copied
+	  without bothering with copyrights.
+
+	- You may not distibute this for a fee, not even "handling"
+	  costs.
+
+Mail me at "torvalds@kruuna.helsinki.fi" if you have any questions.
+
+Sadly, a kernel by itself gets you nowhere. To get a working system you
+need a shell, compilers, a library etc. These are separate parts and may
+be under a stricter (or even looser) copyright. Most of the tools used
+with linux are GNU software and are under the GNU copyleft. These tools
+aren't in the distribution - ask me (or GNU) for more info.
+
+
+		3. Short technical overview of the kernel.
+
+
+The linux kernel has been made under minix, and it was my original idea
+to make it binary compatible with minix. That was dropped, as the
+differences got bigger, but the system still resembles minix a great
+deal. Some of the key points are:
+
+	- Efficient use of the possibilities offered by the 386 chip.
+	  Minix was written on a 8088, and later ported to other
+	  machines - linux takes full advantage of the 386 (which is
+	  nice if you /have/ a 386, but makes porting very difficult)
+
+	- No message passing, this is a more traditional approach to
+	  unix. System calls are just that - calls. This might or might
+	  not be faster, but it does mean we can dispense with some of
+	  the problems with messages (message queues etc). Of course, we
+	  also miss the nice features :-p.
+
+	- Multithreaded FS - a direct consequence of not using messages.
+	  This makes the filesystem a bit (a lot) more complicated, but
+	  much nicer. Coupled with a better scheduler, this means that
+	  you can actually run several processes concurrently without
+	  the performance hit induced by minix.
+
+	- Minimal task switching. This too is a consequence of not using
+	  messages. We task switch only when we really want to switch
+	  tasks - unlike minix which task-switches whatever you do. This
+	  means we can more easily implement 387 support (indeed this is
+	  already mostly implemented)
+
+	- Interrupts aren't hidden. Some people (among them Tanenbaum)
+	  think interrupts are ugly and should be hidden. Not so IMHO.
+	  Due to practical reasons interrupts must be mainly handled by
+	  machine code, which is a pity, but they are a part of the code
+	  like everything else. Especially device drivers are mostly
+	  interrupt routines - see kernel/hd.c etc.
+
+	- There is no distinction between kernel/fs/mm, and they are all
+	  linked into the same heap of code. This has it's good sides as
+	  well as bad. The code isn't as modular as the minix code, but
+	  on the other hand some things are simpler. The different parts
+	  of the kernel are under different sub-directories in the
+	  source tree, but when running everything happens in the same
+	  data/code space.
+
+The guiding line when implementing linux was: get it working fast. I
+wanted the kernel simple, yet powerful enough to run most unix software.
+The file system I couldn't do much about - it needed to be minix
+compatible for practical reasons, and the minix filesystem was simple
+enough as it was. The kernel and mm could be simplified, though:
+
+	- Just one data structure for tasks. "Real" unices have task
+	  information in several places, I wanted everything in one
+	  place.
+
+	- A very simple memory management algorithm, using both the
+	  paging and segmentation capabilities of the i386. Currently
+	  MM is just two files - memory.c and page.s, just a couple of
+	  hundreds of lines of code.
+
+These decisions seem to have worked out well - bugs were easy to spot,
+and things work.
+
+
+		4. The "kernel proper"
+
+
+All the routines handling tasks are in the subdirectory "kernel". These
+include things like 'fork' and 'exit' as well as scheduling and minor
+system calls like 'getpid' etc. Here are also the handlers for most
+exceptions and traps (not page faults, they are in mm), and all
+low-level device drivers (get_hd_block, tty_write etc). Currently all
+faults lead to a exit with error code 11 (Segmentation fault), and the
+system seems to be relatively stable ("crashme" hasn't - yet).
+
+
+		5. Memory management
+
+
+This is the simplest of all parts, and should need only little changes.
+It contains entry-points for some things that the rest of the kernel
+needs, but mostly copes on it's own, handling page faults as they
+happen. Indeed, the rest of the kernel usually doesn't actively allocate
+pages, and just writes into user space, letting mm handle any possible
+'page-not-present' errors.
+
+Memory is dealt with in two completely different ways - by paging and
+segmentation.  First the 386 VM-space (4GB) is divided into a number of
+segments (currently 64 segments of 64Mb each), the first of which is the
+kernel memory segment, with the complete physical memory identity-mapped
+into it.  All kernel functions live within this area. 
+
+Tasks are then given one segment each, to use as they wish. The paging
+mechanism sees to filling the segment with the appropriate pages,
+keeping track of any duplicate copies (created at a 'fork'), and making
+copies on any write. The rest of the system doesn't need to know about
+all this.
+
+
+		6. The file system
+
+
+As already mentioned, the linux FS is the same as in minix. This makes
+crosscompiling from minix easy, and means you can mount a linux
+partition from minix (or the other way around as soon as I implement
+mount :-). This is only on the logical level though - the actual
+routines are very different.
+
+	NOTE! Minix-1.6.16 seems to have a new FS, with minor
+	modifications to the 1.5.10 I've been using. Linux
+	won't understand the new system.
+
+The main difference is in the fact that minix has a single-threaded
+file-system and linux hasn't. Implementing a single-threaded FS is much
+easier as you don't need to worry about other processes allocating
+buffer blocks etc while you do something else. It also means that you
+lose some of the multiprocessing so important to unix.
+
+There are a number of problems (deadlocks/raceconditions) that the linux
+kernel needed to address due to multi-threading.  One way to inhibit
+race-conditions is to lock everything you need, but as this can lead to
+unnecessary blocking I decided never to lock any data structures (unless
+actually reading or writing to a physical device).  This has the nice
+property that dead-locks cannot happen. 
+
+Sadly it has the not so nice property that race-conditions can happen
+almost everywhere.  These are handled by double-checking allocations etc
+(see fs/buffer.c and fs/inode.c).  Not letting the kernel schedule a
+task while it is in supervisor mode (standard unix practise), means that
+all kernel/fs/mm actions are atomic (not counting interrupts, and we are
+careful when writing those) if you don't call 'sleep', so that is one of
+the things we can count on.
+
+
+		7. Apologies :-)
+
+
+This isn't yet the "mother of all operating systems", and anyone who
+hoped for that will have to wait for the first real release (1.0), and
+even then you might not want to change from minix.  This is a source
+release for those that are interested in seeing what linux looks like,
+and it's not really supported yet.  Anyone with questions or suggestions
+(even bug-reports if you decide to get it working on your system) is
+encouraged to mail me. 
+
+
+		8. Getting it working
+
+
+Most hardware dependancies will have to be compiled into the system, and
+there a number of defines in the file "include/linux/config.h" that you
+have to change to get a personalized kernel.  Also you must uncomment
+the right "equ" in the file boot/boot.s, telling the bootup-routine what
+kind of device your A-floppy is.  After that a simple "make" should make
+the file "Image", which you can copy to a floppy (cp Image /dev/PS0 is
+what I use with a 1.44Mb floppy).  That's it. 
+
+Without any programs to run, though, the kernel cannot do anything. You
+should find binaries for 'update' and 'bash' at the same place you found
+this, which will have to be put into the '/bin' directory on the
+specified root-device (specified in config.h). Bash must be found under
+the name '/bin/sh', as that's what the kernel currently executes. Happy
+hacking. 
+
+
+		Linus Torvalds		"torvalds@kruuna.helsinki.fi"
+		Petersgatan 2 A 2
+		00140 Helsingfors 14
+		FINLAND

kernel/Historic/old-versions/RELNOTES-0.12

@@ -0,0 +1,191 @@
+
+
+		RELEASE NOTES FOR LINUX v0.12
+
+
+This is file mostly contains info on changed features of Linux, and
+using old versions as a help-reference might be a good idea.
+
+
+		COPYRIGHT
+
+The Linux copyright will change: I've had a couple of requests to make
+it compatible with the GNU copyleft, removing the "you may not
+distribute it for money" condition.  I agree.  I propose that the
+copyright be changed so that it confirms to GNU - pending approval of
+the persons who have helped write code.  I assume this is going to be no
+problem for anybody: If you have grievances ("I wrote that code assuming
+the copyright would stay the same") mail me.  Otherwise The GNU copyleft
+takes effect as of the first of February.  If you do not know the gist
+of the GNU copyright - read it.
+
+
+		INSTALLATION
+
+This is a SHORT install-note. The installation is very similar to 0.11,
+so read that (INSTALL-0.11) too. There are a couple of programs you will
+need to install linux: something that writes disk images (rawrite.exe or
+NU or...) and something that can create harddisk partitions (fdisk under
+xenix or older versions of dos, edpart.exe or something like that).
+
+NOTE! Repartitioning your harddisk will destroy all data on it (well,
+not exactly, but if you know enough to get back the data you probably
+didn't need this warning).  So be careful.
+
+READ THIS THROUGH, THEN READ INSTALL-0.11, AND IF YOU ARE SURE YOU KNOW
+WHAT YOU ARE DOING, CONTINUE.  OTHERWISE, PANIC.  OR WRITE ME FOR
+EXPLANATIONS.  OR DO ANYTHING BUT INSTALL LINUX - IT'S VERY SIMPLE, BUT
+IF YOU DON'T KNOW WHAT YOU ARE DOING YOU'LL PROBABLY BE SORRY.  I'D
+RATHER ANSWER A FEW UNNECESSARY MAILS THAN GET MAIL SAYING "YOU KILLED
+MY HARDDISK, BASTARD.  I'M GOING TO FIND YOU, AND YOU'LL BE SORRY WHEN I
+DO". 
+
+1) back up everything you have on your harddisk - linux-0.12 is still in
+   beta and might do weird things.  The only thing I guarantee is that
+   it has worked fine on /my/ machine - for all I know it might eat your
+   harddisk and spit it out in small pieces on any other hardware. 
+
+2) Test out the linux boot-disk with the root file system.  If it
+   doesn't work, check the hardware requirements, and mail me if you
+   still think it should work.  I might not be able to help you, but
+   your bug-report would still be appreciated. 
+
+   Test that linux can read your harddisk at least partly: run the fdisk
+   program on the root-disk, and see if it barfs.  If it tells you about
+   any partitions at all, linux can successfully read at least part of
+   your harddisk. 
+
+3) Make sure that you have a free /primary/ partition.  There can be 4
+   primary partitions per drive: newer DOS fdisks seem to be able to
+   create only 2 (one primary and one extended).  In that case use some
+   other partitioning software: edpart.exe etc.  Linux fdisk currently
+   only tells you the partition info - it doesn't write to the disk. 
+
+   Remember to check how big your partition was, as that can be used to
+   tell which device Linux thinks it is. 
+
+4) Boot up linux again, fdisk to make sure you now have the new
+   partition, and use mkfs to make a filesystem on one of the partitions
+   fdisk reports.  Write "mkfs -c /dev/hdX nnn" where X is the device
+   number reported by linux fdisk, and nnn is the size - also reported
+   by fdisk.  nnn is the size in /blocks/, ie kilobytes.  You should be
+   able to use the size info to determine which partition is represented
+   by which device name. 
+
+5) Mount the new disk partition: "mount /dev/hdX /user".  Copy over the
+   root filesystem to the harddisk, eg like this:
+
+	# for i in bin dev etc usr tmp
+	# do
+	# cp +recursive /$i /user
+	# done
+
+   You caanot use just "cp +recursive / /user", as that will result in a
+   loop.
+
+6) Sync the filesystem after you have played around enough, and reboot.
+
+	# sync
+	<wait for it to sync>
+	ctrl-alt-del
+
+   The folklore says you should do this three times before rebooting:
+   once should be enough, but I admit I do it three times anyway :) THIS
+   IS IMPORTANT! NEVER EVER FORGET TO SYNC BEFORE KILLING THE MACHINE.
+
+7) Change the bootdisk to understand which partition it should use as a
+   root filesystem.  See INSTALL-0.11: it's still the word at offset
+   508 into the image. You should be up and running.
+
+
+That's it. Go back and read the INSTALL-0.11
+
+
+		New features of 0.12, in order of appearance
+			(ie in the order you see them)
+
+	Linux now prints cute dots when loading
+
+WoW. Run, don't walk, to see this :). Seriously, it should hopefully now
+load even on machines that never got off the ground before, but
+otherwise the loading hasn't changed. Implemented by drew.
+
+	Super-VGA detection for extended alphamun modes
+
+I cannot guarantee it, I didn't write it, but it works great on a ET400
+SVGA card.  I'm addicted to the new look with 100x40 character editing,
+instead of a cramped 80x25.  This only works on VGA-cards that support
+higher text-resolutions, and which are correctly identified. Implemented
+by d88-man.
+
+	Job Control.
+
+Ok, everybody used to typing ^Z after they started a long command, and
+forgot to put it in the background - now it works on linux too.  Bash
+knows the usualy job-control commands: bg, fg, jobs & kill.  I hope
+there will be no nasty surprises.  Job control was implemented by
+tytso@athena.mit.edu.
+
+	Virtual consoles on EGA/VGA screens.
+
+You can select one of several consoles by pressing the left alt-key and
+a function key at the same time. Linux should report the number of
+virtual consoles available upon bootup. /dev/tty0 is now "the current"
+screen, /dev/tty1 is the main console, and /dev/tty2-8 can exist
+depending on your text-mode or card.
+
+NOTE! Scrolling is noticeably much slower with virtual consoles on a
+EGA/VGA. The reason is that no longer does linux use all the screen
+memory as a long buffer, but crams in several consoles in it. I think
+it's worth it.
+
+The virtual consoles also have some new screen-handling commands: they
+confirm even better to vt200 control codes than 0.11. Special graphic
+characters etc: you can well use them as terminals to VMS (although
+that's a shameful waste of resources).
+
+	pty's
+
+Ok. I have to admit that I didn't get the hangup-code working correctly,
+but that should be easy to add. The general things are there.
+
+	select
+
+I've never used it, so I cannot say how well it works. My minor testing
+seems to indicate that it works ok. vc's, pty's and select were
+implemented by pmacdona, although I hacked it heavily.
+
+	387-emulation.
+
+It's not complete, but it works well enough to run those gcc2.0 compiled
+programs I tested (few).  None of the "heavy" math-functions are
+implemented yet.
+
+	Symbolic links.
+
+Try out a few "ln -s xx yy", and ls -l. Note that I think tar should be
+recompiled to know anout them, and probably some other programs too. The
+0.12 rootimage-disk has most of the recompiled fileutilities.
+
+	Virtual memory.
+
+In addition to the "mkfs" program, there is now a "mkswap" program on
+the root disk.  The syntax is identical: "mkswap -c /dev/hdX nnn", and
+again: this writes over the partition, so be careful.  Swapping can then
+be enabled by changing the word at offset 506 in the bootimage to the
+desired device.  Use the same program as for setting the root file
+system (but change the 508 offset to 506 of course). 
+
+NOTE! This has been tested by Robert Blum, who has a 2M machine, and it
+allows you to run gcc without much memory.  HOWEVER, I had to stop using
+it, as my diskspace was eaten up by the beta-gcc-2.0, so I'd like to
+hear that it still works: I've been totally unable to make a
+swap-partition for even rudimentary testing since about christmastime. 
+Thus the new changes could possibly just have backfired on the VM, but I
+doubt it. 
+
+	And that's it, I think.
+
+Happy hacking.
+
+			Linus

kernel/Historic/old-versions/RELNOTES-0.95

@@ -0,0 +1,265 @@
+
+
+		RELEASE NOTES FOR LINUX v0.95
+		Linus Torvalds, March 7, 1992
+
+
+This is file mostly contains info on changed features of Linux, and
+using old versions as a help-reference might be a good idea.
+
+
+		COPYRIGHT
+
+Linux-0.95 is NOT public domain software, but is copyrighted by me.  The
+copyright conditions are the same as those imposed by the GNU copyleft:
+get a copy of the GNU copyleft at any major ftp-site (if it carries
+linux, it probably carries a lot of GNU software anyway, and they all
+contain the copyright). 
+
+The copyleft is pretty detailed, but it mostly just means that you may
+freely copy linux for your own use, and redistribute all/parts of it, as
+long as you make source available (not necessarily in the same
+distribution, but you make it clear how people can get it for nothing
+more than copying costs).  Any changes you make that you distribute will
+also automatically fall under the GNU copyleft.
+
+NOTE! The linux unistd library-functions (the low-level interface to
+linux: system calls etc) are excempt from the copyright - you may use
+them as you wish, and using those in your binary files won't mean that
+your files are automatically under the GNU copyleft.  This concerns
+/only/ the unistd-library and those (few) other library functions I have
+written: most of the rest of the library has it's own copyrights (or is
+public domain).  See the library sources for details of those. 
+
+
+		INSTALLATION
+
+This is a SHORT install-note.  The installation is very similar to 0.11
+and 0.12, so you should read INSTALL-0.11 too.  There are a couple of
+programs you will need to install linux: something that writes disk
+images (rawrite.exe or NU or...) and something that can create harddisk
+partitions (fdisk under xenix or older versions of dos, edpart.exe or
+something like that). 
+
+NOTE! Repartitioning your harddisk will destroy all data on it (well,
+not exactly, but if you know enough to get back the data you probably
+didn't need this warning).  So be careful.
+
+READ THIS THROUGH, THEN READ INSTALL-0.11, AND IF YOU ARE SURE YOU KNOW
+WHAT YOU ARE DOING, CONTINUE.  OTHERWISE, PANIC.  OR WRITE ME FOR
+EXPLANATIONS.  OR DO ANYTHING BUT INSTALL LINUX - IT'S VERY SIMPLE, BUT
+IF YOU DON'T KNOW WHAT YOU ARE DOING YOU'LL PROBABLY BE SORRY.  I'D
+RATHER ANSWER A FEW UNNECESSARY MAILS THAN GET MAIL SAYING "YOU KILLED
+MY HARDDISK, BASTARD.  I'M GOING TO FIND YOU, AND YOU'LL BE SORRY WHEN I
+DO". 
+
+Minumum files needed:
+
+	RELNOTES-0.95 (this file)
+	INSTALL-0.11 (+ any other docs you might find: the FAQ etc)
+	bootimage-0.96.Z
+	rootimage-0.95.Z
+	rootimage-0.12.Z  (for tar+compress)
+	rawrite.exe
+	some disk partitioner
+
+1) back up everything you have on your harddisk - linux-0.95 is still in
+   beta and might do weird things.  The only thing I guarantee is that
+   it has worked fine on /my/ machine - for all I know it might eat your
+   harddisk and spit it out in small pieces on any other hardware. 
+
+2) Test out the linux boot-disk with the root file system.  If it
+   doesn't work, check the hardware requirements, and mail me if you
+   still think it should work.  I might not be able to help you, but
+   your bug-report would still be appreciated. 
+
+   Linux-0.95 now has an init/login: there should be 4 logins started on
+   the first 4 virtual consoles.  Log in as root (no password), and test
+   it out.  Change to the other logins by pressing left-alt + FN[1-4]. 
+   Note that booting up with a floppy as root is S..L..O..W..  - the
+   floppy driver has been optimized for sequential access (backups etc),
+   and trashes somewhat with demand-loading. 
+
+   Test that linux can read your harddisk at least partly: run the fdisk
+   program on the root-disk, and see if it barfs.  If it tells you about
+   any partitions at all, linux can successfully read at least part of
+   your harddisk. 
+
+   NOTE! Harddisk device names and numbers have changed between versions
+   0.12 and 0.95: the new numbering system was needed for the extended
+   partitions, and a new naming scheme was in order so that people
+   wouldn't cunfuse the old devices with the new ones.
+
+   The new harddisk device names are: /dev/hd followed by an 'a' for the
+   first drive, or a 'b' for the second one.  After that comes the
+   partition number, 1-4 for the primary partitions, 5- for possible
+   extended partitions.  No number means the complete disk. Like this:
+
+	/dev/hda	the whole first harddisk (old: /dev/hd0)
+	/dev/hdb3	partition nr 3 on the second disk (old: /dev/hd8)
+
+3) Make sure that you have a free /primary/ partition.  There can be 4
+   primary partitions per drive: newer DOS fdisks seem to be able to
+   create only 2 (one primary and one extended).  In that case use some
+   other partitioning software: edpart.exe etc.  Linux fdisk currently
+   only tells you the partition info - it doesn't write to the disk. 
+
+   Remember to check how big your partition was, as that can be used to
+   tell which device Linux thinks it is.
+
+   NOTE! Linux-0.95 /might/ recognize extended partitions: but the code
+   for this is utterly untested, as I don't have any of those.  Do NOT
+   use the extended partitions unless you can verify that they are
+   indeed correctly set up - if my routines are wrong, writing to the
+   extended partitions might just overwrite some other partition
+   instead.  Not nice. 
+
+4) Boot up linux again, fdisk to make sure you now have the new
+   partition, and use mkfs to make a filesystem on one of the partitions
+   fdisk reports.  Write "mkfs -c /dev/hdX nnn" where X is the device
+   number reported by linux fdisk, and nnn is the size - also reported
+   by fdisk.  nnn is the size in /blocks/, ie kilobytes.  You should be
+   able to use the size info to determine which partition is represented
+   by which device name. 
+
+5) Mount the new disk partition: "mount /dev/hdX /mnt".  Copy over the
+   root filesystem to the harddisk, eg like this:
+
+	# for i in bin dev etc usr tmp
+	# do
+	# cp +recursive /$i /mnt
+	# done
+
+   You caanot use just "cp +recursive / /mnt", as that will result in a
+   loop.
+
+6) Sync the filesystem after you have played around enough, and reboot.
+
+	# sync
+	# lo
+
+	(none) login: sync
+	<wait for it to sync>
+	ctrl-alt-del
+
+   THIS IS IMPORTANT! NEVER EVER FORGET TO SYNC BEFORE KILLING THE MACHINE.
+
+7) Change the bootdisk to understand which partition it should use as a
+   root filesystem.  See INSTALL-0.11: it's still the word at offset
+   508 into the image. You should be up and running.
+
+
+8) When you've successfully started up with your harddisk as root, you
+   can mount the older rootimage (rootimage-0.12) from a floppy, and
+   copy over any files you find there that weren't on the newer
+   root-image.
+
+   Mounting a floppy is easy: make the directory /floppy, and write:
+
+	# mount /dev/PS0 /floppy	(if you have a 3.5" drive)
+
+   or
+
+	# mount /dev/at0 /floppy	(for 5.25" floppies)
+
+   After that the files can be copied to your harddisk, eg:
+
+	# cp /floppy/usr/bin/compress /usr/bin
+	# ln -s /usr/bin/compress /usr/bin/compress
+	# cp /floppy/usr/bin/tar.Z /usr/bin
+	# uncompress /usr/bin/tar.Z
+
+That's it. Now go back and read the INSTALL-0.11, until you are sure you
+know what you are doing.
+
+
+		New features of 0.95, in order of appearance
+			(ie in the order you see them)
+
+	Init/login
+
+Yeah, thanks to poe (Peter Orbaeck (sp?)), linux now boots up like a
+real unix with a login-prompt.  Login as root (no passwd), and change
+your /etc/passwd to your hearts delight (and add other logins in
+/etc/inittab etc).
+
+	Bash is even bigger
+
+It's really a bummer to boot up from floppies: bash takes a long time to
+load.  Bash is also now so big that I couldn't fit compress and tar onto
+the root-floppy: You'll probably want the old rootimage-0.12 just in
+order to get tar+compress onto your harddisk.  If anybody has pointers
+to a simple shell that is freely distributable, it might be a good idea
+to use that for the root-diskette.
+
+Especially with a small buffer-cache, things aren't fun. Don't worry:
+linux runs much better on a harddisk.
+
+	Virtual consoles on any (?) hardware.
+
+You can select one of several consoles by pressing the left alt-key and
+a function key at the same time. Linux should report the number of
+virtual consoles available upon bootup. /dev/tty0 is now "the current"
+screen, /dev/tty1 is the main console, and /dev/tty2-8 can exist
+depending on your text-mode or card.
+
+The virtual consoles also have some new screen-handling commands: they
+confirm even better to vt200 control codes than 0.11. Special graphic
+characters etc: you can well use them as terminals to VMS (although
+that's a shameful waste of resources), and the PF1-4 keys work somewhat
+in the application-key mode.
+
+	Symbolic links.
+
+0.95 now allows symlinks to point to other symlinks etc (the maximum
+depth is a rather arbitrary 5 links). 0.12 didn't like more than one
+level of indirection.
+
+	Virtual memory.
+
+VM under 0.95 should be better than under 0.12: no more lockups (as far
+as I have seen), and you can now swap to the filesystem as well as to a
+special partition. There are two programs to handle this: mkswap to set
+up a swap-file/partition and swapon to start up swapping.
+
+mkswap needs either a partition or a file that already exists to make a
+swap-area. To make a swap-file, do this:
+
+	# dd bs=1024 count=NN if=/dev/hda of=swapfile
+	# mkswap swapfile NN
+
+The first command just makes a file that is NN blocks long (initializing
+it from /dev/hda, but that could be anything). The second command then
+writes the necessary setup-info into the file. To start swapping, write
+
+	# swapon swapfile
+
+NOTE! 'dd' isn't on the rootdisk: you have to install some things onto
+the harddisk before you can get up and running. 
+
+NOTE2! When linux runs totally out of virtual memory, things slow down
+dramatically. It tries to keep on running as long as it can, but at
+least it shouldn't lock up any more. ^C should work, although you might
+have to wait a while for it..
+
+	Faster floppies
+
+Ok, you don't notice this much when booting up from a floppy: bash has
+grown, so it takes longer to load, and the optimizations work mostly
+with sequential accesses.  When you start un-taring floppies to get the
+programs onto your harddisk, you'll notice that it's much faster now. 
+That should be about the only use for floppies under a unix: nobody in
+their right mind uses floppies as filesystems.
+
+	Better FS-independence
+
+Hopefully you'll never even notice this, but the filesystem has been
+partly rewritten to make it less minix-fs-specific. I haven't
+implemented all the VFS-patches I got, so it's still not ready, but it's
+getting there, slowly.
+
+	And that's it, I think.
+
+Happy hacking.
+
+			Linus (torvalds@kruuna.helsinki.fi)

kernel/Historic/old-versions/RELNOTES-0.95a

@@ -0,0 +1,148 @@
+Please FIRST read the RELNOTES-0.95 file, then read this.  This is only
+a listing of the differences between this release and the last. [-mkj]
+
+CHANGES IN THE LINUX v0.95a ROOT DISKETTE
+Jim Winstead Jr. - March 17, 1992
+
+This file mostly contains info about the changes in the root diskette
+from Linux v0.95/0.12 to Linux v0.95a.
+
+CHANGES
+
+With the release of Linux v0.95a, the maintenance of the root diskette
+has been assumed by Jim Winstead Jr. (jwinstea@jarthur.Claremont.EDU).
+This means there are a few large changes between the Linux 0.95 and
+0.12 root floppies and the Linux 0.95a root floppy.  These are
+detailed (as much as I remember them) below:
+
+-       'bash' has been replaced with 'ash', the BSD 4.3 /bin/sh.  This
+        freed up nearly 200k on the root floppy.  However, there are
+        some problems with 'ash' that haven't been resolved:
+
+        - sometimes the backspace key will not work on a virtual
+          console.  I've found that it usually works on all _but_ one
+          console, so this is only a minor hinderance.
+
+        - 'ash 'supports BSD-style job control, and this has not yet been
+          adapted to Linux's more POSIXish job control.  This means
+          that 'ash' does not yet support job control, but it's being
+          worked upon.
+
+-       'tar' and 'compress' are back on the root floppy.  'tar' is
+        compressed, and both utilities are in /bin.
+
+-       'pfdisk', a disk partitioner, was added to the root floppy.
+        This makes it (almost) possible to install Linux on a machine
+        without looking at another OS.
+
+-       the file pager 'more' has been added to the floppy.  This was
+        added because of the addition of some documentation files on
+        the root floppy.
+
+-       'cat' has been added to /bin.
+
+-       many utilities have been moved from /usr/bin to /bin, to
+        conform to the Linux Directory Structure Standard (v1.0).
+        These utilities are ones that are 'vital to the restoration of
+        other file systems in the case of a corrupting crash.'
+
+-       'init' and 'update' have been moved to /etc from /bin.  This
+        was done because neither program should be executed from the
+        command line by any user, including root.  (That means don't
+        put /etc in your PATH!)  This has been a matter of some
+        controversy, but this is how it will stand until the Linux
+        Standards mailing list/committee decides otherwise.
+
+-       tty64, tty65, etc, have been renamed to ttys1, ttys2, etc.
+
+-       the directory /INSTALL was added, which contains some
+        documentation, and three simple shell scripts to make
+        installing Linux on a hard drive partition easier.  These are:
+
+        - 'mktree', which makes a directory tree on the specified
+          mounted device.
+        - 'mkdev' which creates the standard devices in the dev
+          directory of the specified mounted device
+        - 'install' which installs the programs on the root diskette
+          to the specified mounted device
+
+        These programs will normally be called with '<name> /mnt'.
+
+-       rootdev is different than the one on v0.95.  A couple of days
+        after the release of 0.95, a program called 'rdev' was posted
+        to alt.os.linux that duplicated and extended the functionality
+        of rootdev.  This was renamed to rootdev and replaces the old
+        rootdev.
+
+-       agetty was renamed to getty, to be consistent with common Unix
+        practice.
+
+-       an improved fdisk was added that correctly reports extended
+        partitions,  (Thanks to Linus!)
+
+-       /dev is complete, or at least more complete than the last few
+        releases of the root diskette, which always seemed to be a
+        major complaint.  :)
+
+-       /etc/issue and /etc/motd have been expanded to be a little
+        more informative.  (Yeah, I know, big deal! :)
+
+-       chgrp was removed.  You can use chown to get the same effect,
+        but you just have to specify an owner, too.
+
+Many of these changes were discussed on alt.os.linux, or the Linux
+Standards group, so they may look familiar.
+
+If you have questions, problems, or complaints about the root
+diskette, either post to alt.os.linux, or send mail to me at
+jwinstea@jarthur.Claremont.EDU. 
+
+If you have questions, problems, or complaints about the boot diskette
+or the kernel itself, post to alt.os.linux or send mail to Linus
+Torvalds at torvalds@cc.helsinki.fi.
+
+Remember, the only stupid questions are the ones you don't ask.
+
+FUTURE CHANGES
+
+I'm already anticipating some changes for the next release, so here's
+a sneak preview:
+
+-       shared libraries.  These are currently in alpha testing, and
+        will hopefully free up some more room on the root floppy for
+        more goodies.
+
+-       a generic mtools might be added to the root floppy.
+
+-       a better fdisk to replace the current fdisk/pfdisk pair.  You
+        won't need to know your drive's geometry for this, and it will
+        know about Linux extended partitions.
+
+-       an improved sh.  I'm working on the backspace problem, and
+        adding job control.  I'm also going to look at using the GNU
+        readline library for input, as long as it doesn't add
+        substantially to the size of sh.
+
+-       init/getty/login may be removed from the root floppy.  The
+        main reason they'll still on there is the backspace problem
+        with ash.
+
+-       improved installation documentation.  People have started work
+        on this already - read alt.os.linux for previews.
+
+-       more robust installation scripts.  The current ones are quick
+        and dirty, and work well, but I'd like to add better ones.
+
+-       miscellaneous utilities added.  I'd really like to add an
+        editor to the root disk, but I haven't found one small enough.
+        Any suggestions?
+
+-       various other things that I can't remember right now.
+
+Again, mail your questions, comments and suggestions about the root
+diskette to me at jwinstea@jarthur.Claremont.EDU.
+-- 
+Jim Winstead Jr. (CSci '95)    | "Catch a fish!"
+Harvey Mudd College            |  -Geddy Lee,
+jwinstea@jarthur.Claremont.EDU |   San Diego Sports Arena
+Disclaimer: Mine, not theirs!  |   January 20, 1992

kernel/Historic/old-versions/RELNOTES-0.97

@@ -0,0 +1,75 @@
+Changes in 0.97:
+
+ - The VESA-support was removed.  I'd be happy to put it back once it
+   works on all hardware.  Instead of the VESA-code, I finally put in
+   the automatic SVGA setup patches.  See the top-level Makefile. 
+
+ - The IRQ code has solidified, and should work on all machines.  Not
+   all of the SCSI drivers use it yet, so I expect patches for that.. 
+
+ - Serial interrupts are handled slightly differently, and performance
+   should be up.  I've sent out a few alpha-releases, and testing seems
+   to indicate that's actually true this time.  Reactions have ranged
+   from "nice" to "wonderful" :-)
+
+ - The buffer-cache and memory management code has been edited quite a
+   bit.  ps/free etc programs that reads kernel memory directly no
+   longer work, and even a recompilation won't be enough.  They actually
+   need editing before they work. 
+
+   The buffer-cache now grows and shrinks dynamically depending on how
+   much free memory there is.  Shift+PrintScreen will give some memory
+   statistics.  (Ctrl+PrSc gives task-info, ALT+PrSc gives current
+   register values). 
+
+   The mm code changes removed some race-conditions in the VM code, and
+   I also tried to make the Out-of-swapspace error less severe (better
+   thrashing-detection etc).
+
+ - The super-block code has been cleaned up.  Especially the extended fs
+   needs to be edited a bit to take advantage of the new setup, and I
+   expect Remy Card will have a patch out eventually. 
+
+ - include-files have been moved around some more: there are still some
+   names that clash with the standard headers, but not many. 
+
+ - Unswappable processes implemented: by default only 'init' is
+   unswappable.  This is a bit safer in low-memory conditions, as at
+   least init won't die due to low memory.  I also made killing init
+   impossible: if init doesn't recognize a signal, it simply won't get
+   it.  Some other changes ("while (1) fork();" won't kill the machine
+   for non-root users etc)
+
+ - The new SCSI drivers are in.  These make the kernel noticeably
+   bigger, but you can leave them out if you don't want them.
+
+ - The floppy- and hd-drivers print out more debugging-info in case of
+   errors: this might be irritating if you have hardware that works, but
+   often gives soft-errors.  On the other hand, some old debugging-info
+   was removed - notably for user-level protection errors etc. 
+
+ - Various minor fixes.  I haven't made cdiffs (and I haven't gotten any
+   requests for them, so I probably never will), but they would be
+   pretty big. 
+
+Things that I didn't have time for:
+
+ - I wanted to rewrite the tty drivers to be more "streams-like" (ie not
+   an actual streams-implementation, but some of the ideas from
+   streams).  I never got around to it: there was simply too much else
+   to do. 
+
+ - I got a lot of patches, and some went in, others didn't.  If you
+   think your patch was important, please re-send it relative to the new
+   version.
+
+I'd like comments on the new system: performance / clarity of code etc. 
+0.97 should correct all known bugs (at least the ones I know about), but
+I guess that's just wishful thinking. 
+
+Note that the dynamic buffer-code also handles differently-sized
+buffers, but that the rest of the system (block device drivers,
+filesystem code etc) cannot yet take advantage of this - there is still
+some coding needed. 
+
+		Linus

kernel/Historic/old-versions/impure/linux-0.11.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfxyGugalF9Dw4RAq8hAJ0cS3g7U74kca3oQhWAiqsQmPd7bQCghJPD
+KmPbu7j9voD47NlxVSafG2g=
+=sloi
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/impure/linux-0.11.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfxyGugalF9Dw4RAk3tAJ9DodkF35xtv5ZcldjSWEUpZywT9ACfSYS3
++2f+epG+81mY0UaQ89iV2Q0=
+=4Cph
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/impure/linux-0.11.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLHyGugalF9Dw4RAhV3AJsGANBdjpLEIa6Wr4bXaYsFYwNjRgCfUePq
+A1atohMQb553mcb91Wnpp6A=
+=fgel
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/impure/linux-0.12.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfxyGugalF9Dw4RAryDAJsHHPPb4YyFwAm6fc5imYYkNSSC7ACeJN0w
+h+7H98HPdZPQ4SydDGw1ll0=
+=dKU7
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/impure/linux-0.12.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfxyGugalF9Dw4RAkNRAKCS6WirGqMA4bGI25lqZ/va10fOZACeMO4W
+1p/+5zPViLGPUvD9MYHMw14=
+=MJ6n
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/impure/linux-0.12.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLHyGugalF9Dw4RAppBAJ9UDCLPys98H/wK18ByaN5yyXQDbQCfRsxY
+djE3+UFdt7qbdQQWV9XcS88=
+=wi8Q
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/impure/linux-0.95c.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfwyGugalF9Dw4RAnsxAJ9/6iAmioS47mLdojpRRhJpUEnmTACfZF1b
+h+tVsx+793Y2kSLBX2Ryfzo=
+=hh1O
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/impure/linux-0.95c.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfwyGugalF9Dw4RAmDXAJ4uIfbZfNQ3kz3BUgVaL4GPLd63AgCff1xB
+pBCoMVtC/4s1CzuES+RtnmU=
+=cIGL
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/impure/linux-0.95c.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLHyGugalF9Dw4RAga1AJoCKmGVM6eCbw0yQAeXA9GkwF0GcwCfXei4
+5gsqO/Hr4G1CVzV1HBvnc9Y=
+=02pz
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.11.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfyyGugalF9Dw4RAgRJAJ94tY3f7Oo10tDvpWgcKggvy3BseACdGmbP
+5KBxTc/By3zzHlnA4ia6J9U=
+=TyO6
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.11.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfyyGugalF9Dw4RAiK1AJwO9fD82BasA3HIiHNEFhGRRNZdbgCfa/rY
+kGDmKQ16lCyLanQsoVovRTw=
+=fPZ9
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.11.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLIyGugalF9Dw4RAsQEAJ9/givvJj6X/awIv+K4nPA39kbbCwCcDh3i
+mjyUKwW9SIoXeOQ+w/Zub04=
+=vlms
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.12.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfyyGugalF9Dw4RAsdMAJ4+Y8J5BihshA25vGFtCp4aYg8SVwCfUkF9
+sTNGMmV4WVbEQ7WZdOSZhv0=
+=g12J
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.12.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfyyGugalF9Dw4RAqjSAKCDCmQ644kZi+9LzxgLbhNcPsmJzQCeK1ic
+SXNYni5DRzsN7Kh6XkMqPAg=
+=SfxW
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.12.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLIyGugalF9Dw4RAlQ/AJ4g5ub4aJW2EOK12zvEn72ZjmNBEQCfVB+S
+xPYNNAAiqWkGlPxineYyKgI=
+=52Gj
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.95.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rf0yGugalF9Dw4RAvXTAJ4zZ7VSRsfeHaKsrUFZSCz2jL+FVQCcDEYM
+JEO7fv2MEAZ+j3ULjmMnu+c=
+=DUdZ
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.95.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rf0yGugalF9Dw4RAutOAJ9gyVDrN29V+KrQ8yo6CQdMTq6XFgCffq5P
+v5IDQOvL/wKKESgJETCetJs=
+=VhAz
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.95.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLJyGugalF9Dw4RAjlTAKCGRO1rMNAv2WLnUfDcrq2ZtwyCogCcDZGY
+ttc55w2r9WEyrGQ4WAYnxPA=
+=fE1n
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.95a.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rf0yGugalF9Dw4RAgMSAJ40K0V7umMcrPFPlKvR5ZPVjnQYWACff1Np
+xOKli+G43Of0gJOHgxpTg8A=
+=RLiV
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.95a.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rf0yGugalF9Dw4RAmotAJ9P+1AHSltEKC7R4cHwW/qzwWIV7wCeJja3
+JDPcAFn25KKQo2uyi8Eyauo=
+=G9cK
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.95a.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLJyGugalF9Dw4RAgt5AJ9cN2JvOvZOYkJOkiwoUilV8h3oigCfSFGs
+TzkfkhMbLTGKRr3/R5qTcWI=
+=NN4b
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96a.patch2.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rf0yGugalF9Dw4RAr/qAJ4nVh1pspLj1vHSsQGe/qYQiUhgywCdGbuU
+DHbIoDQMVLmkqjs0Df+jD2I=
+=D7NJ
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96a.patch2.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rf0yGugalF9Dw4RAohXAJ0euzgZwdxB18V3D+1qf/epUYQPXwCePYCe
+OQGw5CupnNGDvPS1DAEez2o=
+=IB0E
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96a.patch2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLJyGugalF9Dw4RAqunAJ4h675FxDkZb7nEmHLhxmp6Pv2xGwCeP+VD
+ha5p9n9/j6oRfVOpfGJpoqU=
+=ENNx
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96a.patch3.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfzyGugalF9Dw4RAnn2AKCI6esY78SCmRnmHo23E0Wviyhz4wCcCXf6
+n2RfJiNmGCLaFqcCBEqo95A=
+=h2Cj
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96a.patch3.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfzyGugalF9Dw4RAgCUAJ9c5ztqcv9/F8MJ0OYvdgNlrVVYqACfYI1u
+DvZVbU5SVJSdWGCh9+yOGz8=
+=rb+3
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96a.patch3.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLJyGugalF9Dw4RAq6JAJ9anw1mRmy3/8ebtC2hAIyH3eRLxQCfdg2R
+VwEoFa119A2xE/dlwHPIoOw=
+=DSsl
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96a.patch4.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfzyGugalF9Dw4RAriNAKCUSCNWetKvopVZ5vR4buBLrt1RgwCeIRsO
+AZwaD0EmSBw2fp8ZCgEiyWM=
+=8VvK
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96a.patch4.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfzyGugalF9Dw4RAi9tAKCHfWSHJgzxP9LNBoNHOlNnGMOYMACeK8hg
+ys3jmHlEZGkFE0e2kfU47Vo=
+=mHCt
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96a.patch4.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLJyGugalF9Dw4RAoa+AJ41QH9Ilxok4ohyQ22+OOZB6LgYnwCfb1df
+yL04KwwdO03JpxZPWbVsKSk=
+=r3xI
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96a.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfyyGugalF9Dw4RAkQzAJ90wqlWjO0vpB0kuLXl3d0AHWE4CgCeKmLH
+KcHPIBclEHkKkNHdCXc0kQc=
+=iyFd
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96a.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfxyGugalF9Dw4RAv9/AJ4k2aJr2Q+G9Nkejj2Pks5cFxejAACfSDYq
+w4JAkXqaLDKsPRMMqsmXaXY=
+=sTt3
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96a.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLJyGugalF9Dw4RAs2JAJ90wOlHj+uf7aVS2E8TLwTWBT42HwCghSiG
+FpR3161vKSRMtQVyYK14+2E=
+=D2CE
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96b.patch1.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rf0yGugalF9Dw4RAmf9AJ41kyu/1wzPs3Sjz0KJAYy8hHrdIwCfRB8b
+29mp+j5hsEV986Kcu64ydVY=
+=EeM1
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96b.patch1.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfzyGugalF9Dw4RApZzAKCQlkBZj2z6r+TQ6wELS3bKTkGIBgCfZwlP
+6u7oODCQE4jLUf4MyErmH6E=
+=JyKh
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96b.patch1.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLJyGugalF9Dw4RAgeQAKCJV1vWyVcdH3XSlIHgKVmNR02dLACfYdzK
+ACvdB0TzY2glZjTd+q/ClB4=
+=2vpP
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96b.patch2.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfzyGugalF9Dw4RAozrAJ44FNxssyTOgruu2VatdRLIh6+p7gCfRaDC
+YMvbMeSfnT7Fs8c2/oB2SOI=
+=f6cj
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96b.patch2.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfzyGugalF9Dw4RAkSGAKCFNWaJY5cuS4YwfPat3Zi7NES2jgCfZGyf
+3MZ4Z1a+1E8LfMXxlw4sn9A=
+=wdgO
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96b.patch2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLKyGugalF9Dw4RAqKgAJoDoHiM3PsMTSaiKyCL2Ph+Eo4dugCgi+Pv
+t+SlOE7KcT+Lu7zZjIdd/9E=
+=3rsI
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96b.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfzyGugalF9Dw4RAl5XAJ4+zugYxhoTB8tqPcNNiz8nGEy9cACfYvUz
+saBdKilyuCy/7zyeAPgxmqk=
+=CpFW
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96b.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfyyGugalF9Dw4RAhumAJ909b0dcAF75RB/Uw9eLIHMPviiVQCfdNBJ
+vAUEiVOy2r3qBmNNO9zaW7I=
+=aEdO
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96b.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLKyGugalF9Dw4RArjkAJ47qIYDTahmK73inJDiDp2oRUY5nACdEaHg
+N80Iz+x5Ik9NN3l0PpD8+Vs=
+=g5UO
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96c.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfyyGugalF9Dw4RAusRAJ9YfCqW49SuUFV858gnVkO0RAS5aACfZn1B
+oh6ybQxRajMrpRkI1yErhVw=
+=RFfo
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96c.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfyyGugalF9Dw4RAqLaAJ9HxqjdjqoFTvwud+BvBrQRnSRSsgCfXPjY
+1h/G9q2ZbyGFQrmpyR61IOI=
+=6r40
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/linux-0.96c.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLKyGugalF9Dw4RAkIsAJwPM9MeqT+/37nw1wZbhvqnRUU/xACggy9F
+TEwuLzJvvz7xtt4OjOWNIhY=
+=3Ij8
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/old/corrupt/linux-0.95c.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfvyGugalF9Dw4RAsmQAJ9V0VYMfaJg0L+Efz4TjVjSwlDpZwCfdq85
+gfBilkYC1hkViDL3eVhrq/k=
+=1Piy
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/old/corrupt/linux-0.95c.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfvyGugalF9Dw4RAigVAJ9rC6C7YVSirBYF4Xqq4WFF3L2KwgCcCgBb
+Ba9jj+YiwRtWurJfm7AznuI=
+=S4g3
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/old/corrupt/linux-0.95c.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLHyGugalF9Dw4RAlztAJsHStgOdrfcb3+YINQ+gNFr31DjaACgk5AF
+zDi0jEl8UXEf0HB6FE0vRzU=
+=BBdC
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/old/corrupt/linux-0.97.5.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfuyGugalF9Dw4RAtNtAJ0TWeaSVoDGJ3cx3icKUcyIikA5ggCfayR8
+qpeRc8sbck0CTP0euWdNXLM=
+=iPUK
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/old/corrupt/linux-0.97.5.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfuyGugalF9Dw4RAjpoAJ9bAfXZbcfWzpDecP5cjON/qCVDcQCfc3vl
+7qelyY+ofDxfTP7gbuHf46o=
+=e14z
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/old/corrupt/linux-0.97.5.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLHyGugalF9Dw4RAqmQAJ0aa22oqC8p7Sy3nm7LzRYOqa8rdACeO/Dz
+FgN+Vz4AlHBwQ+0Ra+bENTM=
+=2vhb
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/old/linux-0.95a.tar.bz2.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfwyGugalF9Dw4RAkybAJ95lZBk+f+trY5gOEt6hOuGCPFOBQCgkdG8
+KVYsGf/jr4eJSiin2Kwrh3A=
+=nRAJ
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/old/linux-0.95a.tar.gz.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.0 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA54rfwyGugalF9Dw4RAlU2AKCNgfvOOvg6P/FuvofUFCne8nluMACfasgJ
+h2R7KT86FEAi35PU29kkD0o=
+=k1Xf
+-----END PGP SIGNATURE-----

kernel/Historic/old-versions/old/linux-0.95a.tar.sign

@@ -0,0 +1,8 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.0.6 (GNU/Linux)
+Comment: See http://www.kernel.org/signature.html for info
+
+iD8DBQA+ekLHyGugalF9Dw4RAs7jAJ92tBoKTu+u3S3PBK3Kg6H2NFfgfgCgiYJ4
+o3oIkb4WeKm/y4Q4MxoWC+g=
+=TEwb
+-----END PGP SIGNATURE-----