All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
Date: Mon, 06 Sep 2010 16:18:58 +0000	[thread overview]
Message-ID: <20100906181858.2fd7d733@hyperion.delvare> (raw)
In-Reply-To: <929339.59525.qm@web50002.mail.re2.yahoo.com>

On Sat, 4 Sep 2010 10:28:32 -0700, Guenter Roeck wrote:
> On Sat, Sep 04, 2010 at 11:55:29AM -0400, Jean Delvare wrote:
> > On Sat, 4 Sep 2010 07:25:34 -0700, Guenter Roeck wrote:
> > > Removing it sounds like overkill to me. After all, it _does_
> > > provide value (when it works). Maybe we should do the above,
> > > and spend some time getting it to work w/ Ubuntu given its
> > > distribution. I should be able to do that.
> > 
> > Where does it work? All distributions I know of, ship their own
> 
> Good question ...
> 
> > initialization script. There are so many dependencies (as you just
> > found out) and conventions (e.g. service naming, as you just found out
> > as well) involved, we can't make everyone happy.
> > 
> > The initialization script is only useful to people installing
> > lm-sensors from the sources on distributions which do not have
> > it already installed via a package. There aren't many doing that these
> > days, I think. And these can probably just add a couple modprobe lines
> > in a custom init script, as sensors-detect suggests. lm_sensors isn't
> > really a service, there's no daemon running (unless you throw sensord
> > into the game) so stopping it is totally optional.
>
> Maybe the best approach is to not (try to) install it at all, but just provide
> it as hint.

Isn't it exactly what we're doing today?

> Or maybe check if /etc/init.d/lm-sensors exists, and if it does
> don't install anything at all.

We could do that, but that's an invitation for distribution to use
lm-sensors instead of lm_sensors as the service name. I'd rather push
all distributions to stick to lm_sensors.

> The shared library locations are yet another problem. Not sure how to address
> that either.

I have no idea what you're talking about, sorry.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2010-09-06 16:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01  6:38 [lm-sensors] lmsensors doesn't detect core-i7 sensors Mahmood Naderan
2010-09-01  7:19 ` Nikola Pajkovsky
2010-09-01  7:30 ` Mahmood Naderan
2010-09-01  7:38 ` Nikola Pajkovsky
2010-09-01  7:46 ` Mahmood Naderan
2010-09-01  7:53 ` Nikola Pajkovsky
2010-09-01  8:03 ` Mahmood Naderan
2010-09-01  8:11 ` Nikola Pajkovsky
2010-09-01  8:16 ` Mahmood Naderan
2010-09-01 13:26 ` Guenter Roeck
2010-09-01 13:56 ` Jean Delvare
2010-09-01 14:32 ` Guenter Roeck
2010-09-01 14:58 ` Mahmood Naderan
2010-09-01 15:52 ` Guenter Roeck
2010-09-01 16:57 ` Mahmood Naderan
2010-09-03 14:31 ` Guenter Roeck
2010-09-04 13:49 ` Jean Delvare
2010-09-04 14:25 ` Guenter Roeck
2010-09-04 14:31 ` Mahmood Naderan
2010-09-04 15:55 ` Jean Delvare
2010-09-04 17:28 ` Guenter Roeck
2010-09-06 16:18 ` Jean Delvare [this message]
2010-09-07  1:32 ` Guenter Roeck
2010-09-07  8:00 ` Jean Delvare
2010-09-13  8:04 ` Mahmood Naderan
2010-09-14 16:20 ` Guenter Roeck

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=20100906181858.2fd7d733@hyperion.delvare \
    --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.