Re: GNU tar problem
- From: mojaveg@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx (Everett M. Greene)
- Date: Tue, 26 Feb 2008 10:44:13 PST
Hans-Bernhard_Br=F6ker?= <HBBroeker@xxxxxxxxxxx> writes:
Everett M. Greene wrote:
Hans-Bernhard_Br=F6ker?= <HBBroeker@xxxxxxxxxxx> writes:
That set aside, even if you think the failure happens regardless of the
file it's told to archive, that doesn't mean we can actually read your
mind over the internet to see what the actual commands passed to that
ancient version of 'tar' might have been.
Why did you not this? Do you seriously expect people to be able to
help without seeing any actual command line input or error message
output from that mysterious, anonymous "tar" you're referring to?
I have numerous canned processes that I've used for years and now
they don't work at all.
And you consider them so sacred that you can't show any of them?
And 'bit rot' is quite a lot less likely the reason than a superficially
unrelated change to your system having changed what actually gets
executed when you call "tar" on the command line.
I've found a later version of tar that I can try except
that the developer of the update decided to package the
components as a tar file.
You missed my point. You say that "now" it no longer works --- so
something must have changed between "then" and "now". Since you left us
with nothing to work on, you'll have to find out yourself what that
something is. It may help to start with "when?", then proceed to "what
did I do then?"
It can hardly be bit rot of the software itself, so the change is
probably in your system enviromnent. E.g. you could unknowingly have
installed *another* program also called "tar", which now gets called
under that name, but does a totally different job, or expect options in
a different format. Or you could have changed the system-wide presets
of your tar program.
I presented the question to see if anyone hard ever encountered
such a problem in the past and jog their memory as to what they
had encountered when the problem arose. I wasn't expecting
anyone to have detailed trouble-shooting answers so I didn't
bother to include specific commands.
FWIW: The only command I ever use is:
tar -c -f <tar file name> -T <file list>
A little digging in the source finds that tar is looking at
file protection/permission bits to determine a file's "type".
I produced a quicky program to see what the stat() function
is obtaining. All the files I'm trying to archive show the
expected rwed bits set along with a bit indicating that they
are "regular" files. How this can be a wrong "file type" is
mystifying.
[Late news: I had a copy of the Gnu tar source so I built a
copy of tar with it with the idea of being able to use a
debugger to get a better handle on the nature of the problem.
When I ran it, it worked without a problem. So the problem
is "resolved" although I don't know why the version I've
been using for so long has suddenly failed.]
.
- Follow-Ups:
- Re: GNU tar problem
- From: CBFalconer
- Re: GNU tar problem
- Prev by Date: Re: Best place to ask dumbish C questions?
- Next by Date: Re: ARM9 Choice
- Previous by thread: PC104 ISA bus.
- Next by thread: Re: GNU tar problem
- Index(es):
Relevant Pages
|
