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