* Vagrant Cascadian [Son Jun 20, 2010 at 07:11:41 -0700]:
> On Sat, Jun 19, 2010 at 06:43:16PM +0200, maximilian attems wrote:
> > On Tue, 08 Jun 2010, Michael Prokop wrote:
> > > * Vagrant Cascadian <firstname.lastname@example.org> [Mit Dez 17, 2008 at 07:01:51 -0800]:
> > > > please consider the attached patch, which adds boot prompt parameters for two
> > > > of ipconfig's commandline options in the configure_networking function:
> > > > - using an alternate DHCP port (dhcpport=NNN, ipconfig -p NNN)
> > > > - specifying the vendor-class-identifier (dhcpvci=XXX, ipconfig -i XXX)
> perhaps it would be better to rewrite in such a way that ipconfig could be
> passed arbitrary arguments? of course, if it ever switched away from ipconfig
> to some other dhcp client, it'd be nice to not have to change syntax or
> configuration names...
> > I do not see so much the point of setting ipconfig vendor class id.
> > why would that be needed for booting?
> in order to distinguish a machine that's doing network boot for
> debian-installer, LTSP or PXE. for example, in each case, you might want to
> hand it a different dhcp filename option. pxe should get pxelinux.0, d-i gets a
> preseeding URL, and ltsp could get a configuration file...
> > the alternate DHCP port looks indeed more interesting, but no idea
> > how common that is in the wild?
> i don't know that it's incredibly common, but is not infrequently asked for in
> LTSP environments, though there are other alternatives using dnsmasq's dhcp
> proxy support now, so it's maybe less important.
> > and if there is not a place in the ip= monster bootparam?
> don't believe so.
Hm, so again no one took care of that for another "period of time".
I'm sorry, Vagrant.
This patch is non-intrusive, but I'd still vote for non-inclusion as
of today since it depends on ipconfig and not too much people seem
to really care about it.
If someone still thinks it should be included please stand up.
maximilian, please comment.