Tony Nguyen wrote:
> Scott Rotondo wrote:
>> A question about the behavior of SMF milestones: If I specify a
>> milestone using boot arguments and that milestone depends upon a
>> disabled service, will the service be enabled?
>>
> No, I'm afraid. Milestones are also services with dependency on other
> smf services. Thus, a milestone won't automatically enable other
> services to satisfy its own dependency.
I was afraid that might be the case. So I guess the boot would just hang
waiting for the ssh service, which will never start because it's
disabled. That's probably the right behavior in general, but it's
unfortunate in this case.
>
>> If so, I'm wondering if that might be a solution to the following
>> problem. When running the miniroot environment found on the install
>> media, ssh is not enabled. However it is sometimes useful (for
>> debugging purposes) to boot with a way to log in remotely. Would it be
>> possible to specify an alternative milestone at boot time that would
>> cause ssh to be enabled?
>>
>> If not, is there another way to affect the SMF state via boot
>> arguments? I'm asking about a general mechanism, not creating a new
>> boot flag that would be interpreted to enable this one specific service.
> Currently, I believe there's no mechanism to affect a service's general
> enable state via boot argument. If this is strictly for install
> debugging, I wonder if it's possible for install miniroot to deliver
> another ssh service with different dependency criteria and
> enable/disable that service as necessary.
Not sure I understand what you're suggesting. I think the ssh service
dependencies are fine, as is the fact that it is normally disabled in
the miniroot. But how do you enable it for a particular boot of the system?
Scott
