On Sunday 20 November 2011, Cristian Rodríguez wrote:
On 20/11/11 07:17, Rüdiger Meier wrote:
There is a "Filesystem Hierarchy Standard"
here we go with this bunch of papers and nice theory...
where admins, users and developers can read about where to find or where to put files. Old standards may not be entirely perfect forever but they are required keep things transparent specially for people who _have_ learned it already. Reading Poettering's email "Hey there, today we have /run" is absolutely the opposite of a doing things straightforward and transparent.
There is no conflict with the FHS, it doesn't forbid distributions to create their own top level directories, it asks for notification of the changes to a (dead) bugtracker/list
How/where exactly opensuse has _made_ that decision? I've missed it.
People who write code and deals with bugs and the consequences have to take decisions,
The user/admin has do deal even more with the consequences. Mounting tmpfs over long time existing dirs is a major change. It could lead to big problems for particular users. How you kown what else the admin is doing in /var/run. Is there enough swap space? What about scripts which don't cross filesystem boundaries now in /var/run? Backup ignore lists might be imperfect now. I'm not criticizing here tmpfs usage or /run itself. But as a major change it should have published on Release Notes at least.
in this case it was agreed among all major distributions.
My question was how such agreement happens in practice. I couldn't find anything about it. cu, RUdi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org