Tony Nguyen wrote:
> Scott Rotondo wrote:
>> Tony Nguyen wrote:
>>> 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
>>
> Scott,
>
> Disclaimer ;^) just an idea as I've not tested this. I think we can't
> simply enable the current default ssh as you suggested since the current
> default ssh service defines dependencies for a "functional" Solaris
> system and I would guess install miniroot wouldn't satisfy these
> dependencies(e.g. svc:/system/cryptosvc, autofs, filesystem/local).
> However, install miniroot is capable of running ssh so delivering
> another ssh service with a smaller set of dependency to operate in the
> miniroot environment.
>
> -tony
No, that's not the issue. As far as I know, there is no problem with
satisfying the dependencies for ssh in the miniroot environment. We
could enable ssh, and it would work fine.
Normally, we want ssh to be disabled when booting from install media, as
it is today. But it would be useful if there were something the user
could do to enable ssh on a specific boot instance.
Scott
