Since init scripts live in a single directory, they must share a single namespace. To avoid conflicts, three means of assigning names from this namespace are provided:
Assigned names. Such names must be chosen from characters in the set [a-z0-9]. This category is desirable for scripts which system administrators may need to run manually: e.g., /etc/init.d/named restart. In order to avoid conflicts these names shall be reserved through the Linux Assigned Names and Numbers Authority (LANANA). Information about the LANANA may be found at www.lanana.org.
Note: Commonly used names should be reserved in advance; developers for projects are encouraged to reserve names from LANANA, so that each distribution can use the same name for the project's init script and avoid conflicts with other projects.
Hierarchical names. Script names in this category take the form <hier1>-<hier2>-...-<name>, where name is chosen from characters in the set [a-z0-9], and where there may be one or more <hier-n> components. <hier1> may either be an LSB provider name assigned by the LANANA, or it may be the owners' DNS name in lower case, with at least one '.' (e.g., "debian.org", or "staroffice.sun.com"). The LSB provider name assigned by LANANA shall consist only of characters chosen from the set [a-z0-9].
Reserved names. Names in this category begin with the character '_', and are reserved for distribution use only. These names should be used for essential system packages only, and in general use of this part of the namespace is highly discouraged.
Note: In general, if a package or some system function is likely to be used on multiple systems, the package developers or the distribution should get a registered name through LANANA, and distributions should strive to use the same name whenever possible. For applications which may not be essential or may not be commonly installed, the hierarchical namespace may be more appropriate. An advantage to the hierarchical namespace is that there is no need to consult with the LANANA before obtaining an assigned name.
Short names are highly desirable, since system administrators may need to manually start and stop services. Given this, they should be standardized on a per-package basis. This is the rationale behind having the LANANA organization assign these names. The LANANA may be called upon to handle other namespace issues, such as package/prerequisites naming.