From: Matt Domsch <Matt_Domsch@dell.com>
To: Dave Jones <davej@redhat.com>,
Brian McGrew <Brian@doubledimension.com>,
linux-kernel@vger.kernel.org
Subject: Re: Probing for System Model Information
Date: Tue, 28 Sep 2004 09:06:27 -0500 [thread overview]
Message-ID: <20040928140627.GA24899@lists.us.dell.com> (raw)
In-Reply-To: <20040928134705.GA11916@redhat.com>
On Tue, Sep 28, 2004 at 02:47:05PM +0100, Dave Jones wrote:
> On Tue, Sep 28, 2004 at 06:32:31AM -0700, Brian McGrew wrote:
> > Good morning All! We exclusively ship Dell boxes with our
> > hardware. However, we use several different models, 1400's,
> > 1600's, 2350's, 4600's and so on. I need to write a small
> > program to probe the system for the model information since I
> > don't seem to find it in the logs anywhere. I know the model
> > info is in there somewhere and it's accessible because if I look
> > on the default factory installed version of Windows, it's listed.
> > Does anyone know how to do this or can you point me to one that's
> > already done or some samples?
>
> You can find this info in the DMI tables assuming Dell filled
> them in with sensible data (which they usually do).
Yes, we do. :-) I've abbreviated the output to serve as an example.
# dmidecode
Handle 0x0000
BIOS Information Block
Vendor: Dell Computer Corporation
Version: A08
Handle 0x0100
System Information Block
Vendor: Dell Computer Corporation
Product: PowerEdge 2400
Handle 0x0300
Chassis Information Block
Serial Number: MY_SERIAL_NUMBER
Asset Tag: 0000001
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2004-09-28 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 13:32 Probing for System Model Information Brian McGrew
2004-09-28 13:47 ` Dave Jones
2004-09-28 14:06 ` Matt Domsch [this message]
2004-09-28 14:23 ` Buddy Lucas
2004-09-28 13:51 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040928140627.GA24899@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=Brian@doubledimension.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.