38

My system has 132 directories whose names end in .d
There are also two scripts whose names end in .d

Aside from the two wayward scripts ('/usr/sbin/invoke-rc.d', '/usr/sbin/update-rc.d'), I assume that .d means directory... (but I do wonder why those scripts are so named).

In some cases, the .d directory's parent folder contains a file of the same name, but without the .d ending. 

# eg.
  /etc/apt/sources.list.d
  /etc/apt/sources.list

Is there some mystical Linux rationale to this naming style?

Is it a deeply entrenched naming convention, or is it about as absolute as 'foo' and 'bar'?

|improve this question
45

This is often used for directories (hence the "d") that contain a collection of partial configuration files. All files in the directory get combined, sometimes also with other files, to make the complete configuration. This is often done when traditionally there was only one configuration file (e.g. in your example sources.list) but there is a desire to make things more modular later.

As Laurence mentions, the /etc/rc?.d directories was probably one of the first times this custom was used.

|improve this answer
  • 10
    I would add to this that other names have a "d" appended to a name without the leading dot, but this does NOT mean directory, but "daemon" or service, such as "named" or "httpd". named is the DNS service, while httpd is the web service (Apache, for example). – jfmessier Oct 16 '10 at 0:59
  • 3
    And as for those two "wayward scripts" mentioned in the question: their names are referring to the /etc/rc?.d directories. – Laurence Gonsalves Oct 16 '10 at 1:09
  • 1
    Thanks.. You've all contributed to a good all-round explanation. – Peter.O Oct 16 '10 at 4:30

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.