Hi!

	To build:
		ln -sf <patched-kernel-dir>/include/linux/oopser.h oopser.h
		make

	This is the basic example of an in-kernel symbolic oopser.
You can load the module and run setup-oopser (as root) to test it out.
To force an oops, you can use ./oopsd --test.  You will usually need
to reboot to read the changes in the dump file.

	Currently, only x86 is supported, with ATA LBA-supporting
drives.  You can dump to a partition or a file.

eg:
	# modprobe oopser_dev
	# ./setup-oopser /boot/System.map-exp test_dump
	Feeding in symbols from /boot/System.map-exp...
	Ignoring symbol .text.lock.process
	<...>
	Done.
	# ./oopsd --test
	Segmentation fault
	# reboot
	...
	# cat test_dump

TODO:
	1...N) Grep for FIXME
	N+1) Include encoded System.map inside module
	N+2) --del-symbols and hooks for modules.
	N+3) Other architectures
	N+4) Non-IDE support (eg. nvram, scsi).
	N+5) Get someone who knows IDE to do check the IDE code
	N+6) Prepend a huffman decode table to each symbol table.
	...
	N+X) Create the Oops Team mentioned in the mail
	N+X+1) All the backend processing for these things
