[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#577149: marked as done (configure_networking: pxelinux BOOTIF fixes)

Your message dated Fri, 4 Jun 2010 12:59:45 -0700
with message-id <20100604195945.GM12505@claws.fglan>
and subject line Re: #577149: configure_networking: pxelinux BOOTIF fixes
has caused the Debian Bug report #577149,
regarding configure_networking: pxelinux BOOTIF fixes
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

577149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577149
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.94.4
Severity: normal
Tags: patch

looks like i missed a few things on implementing BOOTIF support properly.

somehow i managed to get the order of the mac address backwards. i know i
tested it many times, but somehow the patch i submitted got it backwards:

diff --git a/scripts/functions b/scripts/functions
index 7b68255..f854495 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -323,7 +323,7 @@ configure_networking()
 			if [ -z "$bootif_mac" ]; then
-				bootif_mac="$x:$bootif_mac"
+				bootif_mac="$bootif_mac:$x"
 		unset IFS

as mentioned by Christoph Bussenius in #535008, it does appear that setting
BOOTIF from the value in /proc/cmdline is needed. at the time i wrote the
patch, i'm not sure it was, but it definitely is now:

diff --git a/init b/init
index 7d0db07..142eb14 100755
--- a/init
+++ b/init
@@ -175,6 +175,9 @@ for x in $(cat /proc/cmdline); do
+		;;

with these patchese applied, it seems to work. at least for the moment.

live well,

--- End Message ---
--- Begin Message ---
Version: 0.95

this was fixed in the 0.95 upload, but the changelog entry didn't mention the
bug number.

live well,

--- End Message ---

Reply to: