Christin Tran wrote: > Do you want service X to be part of m-u-s? Hard to say, > without asking what sysadmin fuctions are typical when I boot > into m-u-s.
Liane Praza wrote: > To put it simply, I don't see any reason to bother putting a new and > unbundled service into a late-boot milestone. But, there's no harm in > it either. Hmm. OK. Currently our service isn't in any of the milestones, which is compatible with what you're saying. However, it confused one of our QA people, so I'd like to probe a bit more. When we tell an administrator "you can configure the system to boot to milestone/multi-user-server", what do we tell them about what that *means*? What services should the SA expect to be running when the system is at m-u-s? If m-u-s is equivalent to init level 3, then the answer is "all of them", which would suggest that m-u-s should depend on all services. But then again, that's what "all" means, so what's the intended distinction between m-u-s and "all"? Perhaps m-u-s was a mistake, and init level 3 should be equivalent to "all", to avoid that gray area.
