Re: port-i386/39086: dmesg doesn't really identifies CPU any more

[Bernhard Moellemann <zza%serpens.de@localhost>]

The following reply was made to PR port-i386/39086; it has been noted by GNATS.

From: Bernhard Moellemann <zza%serpens.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: Christoph_Egger%gmx.de@localhost
Subject: Re: port-i386/39086: dmesg doesn't really identifies CPU any more
Date: Thu, 3 Jul 2008 08:42:07 +0200

 On Thu, Jul 03, 2008 at 05:35:02AM +0000, Christoph Egger wrote:
 > The following reply was made to PR port-i386/39086; it has been noted by 
 > GNATS.
 > 
 > From: Christoph Egger <Christoph_Egger%gmx.de@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: port-i386-maintainer%netbsd.org@localhost, 
 > netbsd-bugs%netbsd.org@localhost
 > Subject: Re: port-i386/39086: dmesg doesn't really identifies CPU any more
 > Date: Thu, 03 Jul 2008 07:34:41 +0200
 > 
 >  The new way is to use "cpuctl identify <cpu>".
 >  See cpuctl(8) for more information.
 
 I know. But this implies I reach userland and can mount /usr. Both is not
 always true on unknown hardware and very inconvenient even if you happen
 to have a working (and sufficiently new) NetBSD system nearby.
 
   Bernhard  //
           \X/