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