From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Quick question on fossil
Date: Tue, 13 Jan 2009 18:03:44 -0800 [thread overview]
Message-ID: <1231898624.15698.95.camel@goose.sun.com> (raw)
In-Reply-To: <dd6fe68a0901121106h79474132ra2b461d8389ab259@mail.gmail.com>
On Mon, 2009-01-12 at 11:06 -0800, Russ Cox wrote:
> Super.active is the block number of a VtDirType block:
> a block containing a few (I think 3) VtEntry structs.
Turns out there's one extra level of indirection there,
but your response was exactly what I needed to get
me unstuck. Thanks!
> cd /sys/src/cmd/fossil
> mk 8.view
> 8.view /dev/sdC0/fossil
>
> you should get a graphical file system data structure
> browser, though since it is not part of the default
> build it may not need some work to make
> it build again.
Wow! Thanks a bunch for mentioning that. It builds and
works flawlessly. What a treat!
Thanks,
Roman.
prev parent reply other threads:[~2009-01-14 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 18:13 Roman V. Shaposhnik
2009-01-12 19:06 ` Russ Cox
2009-01-14 2:03 ` Roman V. Shaposhnik [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=1231898624.15698.95.camel@goose.sun.com \
--to=rvs@sun.com \
--cc=9fans@9fans.net \
/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).