152 lines · plain
1[LICENSING]2 3ReiserFS is hereby licensed under the GNU General4Public License version 2.5 6Source code files that contain the phrase "licensing governed by7reiserfs/README" are "governed files" throughout this file. Governed8files are licensed under the GPL. The portions of them owned by Hans9Reiser, or authorized to be licensed by him, have been in the past,10and likely will be in the future, licensed to other parties under11other licenses. If you add your code to governed files, and don't12want it to be owned by Hans Reiser, put your copyright label on that13code so the poor blight and his customers can keep things straight.14All portions of governed files not labeled otherwise are owned by Hans15Reiser, and by adding your code to it, widely distributing it to16others or sending us a patch, and leaving the sentence in stating that17licensing is governed by the statement in this file, you accept this.18It will be a kindness if you identify whether Hans Reiser is allowed19to license code labeled as owned by you on your behalf other than20under the GPL, because he wants to know if it is okay to do so and put21a check in the mail to you (for non-trivial improvements) when he22makes his next sale. He makes no guarantees as to the amount if any,23though he feels motivated to motivate contributors, and you can surely24discuss this with him before or after contributing. You have the25right to decline to allow him to license your code contribution other26than under the GPL.27 28Further licensing options are available for commercial and/or other29interests directly from Hans Reiser: hans@reiser.to. If you interpret30the GPL as not allowing those additional licensing options, you read31it wrongly, and Richard Stallman agrees with me, when carefully read32you can see that those restrictions on additional terms do not apply33to the owner of the copyright, and my interpretation of this shall34govern for this license.35 36Finally, nothing in this license shall be interpreted to allow you to37fail to fairly credit me, or to remove my credits, without my38permission, unless you are an end user not redistributing to others.39If you have doubts about how to properly do that, or about what is40fair, ask. (Last I spoke with him Richard was contemplating how best41to address the fair crediting issue in the next GPL version.)42 43[END LICENSING]44 45Reiserfs is a file system based on balanced tree algorithms, which is46described at https://reiser4.wiki.kernel.org/index.php/Main_Page 47 48Stop reading here. Go there, then return.49 50Send bug reports to yura@namesys.botik.ru.51 52mkreiserfs and other utilities are in reiserfs/utils, or wherever your53Linux provider put them. There is some disagreement about how useful54it is for users to get their fsck and mkreiserfs out of sync with the55version of reiserfs that is in their kernel, with many important56distributors wanting them out of sync.:-) Please try to remember to57recompile and reinstall fsck and mkreiserfs with every update of58reiserfs, this is a common source of confusion. Note that some of the59utilities cannot be compiled without accessing the balancing code60which is in the kernel code, and relocating the utilities may require61you to specify where that code can be found.62 63Yes, if you update your reiserfs kernel module you do have to64recompile your kernel, most of the time. The errors you get will be65quite cryptic if your forget to do so.66 67Real users, as opposed to folks who want to hack and then understand68what went wrong, will want REISERFS_CHECK off.69 70Hideous Commercial Pitch: Spread your development costs across other OS71vendors. Select from the best in the world, not the best in your72building, by buying from third party OS component suppliers. Leverage73the software component development power of the internet. Be the most74aggressive in taking advantage of the commercial possibilities of75decentralized internet development, and add value through your branded76integration that you sell as an operating system. Let your competitors77be the ones to compete against the entire internet by themselves. Be78hip, get with the new economic trend, before your competitors do. Send79email to hans@reiser.to.80 81To understand the code, after reading the website, start reading the82code by reading reiserfs_fs.h first.83 84Hans Reiser was the project initiator, primary architect, source of all85funding for the first 5.5 years, and one of the programmers. He owns86the copyright.87 88Vladimir Saveljev was one of the programmers, and he worked long hours89writing the cleanest code. He always made the effort to be the best he90could be, and to make his code the best that it could be. What resulted91was quite remarkable. I don't think that money can ever motivate someone92to work the way he did, he is one of the most selfless men I know.93 94Yura helps with benchmarking, coding hashes, and block pre-allocation95code.96 97Anatoly Pinchuk is a former member of our team who worked closely with98Vladimir throughout the project's development. He wrote a quite99substantial portion of the total code. He realized that there was a100space problem with packing tails of files for files larger than a node101that start on a node aligned boundary (there are reasons to want to node102align files), and he invented and implemented indirect items and103unformatted nodes as the solution.104 105Konstantin Shvachko was taking part in the early days.106 107Mikhail Gilula was a brilliant innovator that has shown much generosity.108 109Grigory Zaigralin was an extremely effective system administrator for110our group.111 112Igor Krasheninnikov was wonderful at hardware procurement, repair, and113network installation.114 115Jeremy Fitzhardinge wrote the teahash.c code, and he gives credit to a116textbook he got the algorithm from in the code. Note that his analysis117of how we could use the hashing code in making 32 bit NFS cookies work118was probably more important than the actual algorithm. Colin Plumb also119contributed to it.120 121Chris Mason dived right into our code, and in just a few months produced122the journaling code that dramatically increased the value of ReiserFS.123He is just an amazing programmer.124 125Igor Zagorovsky is writing much of the new item handler and extent code126for our next major release.127 128Alexander Zarochentcev (sometimes known as zam, or sasha), wrote the129resizer, and is hard at work on implementing allocate on flush. SGI130implemented allocate on flush before us for XFS, and generously took131the time to convince me we should do it also. They are great people,132and a great company.133 134Yuri Shevchuk and Nikita Danilov are doing squid cache optimization.135 136Vitaly Fertman is doing fsck.137 138Jeff Mahoney, of SuSE, contributed a few cleanup fixes, most notably139the endian safe patches which allow ReiserFS to run on any platform140supported by the Linux kernel.141 142SuSE, IntegratedLinux.com, Ecila, MP3.com, bigstorage.com, and the143Alpha PC Company made it possible for me to not have a day job144anymore, and to dramatically increase our staffing. Ecila funded145hypertext feature development, MP3.com funded journaling, SuSE funded146core development, IntegratedLinux.com funded squid web cache147appliances, bigstorage.com funded HSM, and the alpha PC company funded148the alpha port. Many of these tasks were helped by sponsors other149than the ones just named. SuSE has helped in much more than just150funding....151 152