Subject: Re: kern/36660: envsys sensor names are not unique
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>
List: netbsd-bugs
Date: 07/19/2007 07:10:03
The following reply was made to PR kern/36660; it has been noted by GNATS.

From: yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi)
To: juan@xtrarom.org
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/36660: envsys sensor names are not unique
Date: Thu, 19 Jul 2007 12:22:54 +0900 (JST)

 > On Tue, 17 Jul 2007 14:35:01 +0000 (UTC)
 > yamt@mwd.biglobe.ne.jp wrote:
 > 
 > > 	- make the framework ensure that names are unique.
 > 
 > Do you mean per device, right?
 
 it should be unique enough so that an sensor can be specified unambiguously.
 isn't "envstat -s foo" ambiguous if there are two sensors called "foo"
 in a system, even if they belong to different devices?
 
 > > 	- remove the "envstat -m desc=..." functionality.
 > > 	  IMO, it's a misfeature.
 > 
 > A misfeature, why? it's useful if you are not happy with a description.
 > Note that the problem here is ipmi that assigns those names.
 
 keeping user-defined descriptions in kernel is a bad idea in the first place.
 
 besides, because they are used as identifiers as well (it's a bad design IMO),
 changing them just for user's preference is rather confusing than useful.
 do you have a way to know what your sensor with name "foo" actually was?
 
 YAMAMOTO Takashi