reassign 403706 release-notes
severity 403706 important
thanks
On Tuesday 19 December 2006 22:19, Joey Hess wrote:
> It's not particularly clear to me that this is a d-i bug though. If
> ifupdown/udev doesn't behave correctly/reliably for allow-hotplug
> interfaces that are cold-plugged at system
Frans Pop wrote:
> +fprintf(fp, "# Because to potential problems bringing up
> hotpluggable interfaces\n");
> +fprintf(fp, "# both an 'auto' and 'allow-hotplug' are used.\n");
> +fprintf(fp, "# See bugs #403706 and #403805 for further
> information.\n");
> +
On Thu, Jan 04, 2007 at 05:34:34PM +0100, Frans Pop wrote:
> +else {
> +fprintf(fp, "# Because to potential problems bringing up
> hotpluggable interfaces\n");
s/Because to/Because of/
> +fprintf(fp, "# both an 'auto' and 'allow-hotplug' are used.\n");
> +
On Tuesday 19 December 2006 23:00, Joey Hess wrote:
> Here's a patch to netcfg, to do that:
I'd prefer to apply the patch below instead. Although it has two lines to
print an "auto " line, I feel that that is more in line with the
fact that it is a (hopefully temporary) workaround.
I also feel we
> I'm not convinced this really is RC, especially not if the most severe
> issue can be fixed in udev. For one, it is fairly easy to document and
> fix by an admin based on that documentation.
IMHO, it depends on whether any remaining failure mode can make it impossible
to get into the box and fix
Late reply, sorry.
I'm not convinced this really is RC, especially not if the most severe
issue can be fixed in udev. For one, it is fairly easy to document and
fix by an admin based on that documentation.
It's only a real problem for remotely admined boxes, but you kind of do
expect admins of
Joey Hess wrote:
> I can see that causing some potential problems for certian services that
> expect the network to be up after /etc/init.d/networking, but it's not
> clear to me that those problems are acutally release critical. I've
> downgraded this bug for now, but it could be upgraded if there
Another option would be to make netcfg always add an auto line, so it
has:
allow-hotplug eth0
auto eth0
This avoids any problems caused by udev running ifup too early or too
late, for interfaces that arn't really that hotpluggable, or that are
cold-plugged. /etc/init.d/networking will (generally)
If this is actually a d-i/netcfg bug, then one approach would be to
remove net-hotplug.sh (or its udev rule) from hw-detect. This script
detects net device additions, and registers the devices as hotpluggable.
With udev I think that all network devices come in this way, be they pci
cards or usb nic
9 matches
Mail list logo
