Darren J Moffat wrote:
> Martin Bochnig wrote:
>
>> Darren J Moffat wrote:
>>
>
> Okay so you have 3 mounts instead of 1.
> That is 3 lines in one automount map in the nameservice - big deal.
>
> Solaris unlike some other systems really doesn't have a problem
> scaling to thousands of client side
Martin Bochnig wrote:
Darren J Moffat wrote:
Martin Bochnig wrote:
Okay, he is partially right: First you have more mount points when
staying SVR4 compliant with config dirs here and there.
Second, the nfs client may not have /etc/opt/csw or /etc/opt/mrtx yet,
and you need to mkdir them befor
Darren J Moffat wrote:
> Martin Bochnig wrote:
>
>> Okay, he is partially right: First you have more mount points when
>> staying SVR4 compliant with config dirs here and there.
>> Second, the nfs client may not have /etc/opt/csw or /etc/opt/mrtx yet,
>> and you need to mkdir them before you can m
Martin Bochnig wrote:
Okay, he is partially right: First you have more mount points when
staying SVR4 compliant with config dirs here and there.
Second, the nfs client may not have /etc/opt/csw or /etc/opt/mrtx yet,
and you need to mkdir them before you can mount.
Huh ? Thats that the automoun
UNIX admin wrote:
>>Later this year (Q2/Q3 2007) anyone (users of
>>Solaris 10++ [sparc and
>>x86/64]) will additionally have the alternative to
>>use the then
>>available MRTX packages, including MRTXseamonkey.
>>
>>
>
>Do you plan to deliver MRTXseamonkey in /opt/mrtx resp.
>
yes
>/etc/o
> Later this year (Q2/Q3 2007) anyone (users of
> Solaris 10++ [sparc and
> x86/64]) will additionally have the alternative to
> use the then
> available MRTX packages, including MRTXseamonkey.
Do you plan to deliver MRTXseamonkey in /opt/mrtx resp. /etc/opt/mrtx and
/var/opt/mrtx (for config an
