Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.sys.amiga.applications
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion GNU tar problem
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Albert van der Horst  
View profile  
 More options Feb 27 2008, 10:00 am
Newsgroups: comp.sys.amiga.applications, comp.arch.embedded
From: Albert van der Horst <alb...@spenarnc.xs4all.nl>
Date: 27 Feb 2008 15:00:18 GMT
Local: Wed, Feb 27 2008 10:00 am
Subject: Re: GNU tar problem
Print | View thread | Show original | Report this message | Find messages by this author
In article <20080224.7A2CB78.8...@mojaveg.lsan.mdsg-pacwest.com>,
Everett M. Greene <moja...@mojaveg.lsan.mdsg-pacwest.com> wrote:

>I've been using a 1998 version of Gnu tar for years and
>it has worked fine.  Recently, it has started balking at
>working correctly.  It's suffering from bit rot with age?

>The specific problem is that (almost) regardless of the
>file it's told to archive, it returns an error message
>of "<file name>: Unknown file type; file ignored."
>What's really mystifying is how a file can be of the
>wrong type for tar since tar shouldn't be concerned
>with a file "type".  [I strongly suspect the error
>message is erroneous.]

This is not true.
tar is very much aware of what type of file it handles and
treats normal files, directory files, symbolic links,
network mounts, char special devices etc. all differently.
So if it cannot find out whether or not a certain file
is a directory, it has every right to complain.

The first thing you should do is type
        file <file name>
for offending files, and see what happens.
Chances are that ``file'' comes with the same message and
your trouble is not with tar.

>Has anyone else encountered this problem?

Some ways I can imagine to have this is creating an invalid
device, severe file system corruption or a botched network.

Groetjes Albert

--
--
Albert van der Horst, UTRECHT,THE NETHERLANDS
Economic growth -- like all pyramid schemes -- ultimately falters.
albert@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google