Hello!

Sorry I can't remember where I read this before. I am looking for a document that would tell me what the file naming conventions are for. I forgot what this convention/structure is called, but I think this is supposed to be in addition to FHS.

Example:
TIA.

In my experience, configuration files generally have the extension *.conf, except for runtime configuration files, which tend not to have extensions and tend to be named "[program name]rc," such as "bashrc."

In certain cases, such as BSD style init systems such as used by slackware, the rc files that run during system initialization are named "rc.[process name]. Here's examples from my own system (the ones in the far left column are directories).

A web search for "linux file naming conventions" will turn up a number of good articles. This is an excellent one: https://library.stanford.edu/researc...es-file-naming

As an aside, it is common to use an underscore (_), not a hyphen (-), in Linux file names.

spamassassin .cf files start with 10_, 20_, etc., but .cf, not .conf
dovecot .conf files in /etc/dovecot/conf.d/ match that pattern
will show you all files on your system that match that pattern.

Perhaps my question did not come across as intended. What I really need is to understand when to use 10-x, 20-x, etc..

priority?
10-x is prossessed before 20-x, etc.

2 members found this post helpful.

That's exactly it. Grub2 is a good example of this.. I doubt this is a naming/filesystem convention as oppose to just a pragmatic solution utilised by some, for some purpose.

There are two main situations in which this kind of numbering takes place:

1) Programs that can process multiple configuration files need a way of coping with contradictions between them. A common rule is that later specifications override earlier ones. This in turn means that the files need to be processed in a particular order. Giving them a prefix number can ensure this, since files in a directory are always accessed in alphanumeric sorting order. Udev rules files work like this.

2) Sysvinit startup scripts also need to be processed in the correct order because many scripts depend on facilities that an earlier script has installed. So again, they have a sequence number for both startup (Snn) and shutdown (Knn).

3 members found this post helpful.

Thanks, and also thanks to Hazel. I guess I was just overthinking...