Re: finding a tarball on a fat-less fat partition--disk editor? (fwd)

[dochawk@psu.edu]

to: du
reply-to: dochawk@psu.edu, debian-user@lists.debian.org
from: dochawk@psu.edu
Subject: Re: finding a tarball on a fat-less fat partition--disk editor?
In-reply-to: Your message of "Fri, 15 Sep 2000 19:28:34 EDT."
             <[🔎] 20000915192834.A15761@nowonder.com>
References: <[🔎] 200009151503.e8FF3ee10118@fac13.ds.psu.edu> <[🔎] 20000915224602.B5189@ugly.wh8.tu-dresden.de> <[🔎] 200009152228.e8FMSUe30421@fac13.ds.psu.edu> <[🔎] 20000916010038.A7133@ugly.wh8.tu-dresden.de> <[🔎] 20000915192834.A15761@nowonder.com>
Mime-Version: 1.0

> A tar file comes in blocks of 512 bytes.  First is the filename and
> then comes other things including the word "ustar".  After this header
> comes the file and then comes many more header/file combinations.  So
> you should see "ustar" as many times as there are files in your tar
> file.

> If you want all the gory details, download the tar source package and
> read tar.h.  

yikes, I can do without the gory details :)  does this mean that once I 
find a block of a tar, I can start extracting, even if it wasn't the 
middle?

And now that I think of it, someone mentioned that there are bad disk 
editors available for linux. I just realized that I can't use the same 
method I sed on an ext2 on a fat (unless it grew inodes while I wasn't 
looking :)

Or should I just start using "dd if=/dev/hda7 skip=1| tar -tvf -" and 
incrementing the skip until I hit something (I think these two files 
would be the only ones ever to be created on that partition).

thanks

hawk


--