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
Processing commands for [EMAIL PROTECTED]:
> reassign 403706 release-notes
Bug#403706: (sometimes?) fails to bring up interfaces on bootup by default
Bug reassigned from package `netcfg' to `release-notes'.
> severity 403706 important
Bug#403706: (sometimes?) fails to bring up interfaces on bootu
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
7 matches
Mail list logo