Lines Matching full:kernels
428 modern resize2fs's ability to work with older kernels without having
977 kernels.
1087 field to -1, instead of 0. Kernels older then 3.0 will print a
1095 that can support file systems > 16TB, once it arrives in v3.x kernels.
1494 more importantly, some released kernels may crash when this situation
1498 i_size is correct. (Kernels starting with 2.6.34 will set
1570 2.6.34 kernels to make e2fsck not complain about blocks deliberately
1956 kernels (post 2.6.29) will ignore this field. So let's fix it
1980 of information in sysfs when running on kernels (2.6.29 and later)
2789 existed on extremely long-dead PowerPC kernels almost a decade ago.
3063 It's been almost a decade since there have been kernels that don't
4037 reported busy (works on Linux 2.6) kernels. (Addresses Debian Bug
5358 Restrict use of the 2.4 setrlimit ABI f*ckup to kernels between 2.4.10
5520 kernels; the unix IO module will automatically try to set any resource
5550 Work around a bug in 2.4.10+ kernels by trying to unset the filesize
5669 some kernels, I suspect with security enhancement patches.)
6015 filesystem limitation. (Most 2.2 kernels still have a signed int
6451 none" will create a filesystsem compatible with 2.0 kernels.
6523 Linux 2.3 kernels that have renamed i_version to i_generation.
6539 not understood by Linux 2.0 kernels, so they will only allow read-only
6960 people were complaining about breaking compatibility with 1.2 kernels.
6962 the sparse superblock option isn't supported by most kernels yet (1.2
6998 will compile cleanly with 1.2.13 kernels (even with a.out shared
7243 attribute is not yet in production kernels.)
7384 e2fsprogs under Linux 2.0 kernels (as well as late model 1.3 and 1.99
7385 kernels).
7467 Fix to allow e2fsprogs to be compiled on recent 1.3 (pl45+) kernels.
