<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi, That's where Player has put them by default for a while now. I'm just used to it, I didn't even think about it. I tend to regard these examples as static, and never change them. If i need to edit something, I end up making my own config file somewhere else and copying things into it. And since these examples don't always work right out of the box, it might be good to keep them somewhere where people can use them as a reference and not break them. We could even add a readme with guidance on how we intend for people to use them. What do you plan to do with the c/c++ client examples? Do they stay in /usr/share since they're not configuration files, or would you move them to /etc? I'm not opposed to moving the config examples, and I see where you're coming from. I've just never used them as anything more than templates. If you think it's more appropriate, go for it. Rich Tim Niemueller wrote: <blockquote cite="mid:4AE0E1EC.60400@niemueller.de" type="cite"> <pre wrap="">On 23.10.2009 00:14, Hedayat Vatankhah wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi, </pre> </blockquote> <pre wrap=""> Hi Hedayat, thanks for the quick reply! </pre> <blockquote type="cite"> <pre wrap="">If all what I said applies to these configuration files, I think they completely satisfy "read only architecture independent data files". </pre> </blockquote> <pre wrap=""> I thought about your reasoning. But there are device files and the like specified in the config files which may change. Additionally to create a new configuration most of the time you start by copying an existing config file, being able to do this in the very same directory makes things simpler. Additionally having some config files in /usr/share and some in /etc seems odd. I'd like to hear more opinions, but I tend to the /etc solution atm. Regards, Tim </pre> </blockquote> </body> </html>