From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: [9fans] updated 9load
Date: Wed, 8 Sep 2004 16:53:39 -0400 [thread overview]
Message-ID: <b26efe6c577ac1e9246a1dc154ed059f@plan9.bell-labs.com> (raw)
I've put a new version of 9load on sources.
The two main changes are
1) a driver for the Intel GbE cards, courtesy of Geoff Collyer;
2) 9pxeload will now try to get configuration info from a file on
a TFTP server.
Let me know if there are any problems with it.
--jim
reply other threads:[~2004-09-08 20:53 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=b26efe6c577ac1e9246a1dc154ed059f@plan9.bell-labs.com \
--to=jmk@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).