Does anyone know the history behind the ".d" naming convention on
some directories?
For example, /etc/rc.d or ${prefix}/etc/bash_completion.d. I seem to
understand how these directories are used, but what does the ".d" mean?
___
macports-dev maili
On Apr 22, 2009, at 11:09 PM, Ryan Schmidt wrote:
Does anyone know the history behind the ".d" naming convention on
some directories?
For example, /etc/rc.d or ${prefix}/etc/bash_completion.d. I seem to
understand how these directories are used, but what does the ".d"
mean?
simplistic
The history was pretty simple. When we had a file called /etc/foo,
which we later to split into a directory full of individual one-entry-
per-file records rather than the previous "all records in a single
file", we would rename /etc/foo to /etc/foo.d to denote the switch.
Don't forget, /et
http://www.mewburn.net/luke/talks/auug-2003/
On Wed, Apr 22, 2009 at 9:20 PM, Jordan K. Hubbard wrote:
> The history was pretty simple. When we had a file called /etc/foo, which we
> later to split into a directory full of individual one-entry-per-file
> records rather than the previous "all rec
On Apr 22, 2009, at 23:20, Jordan K. Hubbard wrote:
On Apr 22, 2009, at 8:09 PM, Ryan Schmidt wrote:
Does anyone know the history behind the ".d" naming convention on
some directories?
For example, /etc/rc.d or ${prefix}/etc/bash_completion.d. I seem
to understand how these directories a
On Apr 22, 2009, at 23:41, Andre Stechert wrote:
On Apr 22, 2009, at 8:09 PM, Ryan Schmidt wrote:
Does anyone know the history behind the ".d" naming convention on
some
directories?
http://www.mewburn.net/luke/talks/auug-2003/
Thanks. I've skimmed that twice, but I don't see a part wh
On Apr 22, 2009, at 10:33 PM, Ryan Schmidt wrote:
The reason I ask is for a change I'm working on for the php5
extension ports. Currently, ports like php5-memcache just print a
message telling the user to add these lines to their php.ini:
extension_dir=/opt/local/lib/php/extensions/no-debu
On Apr 23, 2009, at 00:46, Jordan K. Hubbard wrote:
On Apr 22, 2009, at 10:33 PM, Ryan Schmidt wrote:
The reason I ask is for a change I'm working on for the php5
extension ports. Currently, ports like php5-memcache just print a
message telling the user to add these lines to their php.ini:
I agree that ${prefix}/var/db is far from ideal, but at least it's
documented as mutable in hier(7). The same cannot be said for $
{prefix}/share, even though it might make more sense from a config
file vs "database" point of view. Think of "database" in the highly
abstract sense, if it he
