From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: /proc/net/bootpc support for non-ASCII vendor specific tags?
Date: Fri, 04 Oct 2002 13:17:22 -0400 [thread overview]
Message-ID: <3D9DCD22.4070205@nortelnetworks.com> (raw)
Currently it appears that /proc/net/bootpc assumes that all reserved
vendor specific tags contain ASCII information. Is this part of the
BOOTP standard? I hadn't thought so, but maybe I'm missing something.
Assuming that binary information is allowable, would a patch printing
out tags 128-254 of the vendor specific information as raw hex
characters be considered acceptable/useful?
I need this for my own purposes, and I'm just wondering if I should
bother trying to push it up.
Chris
next reply other threads:[~2002-10-04 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 17:17 Chris Friesen [this message]
2002-10-04 18:11 ` /proc/net/bootpc support for non-ASCII vendor specific tags? Chris Friesen
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=3D9DCD22.4070205@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.