Stephen Hahn writes: > * 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
network/tor makes more sense to me. The other residents of network/security are specifically security protocols (Kerberos), and it's not clear that this belongs. But the line between "application" and "network" has never been apparent to me. There are many things in svc:/application that are actually networking features, such as application/print/rfc1179 and everything under application/management/*, as well as things under svc:/network that don't seem to be related to networking (such as network/rpc/meta and network/npiv_config). (Our FMRI structure within svc:/network is also quite unclear. In some cases, the path components represent implementation details [such as '/rpc/'], and in other cases, they represent groupings around a particular technology or protocol [such as '/dns/'].) The lack of a clear structure here was one of the comments on the original Greenline case. > * What will "man -k onion" return? Depends on how much you've had to drink, I'd guess. ;-} -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
