From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] unix v5 limitations
Date: Sat, 9 Aug 2014 11:32:02 -0400 (EDT) [thread overview]
Message-ID: <20140809153202.AB1CE18C0AC@mercury.lcs.mit.edu> (raw)
> From: Mark Longridge <cubexyz at gmail.com>
> The first problem I had was I couldn't just cp over all the
> /usr/source/s1 files to the new drive because of "Arg list too long"
John Cowan nailed this; as an aside, I don't know about V5, but in vanilla V6
the entire argument list had to fit into one disk buffer (I would assume V5 is
the same).
The PWB changes to v6 included a rewrite of exec() to accumulate the argument
list in swap space, so it could be much longer; the maximum length was a
parameter, NCARGS, which was set to 5120 (10 blocks) by default.
Noel
next reply other threads:[~2014-08-09 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 15:32 Noel Chiappa [this message]
2014-08-10 23:05 ` Sven Mascheck
-- strict thread matches above, loose matches on Subject: below --
2014-08-09 14:37 Mark Longridge
2014-08-09 15:04 ` John Cowan
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=20140809153202.AB1CE18C0AC@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.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).