Path: utzoo!attcan!uunet!ogicse!uwm.edu!zaphod.mps.ohio-state.edu!usc!wuarchive!texbell!splut!jay From: jay@splut.conmicro.com (Jay "you ignorant splut!" Maynard) Newsgroups: comp.unix.microport Subject: Re: V/AT2.3 Hard Disk File Size Limit? Message-ID: Date: 23 Feb 90 00:32:38 GMT References: <8815@wpi.wpi.edu> Reply-To: jay@splut.conmicro.com (Jay "you ignorant splut!" Maynard) Organization: Confederate Microsystems, League City, TX Lines: 22 In article <8815@wpi.wpi.edu> markc@wpi.wpi.edu (Mark B. Cohen) writes: >I keep encountering what appears to be an intrinsic file >size limit on hard disk files: Any attempt by any program >to write a file larger than 1,228,800 bytes fails. This isn't a bug, it's a feature...officially, according to AT&T. Look up 'ulimit' in the book. Microport made it relatively simple to change: As root, say 'patch /unix ulpatch 0x7fff'. This will raise the ulimit to 32K 512-byte blocks (I think...maybe it's 32K 1K-byte blocks). In any case, the largest file on my system is in the 3.5 meg range, so that has worked well for me. General question: Is that number signed or unsigned? Can I get away with 0xffff, or will it cause problems? -- Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can jay@splut.conmicro.com (eieio)| adequately be explained by stupidity. {attctc,bellcore}!texbell!splut!jay +---------------------------------------- Free the DC-10!