Your message dated Sun, 30 Oct 2016 13:15:52 +0100 with message-id <fd731809-574e-2b1e-fdaf-453264e7c0a8@debian.org> and subject line Re: Bug#826844: netcfg ignoring BOOTF= in kernel cmdline has caused the Debian Bug report #826844, regarding netcfg ignoring BOOTF= in kernel cmdline 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 immediately.) -- 826844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826844 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: netcfg ignoring BOOTF= in kernel cmdline
- From: James Mackie <jc.mackie@gmail.com>
- Date: Thu, 9 Jun 2016 21:11:06 +1000
- Message-id: <CAA=eWUwBPsSOpD=TLQSQXkd2HpSwUS+LBiS0iQ12=m1JrDGfEg@mail.gmail.com>
Thanks.The installer information is:I am going to code my way around this using the preseed/early_command for setting the interface. But it would be nice if this issue was resolved. Let me know if you need more information.But MAC addresses are 15 characters long (including the colons).Line 644 seems to be confusing because it's comparing 'bootif_len' to 20 [(6 * 3 - 1) + 3]I've tried to look at the source (master branch from git://anonscm.debian.org/d-i/netcfg.git) to try and figure out what's wrong, but I am not a C developer.auto=true priority=critical url="" href="http://thebooting.dev2.internal/preseed">http://thebooting.dev2.internal/preseed interface=auto DEBCONF_DEBUG=5 BOOTIF=0c:c4:7a:8e:ad:4a~ # cat /proc/cmdlineThis is me checking /proc/cmdline:netcfg[780]: INFO: Could not find valid BOOTIF= entry in /proc/cmdlinekernel: [0.00000] Command line: auto=true priority=critical url="" href="http://thebooting.dev2.internal/preseed">http://thebooting.dev2.internal/preseed interface=auto DEBCONF_DEBUG=5 BOOTIF=0c:c4:7a:8e:ad:4a~ # grep BOOTIF /var/log/syslogHere is the output from /var/log/syslog (DEBCONF_DEBUG=5 is set) (paraphrased because I'm typing this out by hand):to have iPXE pass the MAC of the boot interface to Jessie d-i. However netcfg refuses to parse the MAC from /proc/cmdline even though I can see it there.BOOTIF=${netX/mac}We use iPXE to pass boot information, and I use:Package: netcfg
Version: 1.131+deb8u1
Severity: importantThe version is based off the http://ftp.nl.debian.org/debian/dists/jessie/main/installer-amd64/current/images/udeb.listI am trying to initiate a full hands off installation of Jessie on a remote server.
kernel: [0.00000] Kernel command line: auto=true priority=critical url="" href="http://thebooting.dev2.internal/preseed">http://thebooting.dev2.internal/preseed interface=auto DEBCONF_DEBUG=5 BOOTIF=0c:c4:7a:8e:ad:4a
Debian GNU/Linux installer
8 (jessie) - installer build 20150422+deb8u3
--- End Message ---
--- Begin Message ---
- To: James Mackie <jc.mackie@gmail.com>, 826844-done@bugs.debian.org
- Subject: Re: Bug#826844: netcfg ignoring BOOTF= in kernel cmdline
- From: Philipp Kern <pkern@debian.org>
- Date: Sun, 30 Oct 2016 13:15:52 +0100
- Message-id: <fd731809-574e-2b1e-fdaf-453264e7c0a8@debian.org>
- In-reply-to: <[🔎] CAA=eWUyW-YNq8MYvu_UwYPHnF4CR6fbo7yAnN03xoyQeQ3ZH9g@mail.gmail.com>
- References: <CAA=eWUwBPsSOpD=TLQSQXkd2HpSwUS+LBiS0iQ12=m1JrDGfEg@mail.gmail.com> <[🔎] 44665246-00e7-df20-e709-6ae585763a73@debian.org> <[🔎] CAA=eWUyW-YNq8MYvu_UwYPHnF4CR6fbo7yAnN03xoyQeQ3ZH9g@mail.gmail.com>
Hi, On 10/24/2016 02:17 AM, James Mackie wrote: > Thanks for your response. Yeah I actually figured that out after looking > looking at the netcfg code and seeing the "01-" being purposefully > excluded from the address capture. So then I looked up the specification > for PXELINUX and saw the hardware type at the start. > > So, I've just hardcoded (eww) a "01-" before the ${netX/mac} in the iPXE > config. > > Thanks for the answer! And sorry for not updating this sooner. This can > probably be closed as a non-issue, but not sure if it's worth while > adding a comment to the code, or something. thanks for the confirmation. I'll go ahead and close the bug. Kind regards Philipp KernAttachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---