On Tue, May 27, 2008 at 10:52:43AM -0700, Jordan Brown wrote: > Nicolas Williams wrote: > >Think, rather than svc FMRIs, how about cron FMRIs? > > I don't know enough about SMF to comment here. Since I view cron jobs > as being much like services - certainly as much like a service as a > network listener is - I want to be able to use all of the standard > "service" mechanisms to manage them - add, remove, enable, disable, > status, parameters. > > If cron jobs use "cron:" FMRIs, why do inetd-based network listeners use > "svc:" FMRIs instead of "inet:" FMRIs?
That's a good question, but I do think that in.inetd-managed services are still very much like svc.startd-managed services -- in fact, some services can easily work with either restarted (e.g., ssh). So I think it makes plenty of sense for inetd-managed services to have "svc" FMRIs. > >>IMHO, the right human readable representation is a GUI. > > > >Don't forget CLI/text-based UIs, and APIs. > > CLIs, yes, though I would consider them secondary as human interfaces. I don't. For one text-based UIs have nice a11y properties. > In particular, they can sacrifice readability for compatibility, > parseability, and extensibility. I don't follow. > APIs (other than CLIs) are by definition not intended for human > consumption :-) One word: developers. Nico --
