From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: lm_sensors2/prog/detect sensors-detect
Date: Thu, 19 May 2005 06:24:25 +0000 [thread overview]
Message-ID: <20031115104547.50399d8d.khali@linux-fr.org> (raw)
In-Reply-To: <20021107235845.0037e195.khali@linux-fr.org>
> never mind.
> I think, on the iopener, when sensors-detect gave the IBM warning,
> I was running as non-root.
> It doesn't give the warning when run as root.
> Sorry for the false alarm.
I prefer it that way, since I had some difficulties imagining what would
have cause such a failure in the detection code.
> But anyway, would it be helpful to put out a message in sensors-detect
> when it can't determine the system type, even as root?
Auxiliary question, should we even accept running as non-root? We can't
detect an IBM system if we are not root, still the user can scan any
already-loaded bus driver, providing i2c-dev is loaded too. Isn't it
dangerous? OTOH i2c-dev shouldn't be loaded on such a system, and
i2c-piix4 shouldn't possibly load anyway.
(BTW, should I replace DMI with VPD in i2c-piix4/dmi_scan? Or is it
considered a feature to use different protection systems? Not all
Thinkpads have a DMI table. OTOH, DMI scan is already handled by the
kernel so idealy we could get rid of dmi_scan, as it was done in
Linux 2.6. And after all, the eeprom module is supposed to be safe WRT
faulty eeproms now, so dmi/vpd detection at this level is not really
required anymore, right?)
To answer your question, failing to detect the system type now (with
VPD) can only occur if we can't read /dev/mem (because we are not root,
or because a read error occured, which could happen on some non-i386
architectures). Since all Thinkpads are i386 systems AFAIK, the second
case isn't really a problem.
And we already output a message if the system type couldn't be detected.
I'll just leave it in place.
> And yes, on the 2 "typical" machines, it doesn't mention VPD.
Which basically means "the system is safe", left apart the two cases
mentioned above.
> nice job on the dmidecode package and website BTW.
Thanks :) Do you really like the website. I'm not sure how to organize
it. For now, there's a single page with anything on it. I wonder if I
should split it into many pages, but actually there isn't that much to
write about it, so my conclusion so far was that it wasn't necessary.
As for the design, see how clean and easy it is to use CSS and XHTML to
get an easy-to-maintain site. Admittedly, I kept the look very simple,
half because I like simple and fast-loading pages as a user, half
because I am not particularily talented when it comes to complex design.
I'd love to see the lm_sensors website with a single CSS and clean HTML
pages too, unfortunately I don't really have the time to work on this -
and after all the current website does its job rather well, methinks.
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:23 lm_sensors2/prog/detect sensors-detect Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jim Morris
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jim Morris
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare [this message]
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
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=20031115104547.50399d8d.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=lm-sensors@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.