* /proc/net/bootpc support for non-ASCII vendor specific tags?
@ 2002-10-04 17:17 Chris Friesen
2002-10-04 18:11 ` Chris Friesen
0 siblings, 1 reply; 2+ messages in thread
From: Chris Friesen @ 2002-10-04 17:17 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: /proc/net/bootpc support for non-ASCII vendor specific tags?
2002-10-04 17:17 /proc/net/bootpc support for non-ASCII vendor specific tags? Chris Friesen
@ 2002-10-04 18:11 ` Chris Friesen
0 siblings, 0 replies; 2+ messages in thread
From: Chris Friesen @ 2002-10-04 18:11 UTC (permalink / raw)
To: linux-kernel
Friesen, Christopher [CAR:7Q26:EXCH] wrote:
> 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?
Bah...I just realized I can use hexdump to get the raw data. Sorry to
bother you all, return to your regularly scheduled activities.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-10-04 18:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-10-04 17:17 /proc/net/bootpc support for non-ASCII vendor specific tags? Chris Friesen
2002-10-04 18:11 ` Chris Friesen
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.