From: will.senn@gmail.com (Will Senn)
Subject: [TUHS] tar on v6 not creating directories on v6
Date: Sat, 12 Dec 2015 17:10:11 -0600 [thread overview]
Message-ID: <566CA953.3020207@gmail.com> (raw)
In-Reply-To: <20151212222358.GD5686@server.rulingia.com>
On 12/12/15 4:23 PM, Peter Jeremy wrote:
> On 2015-Dec-12 15:53:54 -0600, Will Senn <will.senn at gmail.com> wrote:
>> That was ugly and all of it was output. What exactly did I wind up with?:
>> # ls -l
>> total 19
>> drwxrwxrwx 2 root 32 Oct 10 12:54 y
>> -rw-rw-rw- 1 root 8704 Oct 10 12:54 t.tar
>>
>> Ugh. Probably don't need the y directory...
>> # rmdir y
>> y ?
>> # ls y
>> y not found
> Presumably, it's not 'y' but has some non-printable characters in it.
> You could try "od -c ." to see what the entry actually is, or move
> t.tar out of the way and "rm -r" remove the next level up.
>
It looks like you are correct about it not being 'y':
# od -c .
0000000 I \? . \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
0000020 \? \0 . . \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
0000040 K \? t . t a r \0 \0 \0 \0 \0 \0 \0 \0 \0
0000060 N \? \? \? \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
0000100
I moved t.tar out and then tried rm -r, it complained (t is the parent):
# rm -r t
No match
I don't think rm -r will delete directories, but only the files in the
directory.
>> I think this error is simply an effect related to the failure to create
>> the necessary directories properly.
> If you run "mkdir foo" from the shell, does it work properly? That will
> let you split between the problem being in tar and the problem being in
> mkdir. Adding some printf()s to checkdir() seems a reasonable step.
>
Yes, mkdir foo works. I'll add the print statements.
Thanks,
will
next prev parent reply other threads:[~2015-12-12 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 21:53 Will Senn
2015-12-12 22:23 ` Peter Jeremy
2015-12-12 23:10 ` Will Senn [this message]
2015-12-13 4:50 ` Will Senn
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=566CA953.3020207@gmail.com \
--to=will.senn@gmail.com \
/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).