From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dhcpd and other CPU server fun.
Date: Mon, 21 Apr 2003 07:34:18 +0100 [thread overview]
Message-ID: <c6ed00697e5ed20a4dff5da2d181ac92@9fs.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0304210003180.15159-100000@maxroach.lanl.gov>
> Now I'm curious. There is no entry in the standard DHCP packet for custom
> entries like auth and fs, right? I've read the DHCP RFCs and it seems not
> flexible enough for arbitrary named parameters, but maybe I misread it.
>
There is indeed a vendor extensions section in bootp (which dhcp is an
extension of) which Plan 9 uses for this purpose. Right click on this:
/sys/src/cmd/ip/dhcpd/dhcpd.c:/add plan9 specific options/
next prev parent reply other threads:[~2003-04-21 6:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 6:14 ron minnich
2003-04-21 6:34 ` nigel [this message]
2003-04-21 12:09 ` David Presotto
2003-04-21 16:02 ` ron minnich
2003-04-21 14:29 ` 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=c6ed00697e5ed20a4dff5da2d181ac92@9fs.org \
--to=nigel@9fs.org \
--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).