From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from highwire.stanford.edu ([171.64.249.40]) by hawkwind.utcs.utoronto.ca with SMTP id <25694>; Fri, 15 Oct 1999 02:50:58 -0400 Received: from aubrey.stanford.edu (aubrey.Stanford.EDU [36.48.0.102]) by highwire.stanford.edu (8.8.5/8.7.1) with ESMTP id HAA11298 for ; Thu, 14 Oct 1999 07:03:41 -0700 (PDT) Message-Id: <199910141403.HAA11298@highwire.stanford.edu> X-url: http://highwire.stanford.edu/~jimr/ X-face: "!ZH^<"U,NeU:732A To: "sam Fans" Subject: large file in sam? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19370.939909820.1@aubrey.stanford.edu> Date: Thu, 14 Oct 1999 10:03:40 -0400 Sender: jimr@aubrey.stanford.edu >From my reading of Pike's main paper on sam, I got the impression that sam could handle very large files. I thought it only read in the blocks being worked on, as it needed access to them. I find that when I try and open an 80mb text file, I get a message 'write: ?I/O error: "Success"', and no file appears. =( Anyone know if this is just a limitation of the sam port to linux? Or if there is some way around the problem (other than split(1)!)? Jim - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - James A. Robinson jim.robinson@stanford.edu Stanford University HighWire Press http://highwire.stanford.edu/ 650-723-7294 (W) 650-725-9335 (F)