Date: Tue, 23 Mar 2010 12:10:52 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: Atom Smasher <atom@smasher.org> Cc: FreeBSD-Hackers <freebsd-hackers@freebsd.org>, Andrew Thompson <thompsa@freebsd.org> Subject: Re: kenv - output needed Message-ID: <7d6fde3d1003231210s38ec9419r5149fa7af6f5bd2b@mail.gmail.com> In-Reply-To: <1003240736570.40436@smasher> References: <1003231706140.40436@smasher> <20100323180354.GD45454@citylink.fud.org.nz> <1003240736570.40436@smasher>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 23, 2010 at 12:06 PM, Atom Smasher <atom@smasher.org> wrote: > 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 variat= ions >>> of formatting and usefulness. >>> >>> i'd like to collect as much output as i can get (off-list should be fin= e) >>> from one of these two commands: >>> >>> 1) preferred: >>> =A0 =A0 =A0 =A0kenv | egrep bios >>> >>> 2) i can also use this: >>> =A0 =A0 =A0 =A0kenv | egrep 'product|maker' >> >> kenv is essentially dumping all the variables set by the bootloader prio= r >> to starting the kernel. If you want something more structured then maybe= the >> dmidecode utility would be useful. > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > 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 runn= ing > with root privileges, is there any ~real~ difference between the informat= ion > 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 o= f > how it's formatted. Are you looking for data represented similar to sysctl(8)? Cheers, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d1003231210s38ec9419r5149fa7af6f5bd2b>