From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] old fossil vac scores
Date: Wed, 26 Mar 2003 11:53:21 -0500 [thread overview]
Message-ID: <8ba9e468e9c44a75d96622c16f128e1a@plan9.bell-labs.com> (raw)
In-Reply-To: <9df4e1d4b9e0540a04c965b1cf3fc138@plan9.escet.urjc.es>
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
Also you can do
fn h2d { echo 'ibase=16;' print `{echo $1|tr a-z A-Z} |bc }
header=`{dd -bs 1024 -iseek 128 -count 1 -if /dev/sdC0/fossil | xd -b | sed 1q}
bsize=`{h2d $header(8)^$header(9)}
super=`{h2d 0$header(10)^$header(11)^$header(12)^$header(13)}
dd -bs $bsize -iseek $super -count 1 -if /dev/sdC0/fossil | xd -b |
sed '1,2d;3s/^....... .. .. //;4s/^....... (.. .. .. .. .. ..).*/\1/;4q' | tr -d ' '
to get the most recent one, though I like nemo's way better.
[-- Attachment #2: Type: message/rfc822, Size: 2954 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 152 bytes --]
I use the vac command from fossilcons(8)
to print (lp ☺) the vac numbers when I dump the
venti arenas to cdroms.
I think that does what you want.
[-- Attachment #2.1.2: Type: message/rfc822, Size: 1187 bytes --]
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: [9fans] old fossil vac scores
Date: Wed, 26 Mar 2003 16:38:32 0000
Message-ID: <233d7344eb001abe8b9a41684c738596@vitanuova.com>
is it possible to find out a vac score that was printed
out previously from snap -a and not recorded?
next prev parent reply other threads:[~2003-03-26 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 16:38 rog
2003-03-26 16:37 ` Fco.J.Ballesteros
2003-03-26 16:53 ` Russ Cox [this message]
2003-03-26 17:53 rog
2003-03-26 18:19 ` Fco.J.Ballesteros
2003-03-26 19:21 rog
2003-03-27 3:26 ` Russ Cox
2003-03-27 8:49 ` Fco.J.Ballesteros
2003-03-27 13:51 ` Russ Cox
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=8ba9e468e9c44a75d96622c16f128e1a@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).