Bug 63900 has some discussion regarding blocking/handling SIGXFSZ. I'm convinced that handling this signal is the right way to fix it; patching vfat to not generate the signal isn't appropriate, as other filesystems may still cause this.
IMO, SIGXFSZ should never have been given a default behavior to dump core; but now that that's been established (in BSD?), we can't do much about that. :-/ The commentor on bug 63900 is right that it's stupid to expect the writers of all tools to deal with this signal (grossly paraphrased), but we don't really have a choice now. :( -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
