James Carlson wrote: > Scott Rotondo writes: >> James Carlson wrote: >>> Darren J Moffat writes: >>>> We already have a "system" project why not: >>>> "system.inetd" >>>> "system.foo" >>> I think Scott's concern about nesting is valid, but that's otherwise a >>> nice idea. >>> >> I have another suggestion. Seeing that /etc/project already uses >> user.<name> and group.<name>, why not svc.<name>, where <name> is >> derived from the service FMRI? That seems sufficient to achieve our real >> purpose, which is creating unambiguous names rather than reserving a >> Sun- or Solaris-controlled namespace. > > Doubleplus good.
Like the use of svc as well when this is for a service, for other cases that aren't services (do we have any of those still ?) I'd be equally happy if system were used, but I'd prefer just one prefix (svc) be used unless there was a compelling reason otherwise. -- Darren J Moffat
