Jean Delvare wrote: > > Also, storing the configuration files in the wiki is probably the worse > thing we could come up with in these conditions, but hopefully we'll > have something better shortly after lm-sensors 3.0.1 is released. > Hmm, Do you have something planned? As you know I've had several students work on a motherboard config website without much success, I do think Ivo's sensors-detect changes for dmi based autoconf are good (we need to get those integrated, plan?). But the website delivered by one of his fellow students is less good. I do have a friend who is a php guru who is willing to write a php driven site for us if we can provide him with proper specs. I can start writing a spec for the website as time permits, then discuss it here, and once approved ask him to write it (under an OSS license of course). Another option would be to stay with the wiki, add some special markup comments for the dmi strings and write a script to generate a tarbal / "database" for the dmi based detect code. For me putting the info in the wiki works well, its not like we are getting multiple motherboard configs per day, and the wiki keeps history which can be benifitial (a sufficiently advanced website could do this too). Regards, Hans
