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] Motherboard-specific configurations (sensors4mobo)
Date: Sat, 31 Mar 2007 12:36:00 +0000	[thread overview]
Message-ID: <20070331143600.9bdaef1e.khali@linux-fr.org> (raw)
In-Reply-To: <46084A44.4070101@eberian.com>

Hi Hans,

On Wed, 28 Mar 2007 13:20:33 +0200, Hans de Goede wrote:
> Ivo Manca wrote:
> > Hey Ed,
> > 
> >> I looked at sqlite when developing sensors4mobo but many ISPs do not 
> >> include it and I did not want to add any dependencies that would limit 
> >> usage or make installation harder.
> 
> <lots of explanation by Ivo about sqlite plans snipped>
> 
> Actually I have been thinking about using the annotating of sensors.conf file 
> myself in the past, but I thought sqlite would be easier to use, esp. on the 
> web-side. Since with sensors4mobo we kinda get the web-side for free, and I 
> also _really_ like the idea of the database being a dir of textfiles with one 
> file per motherboard allowing for easy tinkering / experimenting by end users, 
> I think it might be a good idea to go with the dir with one textfile per mobo.
> 
> But less discuss this further tomorrow at our (face to face) meeting. Jean, any 
> thoughts / preferences on this?

For the local data, I'd go for text files. Each motherboard being
uniquely identified by a finite number of DMI strings, we can
combine them to form a unique identifier and use that in the
configuration file name. Ideally this should be something like
sensors-$manufacturer-$model-$version.conf, but we'll see how it goes
in practice. With this naming convention, lookups are in O(1), which is
perfect.

Now, it might still be good to have a database as the backend of the
website, that's a different story. It should be easy enough to generate
all the text files from the database, adding metadata as comments at
the beginning of the files.

-- 
Jean Delvare

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

  parent reply	other threads:[~2007-03-31 12:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 22:33 [lm-sensors] Motherboard-specific configurations (sensors4mobo) Ed Lucas
2007-03-27 15:39 ` Jean Delvare
2007-03-27 16:07 ` Ivo Manca
2007-03-28  9:30 ` Ed Lucas
2007-03-28 10:56 ` Ivo Manca
2007-03-28 11:20 ` Hans de Goede
2007-03-28 11:49 ` Ed Lucas
2007-03-28 12:07 ` Ivo Manca
2007-03-28 17:09 ` David Hubbard
2007-03-29  8:03 ` Pinkel
2007-03-29 10:00 ` Ed Lucas
2007-03-29 13:20 ` Ivo Manca
2007-03-29 14:18 ` Ed Lucas
2007-03-29 14:56 ` Hans de Goede
2007-03-31 12:22 ` Jean Delvare
2007-03-31 12:36 ` Jean Delvare [this message]
2007-03-31 12:42 ` Jean Delvare
2007-03-31 12:45 ` Jean Delvare
2007-03-31 12:50 ` Jean Delvare
2007-04-04  9:34 ` Ivo Manca
2007-04-08 11:13 ` 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=20070331143600.9bdaef1e.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.