The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] unix v5 limitations
Date: Sat, 9 Aug 2014 11:04:39 -0400	[thread overview]
Message-ID: <20140809150439.GC13364@mercury.ccil.org> (raw)
In-Reply-To: <CADxT5N4cYkw_p9n=_v02TexgkB2TKMKf+Dqgbzz_i79kB3tgyg@mail.gmail.com>

Mark Longridge scripsit:

> 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"
> so I figured I would just create an archive file called all.a which
> would include all the files in /usr/source/s1 and copy that over.

That is not a cp error: it is the kernel reporting that the limited
amount of space in userland reserved for command arguments on an exec()
has been exceeded.  It can still happen in modern systems if directories
are exceedingly large.

> But then I got "phase error" when I tried to keep adding files to the
> archive 

"Phase error" means that a file has been modified while "ar" is working
on it.  The most common reason (which doesn't seem to be relevant in
this case) is that "ar" is trying to archive the archive.

> ar u all.a /usr/source/s1/b*

If that worked, then "cp /usr/source/s1/b* ." would work too.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan at ccil.org
I am expressing my opinion.  When my honorable and gallant friend is
called, he will express his opinion.  This is the process which we
call Debate.                   --Winston Churchill



  reply	other threads:[~2014-08-09 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09 14:37 Mark Longridge
2014-08-09 15:04 ` John Cowan [this message]
2014-08-09 15:32 Noel Chiappa
2014-08-10 23:05 ` Sven Mascheck

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=20140809150439.GC13364@mercury.ccil.org \
    --to=cowan@mercury.ccil.org \
    /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).