RE: [dhcwg] RFC 3942 notice: GNU GRUB, DHCP option 150

2005-09-28 Thread Bernie Volz (volz)
should document the historic usage (that option 150 was/is in use). But, they should also request a NEW official IANA assignment. And, IANA obviously can't put option 150 in the pool for future options. Given what we know today, RFC 3942 could certainly have documented more of this, but it also

RE: [dhcwg] RFC 3942 notice: GNU GRUB, DHCP option 150

2005-09-28 Thread C. M. Heard
:07:35 -0500 Bernie Volz replied: Bernie Looks like we now have 3 users of Option 150: Bernie Bernie 1. GNU GRUB Bernie 2. DRAFT-RAJ-DHC-TFTP-ADDR-OPTION-00.TXT Bernie 3. Etherboot In http://www.iana.org/assignments/bootp-dhcp-parameters, however, I see the following: 150 TFTP server address

RE: [dhcwg] RFC 3942 notice: GNU GRUB, DHCP option 150

2005-09-28 Thread C. M. Heard
, they won't be able to use 150. The I-Ds that they write should document the historic usage (that option 150 was/is in use). But, they should also request a NEW official IANA assignment. And, IANA obviously can't put option 150 in the pool for future options. Given what we know today, RFC

Re: [dhcwg] RFC 3942 notice: GNU GRUB, DHCP option 150

2005-03-16 Thread Timothy Legge
Bernie Volz wrote: Looks like we now have 3 users of Option 150: 1. GNU GRUB 2. DRAFT-RAJ-DHC-TFTP-ADDR-OPTION-00.TXT 3. Etherboot Noted. It looks like we all get to apply for a new option code when the process becomes available. Timothy Legge Etherboot Developer

Re: [dhcwg] RFC 3942 notice: GNU GRUB, DHCP option 150

2005-03-16 Thread Ted Lemon
draft describing what you want to do. In the case of GRUB, specifically, what I would suggest is that new versions of GRUB should send a vendor-class-identifier option, and should be prepared to receive a vendor-specific encapsulated option. However, it should also request option 150

Re: [dhcwg] RFC 3942 notice: GNU GRUB, DHCP option 150

2005-03-14 Thread Yoshinori K. Okuji
On Saturday 12 March 2005 06:38 pm, Ted Lemon wrote: I would like to notify that GNU GRUB uses the DHCP option 150, according to RFC 3942. Thanks for the notification. Would you guys be interested in fixing this so that GRUB uses a vendor-encapsulated option, or do you think this usage

RFC 3942 notice: GNU GRUB, DHCP option 150

2005-03-12 Thread Yoshinori K. Okuji
Hello, I would like to notify that GNU GRUB uses the DHCP option 150, according to RFC 3942. GNU GRUB Configuration Path This specifies the path-name that contains a configuration for GNU GRUB. The code for this option is 150. Its minimum length is 1. Code LenConfiguration

Re: [dhcwg] RFC 3942 notice: GNU GRUB, DHCP option 150

2005-03-12 Thread Ted Lemon
On Mar 12, 2005, at 7:25 AM, Yoshinori K. Okuji wrote: I would like to notify that GNU GRUB uses the DHCP option 150, according to RFC 3942. Thanks for the notification. Would you guys be interested in fixing this so that GRUB uses a vendor-encapsulated option, or do you think this usage

Option-150

2002-03-13 Thread Joe LeKostaj
I've got grub PXEing, but it just gets to a grub prompt and disregards the config file i pass it here's the entry i'm using in dhcpd.conf: host fred { hardware ethernet XX:XX:XX:XX:XX:XX; fixed-address XXX.XXX.XXX.XXX; option option-150 grubconfig; filename pxegrub; } both pxegrub

Re: Option-150

2002-03-13 Thread Christoph Plattner
It may be dependent of the TFTP-Server setup, but under normal circumstances you must give the full path to DHCP, especially for the files passed to GRUB (i.e. option-150). So use option option-150 (nd)/tftpboot/grubconfig The (nd) prefix is also important. There are constellations

Prefix `(nd)' in option-150 ...[Fwd: Option-150]

2002-03-13 Thread Christoph Plattner
Hello Mr. Okuji, I have not analysed the contents of the documentation yet in this detail, but is there mentioned, that the string passed over via `option-150' (TAG 150) should include the `(nd)' prefix. As described in the mail (see below), there are constellations, where a missed `(nd)' can

Re: DHCP option 150 = config file (untested)

2000-06-07 Thread OKUJI Yoshinori
From: Chip Salzenberg [EMAIL PROTECTED] Subject: Re: DHCP option 150 = config file (untested) Date: Tue, 6 Jun 2000 20:16:19 -0700 According to Christoph Plattner: I'm not sure, if Mr. Salzenberg's implementation is correct. I don't know, if the BOOTP record uses '\0' termnated strings

Re: [PATCH] DHCP option 150 = config file (untested)

2000-06-06 Thread OKUJI Yoshinori
From: Chip Salzenberg [EMAIL PROTECTED] Subject: [PATCH] DHCP option 150 = config file (untested) Date: Mon, 5 Jun 2000 19:38:46 -0700 Here's a so-far-untested patch that should make GRUB use BOOTP/DHCP vendor attribute 150 to specify the name of the configuration file to use. Thanks

Re: [PATCH] DHCP option 150 = config file (untested)

2000-06-06 Thread Christoph Plattner
Yoshinori wrote: From: Chip Salzenberg [EMAIL PROTECTED] Subject: [PATCH] DHCP option 150 = config file (untested) Date: Mon, 5 Jun 2000 19:38:46 -0700 Here's a so-far-untested patch that should make GRUB use BOOTP/DHCP vendor attribute 150 to specify the name of the configuration file to use

[PATCH] DHCP option 150 = config file (untested)

2000-06-05 Thread Chip Salzenberg
Here's a so-far-untested patch that should make GRUB use BOOTP/DHCP vendor attribute 150 to specify the name of the configuration file to use. --- 2000-06-05 Chip Salzenberg [EMAIL PROTECTED] * netboot/etherboot.h