Re: Bug#433568: VLANs during install are important
On Friday 29 January 2010, Josef Wolf wrote:
> But at that time the interface chosen interface is not known. So
> deducing from chosen interface name (as outlined above) is not possible
> and this method would only work with preseeding or if additional
> questions are asked.
No. The sequence should be:
- if the interfaces are there, hw-setup should install additional needed
stuff
- if additional needed stuff is not available, netcfg should not offer
the interfaces for selection
> > And for e.g. netboot
> > images the vlan udeb would need to be included in the initrd for
> > relevant architectures.
>
> Oh, I've completely forgotten about netboot. To be honest, I have no
> clue what this means exactly. Can you point me to some information about
> that?
Just build the target and use the mini.iso for your development and
testing. It's by far the easiest way to develop new functionality anyway.
See further the document I pointed t earlier, especially the comments about
localudebs and pkg-lists/local.
> BTW:
> Actually there are two udebs:
> - one udeb created from vlan.deb (only the XC-Package-Type line needs
> to be added to debian/control)
Not needed according to Bastian.
> - the kernel modules would be created via kernel-wedge
Correct. Only question is whether they should be in a separate udeb, or
included in one of the existing network-drivers udebs. That depends on:
- size
- whether it is generally needed/useful or only for selected arches.
I think a separate udeb is the best option to start with.
Reply to: