From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: [9fans] 9load interrupt 14
Date: Fri, 16 Nov 2007 19:06:23 -0500 [thread overview]
Message-ID: <cccd9617c2680f7dd67b71fb390dfbc9@quanstro.net> (raw)
i finally ran into this problem today when setting up a machine to
boot standalone. the problem was that 9load was updated and no
longer contiguous. dossrv(4) has more information but generally
using format(8) is a safer than using dossrv when dropping in a
new 9load.
- erik
reply other threads:[~2007-11-17 0:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cccd9617c2680f7dd67b71fb390dfbc9@quanstro.net \
--to=quanstro@quanstro.net \
--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).