-sphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget$/translations/zh_CN/filesystems/hpfsmodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget$/translations/zh_TW/filesystems/hpfsmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget$/translations/it_IT/filesystems/hpfsmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget$/translations/ja_JP/filesystems/hpfsmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget$/translations/ko_KR/filesystems/hpfsmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hPortuguese (Brazilian)}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget$/translations/pt_BR/filesystems/hpfsmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget$/translations/sp_SP/filesystems/hpfsmodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhcomment)}(h SPDX-License-Identifier: GPL-2.0h]h SPDX-License-Identifier: GPL-2.0}hhsbah}(h]h ]h"]h$]h&] xml:spacepreserveuh1hhhhhh>/var/lib/git/docbuild/linux/Documentation/filesystems/hpfs.rsthKubhsection)}(hhh](htitle)}(hRead/Write HPFS 2.09h]hRead/Write HPFS 2.09}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh paragraph)}(h1998-2004, Mikulas Patockah]h1998-2004, Mikulas Patocka}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh field_list)}(hhh](hfield)}(hhh](h field_name)}(hemailh]hemail}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhKubh field_body)}(h mikulas@artax.karlin.mff.cuni.czh]h)}(hj h]h reference)}(hj h]h mikulas@artax.karlin.mff.cuni.cz}(hjhhhNhNubah}(h]h ]h"]h$]h&]refuri'mailto:mikulas@artax.karlin.mff.cuni.czuh1jhj ubah}(h]h ]h"]h$]h&]uh1hhhhK hj ubah}(h]h ]h"]h$]h&]uh1jhhubeh}(h]h ]h"]h$]h&]uh1hhhhK hhhhubh)}(hhh](h)}(hhomepageh]hhomepage}(hj6hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj3hhhKubj)}(hChttps://artax.karlin.mff.cuni.cz/~mikulas/vyplody/hpfs/index-e.cgi h]h)}(hBhttps://artax.karlin.mff.cuni.cz/~mikulas/vyplody/hpfs/index-e.cgih]j)}(hjJh]hBhttps://artax.karlin.mff.cuni.cz/~mikulas/vyplody/hpfs/index-e.cgi}(hjLhhhNhNubah}(h]h ]h"]h$]h&]refurijJuh1jhjHubah}(h]h ]h"]h$]h&]uh1hhhhK hjDubah}(h]h ]h"]h$]h&]uh1jhj3ubeh}(h]h ]h"]h$]h&]uh1hhhhK hhhhubeh}(h]h ]h"]h$]h&]uh1hhhhhhhhK ubh)}(hhh](h)}(hCreditsh]hCredits}(hjuhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjrhhhhhK ubhdefinition_list)}(hhh]hdefinition_list_item)}(h`Chris Smith, 1993, original read-only HPFS, some code and hpfs structures file is taken from it h](hterm)}(hNChris Smith, 1993, original read-only HPFS, some code and hpfs structures fileh]hNChris Smith, 1993, original read-only HPFS, some code and hpfs structures file}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubh definition)}(hhh]h)}(his taken from ith]his taken from it}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjrhhhhhNubh)}(hNJacques Gelinas, MSDos mmap, Inspired by fs/nfs/mmap.c (Jon Tombs 15 Aug 1993)h]hNJacques Gelinas, MSDos mmap, Inspired by fs/nfs/mmap.c (Jon Tombs 15 Aug 1993)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjrhhubh)}(hFWerner Almesberger, 1992, 1993, MSDos option parser & CR/LF conversionh]hFWerner Almesberger, 1992, 1993, MSDos option parser & CR/LF conversion}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjrhhubh)}(h Mount optionsh]h Mount options}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjrhhubj)}(hhh](j)}(hXuid=xxx,gid=xxx,umask=xxx (default uid=gid=0 umask=default_system_umask) Set owner/group/mode for files that do not have it specified in extended attributes. Mode is inverted umask - for example umask 027 gives owner all permission, group read permission and anybody else no access. Note that for files mode is anded with 0666. If you want files to have 'x' rights, you must use extended attributes.h](j)}(hHuid=xxx,gid=xxx,umask=xxx (default uid=gid=0 umask=default_system_umask)h]hHuid=xxx,gid=xxx,umask=xxx (default uid=gid=0 umask=default_system_umask)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hhh]h)}(hXFSet owner/group/mode for files that do not have it specified in extended attributes. Mode is inverted umask - for example umask 027 gives owner all permission, group read permission and anybody else no access. Note that for files mode is anded with 0666. If you want files to have 'x' rights, you must use extended attributes.h]hXJSet owner/group/mode for files that do not have it specified in extended attributes. Mode is inverted umask - for example umask 027 gives owner all permission, group read permission and anybody else no access. Note that for files mode is anded with 0666. If you want files to have ‘x’ rights, you must use extended attributes.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(h@case=lower,asis (default asis) File name lowercasing in readdir.h](j)}(hcase=lower,asis (default asis)h]hcase=lower,asis (default asis)}(hj#hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hhh]h)}(h!File name lowercasing in readdir.h]h!File name lowercasing in readdir.}(hj4hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj1ubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhKhjhhubj)}(hXHconv=binary,text,auto (default binary) CR/LF -> LF conversion, if auto, decision is made according to extension - there is a list of text extensions (I thing it's better to not convert text file than to damage binary file). If you want to change that list, change it in the source. Original readonly HPFS contained some strange heuristic algorithm that I removed. I thing it's danger to let the computer decide whether file is text or binary. For example, DJGPP binaries contain small text message at the beginning and they could be misidentified and damaged under some circumstances.h](j)}(h&conv=binary,text,auto (default binary)h]h&conv=binary,text,auto (default binary)}(hjRhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhK&hjNubj)}(hhh]h)}(hX!CR/LF -> LF conversion, if auto, decision is made according to extension - there is a list of text extensions (I thing it's better to not convert text file than to damage binary file). If you want to change that list, change it in the source. Original readonly HPFS contained some strange heuristic algorithm that I removed. I thing it's danger to let the computer decide whether file is text or binary. For example, DJGPP binaries contain small text message at the beginning and they could be misidentified and damaged under some circumstances.h]hX%CR/LF -> LF conversion, if auto, decision is made according to extension - there is a list of text extensions (I thing it’s better to not convert text file than to damage binary file). If you want to change that list, change it in the source. Original readonly HPFS contained some strange heuristic algorithm that I removed. I thing it’s danger to let the computer decide whether file is text or binary. For example, DJGPP binaries contain small text message at the beginning and they could be misidentified and damaged under some circumstances.}(hjchhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hj`ubah}(h]h ]h"]h$]h&]uh1jhjNubeh}(h]h ]h"]h$]h&]uh1jhhhK&hjhhubj)}(hXTcheck=none,normal,strict (default normal) Check level. Selecting none will cause only little speedup and big danger. I tried to write it so that it won't crash if check=normal on corrupted filesystems. check=strict means many superfluous checks - used for debugging (for example it checks if file is allocated in bitmaps when accessing it).h](j)}(h)check=none,normal,strict (default normal)h]h)check=none,normal,strict (default normal)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhK,hj}ubj)}(hhh]h)}(hX*Check level. Selecting none will cause only little speedup and big danger. I tried to write it so that it won't crash if check=normal on corrupted filesystems. check=strict means many superfluous checks - used for debugging (for example it checks if file is allocated in bitmaps when accessing it).h]hX,Check level. Selecting none will cause only little speedup and big danger. I tried to write it so that it won’t crash if check=normal on corrupted filesystems. check=strict means many superfluous checks - used for debugging (for example it checks if file is allocated in bitmaps when accessing it).}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK)hjubah}(h]h ]h"]h$]h&]uh1jhj}ubeh}(h]h ]h"]h$]h&]uh1jhhhK,hjhhubj)}(h]errors=continue,remount-ro,panic (default remount-ro) Behaviour when filesystem errors found.h](j)}(h5errors=continue,remount-ro,panic (default remount-ro)h]h5errors=continue,remount-ro,panic (default remount-ro)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhK.hjubj)}(hhh]h)}(h'Behaviour when filesystem errors found.h]h'Behaviour when filesystem errors found.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK/hjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhK.hjhhubj)}(h^chkdsk=no,errors,always (default errors) When to mark filesystem dirty so that OS/2 checks it.h](j)}(h(chkdsk=no,errors,always (default errors)h]h(chkdsk=no,errors,always (default errors)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhK0hjubj)}(hhh]h)}(h5When to mark filesystem dirty so that OS/2 checks it.h]h5When to mark filesystem dirty so that OS/2 checks it.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK1hjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhK0hjhhubj)}(hX"eas=no,ro,rw (default rw) What to do with extended attributes. 'no' - ignore them and use always values specified in uid/gid/mode options. 'ro' - read extended attributes but do not create them. 'rw' - create extended attributes when you use chmod/chown/chgrp/mknod/ln -s on the filesystem.h](j)}(heas=no,ro,rw (default rw)h]heas=no,ro,rw (default rw)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhK5hj ubj)}(hhh]h)}(hXWhat to do with extended attributes. 'no' - ignore them and use always values specified in uid/gid/mode options. 'ro' - read extended attributes but do not create them. 'rw' - create extended attributes when you use chmod/chown/chgrp/mknod/ln -s on the filesystem.h]hXWhat to do with extended attributes. ‘no’ - ignore them and use always values specified in uid/gid/mode options. ‘ro’ - read extended attributes but do not create them. ‘rw’ - create extended attributes when you use chmod/chown/chgrp/mknod/ln -s on the filesystem.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK3hjubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhhhK5hjhhubj)}(htimeshift=(-)nnn (default 0) Shifts the time by nnn seconds. For example, if you see under linux one hour more, than under os/2, use timeshift=-3600. h](j)}(htimeshift=(-)nnn (default 0)h]htimeshift=(-)nnn (default 0)}(hj=hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhK:hj9ubj)}(hhh]h)}(hxShifts the time by nnn seconds. For example, if you see under linux one hour more, than under os/2, use timeshift=-3600.h]hxShifts the time by nnn seconds. For example, if you see under linux one hour more, than under os/2, use timeshift=-3600.}(hjNhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK8hjKubah}(h]h ]h"]h$]h&]uh1jhj9ubeh}(h]h ]h"]h$]h&]uh1jhhhK:hjhhubeh}(h]h ]h"]h$]h&]uh1jhjrhhhhhNubeh}(h]creditsah ]h"]creditsah$]h&]uh1hhhhhhhhK ubh)}(hhh](h)}(h File namesh]h File names}(hjyhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjvhhhhhK=ubh)}(hXAs in OS/2, filenames are case insensitive. However, shell thinks that names are case sensitive, so for example when you create a file FOO, you can use 'cat FOO', 'cat Foo', 'cat foo' or 'cat F*' but not 'cat f*'. Note, that you also won't be able to compile linux kernel (and maybe other things) on HPFS because kernel creates different files with names like bootsect.S and bootsect.s. When searching for file whose name has characters >= 128, codepages are used - see below. OS/2 ignores dots and spaces at the end of file name, so this driver does as well. If you create 'a. ...', the file 'a' will be created, but you can still access it under names 'a.', 'a..', 'a . . . ' etc.h]hXAs in OS/2, filenames are case insensitive. However, shell thinks that names are case sensitive, so for example when you create a file FOO, you can use ‘cat FOO’, ‘cat Foo’, ‘cat foo’ or ‘cat F*’ but not ‘cat f*’. Note, that you also won’t be able to compile linux kernel (and maybe other things) on HPFS because kernel creates different files with names like bootsect.S and bootsect.s. When searching for file whose name has characters >= 128, codepages are used - see below. OS/2 ignores dots and spaces at the end of file name, so this driver does as well. If you create ‘a. ...’, the file ‘a’ will be created, but you can still access it under names ‘a.’, ‘a..’, ‘a . . . ‘ etc.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK?hjvhhubeh}(h] file-namesah ]h"] file namesah$]h&]uh1hhhhhhhhK=ubh)}(hhh](h)}(hExtended attributesh]hExtended attributes}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKLubh)}(hXOn HPFS partitions, OS/2 can associate to each file a special information called extended attributes. Extended attributes are pairs of (key,value) where key is an ascii string identifying that attribute and value is any string of bytes of variable length. OS/2 stores window and icon positions and file types there. So why not use it for unix-specific info like file owner or access rights? This driver can do it. If you chown/chgrp/chmod on a hpfs partition, extended attributes with keys "UID", "GID" or "MODE" and 2-byte values are created. Only that extended attributes those value differs from defaults specified in mount options are created. Once created, the extended attributes are never deleted, they're just changed. It means that when your default uid=0 and you type something like 'chown luser file; chown root file' the file will contain extended attribute UID=0. And when you umount the fs and mount it again with uid=luser_uid, the file will be still owned by root! If you chmod file to 444, extended attribute "MODE" will not be set, this special case is done by setting read-only flag. When you mknod a block or char device, besides "MODE", the special 4-byte extended attribute "DEV" will be created containing the device number. Currently this driver cannot resize extended attributes - it means that if somebody (I don't know who?) has set "UID", "GID", "MODE" or "DEV" attributes with different sizes, they won't be rewritten and changing these values doesn't work.h]hXOn HPFS partitions, OS/2 can associate to each file a special information called extended attributes. Extended attributes are pairs of (key,value) where key is an ascii string identifying that attribute and value is any string of bytes of variable length. OS/2 stores window and icon positions and file types there. So why not use it for unix-specific info like file owner or access rights? This driver can do it. If you chown/chgrp/chmod on a hpfs partition, extended attributes with keys “UID”, “GID” or “MODE” and 2-byte values are created. Only that extended attributes those value differs from defaults specified in mount options are created. Once created, the extended attributes are never deleted, they’re just changed. It means that when your default uid=0 and you type something like ‘chown luser file; chown root file’ the file will contain extended attribute UID=0. And when you umount the fs and mount it again with uid=luser_uid, the file will be still owned by root! If you chmod file to 444, extended attribute “MODE” will not be set, this special case is done by setting read-only flag. When you mknod a block or char device, besides “MODE”, the special 4-byte extended attribute “DEV” will be created containing the device number. Currently this driver cannot resize extended attributes - it means that if somebody (I don’t know who?) has set “UID”, “GID”, “MODE” or “DEV” attributes with different sizes, they won’t be rewritten and changing these values doesn’t work.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKNhjhhubeh}(h]extended-attributesah ]h"]extended attributesah$]h&]uh1hhhhhhhhKLubh)}(hhh](h)}(hSymlinksh]hSymlinks}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKeubh)}(hXYou can do symlinks on HPFS partition, symlinks are achieved by setting extended attribute named "SYMLINK" with symlink value. Like on ext2, you can chown and chgrp symlinks but I don't know what is it good for. chmoding symlink results in chmoding file where symlink points. These symlinks are just for Linux use and incompatible with OS/2. OS/2 PmShell symlinks are not supported because they are stored in very crazy way. They tried to do it so that link changes when file is moved ... sometimes it works. But the link is partly stored in directory extended attributes and partly in OS2SYS.INI. I don't want (and don't know how) to analyze or change OS2SYS.INI.h]hXYou can do symlinks on HPFS partition, symlinks are achieved by setting extended attribute named “SYMLINK” with symlink value. Like on ext2, you can chown and chgrp symlinks but I don’t know what is it good for. chmoding symlink results in chmoding file where symlink points. These symlinks are just for Linux use and incompatible with OS/2. OS/2 PmShell symlinks are not supported because they are stored in very crazy way. They tried to do it so that link changes when file is moved ... sometimes it works. But the link is partly stored in directory extended attributes and partly in OS2SYS.INI. I don’t want (and don’t know how) to analyze or change OS2SYS.INI.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKghjhhubeh}(h]symlinksah ]h"]symlinksah$]h&]uh1hhhhhhhhKeubh)}(hhh](h)}(h Codepagesh]h Codepages}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKsubh)}(hXHPFS can contain several uppercasing tables for several codepages and each file has a pointer to codepage its name is in. However OS/2 was created in America where people don't care much about codepages and so multiple codepages support is quite buggy. I have Czech OS/2 working in codepage 852 on my disk. Once I booted English OS/2 working in cp 850 and I created a file on my 852 partition. It marked file name codepage as 850 - good. But when I again booted Czech OS/2, the file was completely inaccessible under any name. It seems that OS/2 uppercases the search pattern with its system code page (852) and file name it's comparing to with its code page (850). These could never match. Is it really what IBM developers wanted? But problems continued. When I created in Czech OS/2 another file in that directory, that file was inaccessible too. OS/2 probably uses different uppercasing method when searching where to place a file (note, that files in HPFS directory must be sorted) and when searching for a file. Finally when I opened this directory in PmShell, PmShell crashed (the funny thing was that, when rebooted, PmShell tried to reopen this directory again :-). chkdsk happily ignores these errors and only low-level disk modification saved me. Never mix different language versions of OS/2 on one system although HPFS was designed to allow that. OK, I could implement complex codepage support to this driver but I think it would cause more problems than benefit with such buggy implementation in OS/2. So this driver simply uses first codepage it finds for uppercasing and lowercasing no matter what's file codepage index. Usually all file names are in this codepage - if you don't try to do what I described above :-)h]hXHPFS can contain several uppercasing tables for several codepages and each file has a pointer to codepage its name is in. However OS/2 was created in America where people don’t care much about codepages and so multiple codepages support is quite buggy. I have Czech OS/2 working in codepage 852 on my disk. Once I booted English OS/2 working in cp 850 and I created a file on my 852 partition. It marked file name codepage as 850 - good. But when I again booted Czech OS/2, the file was completely inaccessible under any name. It seems that OS/2 uppercases the search pattern with its system code page (852) and file name it’s comparing to with its code page (850). These could never match. Is it really what IBM developers wanted? But problems continued. When I created in Czech OS/2 another file in that directory, that file was inaccessible too. OS/2 probably uses different uppercasing method when searching where to place a file (note, that files in HPFS directory must be sorted) and when searching for a file. Finally when I opened this directory in PmShell, PmShell crashed (the funny thing was that, when rebooted, PmShell tried to reopen this directory again :-). chkdsk happily ignores these errors and only low-level disk modification saved me. Never mix different language versions of OS/2 on one system although HPFS was designed to allow that. OK, I could implement complex codepage support to this driver but I think it would cause more problems than benefit with such buggy implementation in OS/2. So this driver simply uses first codepage it finds for uppercasing and lowercasing no matter what’s file codepage index. Usually all file names are in this codepage - if you don’t try to do what I described above :-)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKuhjhhubeh}(h] codepagesah ]h"] codepagesah$]h&]uh1hhhhhhhhKsubh)}(hhh](h)}(h Known bugsh]h Known bugs}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hX HPFS386 on OS/2 server is not supported. HPFS386 installed on normal OS/2 client should work. If you have OS/2 server, use only read-only mode. I don't know how to handle some HPFS386 structures like access control list or extended perm list, I don't know how to delete them when file is deleted and how to not overwrite them with extended attributes. Send me some info on these structures and I'll make it. However, this driver should detect presence of HPFS386 structures, remount read-only and not destroy them (I hope).h]hXHPFS386 on OS/2 server is not supported. HPFS386 installed on normal OS/2 client should work. If you have OS/2 server, use only read-only mode. I don’t know how to handle some HPFS386 structures like access control list or extended perm list, I don’t know how to delete them when file is deleted and how to not overwrite them with extended attributes. Send me some info on these structures and I’ll make it. However, this driver should detect presence of HPFS386 structures, remount read-only and not destroy them (I hope).}(hj#hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hgWhen there's not enough space for extended attributes, they will be truncated and no error is returned.h]hiWhen there’s not enough space for extended attributes, they will be truncated and no error is returned.}(hj1hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hOS/2 can't access files if the path is longer than about 256 chars but this driver allows you to do it. chkdsk ignores such errors.h]hOS/2 can’t access files if the path is longer than about 256 chars but this driver allows you to do it. chkdsk ignores such errors.}(hj?hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hXSometimes you won't be able to delete some files on a very full filesystem (returning error ENOSPC). That's because file in non-leaf node in directory tree (one directory, if it's large, has dirents in tree on HPFS) must be replaced with another node when deleted. And that new file might have larger name than the old one so the new name doesn't fit in directory node (dnode). And that would result in directory tree splitting, that takes disk space. Workaround is to delete other files that are leaf (probability that the file is non-leaf is about 1/50) or to truncate file first to make some space. You encounter this problem only if you have many directories so that preallocated directory band is full i.e.::h]hXSometimes you won’t be able to delete some files on a very full filesystem (returning error ENOSPC). That’s because file in non-leaf node in directory tree (one directory, if it’s large, has dirents in tree on HPFS) must be replaced with another node when deleted. And that new file might have larger name than the old one so the new name doesn’t fit in directory node (dnode). And that would result in directory tree splitting, that takes disk space. Workaround is to delete other files that are leaf (probability that the file is non-leaf is about 1/50) or to truncate file first to make some space. You encounter this problem only if you have many directories so that preallocated directory band is full i.e.:}(hjMhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh literal_block)}(h5number_of_directories / size_of_filesystem_in_mb > 4.h]h5number_of_directories / size_of_filesystem_in_mb > 4.}hj]sbah}(h]h ]h"]h$]h&]hhuh1j[hhhKhjhhubh)}(h"You can't delete open directories.h]h$You can’t delete open directories.}(hjkhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(h9You can't rename over directories (what is it good for?).h]h;You can’t rename over directories (what is it good for?).}(hjyhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hRenaming files so that only case changes doesn't work. This driver supports it but vfs doesn't. Something like 'mv file FILE' won't work.h]hRenaming files so that only case changes doesn’t work. This driver supports it but vfs doesn’t. Something like ‘mv file FILE’ won’t work.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hAll atimes and directory mtimes are not updated. That's because of performance reasons. If you extremely wish to update them, let me know, I'll write it (but it will be slow).h]hAll atimes and directory mtimes are not updated. That’s because of performance reasons. If you extremely wish to update them, let me know, I’ll write it (but it will be slow).}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hWhen the system is out of memory and swap, it may slightly corrupt filesystem (lost files, unbalanced directories). (I guess all filesystem may do it).h]hWhen the system is out of memory and swap, it may slightly corrupt filesystem (lost files, unbalanced directories). (I guess all filesystem may do it).}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hlWhen compiled, you get warning: function declaration isn't a prototype. Does anybody know what does it mean?h]hnWhen compiled, you get warning: function declaration isn’t a prototype. Does anybody know what does it mean?}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubeh}(h] known-bugsah ]h"] known bugsah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(h)What does "unbalanced tree" message mean?h]h-What does “unbalanced tree” message mean?}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hXOld versions of this driver created sometimes unbalanced dnode trees. OS/2 chkdsk doesn't scream if the tree is unbalanced (and sometimes creates unbalanced trees too :-) but both HPFS and HPFS386 contain bug that it rarely crashes when the tree is not balanced. This driver handles unbalanced trees correctly and writes warning if it finds them. If you see this message, this is probably because of directories created with old version of this driver. Workaround is to move all files from that directory to another and then back again. Do it in Linux, not OS/2! If you see this message in directory that is whole created by this driver, it is BUG - let me know about it.h]hXOld versions of this driver created sometimes unbalanced dnode trees. OS/2 chkdsk doesn’t scream if the tree is unbalanced (and sometimes creates unbalanced trees too :-) but both HPFS and HPFS386 contain bug that it rarely crashes when the tree is not balanced. This driver handles unbalanced trees correctly and writes warning if it finds them. If you see this message, this is probably because of directories created with old version of this driver. Workaround is to move all files from that directory to another and then back again. Do it in Linux, not OS/2! If you see this message in directory that is whole created by this driver, it is BUG - let me know about it.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubeh}(h]&what-does-unbalanced-tree-message-meanah ]h"])what does "unbalanced tree" message mean?ah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(h Bugs in OS/2h]h Bugs in OS/2}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hoWhen you have two (or more) lost directories pointing each to other, chkdsk locks up when repairing filesystem.h]hoWhen you have two (or more) lost directories pointing each to other, chkdsk locks up when repairing filesystem.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hSometimes (I think it's random) when you create a file with one-char name under OS/2, OS/2 marks it as 'long'. chkdsk then removes this flag saying "Minor fs error corrected".h]hSometimes (I think it’s random) when you create a file with one-char name under OS/2, OS/2 marks it as ‘long’. chkdsk then removes this flag saying “Minor fs error corrected”.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hFile names like "a .b" are marked as 'long' by OS/2 but chkdsk "corrects" it and marks them as short (and writes "minor fs error corrected"). This bug is not in HPFS386.h]hFile names like “a .b” are marked as ‘long’ by OS/2 but chkdsk “corrects” it and marks them as short (and writes “minor fs error corrected”). This bug is not in HPFS386.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubeh}(h] bugs-in-os-2ah ]h"] bugs in os/2ah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hCodepage bugs described aboveh]hCodepage bugs described above}(hj4hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj1hhhhhKubh)}(h;If you don't install fixpacks, there are many, many more...h]h=If you don’t install fixpacks, there are many, many more...}(hjBhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj1hhubeh}(h]codepage-bugs-described-aboveah ]h"]codepage bugs described aboveah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hHistoryh]hHistory}(hj[hhhNhNubah}(h]h ]h"]h$]h&]uh1hhjXhhhhhKubhtable)}(hhh]htgroup)}(hhh](hcolspec)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jshjpubjt)}(hhh]h}(h]h ]h"]h$]h&]colwidthKKuh1jshjpubhtbody)}(hhh](hrow)}(hhh](hentry)}(hhh]h)}(h0.90h]h0.90}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hFirst public releaseh]hFirst public release}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h0.91h]h0.91}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hdFixed bug that caused shooting to memory when write_inode was called on open inode (rarely happened)h]hdFixed bug that caused shooting to memory when write_inode was called on open inode (rarely happened)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h0.92h]h0.92}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h6Fixed a little memory leak in freeing directory inodesh]h6Fixed a little memory leak in freeing directory inodes}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h0.93h]h0.93}(hj=hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj:ubah}(h]h ]h"]h$]h&]uh1jhj7ubj)}(hhh]h)}(hFixed bug that locked up the machine when there were too many filenames with first 15 characters same Fixed write_file to zero file when writing behind file endh]hFixed bug that locked up the machine when there were too many filenames with first 15 characters same Fixed write_file to zero file when writing behind file end}(hjThhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjQubah}(h]h ]h"]h$]h&]uh1jhj7ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h0.94h]h0.94}(hjthhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjqubah}(h]h ]h"]h$]h&]uh1jhjnubj)}(hhh]h)}(hGFixed a little memory leak when trying to delete busy file or directoryh]hGFixed a little memory leak when trying to delete busy file or directory}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjnubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h0.95h]h0.95}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hDFixed a bug that i_hpfs_parent_dir was not updated when moving filesh]hDFixed a bug that i_hpfs_parent_dir was not updated when moving files}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h1.90h]h1.90}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h!First version for 2.1.1xx kernelsh]h!First version for 2.1.1xx kernels}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h1.91h]h1.91}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](h)}(hFixed a bug that chk_sectors failed when sectors were at the end of disk Fixed a race-condition when write_inode is called while deleting file Fixed a bug that could possibly happen (with very low probability) when using 0xff in filenames.h]hFixed a bug that chk_sectors failed when sectors were at the end of disk Fixed a race-condition when write_inode is called while deleting file Fixed a bug that could possibly happen (with very low probability) when using 0xff in filenames.}(hj0hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj-ubh)}(h*Rewritten locking to avoid race-conditionsh]h*Rewritten locking to avoid race-conditions}(hj>hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj-ubh)}(hMount option 'eas' now worksh]h Mount option ‘eas’ now works}(hjLhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj-ubh)}(hFsync no longer returns errorh]hFsync no longer returns error}(hjZhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj-ubh)}(h*Files beginning with '.' are marked hiddenh]h.Files beginning with ‘.’ are marked hidden}(hjhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj-ubh)}(hRemount support addedh]hRemount support added}(hjvhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj-ubh)}(h1Alloc is not so slow when filesystem becomes fullh]h1Alloc is not so slow when filesystem becomes full}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj-ubh)}(h:Atimes are no more updated because it slows down operationh]h:Atimes are no more updated because it slows down operation}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj-ubh)}(h1Code cleanup (removed all commented debug prints)h]h1Code cleanup (removed all commented debug prints)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj-ubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h1.92h]h1.92}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h=Corrected a bug when sync was called just before closing fileh]h=Corrected a bug when sync was called just before closing file}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h1.93h]h1.93}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](h)}(hcModified, so that it works with kernels >= 2.1.131, I don't know if it works with previous versionsh]heModified, so that it works with kernels >= 2.1.131, I don’t know if it works with previous versions}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubh)}(hTFixed a possible problem with disks > 64G (but I don't have one, so I can't test it)h]hXFixed a possible problem with disks > 64G (but I don’t have one, so I can’t test it)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubh)}(hFixed a file overflow at 2Gh]hFixed a file overflow at 2G}(hj*hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hj ubh)}(hAdded new option 'timeshift'h]h Added new option ‘timeshift’}(hj8hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hj ubh)}(hXChanged behaviour on HPFS386: It is now possible to operate on HPFS386 in read-only modeh]hXChanged behaviour on HPFS386: It is now possible to operate on HPFS386 in read-only mode}(hjFhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hj ubh)}(heFixed a bug that slowed down alloc and prevented allocating 100% space (this bug was not destructive)h]heFixed a bug that slowed down alloc and prevented allocating 100% space (this bug was not destructive)}(hjThhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h1.94h]h1.94}(hjthhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjqubah}(h]h ]h"]h$]h&]uh1jhjnubj)}(hhh](h)}(h%Added workaround for one bug in Linuxh]h%Added workaround for one bug in Linux}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubh)}(hFixed one buffer leakh]hFixed one buffer leak}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubh)}(hFixed some incompatibilities with large extended attributes (but it's still not 100% ok, I have no info on it and OS/2 doesn't want to create them)h]hFixed some incompatibilities with large extended attributes (but it’s still not 100% ok, I have no info on it and OS/2 doesn’t want to create them)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubh)}(hRewritten allocationh]hRewritten allocation}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubh)}(hFFixed a bug with i_blocks (du sometimes didn't display correct values)h]hHFixed a bug with i_blocks (du sometimes didn’t display correct values)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubh)}(hNDirectories have no longer archive attribute set (some programs don't like it)h]hPDirectories have no longer archive attribute set (some programs don’t like it)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubh)}(hSFixed a bug that it set badly one flag in large anode tree (it was not destructive)h]hSFixed a bug that it set badly one flag in large anode tree (it was not destructive)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hjubeh}(h]h ]h"]h$]h&]uh1jhjnubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h1.95h]h1.95}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM"hjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](h)}(h@Fixed one buffer leak, that could happen on corrupted filesystemh]h@Fixed one buffer leak, that could happen on corrupted filesystem}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM"hj ubh)}(h#Fixed one bug in allocation in 1.94h]h#Fixed one bug in allocation in 1.94}(hj$ hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM$hj ubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h1.96h]h1.96}(hjD hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM%hjA ubah}(h]h ]h"]h$]h&]uh1jhj> ubj)}(hhh](h)}(h{Added workaround for one bug in OS/2 (HPFS locked up, HPFS386 reported error sometimes when opening directories in PMSHELL)h]h{Added workaround for one bug in OS/2 (HPFS locked up, HPFS386 reported error sometimes when opening directories in PMSHELL)}(hj[ hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM%hjX ubh)}(hFixed a possible bitmap raceh]hFixed a possible bitmap race}(hji hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM(hjX ubh)}(h%Fixed possible problem on large disksh]h%Fixed possible problem on large disks}(hjw hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM*hjX ubh)}(hYou can now delete open filesh]hYou can now delete open files}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM,hjX ubh)}(h%Fixed a nondestructive race in renameh]h%Fixed a nondestructive race in rename}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM.hjX ubeh}(h]h ]h"]h$]h&]uh1jhj> ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h1.97h]h1.97}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM/hj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh](h)}(h)Support for HPFS v3 (on large partitions)h]h)Support for HPFS v3 (on large partitions)}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM/hj ubh)}(hLZFixed a bug that it didn't allow creation of files > 128M (it should be 2G)h]hNZFixed a bug that it didn’t allow creation of files > 128M (it should be 2G)}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM1hj ubeh}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h1.97.1h]h1.97.1}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM3hj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh](h)}(hChanged names of global symbolsh]hChanged names of global symbols}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM3hj ubh)}(h4Fixed a bug when chmoding or chowning root directoryh]h4Fixed a bug when chmoding or chowning root directory}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM5hj ubeh}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h1.98h]h1.98}(hj= hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM6hj: ubah}(h]h ]h"]h$]h&]uh1jhj7 ubj)}(hhh]h)}(hoFixed a deadlock when using old_readdir Better directory handling; workaround for "unbalanced tree" bug in OS/2h]hsFixed a deadlock when using old_readdir Better directory handling; workaround for “unbalanced tree” bug in OS/2}(hjT hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM6hjQ ubah}(h]h ]h"]h$]h&]uh1jhj7 ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h1.99h]h1.99}(hjt hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM8hjq ubah}(h]h ]h"]h$]h&]uh1jhjn ubj)}(hhh](h)}(hNCorrected a possible problem when there's not enough space while deleting fileh]hPCorrected a possible problem when there’s not enough space while deleting file}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM8hj ubh)}(hKNow it tries to truncate the file if there's not enough space when deletingh]hMNow it tries to truncate the file if there’s not enough space when deleting}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM;hj ubh)}(hRemoved a lot of redundant codeh]hRemoved a lot of redundant code}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM>hj ubeh}(h]h ]h"]h$]h&]uh1jhjn ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h2.00h]h2.00}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM?hj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(hRFixed a bug in rename (it was there since 1.96) Better anti-fragmentation strategyh]hRFixed a bug in rename (it was there since 1.96) Better anti-fragmentation strategy}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM?hj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h2.01h]h2.01}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMAhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh](h)}(h-Fixed problem with directory listing over NFSh]h-Fixed problem with directory listing over NFS}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMAhj ubh)}(h0Directory lseek now checks for proper parametersh]h0Directory lseek now checks for proper parameters}(hj# hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMChj ubh)}(hFixed race-condition in buffer code - it is in all filesystems in Linux; when reading device (cat /dev/hda) while creating files on it, files could be damagedh]hFixed race-condition in buffer code - it is in all filesystems in Linux; when reading device (cat /dev/hda) while creating files on it, files could be damaged}(hj1 hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMEhj ubeh}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h2.02h]h2.02}(hjQ hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMHhjN ubah}(h]h ]h"]h$]h&]uh1jhjK ubj)}(hhh]h)}(hZWorkaround for bug in breada in Linux. breada could cause accesses beyond end of partitionh]hZWorkaround for bug in breada in Linux. breada could cause accesses beyond end of partition}(hjh hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMHhje ubah}(h]h ]h"]h$]h&]uh1jhjK ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h2.03h]h2.03}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMJhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh](h)}(h3Char, block devices and pipes are correctly createdh]h3Char, block devices and pipes are correctly created}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMJhj ubh)}(h2Fixed non-crashing race in unlink (Alexander Viro)h]h2Fixed non-crashing race in unlink (Alexander Viro)}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMLhj ubh)}(h*Now it works with Japanese version of OS/2h]h*Now it works with Japanese version of OS/2}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMNhj ubeh}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h2.04h]h2.04}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMOhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(h.Fixed error when ftruncate used to extend fileh]h.Fixed error when ftruncate used to extend file}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMOhj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(h2.05h]h2.05}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMPhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh](h)}(h/Fixed crash when got mount parameters without =h]h/Fixed crash when got mount parameters without =}(hj) hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMPhj& ubh)}(h