To be clear: it's not a vfat issue: vfat just determines where the file limit is, but as didier comments in bug 63900, the actual generation of SIGXFSZ upon /encountering/ file size limits is a default thing, and is found in mm/filemap.c (the one generated for exceeding rlimits is SUS- mandated and should remain: IMO, the others should be removed, leaving just the return of -EFBIG).
-- cp dumps core when copying >4GB files to a VFAT filesystem https://bugs.launchpad.net/bugs/75574 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
