On Sun, Nov 18, 2001, Miki Shapiro wrote about "2Gig filesize limit problem....": >... > SuSE Linux 7.0 > Custom-tailored 2.4.9 kernel > Absolutely latest reiserfs binaries (from yesterday - the 3.x... version) > shell-limit (limit/unlimit) filesize removed > If it matters, the partition was created by the new mkreiserfs util. > > Is there ***ANY*** document at all that thoroughly explains how to make > a system compliant with 2+gig files (unlike what's on www.suse.de which > explains which version of SuSE I need to run with it's default kernel for > it to work). I didn't find scratch on linuxdoc.org... >...
I never had the opportunity to get annoyed by this problem (I never needed such huge single files...), but I do remember that the open(2) system call got a O_LARGEFILE option that you must pass in order to open files larger than exactly that 2 GB limit. I assume that new GNU fileutils and other applications that use files (SuSE 7.0 isn't the latest version, right?) were modified to add this flag. Or, maybe someone knows, were the latest version of glibc modified to add this flag even if the user doesn't pass it? If not, how on earth do you get fopen to open a file like this, without open(2)ing it yourself and using fdopen? What is the downside of using this flag all the time, anyway? -- Nadav Har'El | Sunday, Nov 18 2001, 3 Kislev 5762 [EMAIL PROTECTED] |----------------------------------------- Phone: +972-53-245868, ICQ 13349191 |Deja Moo: The feeling that you've heard http://nadav.harel.org.il |this bull before. ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
