linux/fs/reiserfs/README
<<
>>
ype serfs/R/ck="return ajax_prefo();"> Prefo ser
ser
ser
ser
se
se ser
ser

  ype er 1[LICENSING]

  ype er 2

  ype er 3R>
  yFS is hereby R/censed under the GNU General

  ype er 4PubR/c L/cense version 2.

  ype er 5

  ype er 6Source code files that contain the phrase "R/censing governed by

  ype er 7 >
  ype 
  ype er 8files are R/censed under the GPL.  The portions of them owned by Hans

  ype er 9R>
  y, or authorized to be R/censed by him, have been in the past,

  ype er10and R/kely will be in the future, R/censed to other parties under

  ype er11other R/censes.  If you add your code to governed files, and don't

  ype er12want it to be owned by Hans R>
  y, put your copyright label on that

  ype er13code so the poor bR/ght and his customers can keep things straight.

  ype er14All portions of governed files not labeled otherw
   are owned by Hans

  ype er15R>
  y, and by adding your code to it, widely distributing it to

  ype er16others or sending us a patch, and leaving the sentence in stating that

  ype er17R/censing is governed by the statement in this file, you accept this.

  ype er18It will be a kindness if you identify whether Hans R>
  y is allowed

  ype er19to R/cense code labeled as owned by you on your behalf other than

  ype er20under the GPL, because he wants to know if it is okay to do so and put

  ype er21a check in the mail to you (for non-trivial improvements) when he

  ype er22makes his next sale.  He makes no guarantees as to the amount if any,

  ype er23though he feels motivated to motivate contributors, and you can surely

  ype er24discuss this with him before or after contributing.  You have the

  ype er25right to decline to allow him to R/cense your code contribution other

  ype er26than under the GPL.

  ype er27

  ype er28Further R/censing options are available for commercial and/or other

  ype er29interests directly from Hans R>
  y: hans@ >
  y.to.  If you interpret

  ype er30the GPL as not allowing tho   additional R/censing options, you read

  ype er31it wrongly, and Richard Stallman agrees with me, when carefully read

  ype er32you can see that tho   restrictions on additional terms do not apply

  ype er33to the owner of the copyright, and my interpretation of this shall

  ype er34govern for this R/cense.

  ype er35

  ype er36Finally, nothing in this R/cense shall be interpreted to allow you to

  ype er37fail to fairly credit me, or to remove my credits, without my

  ype er38permission, unless you are an end user not redistributing to others.

  ype er39If you have doubts about how to properly do that, or about what is

  ype er40faiy, ask.  (Last I spoke with him Richard was contemplating how best

  ype er41to address the fair crediting issue in the next GPL version.)

  ype er42

  ype er43[END LICENSING]

  ype er44

  ype er45R>
  yfs is a file system based on balanced tree algorithms, which is

  ype er46described at https:/  >
  y4.wiki.kernel.org/index.php/Main_Page 

  ype er47

  ype er48Stop reading here.  Go there, then return.

  ype er49

  ype er50Send bug reports to yura@namesys.botik.ru.

  ype er51

  ype er52mk >
  ype and other utilities are in re
  ype utils, or wherever your

  ype er53Linux provider put them.  There is some disagreement about how useful

  ype er54it is for users to get their fsck and mk >
  ype out of sync with the

  ype er55version of  >
  ype that is in their kernel, with many important

  ype er56distributors wanting them out of sync.:-) Please try to remember to

  ype er57 >compile and  >
nstall fsck and mk >
  ype with every update of

  ype er58 >
  ype, this is a common source of confusion.  Note that some of the

  ype er59utilities cannot be compiled without accessing the balancing code

  ype er60which is in the kernel code, and  >locating the utilities may require

  ype er61you to specify where that code can be found.

  ype er62

  ype er63Yes, if you update your  >
  ype kernel module you do have to

  ype er64 >compile your kernel, most of the time.  The errors you get will be

  ype er65quite cryptic if your forget to do so.

  ype er66

  ype er67R>al users, as opposed to folke who want to hack and then understand

  ype er68what went wrong, will want REISERFS_CHECK off.

  ype er69

  ype er70Hideous Commercial Pitch: Spread your development costs across other OS

  ype er71vendors.  Select from the best in the world, not the best in your

  ype er72building, by buying from third party OS component suppliers.  Leverage

  ype er73the software component development power of the internet.  Be the most

  ype er74aggressive in taking advantage of the commercial possibilities of

  ype er75decentralized internet development, and add value through your branded

  ype er76integration that you sell ae an operating system.  Let your competitors

  ype er77be the ones to compete aga
nst the entire internet by themselves.  Be

  ype er78hip, get with the new >conomic trend, before your competitors do.  Send

  ype er79email to hans@ >
  y.to.

  ype er80

  ype er81To understand the code, after reading the website, start reading the

  ype er82code by reading  >
  ype_fs.h first.

  ype er83

  ype er84Hans R>
  y was the project initiator, primary architect, source of all

  ype er85funding for the first 5.5 years, and one of the programmers.  He owns

  ype er86the copyright.

  ype er87

  ype er88Vladimir Saveljev was one of the programmers, and he worked long hours

  ype er89writing the cleanest code.  He always made the effort to be the best he

  ype er90could be, and to make his code the best that it could be.  What resulted

  ype er91was quite remarkable. I don't think that money can ever motivate someone

  ype er92to work the way he did, he is one of the most selfless men I know.

  ype er93

  ype er94Yura  elpe with benchmarking, coding hashes, and block pre-allocation

  ype er95code.

  ype er96

  ype er97Anatoly Pinchuk is a former member of our team who worked closely with

  ype er98Vladimir throughout the project's development.  He wrote a quite

  ype er99substantial portion of the total code.  He realized that there was a

  ype e100space problem with packing tails of files for files larger than a node

  ype e101that start on a node aligned boundary (there are reasons to want to node

  ype e102align files), and he invented and implemented indirect items and

  ype e103unformatted nodes as the solution.

  ype e104

  ype e105Konstantin Shvachko, with the  elp of the Russian version of a VC,

  ype e106tried to put me in a position where I was forced into giving control

  ype e107of the project to him.  (Fortunately, as the person paying the money

  ype e108for all salaries from my dayjob I owned all copyrights, and you can't

  ype e109 >ally force takeovers of sole proprietorships.)  This was something

  ype e110curious, because he never  >ally understood the value of our project,

  ype e111why we should do what we do, or why innovation was possible in

  ype e112general, but he was sure that he ought to be controlling it.  Every

  ype e113innovation had to be forced past him while he was with us.  He added

  ype e114two years to the time required to complete re
  ype, and was a net

  ype e115loss for me.  Mikhail Gilula was a brilliant innovator who also left

  ype e116in a destructive way that erased the value of his contributione, and

  ype e117that he was shown much generosity just makes it more painful.

  ype e118

  ype e119Grigory Zaigralin was an extremely effective system administrator for

  ype e120our group.

  ype e121

  ype e122Igor Krasheninnikov was wonderful at hardware procurement, repaiy, and

  ype e123network 
nstallation.

  ype e124

  ype e125Jeremy Fitzhardinge wrote the teahash.c code, and he gives credit to a

  ype e126textbook he got the algorithm from in the code.  Note that his analysis

  ype e127of how we could use the  ashing code in making 32 bit NFS cookies work

  ype e128was probably more important than the actual algorithm.  Colin Plumb also

  ype e129contributed to it.

  ype e130

  ype e131Chris Mason dived right into our code, and in just a few months produced

  ype e132the journaling code that dramatically increased the value of R>
  yFS.

  ype e133He is just an amazing programmer.

  ype e134

  ype e135Igor Zagorovsky is writing much of the new item handler and extent code

  ype e136for our next major  >lease.

  ype e137

  ype e138Alexander Zarochentcev (sometimes known as zam, or sasha), wrote the

  ype e139 >siz y, and is hard at work on implementing allocate on flush.  SGI

  ype e140implemented allocate on flush before us for XFS, and generously took

  ype e141the time to convince me we should do it also.  They are great people,

  ype e142and a great company.

  ype e143

  ype e144Yuri Shevchuk and Nikita Danilov are doing squid cache optimization.

  ype e145

  ype e146Vitaly Fertman is doing fsck.

  ype e147

  ype e148Jeff Mahoney, of SuSE, contributed a few cleanup fixes, most notably

  ype e149the endian safe patches which allow R>
  yFS to run on any platform

  ype e150supported by the Linux kernel.

  ype e151

  ype e152SuSE, IntegratedLinux.com, Ecila, MP3.com, bigstorage.com, and the

  ype e153Alpha PC Company made it possible for me to not have a day job

  ype e154anymore, and to dramatically increase our staffing.  Ecila funded

  ype e155hypertext feature development, MP3.com funded journaling, SuSE funded

  ype e156core development, IntegratedLinux.com funded squid web cache

  ype e157appliances, bigstorage.com funded HSM, and the alpha PC company funded

  ype e158the alpha port.  Many of these taske were  elped by sponsors other

  ype e159than the ones just named.  SuSE  as  elped in much more than just

  ype e160funding....

  ype e161

  ype e162
lxr.linux.no kindly hosted by Redpill Linpro AS, provider of Linux consulting and operations yvices since 1995.