README 7.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161
  1. [LICENSING]
  2. ReiserFS is hereby licensed under the GNU General
  3. Public License version 2.
  4. Source code files that contain the phrase "licensing governed by
  5. reiserfs/README" are "governed files" throughout this file. Governed
  6. files are licensed under the GPL. The portions of them owned by Hans
  7. Reiser, or authorized to be licensed by him, have been in the past,
  8. and likely will be in the future, licensed to other parties under
  9. other licenses. If you add your code to governed files, and don't
  10. want it to be owned by Hans Reiser, put your copyright label on that
  11. code so the poor blight and his customers can keep things straight.
  12. All portions of governed files not labeled otherwise are owned by Hans
  13. Reiser, and by adding your code to it, widely distributing it to
  14. others or sending us a patch, and leaving the sentence in stating that
  15. licensing is governed by the statement in this file, you accept this.
  16. It will be a kindness if you identify whether Hans Reiser is allowed
  17. to license code labeled as owned by you on your behalf other than
  18. under the GPL, because he wants to know if it is okay to do so and put
  19. a check in the mail to you (for non-trivial improvements) when he
  20. makes his next sale. He makes no guarantees as to the amount if any,
  21. though he feels motivated to motivate contributors, and you can surely
  22. discuss this with him before or after contributing. You have the
  23. right to decline to allow him to license your code contribution other
  24. than under the GPL.
  25. Further licensing options are available for commercial and/or other
  26. interests directly from Hans Reiser: hans@reiser.to. If you interpret
  27. the GPL as not allowing those additional licensing options, you read
  28. it wrongly, and Richard Stallman agrees with me, when carefully read
  29. you can see that those restrictions on additional terms do not apply
  30. to the owner of the copyright, and my interpretation of this shall
  31. govern for this license.
  32. Finally, nothing in this license shall be interpreted to allow you to
  33. fail to fairly credit me, or to remove my credits, without my
  34. permission, unless you are an end user not redistributing to others.
  35. If you have doubts about how to properly do that, or about what is
  36. fair, ask. (Last I spoke with him Richard was contemplating how best
  37. to address the fair crediting issue in the next GPL version.)
  38. [END LICENSING]
  39. Reiserfs is a file system based on balanced tree algorithms, which is
  40. described at http://devlinux.com/namesys.
  41. Stop reading here. Go there, then return.
  42. Send bug reports to yura@namesys.botik.ru.
  43. mkreiserfs and other utilities are in reiserfs/utils, or wherever your
  44. Linux provider put them. There is some disagreement about how useful
  45. it is for users to get their fsck and mkreiserfs out of sync with the
  46. version of reiserfs that is in their kernel, with many important
  47. distributors wanting them out of sync.:-) Please try to remember to
  48. recompile and reinstall fsck and mkreiserfs with every update of
  49. reiserfs, this is a common source of confusion. Note that some of the
  50. utilities cannot be compiled without accessing the balancing code
  51. which is in the kernel code, and relocating the utilities may require
  52. you to specify where that code can be found.
  53. Yes, if you update your reiserfs kernel module you do have to
  54. recompile your kernel, most of the time. The errors you get will be
  55. quite cryptic if your forget to do so.
  56. Real users, as opposed to folks who want to hack and then understand
  57. what went wrong, will want REISERFS_CHECK off.
  58. Hideous Commercial Pitch: Spread your development costs across other OS
  59. vendors. Select from the best in the world, not the best in your
  60. building, by buying from third party OS component suppliers. Leverage
  61. the software component development power of the internet. Be the most
  62. aggressive in taking advantage of the commercial possibilities of
  63. decentralized internet development, and add value through your branded
  64. integration that you sell as an operating system. Let your competitors
  65. be the ones to compete against the entire internet by themselves. Be
  66. hip, get with the new economic trend, before your competitors do. Send
  67. email to hans@reiser.to.
  68. To understand the code, after reading the website, start reading the
  69. code by reading reiserfs_fs.h first.
  70. Hans Reiser was the project initiator, primary architect, source of all
  71. funding for the first 5.5 years, and one of the programmers. He owns
  72. the copyright.
  73. Vladimir Saveljev was one of the programmers, and he worked long hours
  74. writing the cleanest code. He always made the effort to be the best he
  75. could be, and to make his code the best that it could be. What resulted
  76. was quite remarkable. I don't think that money can ever motivate someone
  77. to work the way he did, he is one of the most selfless men I know.
  78. Yura helps with benchmarking, coding hashes, and block pre-allocation
  79. code.
  80. Anatoly Pinchuk is a former member of our team who worked closely with
  81. Vladimir throughout the project's development. He wrote a quite
  82. substantial portion of the total code. He realized that there was a
  83. space problem with packing tails of files for files larger than a node
  84. that start on a node aligned boundary (there are reasons to want to node
  85. align files), and he invented and implemented indirect items and
  86. unformatted nodes as the solution.
  87. Konstantin Shvachko, with the help of the Russian version of a VC,
  88. tried to put me in a position where I was forced into giving control
  89. of the project to him. (Fortunately, as the person paying the money
  90. for all salaries from my dayjob I owned all copyrights, and you can't
  91. really force takeovers of sole proprietorships.) This was something
  92. curious, because he never really understood the value of our project,
  93. why we should do what we do, or why innovation was possible in
  94. general, but he was sure that he ought to be controlling it. Every
  95. innovation had to be forced past him while he was with us. He added
  96. two years to the time required to complete reiserfs, and was a net
  97. loss for me. Mikhail Gilula was a brilliant innovator who also left
  98. in a destructive way that erased the value of his contributions, and
  99. that he was shown much generosity just makes it more painful.
  100. Grigory Zaigralin was an extremely effective system administrator for
  101. our group.
  102. Igor Krasheninnikov was wonderful at hardware procurement, repair, and
  103. network installation.
  104. Jeremy Fitzhardinge wrote the teahash.c code, and he gives credit to a
  105. textbook he got the algorithm from in the code. Note that his analysis
  106. of how we could use the hashing code in making 32 bit NFS cookies work
  107. was probably more important than the actual algorithm. Colin Plumb also
  108. contributed to it.
  109. Chris Mason dived right into our code, and in just a few months produced
  110. the journaling code that dramatically increased the value of ReiserFS.
  111. He is just an amazing programmer.
  112. Igor Zagorovsky is writing much of the new item handler and extent code
  113. for our next major release.
  114. Alexander Zarochentcev (sometimes known as zam, or sasha), wrote the
  115. resizer, and is hard at work on implementing allocate on flush. SGI
  116. implemented allocate on flush before us for XFS, and generously took
  117. the time to convince me we should do it also. They are great people,
  118. and a great company.
  119. Yuri Shevchuk and Nikita Danilov are doing squid cache optimization.
  120. Vitaly Fertman is doing fsck.
  121. Jeff Mahoney, of SuSE, contributed a few cleanup fixes, most notably
  122. the endian safe patches which allow ReiserFS to run on any platform
  123. supported by the Linux kernel.
  124. SuSE, IntegratedLinux.com, Ecila, MP3.com, bigstorage.com, and the
  125. Alpha PC Company made it possible for me to not have a day job
  126. anymore, and to dramatically increase our staffing. Ecila funded
  127. hypertext feature development, MP3.com funded journaling, SuSE funded
  128. core development, IntegratedLinux.com funded squid web cache
  129. appliances, bigstorage.com funded HSM, and the alpha PC company funded
  130. the alpha port. Many of these tasks were helped by sponsors other
  131. than the ones just named. SuSE has helped in much more than just
  132. funding....