Home
last modified time | relevance | path

Searched refs:not (Results 1 – 25 of 41) sorted by relevance

12

/fs/ocfs2/
Dstack_o2cb.c43 # error Lock modes do not match
46 # error Lock modes do not match
49 # error Lock modes do not match
52 # error Lock modes do not match
55 # error Lock modes do not match
58 # error Lock modes do not match
61 # error Lock modes do not match
/fs/nls/
DKconfig25 the NLS used by your console, not the NLS used by a specific file
47 only, not to the file contents. You can include several codepages;
59 only, not to the file contents. You can include several codepages;
71 only, not to the file contents. You can include several codepages;
84 only, not to the file contents. You can include several codepages;
88 languages that are not part of the US codepage 437.
100 only, not to the file contents. You can include several codepages;
115 only, not to the file contents. You can include several codepages;
126 only, not to the file contents. You can include several codepages;
137 only, not to the file contents. You can include several codepages;
[all …]
/fs/affs/
DChanges2 that I do not like numbers like 0.1 and the like for
12 apparently not causing the failure, as directory
24 - When a file is truncated to a size that is not
26 last allocated block is not cleared. Well,
114 It also marks the inode dirty now (which is not
147 - getblock() did not invalidate the key cache
161 - File mode changes were not updated on disk.
172 inode if the fs was not an OFS. This bug only shows
174 was not enough space.
188 - Fixed bug in balloc(): Superblock was not set dirty after
[all …]
/fs/ntfs/
DKconfig26 If you are not using Windows NT, 2000, XP or 2003 in addition to
63 While we cannot guarantee that it will not damage any data, we have
64 so far not received a single report where the driver would have
70 is not safe.
74 hard disk. Unlike other Linux distributions TopologiLinux does not
/fs/jffs2/
DLICENCE17 with JFFS2; if not, write to the Free Software Foundation, Inc.,
23 files, these files do not by themselves cause the resulting work to be
28 This exception does not invalidate any other reasons why a work based on
DREADME.Locking6 JFFS2. It is not expected to remain perfectly up to date, but ought to
27 time this happens are part of the new node, not just something that
90 long as the pointer you're holding is to a _valid_ node, not an
112 will not be removed. So, it is allowed to access it without locking
/fs/logfs/
DKconfig12 not been measured yet.
15 not be used for other than testing purposes.
/fs/ncpfs/
DKconfig16 You do not have to say Y here if you want your Linux box to act as a
46 parameter "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not
78 Long filenames (created by Win95) will not be affected.
80 This option does not solve the problem that filenames appear
103 bit on NCPFS. The file server need not have long name space or NFS
/fs/cramfs/
DREADME25 The order of inode traversal is described as "width-first" (not to be
33 allows cramfs_lookup to return more quickly when a filename does not
61 <block>s are merely byte-aligned, not generally u32-aligned.
99 This discrepancy is a bug, though it's not clear which should be
107 kernels, not even necessarily kernels of the same architecture if
152 cost is greater complexity. Probably not worth it, but I hope someone
/fs/autofs4/
DKconfig17 If you are not a part of a fairly large, distributed network or
19 local network, you probably do not need an automounter, and can say
/fs/fat/
DKconfig12 This FAT support is not a file system in itself, it only provides
18 partitions from within Linux (but not transparently) is with the
52 support" below), or you will not be able to see the long filenames
95 Note that "utf8" is not recommended for FAT filesystems.
/fs/reiserfs/
DREADME14 All portions of governed files not labeled otherwise are owned by Hans
30 the GPL as not allowing those additional licensing options, you read
32 you can see that those restrictions on additional terms do not apply
38 permission, unless you are an end user not redistributing to others.
71 vendors. Select from the best in the world, not the best in your
153 Alpha PC Company made it possible for me to not have a day job
DKconfig5 Stores not just filenames but the files themselves in a balanced
87 If you are not using a security module that requires using
/fs/jfs/
DKconfig9 If you do not intend to use the JFS filesystem, say N.
33 If you are not using a security module that requires using
/fs/ext4/
DKconfig2 # have EXT3_FS set but not EXT4_FS set and thus would result in non-bootable
44 the on-disk format of ext4 is not forwards compatible with
98 If you are not using a security module that requires using
/fs/xfs/
DKconfig81 lighter weight than XFS_DEBUG and does not modify algorithms and will
82 not cause the kernel to panic on non-fatal errors.
96 not useful unless you are debugging a particular problem.
/fs/squashfs/
DKconfig105 LZ4 is not the standard compression used in Squashfs and so most
120 LZO is not the standard compression used in Squashfs and so most
135 XZ is not the standard compression used in Squashfs and so most
182 much more than three will probably not make much difference.
/fs/
DKconfig48 If you do not have a block device that is capable of using this,
167 files for sound to work properly. In short, if you're not sure,
219 This option alone does not add any kernel code.
267 This option alone does not add any kernel code.
/fs/nfsd/
DKconfig55 this protocol is available or not.
129 not for use in production.
143 If you do not wish to enable fine-grained security labels SELinux or
/fs/btrfs/
DKconfig18 The filesystem disk format is no longer unstable, and it's not
57 functionality is not intended for normal use.
/fs/f2fs/
DKconfig14 and tools support various parameters not only for configuring on-disk
67 If you are not using a security module, say N.
/fs/befs/
DTODO6 * Befs_fs.h has gotten big and messy. No reason not to break it up into
DChangeLog7 * Fixed module makefile problem. It was not compiling all the correct
150 * Anton also told me that the blocksize is not allowed to be larger than
184 with kmalloc(). put_super and put_inode free them. This allows us not
218 seems stable and not outragously slow. Existing features are more-or-less
315 The i_blocks field of the inode struct is not the number of blocks for the
316 inode, it is the number of blocks for the file. Also, i_blksize is not
/fs/configfs/
DKconfig11 same system. One is not a replacement for the other.
/fs/omfs/
DKconfig7 player and ReplayTV DVR. Despite the name, this filesystem is not

12