patches also available in a git branch:

http://dev.freegeek.org/~vagrant/git/initramfs-tools/

live well,
vagrant



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

* Vagrant Cascadian <vagrant+debianbugs@freegeek.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)

> supporting these options gives additional flexibility in distinguishing thin
> clients from conventional workstations in a mixed network.

Sorry that no one took care of your bugreport for so long, Vagrant.
Patch looks fine to me.

maks, any objections against inclusion of the patches?

regards,
-mika-

On Tue, 08 Jun 2010, Michael Prokop wrote:

> * Vagrant Cascadian <vagrant+debianbugs@freegeek.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)
>
> > supporting these options gives additional flexibility in distinguishing thin
> > clients from conventional workstations in a mixed network.
>
> Sorry that no one took care of your bugreport for so long, Vagrant.
> Patch looks fine to me.
>
> maks, any objections against inclusion of the patches?

I had been dragging that patch as I do not like to add to many
bootparams that are outside of documented upstream linux-2.6 handling
and thus initramfs-tools specific. waited to see if a second voice
would raise..

I do not see so much the point of setting ipconfig vendor class id.
why would that be needed for booting?

the alternate DHCP port looks indeed more interesting, but no idea
how common that is in the wild? and if there is not a place in the
ip= monster bootparam?

thanks

--
maks



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100619164316.GC24243@stro.at">http://lists.debian.org/20100619164316.GC24243@stro.at

On Sat, 2010-06-19 at 18:43 +0200, maximilian attems wrote:
> On Tue, 08 Jun 2010, Michael Prokop wrote:
>
> > * Vagrant Cascadian <vagrant+debianbugs@freegeek.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)
> >
> > > supporting these options gives additional flexibility in distinguishing thin
> > > clients from conventional workstations in a mixed network.
> >
> > Sorry that no one took care of your bugreport for so long, Vagrant.
> > Patch looks fine to me.
> >
> > maks, any objections against inclusion of the patches?
>
> I had been dragging that patch as I do not like to add to many
> bootparams that are outside of documented upstream linux-2.6 handling
> and thus initramfs-tools specific. waited to see if a second voice
> would raise..
>
> I do not see so much the point of setting ipconfig vendor class id.
> why would that be needed for booting?

It would be used for selecting the boot image.

> the alternate DHCP port looks indeed more interesting, but no idea
> how common that is in the wild? and if there is not a place in the
> ip= monster bootparam?

Using an alternate DHCP port sounds pretty crazy.

Another possibility is to configure the switch(es) to put the thin
clients on a separate VLAN. But I suppose people also want to use cheap
switches with no VLAN support.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

On Sat, Jun 19, 2010 at 06:43:16PM +0200, maximilian attems wrote:
> On Tue, 08 Jun 2010, Michael Prokop wrote:
> > * Vagrant Cascadian <vagrant+debianbugs@freegeek.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)
> >
> > > supporting these options gives additional flexibility in distinguishing thin
> > > clients from conventional workstations in a mixed network.
> >
> > Sorry that no one took care of your bugreport for so long, Vagrant.
> > Patch looks fine to me.
> >
> > maks, any objections against inclusion of the patches?
>
> I had been dragging that patch as I do not like to add to many
> bootparams that are outside of documented upstream linux-2.6 handling
> and thus initramfs-tools specific. waited to see if a second voice
> would raise..

understandable.

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.

live well,
vagrant



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100621021141.GP9805@claws.fglan">http://lists.debian.org/20100621021141.GP9805@claws.fglan