On Mon, Apr 19, 2010 at 02:20:52PM -0700, Russ Allbery wrote:
[...]
> The most common convention adopted was to permit including a directory
> full of configuration files, where anything dropped into that directory
> would become active and part of that configuration. As that convention
> became more widespread, that directory was usually named after the
> configuration file that it was replacing or augmenting. But since one
> cannot have a directory and a file with the same name, some method was
> required to distinguish, so .d was appended to the end of the
> configuration file name.
[...]
The earliest example of this precedent which springs to mind is
replacement of the monolothic /etc/rc boot script with an /etc/rc.d
directory.
--
{ IRL(Jeremy_Stanley); PGP(9E8DFF2E4F5995F8FEADDC5829ABF7441FB84657);
SMTP(fu...@yuggoth.org); IRC(fu...@irc.yuggoth.org#ccl); ICQ(114362511);
AIM(dreadazathoth); YAHOO(crawlingchaoslabs); FINGER(fu...@yuggoth.org);
MUD(fu...@katarsis.mudpy.org:6669); WWW(http://fungi.yuggoth.org/); }
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100420012818.ga2...@yuggoth.org
