OSCL-LXR

Linux kernel
There are several guides for kernel developers and users. These guides can be rendered in a number of formats, like HTML and PDF. Please read Documentation/admin-guide/README.rst first.
In order to build the documentation, use ``make htmldocs`` or ``make pdfdocs``. The formatted documentation can also be read online at:
https://www.kernel.org/doc/html/latest/
There are various text files in the Documentation/ subdirectory, several of them using the Restructured Text markup notation.
Please read the Documentation/process/changes.rst file, as it contains the requirements for building and running the kernel, and information about the problems which may result by upgrading your kernel.

Notes on Filesystem Layout
These notes describe what mkcramfs generates. Kernel requirements are a bit looser, e.g. it doesn't care if the <file_data> items are swapped around (though it does care that directory entries (inodes) in a given directory are contiguous, as this is used by readdir).
All data is currently in host-endian format; neither mkcramfs nor the kernel ever do swabbing. (See section `Block Size' below.)

SEE ALSO: README

This is a snapshot of the QNX4 filesystem for Linux. Please send diffs and remarks to <alarsen.net">al@alarsen.net> .
Credits :
Richard "Scuba" A. Frowijn <wxs.nl">scuba@wxs.nl> Frank "Jedi/Sector One" Denis <pureftpd.org">j@pureftpd.org> Anders Larsen <alarsen.net">al@alarsen.net> (Maintainer)

This is a snapshot of the QNX6 filesystem for Linux. Please send diffs and remarks to <ontika.net">chaosman@ontika.net> .
Credits :
Al Viro <ZenIV.linux.org.uk">viro@ZenIV.linux.org.uk> (endless patience with me & support ;)) Kai Bankett <ontika.net">chaosman@ontika.net> (Maintainer)

[LICENSING]
ReiserFS is hereby licensed under the GNU General Public License version 2.
Source code files that contain the phrase "licensing governed by reiserfs/README" are "governed files" throughout this file. Governed files are licensed under the GPL. The portions of them owned by Hans Reiser, or authorized to be licensed by him, have been in the past, and likely will be in the future, licensed to other parties under other licenses. If you add your code to governed files, and don't want it to be owned by Hans Reiser, put your copyright label on that code so the poor blight and his customers can keep things straight. All portions of governed files not labeled otherwise are owned by Hans Reiser, and by adding your code to it, widely distributing it to others or sending us a patch, and leaving the sentence in stating that licensing is governed by the statement in this file, you accept this. It will be a kindness if you identify whether Hans Reiser is allowed to license code labeled as owned by you on your behalf other than under the GPL, because he wants to know if it is okay to do so and put a check in the mail to you (for non-trivial improvements) when he makes his next sale. He makes no guarantees as to the amount if any, though he feels motivated to motivate contributors, and you can surely discuss this with him before or after contributing. You have the right to decline to allow him to license your code contribution other than under the GPL.

SEE ALSO: README