From: Hans de Goede <hdegoede@redhat.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [RFC PATCH v1 0/2] Add the sensors-config tool
Date: Wed, 24 Feb 2010 13:58:56 +0000 [thread overview]
Message-ID: <4B8530A0.9010603@redhat.com> (raw)
In-Reply-To: <20100219193821.GA1917@andre-laptop>
Hi,
On 02/23/2010 09:35 PM, Andre Prendel wrote:
> On Mon, Feb 22, 2010 at 10:26:47PM +0100, Hans de Goede wrote:
>> Hi,
>
> Hello,
>
>> On 02/22/2010 09:28 PM, Andre Prendel wrote:
>
>> Well, we can have one config file which is valid for multiple versions /
>> variants (think extra slots, extra onboard nic, whatever) boards, I
>> think we should not have multiple copies of that file then, using
>> a hierarchy with multiple levels is fine by me too, but then:
>>
>> 1) How will you deal with board / produty version (we are going to need
>> these to uniquely identify some boards)
>> 2) Are you going to handle having multiple board_name's in the same
>> config file.
>
> I like the multiple level directory layout because printing all
> vendors or all boards for a specific vendor is a simple directory
> listing (see -l and -b options). BTW I like a clean layout.
>
> Of course we can encode the version by another directory level or in
> the board name, couldn't we?
>
> To avoid multiple files for the same board we could place the symlinks
> into root directory. This layout would also avoid the problem of
> identical board names of different vendors.
>
Having multiple directory levels is fine by me. I was merely
pointing out that there are some issues with that approach.
Thinking of this another possible issue is that vendors don't
always use the same vendor string in the DMI data.
So I think that the following would be a good solution:
1 dir per vendor, with vendor board configs in there, just like
the wiki.
symlinks in the base dir following the symlink structure I suggested
earlier.
This way we get the best of both worlds I think.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2010-02-24 13:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 19:38 [lm-sensors] [RFC PATCH v1 0/2] Add the sensors-config tool Andre Prendel
2010-02-22 9:04 ` Hans de Goede
2010-02-22 9:52 ` Jean Delvare
2010-02-22 12:24 ` Hans de Goede
2010-02-22 20:28 ` Andre Prendel
2010-02-22 20:31 ` Andre Prendel
2010-02-22 20:40 ` Andre Prendel
2010-02-22 20:43 ` Jean Delvare
2010-02-22 21:26 ` Hans de Goede
2010-02-22 22:40 ` VDR User
2010-02-23 8:20 ` Hans de Goede
2010-02-23 17:00 ` VDR User
2010-02-23 20:35 ` Andre Prendel
2010-02-24 13:58 ` Hans de Goede [this message]
2010-02-24 20:24 ` Andre Prendel
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=4B8530A0.9010603@redhat.com \
--to=hdegoede@redhat.com \
--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.