From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] OK, cpu server is up.
Date: Fri, 25 Apr 2003 16:32:16 +0100 [thread overview]
Message-ID: <58df166ed4fcec6132f6342836a11b23@vitanuova.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304250836140.8939-100000@maxroach.lanl.gov>
i did check that it can indeed make such an entry (eg, dhcpd.c:/^arpenter) and that
it called it in plausible places (eg):
if(bp->htype == 1)
arpenter(up->raddr, bp->chaddr);
i was fairly sure that the surrounding conditionals
had it called in response to a 9load packet because it
was only prevented if the request was
gatewayed by some intervening device,
or the bootp (sorry, dhcp) flags said `broadcast',
but 9load sets them to 0.
prev parent reply other threads:[~2003-04-25 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 19:40 ron minnich
2003-04-25 1:30 ` okamoto
2003-04-25 4:49 ` andrey mirtchovski
2003-04-25 14:03 ` ron minnich
2003-04-25 13:56 ` ron minnich
2003-04-25 14:30 ` Charles Forsyth
2003-04-25 14:38 ` ron minnich
2003-04-25 15:10 ` David Presotto
2003-04-25 15:32 ` C H Forsyth [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=58df166ed4fcec6132f6342836a11b23@vitanuova.com \
--to=forsyth@vitanuova.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).