* Wyllys Ingersoll <Wyllys.Ingersoll at sun.com> [2009-03-12 18:14]:
> This project will deliver an SMF manifest and script that will allow
> the tor relay daemon to be restarted via SMF. The SMF service will be:
> svc:/application/security/tor:default (Tor Relay Daemon)
A minor point on naming: I wonder if
network/security/tor
or even
network/tor
would be more clear. The skeleton of the namespace in 2002/547
(sanitized and included below) didn't really anticipate an
external-network-mostly service that was security related.
- Stephen
* What will "man -k onion" return?
----
8.2.3 Service FMRI naming
In this subsection and those following, we propose a convention for naming
services. Generally, we are trying to introduce only one or two layers of
service groupings to show relations, and naming services proper based on
* a functional description,
* a well-known component, or
* a standard protocol.
These choices may not provide suitable names for all services.
We propose the following top- (or two-level) names for services:
* milestone/ Synthetic services for clean dependency statements.
* device/ General device services.
* system/ Services concerned with host-centric, non-networked capabilities.
* system/security/ Low-level host-centric services implementing security
facilities.
* network/ Services concerned with host-centric, network infrastructure
capabilities[, and also services implementing standard internet protocols].
* platform/ Services concerned with host-centric, hardware- or
platform-specific capa-
bilities.
* application/ General software services.
* application/management/ Services implementing management facilities.
* application/security/ Services implementing high-level security
facilities.
(It probably cannot be stressed enough that [social and organizational
structures] should not be a basis for service name choices in Solaris.)
----
