9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Corrupted file entry on QEMU - how to recover?
Date: Fri, 11 Jan 2008 17:29:23 -0500	[thread overview]
Message-ID: <9992EA73-642B-40FE-A5AC-E347D762F633@mac.com> (raw)
In-Reply-To: <621A9C41-8FF8-421E-B3C1-294A1EEDCA19@mac.com>

That part was missing some lines, so I decided to start over. This  
time, an AWK script is used:

	awk '
	/^fn unt[gb]z/ { p(); next; pr(); }
	/^fn df/ { pr(); next; pr(); }
	/^\.C$/ { pr() }
	function pr() { print NR, $0 }' hd.raw

untgz and untbz are functions that extract .tar.gz/.tgz  
and .tar.bz2/.tbz files automatically. df shows the disk usage. .C is  
the macro in my book for a chapter (one of the lines that was  
missing). I tell AWK to print the multi-line functions (with line  
numbers).

On Jan 11, 2008, at 3:47 PM, Pietro Gagliardi wrote:

> I got that done and did a test run. I found a book I was working  
> on! :-)
>
> On Jan 11, 2008, at 3:01 PM, Pietro Gagliardi wrote:
>
>> I decided to stop doing this with Plan 9 and decided to do it from  
>> within Mac OS X. I'm running Plan 9 atop QEMU, which is  
>> implemented as a program called Q (http://www.kju-app.org/). The  
>> first step was to convert the compressed QCOW hard disk image to a  
>> raw one for analysis:
>>
>> 	$ /Applications/Q.app/Contents/MacOS/qemu-img convert ~/Documents/ 
>> QEMU/Plan\ 9\ from\ Bell\ Labs.qvm/Harddisk_1.qcow2 -O raw ~/ 
>> Desktop/hd.raw
>>
>> When that is done, I'll examine hd.raw in a text editor and get my  
>> files back.
>>
>


      reply	other threads:[~2008-01-11 22:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16  2:48 Pietro Gagliardi
2007-12-16  9:10 ` Skip Tavakkolian
2007-12-16 14:22   ` Pietro Gagliardi
2007-12-16 16:25     ` erik quanstrom
2007-12-16 16:54       ` Pietro Gagliardi
2007-12-16 17:25         ` erik quanstrom
2007-12-16 23:57           ` Pietro Gagliardi
2007-12-17  1:34           ` Pietro Gagliardi
2007-12-17  1:36             ` Pietro Gagliardi
2007-12-17  1:42               ` erik quanstrom
2007-12-17  1:57                 ` Pietro Gagliardi
2007-12-17 19:24                   ` john
2007-12-17 21:10                     ` Pietro Gagliardi
2007-12-18 18:13                       ` erik quanstrom
2007-12-18 18:19                         ` erik quanstrom
2007-12-19 21:02                 ` Pietro Gagliardi
2007-12-20  1:15                   ` Juan M. Mendez
2007-12-20  1:52                     ` Pietro Gagliardi
2007-12-20  2:02                       ` erik quanstrom
2007-12-20  2:10                         ` Pietro Gagliardi
2007-12-20 19:58                           ` Pietro Gagliardi
2007-12-22 22:29                             ` Pietro Gagliardi
2007-12-23  2:35                               ` Bakul Shah
2007-12-27 16:23                               ` Russ Cox
2007-12-29 16:33                                 ` Pietro Gagliardi
2007-12-29 19:06                                   ` Pietro Gagliardi
2008-01-01  1:37                                 ` Pietro Gagliardi
2008-01-11 20:01                                   ` Pietro Gagliardi
2008-01-11 20:47                                     ` Pietro Gagliardi
2008-01-11 22:29                                       ` Pietro Gagliardi [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=9992EA73-642B-40FE-A5AC-E347D762F633@mac.com \
    --to=pietro10@mac.com \
    --cc=9fans@cse.psu.edu \
    /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).