From: Fernan Bolando <fernanbolando@mailc.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] unvac troubles...
Date: Fri, 21 Aug 2009 15:43:21 +0800 [thread overview]
Message-ID: <1d5d51400908210043w742ea31dke12c445079335b64@mail.gmail.com> (raw)
In-Reply-To: <f75780240908202315o7bb8e0ecq88afd4c3c9723ed5@mail.gmail.com>
On Fri, Aug 21, 2009 at 2:15 PM, Venkatesh Srinivas<me@acm.jhu.edu> wrote:
> Hi,
>
> I'm using unvac to try to extract some vac archives I made in the fall
> of 2008. I'm running into a pair of problems.
>
> First, unvac is outputting directories with the write bit off. This
> causes it to fail pretty early, as it can't write files to the
> newly-extracted directories. Is this expected? Is there a way to avoid
> this problem?
This happens to me too. I usually just delete the old directory and
extract again.
fernan
--
http://www.fernski.com
prev parent reply other threads:[~2009-08-21 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 6:15 Venkatesh Srinivas
2009-08-21 7:43 ` Fernan Bolando [this message]
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=1d5d51400908210043w742ea31dke12c445079335b64@mail.gmail.com \
--to=fernanbolando@mailc.net \
--cc=9fans@9fans.net \
/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).