From: Michael Brown <Michael_E_Brown@Dell.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com
Subject: Re: [PATCH 2.4] add SMBIOS information to /proc/smbios -- UPDATED
Date: Fri, 30 Apr 2004 22:43:26 -0500 [thread overview]
Message-ID: <1083383006.1197.2984.camel@debian> (raw)
In-Reply-To: <1083382204.1203.2971.camel@debian>
On Fri, 2004-04-30 at 22:30, Michael Brown wrote:
> On Fri, 2004-04-30 at 14:22, Andi Kleen wrote:
> > Michael Brown <mebrown@michaels-house.net> writes:
> >
> > > Below is an updated patch to add SMBIOS information to /proc/smbios.
> > > Updates have been made per Al's previous comments. Please apply.
> >
> > What is this good for? There are tools to read this from
> > /dev/mem; and that is fine because the information is static.
> > There is no reason to bloat the kernel with this.
Sorry, I missed one other reason.
This procfs/sysfs driver allows access to smbios information by
non-root, non CAP_SYS_RAWIO users. I've had several occasions where I
have been bitten by having to be root to read smbios when I did not need
root for anything else.
--
Michael
next prev parent reply other threads:[~2004-05-01 3:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1QvX0-A4-29@gated-at.bofh.it>
2004-04-30 19:22 ` [PATCH 2.4] add SMBIOS information to /proc/smbios -- UPDATED Andi Kleen
2004-05-01 3:30 ` Michael Brown
2004-05-01 3:43 ` Michael Brown [this message]
2004-05-01 15:01 ` Andi Kleen
2004-05-03 23:49 Michael_E_Brown
-- strict thread matches above, loose matches on Subject: below --
2004-05-01 21:00 Lev Makhlis
2004-05-01 21:20 ` Andi Kleen
2004-04-30 2:21 Michael Brown
2004-04-30 3:34 ` viro
2004-04-30 4:37 ` Michael Brown
2004-05-03 23:40 ` Marcelo Tosatti
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=1083383006.1197.2984.camel@debian \
--to=michael_e_brown@dell.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox