Lines Matching refs:that
16 Set owner/group/mode for files that do not have it specified in extended
19 that for files mode is anded with 0666. If you want files to have 'x'
26 text file than to damage binary file). If you want to change that list,
28 heuristic algorithm that I removed. I thing it's danger to let the
34 danger. I tried to write it so that it won't crash if check=normal on
41 When to mark filesystem dirty so that OS/2 checks it.
54 As in OS/2, filenames are case insensitive. However, shell thinks that names
56 'cat FOO', 'cat Foo', 'cat foo' or 'cat F*' but not 'cat f*'. Note, that you
70 an ascii string identifying that attribute and value is any string of bytes of
75 that extended attributes those value differs from defaults specified in mount
77 they're just changed. It means that when your default uid=0 and you type
85 that if somebody (I don't know who?) has set "UID", "GID", "MODE" or "DEV"
97 stored in very crazy way. They tried to do it so that link changes when file is
111 Czech OS/2, the file was completely inaccessible under any name. It seems that
115 Czech OS/2 another file in that directory, that file was inaccessible too. OS/2
117 (note, that files in HPFS directory must be sorted) and when searching for
119 funny thing was that, when rebooted, PmShell tried to reopen this directory
122 system although HPFS was designed to allow that.
149 with another node when deleted. And that new file might have larger name than
150 the old one so the new name doesn't fit in directory node (dnode). And that
151 would result in directory tree splitting, that takes disk space. Workaround is
152 to delete other files that are leaf (probability that the file is non-leaf is
154 You encounter this problem only if you have many directories so that
162 Renaming files so that only case changes doesn't work. This driver supports it
180 unbalanced trees too :-) but both HPFS and HPFS386 contain bug that it rarely
184 Workaround is to move all files from that directory to another and then back
185 again. Do it in Linux, not OS/2! If you see this message in directory that is
210 0.91 Fixed bug that caused shooting to memory when write_inode was called on
213 0.93 Fixed bug that locked up the machine when there were too many filenames
217 0.95 Fixed a bug that i_hpfs_parent_dir was not updated when moving files
219 1.91 Fixed a bug that chk_sectors failed when sectors were at the end of disk
221 Fixed a bug that could possibly happen (with very low probability) when
232 1.93 Modified, so that it works with kernels >= 2.1.131, I don't know if it
240 Fixed a bug that slowed down alloc and prevented allocating 100% space
250 Fixed a bug that it set badly one flag in large anode tree (it was not
252 1.95 Fixed one buffer leak, that could happen on corrupted filesystem
261 Fixed a bug that it didn't allow creation of files > 128M (it should be 2G)
288 Reschedule points added so that it doesn't lock CPU long time