From owner-freebsd-hackers@FreeBSD.ORG Wed Oct 26 17:17:49 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B12E616A41F for ; Wed, 26 Oct 2005 17:17:49 +0000 (GMT) (envelope-from dr2867@pacbell.net) Received: from smtp111.sbc.mail.mud.yahoo.com (smtp111.sbc.mail.mud.yahoo.com [68.142.198.210]) by mx1.FreeBSD.org (Postfix) with SMTP id BA81243D45 for ; Wed, 26 Oct 2005 17:17:48 +0000 (GMT) (envelope-from dr2867@pacbell.net) Received: (qmail 36803 invoked from network); 26 Oct 2005 17:17:48 -0000 Received: from unknown (HELO ?192.168.0.190?) (dr2867.business@pacbell.net@68.126.211.246 with plain) by smtp111.sbc.mail.mud.yahoo.com with SMTP; 26 Oct 2005 17:17:47 -0000 Message-ID: <435FBA42.1070604@pacbell.net> Date: Wed, 26 Oct 2005 10:17:54 -0700 From: Daniel Rudy User-Agent: Mozilla/5.0 (X11R6; UNIX; FreeBSD/i386 5.4-RELEASE-p7; en-US; ja-JP; rv:1.7.12) Gecko/20050915 MultiZilla/1.6.2.0c Mnenhy/0.7.2.0 X-Accept-Language: en-us, en, ja MIME-Version: 1.0 To: soc-victor@freebsd.org References: <49402550510240728y555979c9i2fe4adc73137a1e7@mail.gmail.com> <435E6F9C.9090008@pacbell.net> <49402550510251250g66a89037q9a1eb3bdbedf94c3@mail.gmail.com> In-Reply-To: <49402550510251250g66a89037q9a1eb3bdbedf94c3@mail.gmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: devinfo(3) problem... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2005 17:17:49 -0000 At about the time of 10/25/2005 12:50 PM, victor cruceru stated the following: > Hi Daniel, > Yes, this is the fix. And yes, I think that the bug was reported (at > least on a mailing list...) > BTW: I dare to suggest to fully upgrade your system to the "latest" > 6.0, it is a huge step forward from 5.4. Before doing this you may > want to give it a try by booting from a CD and check that your hw is > fully functional (and detected). For stability reasons, I don't run the absolute latest software. When 6.x comes out, I'll wait awhile for the bugs to be worked out before I migrate to it. As for hardware, I tend to run FreeBSD on older hardware, so I don't think that there will be a problem with the hardware being properly detected. > To check if it is your mistake or another bug in libdevinfo, you may > want to run the associated tool (man -k devinfo). > Hope this helps. > Actually, the devinfo tool was working the whole time. I tried the devinfo tool before I decided to use the libdevinfo.so library. I've tested it with my code and it is working now with that one line of additional code. > On 10/25/05, Daniel Rudy wrote: > >>At about the time of 10/24/2005 7:28 AM, victor cruceru stated the >>following: >> >>>Daniel, >>>What is the OS version you are using when this is happening? >>>Did you try to update the libdevinfo (using cvsup for example) to a >>>newer version? >>>I think that under the original 5.4 it is a bug in devinfo(4) with the >>>described behaviour below. >> >>I'm running 5.4-RELEASE. >> >>When you mentioned that it might be a bug, I went and looked at >>/usr/src/lib/libdevinfo/devinfo.c using the cvs web depository. I found >>that devinfo_generation = 0 was added to the end of the devinfo_free >>function starting at line 367. I added the code and recompiled just >>that library, and now everything seems to be working ok, except now I'm >>getting a bunch of garbage on the serial number of the USB flash drive. >> I'm not sure if it's my code, or if it's a bug in the library. >> >>-- >>Daniel Rudy >> > > > > -- > victor cruceru > ------------------------------------------------ > Non est respondendum ad omnia. > ( Cicero, Pro Murena Oratio ) > ------------------------------------------------ > -- Daniel Rudy