From owner-freebsd-current@FreeBSD.ORG Sat Jul 23 18:50:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA33F16A41F for ; Sat, 23 Jul 2005 18:50:07 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail1.fluidhosting.com (mail1.fluidhosting.com [204.14.90.61]) by mx1.FreeBSD.org (Postfix) with SMTP id 162ED43D46 for ; Sat, 23 Jul 2005 18:50:06 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 65530 invoked by uid 399); 23 Jul 2005 18:50:06 -0000 Received: from mail1.fluidhosting.com (66.150.201.101) by mail1.fluidhosting.com with SMTP; 23 Jul 2005 18:50:06 -0000 Received: (qmail 61681 invoked by uid 399); 23 Jul 2005 18:50:01 -0000 Received: from unknown (HELO ?192.168.15.101?) (dougb@dougbarton.net@67.20.70.103) by mail1.fluidhosting.com with SMTP; 23 Jul 2005 18:50:01 -0000 Message-ID: <42E29157.3090908@FreeBSD.org> Date: Sat, 23 Jul 2005 11:49:59 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050722) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ben Kaduk References: <200507220549.j6M5nfhO059858@repoman.freebsd.org> <47d0403c05072218091264a990@mail.gmail.com> <47d0403c05072218491c78e2e9@mail.gmail.com> In-Reply-To: <47d0403c05072218491c78e2e9@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Jung-uk Kim Subject: Re: cvs commit: src/usr.sbin/ndiscvt ndisgen.sh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jul 2005 18:50:07 -0000 Ben Kaduk wrote: > I know it's bad form to reply to myself, It's not actually, that's a myth that needs to be busted. :) This is especially true when you have found the right answer, and can save others time investigating the problem. > but this patch seems to allow > ndisgen to recognize my .inf file: Thanks! I noticed a similar problem with my own INF file, and in my case it turned out that the various lines it was searching for did not occur in the first column, but were indented. Removing the ^ in all places it occurred fixed this for me, so I've committed the fix. Good hunting, Doug -- This .signature sanitized for your protection