From: Sam Ducksworth <sam@ducksworth.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] worm problems
Date: Sun, 9 Dec 2001 17:52:26 -0600 [thread overview]
Message-ID: <Pine.BSF.4.33.0112091751400.80396-100000@lucifer.ducksworth.com> (raw)
In-Reply-To: <20011209220338.9EE0D199EC@mail.cse.psu.edu>
russ,
ok here is what i get with that command:
....
0000ff0 02 00 00 00 05 00 00 00 00 00 01 00 02 00 00 00
0001000
0001000
the last six bytes are just as you said.
--sam
On Sun, 9 Dec 2001, Russ Cox wrote:
> try
> dd -bs 4096 -count 1 -skip 2 < /dev/sdC0/data | xd -b | tail -10
>
> to get the end of the superblock, where the "header" is.
> if i'm reading the code right, the last six bytes should be
> 01 00 02 00 00 00
>
> the 01 00 is 0x0001 - the Tsuper tag; 02 00 00 00 is the
> block address: 2.
>
>
--sam
next prev parent reply other threads:[~2001-12-09 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 22:03 Russ Cox
2001-12-09 23:52 ` Sam Ducksworth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-09 17:45 Russ Cox
2001-12-09 19:44 ` Sam Ducksworth
2001-12-09 13:47 Sam Ducksworth
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=Pine.BSF.4.33.0112091751400.80396-100000@lucifer.ducksworth.com \
--to=sam@ducksworth.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).