From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 23 19:06:15 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69359106567C for ; Tue, 23 Mar 2010 19:06:15 +0000 (UTC) (envelope-from atom@smasher.org) Received: from atom.smasher.org (atom.smasher.org [69.55.237.145]) by mx1.freebsd.org (Postfix) with SMTP id 4C16B8FC18 for ; Tue, 23 Mar 2010 19:06:15 +0000 (UTC) Received: (qmail 22780 invoked by uid 1000); 23 Mar 2010 19:06:13 -0000 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Date: Wed, 24 Mar 2010 08:06:23 +1300 (NZDT) From: Atom Smasher In-Reply-To: <20100323180354.GD45454@citylink.fud.org.nz> Message-ID: <1003240736570.40436@smasher> MIME-Version: 1.0 OpenPGP: id=0xB88D52E4D9F57808; algo=1 (RSA); size=4096; url=http://atom.smasher.org/pgp.txt References: <1003231706140.40436@smasher> <20100323180354.GD45454@citylink.fud.org.nz> To: Andrew Thompson X-POM: The Moon is Waxing Gibbous (54% of Full) X-Hashcash: 1:20:1003231906:thompsa@freebsd.org::LlZ+y60VQCeHYu7n:00000000000000 0000000000000000000000005A+T X-Hashcash: 1:20:1003231906:freebsd-hackers@freebsd.org::kT1HKUQGH+rk04Rw:000000 0000000000000000000000000JBK Cc: FreeBSD-Hackers Subject: Re: kenv - output needed 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: Tue, 23 Mar 2010 19:06:15 -0000 On Wed, 24 Mar 2010, Andrew Thompson wrote: > On Tue, Mar 23, 2010 at 05:12:47PM +1300, Atom Smasher wrote: >> i'm trying to figure out what might be reasonable output from kenv. on >> the three machines that i have access to i'm already seeing wide >> variations of formatting and usefulness. >> >> i'd like to collect as much output as i can get (off-list should be >> fine) from one of these two commands: >> >> 1) preferred: >> kenv | egrep bios >> >> 2) i can also use this: >> kenv | egrep 'product|maker' > > kenv is essentially dumping all the variables set by the bootloader > prior to starting the kernel. If you want something more structured then > maybe the dmidecode utility would be useful. =============== structure is cool, but it seems like you're being human-centric in your reference to structure; i actually want to parse the info with a script, making kenv preferable. i want the ability to run the script without any privileges; again making kenv preferable. so with an unprivileged script, i'm leaning towards kenv to find out what hardware is running (motherboard & system info, eg "Dell Inc., 0H603H, PowerEdge 2950" or "Acer, Navarro, Aspire 5100"). other than being formatted more nicely (for humans, anyway) and only running with root privileges, is there any ~real~ difference between the information i would get from dmidecode rather than kenv (as it relates to motherboard & system make & model)? it seems like in either case, i'm just getting the info from smbios... and that info could be good, bad or ugly regardless of how it's formatted. -- ...atom ________________________ http://atom.smasher.org/ 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808 ------------------------------------------------- "I know a lot of people without brains who do an awful lot of talking." -- The Scarecrow, Wizard of Oz