From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] fossil
Date: Tue, 4 Jan 2005 05:37:45 +1100 [thread overview]
Message-ID: <775b8d1905010310375d31b770@mail.gmail.com> (raw)
ok. it's happened again. i have a buggered fossil on a machine
that uses fossil as its root. (corrupted superblock). i have no idea
how it happened. i guess the obvious is to rebuild the machine
with an extra disk and cd-rom and boot from that and poke around.
any chances of retrieving the significant work i've done since the
last venti snap?
brucee
next reply other threads:[~2005-01-03 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 18:37 Bruce Ellis [this message]
2005-01-03 18:51 ` Russ Cox
2005-01-04 17:42 ` Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2024-05-17 16:16 [9fans] Interoperating between 9legacy and 9front Noam Preil
2024-05-18 19:08 ` [9fans] fossil Richard Miller
2009-06-04 9:29 Charles Forsyth
2009-06-04 19:25 ` erik quanstrom
2004-06-12 3:12 Russ Cox
2004-03-20 2:27 David Presotto
2003-04-15 5:26 Andrew
2003-04-15 15:12 ` Russ Cox
2003-04-15 21:00 ` Andrew
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=775b8d1905010310375d31b770@mail.gmail.com \
--to=bruce.ellis@gmail.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).