Lines Matching full:file

14 Chris Smith, 1993, original read-only HPFS, some code and hpfs structures file
30 	File name lowercasing in readdir.
34 	text file than to damage binary file). If you want to change that list,
37 	computer decide whether file is text or binary. For example, DJGPP
44 	used for debugging (for example it checks if file is allocated in
60 File names
64 are case sensitive, so for example when you create a file FOO, you can use
68 bootsect.s. When searching for file thats name has characters >= 128, codepages
70 OS/2 ignores dots and spaces at the end of file name, so this driver does as
71 well. If you create 'a. ...', the file 'a' will be created, but you can still
78 On HPFS partitions, OS/2 can associate to each file a special information called
81 variable length. OS/2 stores window and icon positions and file types there. So
82 why not use it for unix-specific info like file owner or access rights? This
88 something like 'chown luser file; chown root file' the file will contain
90 uid=luser_uid, the file will be still owned by root! If you chmod file to 444,
106 in chmoding file where symlink points. These symlinks are just for Linux use and
108 stored in very crazy way. They tried to do it so that link changes when file is
118 file has a pointer to codepage its name is in. However OS/2 was created in
121 Once I booted English OS/2 working in cp 850 and I created a file on my 852
122 partition. It marked file name codepage as 850 - good. But when I again booted
123 Czech OS/2, the file was completely inaccessible under any name. It seems that
124 OS/2 uppercases the search pattern with its system code page (852) and file
127 Czech OS/2 another file in that directory, that file was inaccessible too. OS/2
128 probably uses different uppercasing method when searching where to place a file
130 a file. Finally when I opened this directory in PmShell, PmShell crashed (the
138 lowercasing no matter what's file codepage index. Usually all file names are in
148 list, I don't know how to delete them when file is deleted and how to not
160 (returning error ENOSPC). That's because file in non-leaf node in directory tree
162 with another node when deleted. And that new file might have larger name than
165 to delete other files that are leaf (probability that the file is non-leaf is
166 about 1/50) or to truncate file first to make some space.
177 but vfs doesn't. Something like 'mv file FILE' won't work.
210 Sometimes (I think it's random) when you create a file with one-char name under
214 File names like "a .b" are marked as 'long' by OS/2 but chkdsk "corrects" it and
234        Fixed write_file to zero file when writing behind file end
235 0.94   Fixed a little memory leak when trying to delete busy file or directory
239        Fixed a race-condition when write_inode is called while deleting file
258 1.92   Corrected a bug when sync was called just before closing file
265        Fixed a file overflow at 2G
313        file
315        Now it tries to truncate the file if there's not enough space when
335 2.04   Fixed error when ftruncate used to extend file
351        An attempt to sync deleted file does not generate filesystem error