From: "James A. Robinson" <jim.robinson@stanford.edu>
To: "sam Fans" <sam-fans@hawkwind.utcs.toronto.edu>
Subject: large file in sam?
Date: Thu, 14 Oct 1999 10:03:40 -0400 [thread overview]
Message-ID: <199910141403.HAA11298@highwire.stanford.edu> (raw)
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)
next reply other threads:[~1999-10-15 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-14 14:03 James A. Robinson [this message]
1999-10-15 11:19 Bengt Kleberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199910141403.HAA11298@highwire.stanford.edu \
--to=jim.robinson@stanford.edu \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).