*- On 6 Aug, H. Peter Anvin wrote about "Re: program map-types - y-a-way"
> Alvin Oga wrote:
>>
>> hi ya brian...hi peter
>>
>> i was just thinking of a different way ( script ) tooo...
>>
>> problem is if win95 ( viritual host stays down )...no problem
>> the script mounts it...and we're done...
>>
>> but while mounted... someone fires up the win95 virtual host w/ vmware...
>> than you are asking for disaster..
>>
>> if it was already up... than autofs can figure out what to do...
>>
>
> Indeed... you're putting the cart (the simulated system) before the
> horse (the real system). You would be better off statically mounting it
> on your Linux side, exporting it via Samba, and have the simulation pick
> it up that way.
>
Yes this is true. The problem is that the guest os needs at least one
drive to boot off of. This one can not be exported from samba for
boot. I would also prefer to use the vfat drives natively under the
guest win95 system as opposed to through another layer via samba. I
understand the limitations and drawbacks to this setup.
Thank you all for your help. I think I have it down now, I am building
my program map now. Just to clarify two things. 1) The program map is
a script such as shown by hpa and is the map file with the exacutable
bit set, this returns the '[-options] location' part of the map file. 2)
The key is taken from whatever command is making autofs try and mount a
directory under the mountpoint, there is no map file that has the keys
defined in it.
Thanks,
--
Brian
---------------------------------------------------------------------
Mechanical Engineering [EMAIL PROTECTED]
Purdue University http://www.ecn.purdue.edu/~servis
---------------------------------------------------------------------
