Orb Home   Index (& Links) Here   
Back to VM Beta 2 main page

Written Saturday January 29, 2000, 06:30

Installation script capture... My comments are in RED

 ./vmware-install.pl
Installing the content of the package.

In which directory do you want to install the binary files?
[/usr/bin] y

Clearly I wasn't reading properly at this point - 'y' isn't a directory -g-

The path "y" does not exist currently. This script is going to create it,
including needed parent directories. Is this what you want? [yes] no

In which directory do you want to install the binary files?
[/usr/bin]

In which directory do you want to install the library files?
[/usr/lib/vmware]

The path "/usr/lib/vmware" does not exist currently. This script is going to
create it, including needed parent directories. Is this what you want? [yes]

In which directory do you want to install the manual files?
[/usr/man]

In which directory do you want to install the documentation files?
[/usr/doc/vmware]

The path "/usr/doc/vmware" does not exist currently. This script is going to
create it, including needed parent directories. Is this what you want? [yes]

What is the directory under which the init scripts reside (it should contain
init.d/, and from rc0.d/ to rc6.d/)? [/etc/rc.d]

The installation of VMware 2.0 build-444 for Linux completed successfully. 
You can decide to remove this software from your system at any time by invoking the

following command: "/usr/bin/vmware-uninstall.pl".

Before running VMware for the first time, you need to configure it for your
running kernel by invoking the following command: "/usr/bin/vmware-config.pl".
Do you want this script to invoke the command for you now? [yes]

Making sure VMware's services are stopped.

Stopping VMware services:
   Virtual machine monitor                                 [  OK  ]

Now for the EULA - unlike most windows EULA's which give you virtually no
rights, and less functionality, I usually read the licenses that come
with software for Linux - Nothing vastly exciting about this one, though.

You must read and accept the End User License Agreement to continue.
Press enter to display it.

VMware, Inc. End User License Agreement

Notice to User: This End User License Agreement (EULA) is a CONTRACT
between you (either an individual or a single entity) and VMware,
Inc. (VMware), which covers your use of either "VMware for Linux" or
"VMware for Windows NT and Windows 2000" and related software components,
which may include associated media, printed materials, and "online" or
electronic documentation.  All such software and materials are referred to
here as the "Software Product." If you do not agree to the terms of this
EULA, then do not install or use the Software Product.  By explicitly
accepting this EULA, however, or by installing, copying, downloading,
accessing or otherwise using the Software Product and/or license key,
you are acknowledging and agreeing to be bound by the following terms:

1. WARNING -- "Beta" Version Software
This Software Product contains "pre-release" or "beta" code that
may be changed substantially before final commercial release.  You may
therefore not use any portion of the Software Product in a live
operating environment where it may be relied upon to perform in the same
manner as a commercially released product or with data that has not been
sufficiently backed up.

2. GRANT OF NON-EXCLUSIVE LICENSE.
A software license key ("Software License Key") issued to a designated
user only by VMware or its authorized agents is required for each user
of the Software Product. This Software License Key enables a designated
user to use the Software Product on a single computer system.  Each user
on a multi-user computer system who uses VMware requires an additional
license, and associated Software License Key, for Software Product.

VMware grants you the nonexclusive, nontransferable right to have each
such designated user use the Software Product on a single computer
running validly licensed copies of the operating system for which the
Software Product was designed. You may not modify or create derivative
copies of the Software Product.  All rights not expressly granted to
you are retained by VMware.

Mere remote access to applications running in a Guest Operating System
running under the control of the Software Product, does not constitute
use of the Software Product requiring an additional license and associated
Software License Key.

You may make copies of Software Product as reasonably necessary for the
use authorized above, including as needed for backup and/or archival
purposes.  No other copies may be made.  Each copy must reproduce all
copyright and other proprietary rights notices on or in the Software
Product.

You may install each Software License Key on a single computer system
and make copies of the Software License Key as necessary only for backup
and/or archival purposes. No other copies may be made.  Each copy must
reproduce all copyright and other proprietary rights notices on or in
the license key. You may not modify or create derivative copies of the
Software License Key.

3. LICENSES REQUIRED FOR GUEST OPERATING SYSTEMS
The Software Product allows additional operating systems ("Guest Operating
Systems") to run on a computer system. You must have a valid licensed
copy of each Guest Operating System for such use.

4. INTELLECTUAL PROPERTY RIGHTS RESERVED BY VMWARE.
The Software Product is protected by U.S. and international copyright laws
and treaties, as well as other intellectual property laws and treaties.
You must not remove or alter any copyright notices on any copies of the
Software Product.  This Software Product copy is licensed, not sold.
Furthermore, this EULA does not grant you any rights in connection
with any trademarks or service marks of VMware.  VMware reserves all
intellectual property rights, including copyrights and trademark rights.

5. NO RIGHT TO TRANSFER.
You may not rent, lease, lend or in any way distribute or transfer any
rights in this EULA or the Software Product to third parties without
VMware's written approval and subject to written agreement by the
recipient of the terms of this EULA.

6. PROHIBITION ON REVERSE ENGINEERING, DECOMPILATION, AND DISASSEMBLY.
You may not reverse engineer, decompile, defeat license key encryption
mechanisms or disassemble the Software Product or Software License Key
except and only to the extent that such activity is expressly permitted
by applicable law notwithstanding this limitation.

7.  RESTRICTIONS ON PUBLICATION OF TEST RESULTS
You understand that you are receiving only a beta version of the
Software Product.  As such, the Software Product you receive is not
optimized for maximum speed and performance.  Moreover, you understand
that the speed and performance of the beta version of the Software
Product has been deliberately reduced in order to permit efficient de-
bugging, evaluation and error reporting.  You therefore agree not to
publish the results of any benchmarking or other testing of the Software
Product, except with a notice that the benchmarked or tested version of
the Software Product is a beta version; the notice must be prominently
and clearly displayed on any such publication.

8.  EXPIRATION OF THE SOFTWARE PRODUCT
The Software Product has an expiration date, after which you
understand and agree that you must stop using the Software Product.
VMware bears no liability for any damages resulting from use or
attempted use of the Software Product, and no duty to provide any
support, after the expiration date.

9. THIRD PARTY RIGHTS.
Any software provided along with the Software Product that is associated
with a separate license agreement is licensed to you under the terms
of that license agreement.  VMware will make available for review any
such third party license agreements if you contact VMware at the address
given below.

10. SUPPORT SERVICES.
VMware may provide you with support services related to the Software
Product.  Use of any such support services is governed by the VMware
polices and programs described in "on line" documentation and/or other
VMware-provided materials.  Any supplemental software code or related
materials that VMware provides to you as part of the support services
is to be considered part of the Software Product and is subject to
the terms and conditions of this EULA.  With respect to any technical
information you provide to VMware as part of the support services, VMware
may use such information for its business purposes without restriction,
including for product support and development.  VMware will not use such
technical information in a form that personally identifies you.

11. TERMINATION WITHOUT PREJUDICE TO ANY OTHER RIGHTS.
VMware may terminate this EULA if you fail to comply with any term or
condition of this EULA.  In such event, you must destroy all copies of
the Software Product and Software License Keys.

12. U.S. GOVERNMENT USE.
The Software Product is deemed to be "commercial computer software" and
"commercial computer software documentation" pursuant to DFAR Section
227.7202 and FAR Section 12.212, as applicable.  Any use, modification,
reproduction, release, performing, displaying or disclosing of the
Software Product by the U.S. government shall be governed solely by the
terms of this EULA and shall be prohibited except to the extent expressly
permitted by the terms of this EULA.

13. EXPORT RESTRICTIONS.
You will not export (including transferring electronically over any
network, including the Internet) or re-export the Software Product,
any part thereof, or any process or service that is the direct product
of the Software Product (collectively referred to as the "Restricted
Components"), to any country, person or entity -- even to foreign units
of your own company - in violation of U.S. export restrictions.

14. NO WARRANTIES.
YOU ACCEPT THE SOFTWARE PRODUCT AND SOFTWARE LICENSE KEYS "AS
IS," AND VMWARE (AND ITS THIRD PARTY SUPPLIERS AND LICENSORS)
MAKE NO WARRANTY AS TO ITS USE, PERFORMANCE, OR OTHERWISE.  TO
THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VMWARE (AND ITS
THIRD PARTY SUPPLIERS AND LICENSORS) DISCLAIM ALL OTHER
REPRESENTATIONS, WARRANTIES AND CONDITIONS, EXPRESS, IMPLIED,
STATUTORY, OR OTHERWISE, INCLUDING, BUT NOT LIMITED TO, IMPLIED
WARRANTIES OR CONDITIONS OF MERCHANTABILITY, SATISFACTORY
QUALITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND
NON-INFRINGEMENT. THE ENTIRE RISK ARISING OUT OF USE OR
PERFORMANCE OF THE SOFTWARE PRODUCT REMAINS WITH YOU.

15. LIMITATION OF LIABILITY.
THIS LIMITATION OF LIABILITY IS TO THE MAXIMUM EXTENT PERMITTED
BY APPLICABLE LAW. IN NO EVENT SHALL VMWARE (OR ITS THIRD PARTY
SUPPLIERS AND LICENSORS) BE LIABLE FOR ANY COSTS OF SUBSTITUTE
PRODUCTS OR SERVICES, OR FOR ANY SPECIAL, INCIDENTAL, INDIRECT,
OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT
LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS
INTERRUPTION, OR LOSS OF BUSINESS INFORMATION) ARISING OUT OF
THIS EULA OR THE USE OF OR INABILITY TO USE THE SOFTWARE PRODUCT
OR THE FAILURE TO PROVIDE SUPPORT SERVICES, EVEN IF VMWARE HAS
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.  IN ANY CASE,
VMWARE'S (AND ITS THIRD PARTY SUPPLIERS' AND LICENSORS') ENTIRE
LIABILITY ARISING OUT OF THIS EULA SHALL BE LIMITED TO THE GREATER
OF THE AMOUNT ACTUALLY PAID BY YOU FOR THE SOFTWARE PRODUCT OR
U.S. $5.00; PROVIDED, HOWEVER, THAT IF YOU HAVE ENTERED INTO A
VMWARE SUPPORT SERVICES AGREEMENT, VMWARE'S ENTIRE LIABILITY
REGARDING SUPPORT SERVICES SHALL BE GOVERNED BY THE TERMS OF
THAT AGREEMENT.

16. GOVERNING LAW; ENTIRE AGREEMENT.
This EULA is governed by the laws of the State of California, U.S.A.,
excluding the application of its conflict of law rules.  The United
Nations Convention for the International Sale of Goods shall not apply.
This EULA is the entire agreement between us and supersedes any other
communications or advertising with respect to the Software Product;
this EULA may be modified only by written agreement signed by authorized
representatives of you and VMware.

17. CONTACT INFORMATION
If you have any questions about this EULA, or if you want to contact
VMware for any reason, please contact VMware: VMware, Inc., 3145 Porter
Drive, Building F, Palo Alto, CA 94304, United States of America or
email [email protected].


Do you accept? (yes/no) yes

Thank you.

Next, building the bits required - unless you have a very stock kernel, then
VMware will build you the modules you need, but you must have the compiler
and kernel headers installed.

Trying to find a suitable vmmon module for your running kernel.

None of VMware's pre-built vmmon modules is suitable for your running kernel. Do
you want this script to try to build the vmmon module for your system (you need
to have a C compiler installed on your system)? [yes]

What is the location of the directory of C header files that match your running

kernel? [/usr/src/linux/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

make: Entering directory `/tmp/vmware/config/981/vmmon-only'
make[1]: Entering directory `/tmp/vmware/config/981/vmmon-only'
make[2]: Entering directory `/tmp/vmware/config/981/vmmon-only/driver-2.2.14-15
mdk'
make[2]: Leaving directory `/tmp/vmware/config/981/vmmon-only/driver-2.2.14-15m
dk'
make[2]: Entering directory `/tmp/vmware/config/981/vmmon-only/driver-2.2.14-15
mdk'
make[2]: Leaving directory `/tmp/vmware/config/981/vmmon-only/driver-2.2.14-15m
dk'
make[1]: Leaving directory `/tmp/vmware/config/981/vmmon-only'
make: Leaving directory `/tmp/vmware/config/981/vmmon-only'
The module loads perfectly in the running kernel.

Making sure that both the parport and parport_pc kernel services are available.

Trying to find a suitable vmppuser module for your running kernel.

None of VMware's pre-built vmppuser modules is suitable for your running kernel.
Do you want this script to try to build the vmppuser module for your system (you
need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmppuser module.

Building the vmppuser module.

make: Entering directory `/tmp/vmware/config/981/vmppuser-only'
make: Leaving directory `/tmp/vmware/config/981/vmppuser-only'
The module loads perfectly in the running kernel.

Do you want this script to automatically configure your system to allow your
Virtual Machines to access the host filesystem? (yes/no/help) yes

Enabling networking (this is required to share the host filesystem).

Trying to find a suitable vmnet module for your running kernel.

None of VMware's pre-built vmnet modules is suitable for your running kernel. Do
you want this script to try to build the vmnet module for your system (you need
to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmnet module.

Building the vmnet module.

make: Entering directory `/tmp/vmware/config/981/vmnet-only'
make: Leaving directory `/tmp/vmware/config/981/vmnet-only'
The module loads perfectly in the running kernel.

Enabling host-only networking (this is required to share the host filesystem).
Do you want this script to probe for an unused private subnet? (yes/no/help)
[yes] help

Virtual machines configured to use host-only networking are placed on a virtual
network that is confined to this host. Virtual machines on this network can
communicate with each other and the host, but no one else.

To setup this host-only networking you need to select a network number that is 
normally unreachable from the host. We can automatically select this number for
you, or you can specify a network number that you want.

The automatic selection process works by testing a series of Class C subnet
numbers to see if they are reachable from the host. The first one that is
unreachable is used. The subnet numbers are chosen from the private network
numbers specified by the Internet Engineering Task Force (IETF) in RFC 1918
(http://www.isi.edu/in-notes/rfc1918.txt).

Remember that the host-only network that virtual machines reside on will not be
accessible outside the host. This means that it is ok to use the same number on
different systems so long as you do not enable communication between these
networks.

Do you want this script to probe for an unused private subnet? (yes/no/help)
[yes] no

What will be the IP address of your host on the private network? ^[[F^[[5~^[[B^
192.168.0.5

What will be the netmask of your private network? 255.255.255.0

Press enter to display the DHCP server copyright information.

The VMware host-only networking support uses a customized version
of the DHCP server application distributed by the Internet Software
Consortium (ISC).  This software is used in compliance with their
copyright notice which appears in its entirety below.

Please note that it is NOT advised that you use our customized
server for normal DHCP service; you can retrieve this software
directly from the ISC (http://www.isc.org).

#
# Copyright (c) 1996, 1997, 1998 The Internet Software Consortium.
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
#
# 1. Redistributions of source code must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
#    notice, this list of conditions and the following disclaimer in the
#    documentation and/or other materials provided with the distribution.
# 3. Neither the name of The Internet Software Consortium nor the names of its
#    contributors may be used to endorse or promote products derived
#    from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE INTERNET SOFTWARE CONSORTIUM AND
# CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
# BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
# FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL
# THE INTERNET SOFTWARE CONSORTIUM OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
# INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
# (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
# SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
# STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
# ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
# OF THE POSSIBILITY OF SUCH DAMAGE.

This system appears to have a CIFS/SMB server (Samba) configured for normal use.
If this server is intended to run, you need to make sure that it will not
conflict with the Samba server setup on the private network (the one that we use
to share the host filesystem). Please check your /etc/smb.conf file so that:

. The "interfaces" line does not contain "192.168.0.5/255.255.255.0"
. There is a "socket address" line that contains only your real host IP address

Hit enter to continue.

Starting VMware services:
   Virtual machine monitor                                 [  OK  ]
   Virtual bidirectional parallel port                     [  OK  ]
   Virtual ethernet                                        [  OK  ]
   Bridged networking                                      [  OK  ]
   Host-only and samba networking (background)             [  OK  ]

You have successfully configured VMware to allow your Virtual Machines to access
the host filesystem. Would you like to add a username and password for accessing
your host filesystem at this time? (yes/no/help) [yes]

Please specify a username that is known to your host: brian

New SMB password:
Retype new SMB password:
Added user brian.
Password changed for user brian.

You have successfully configured VMware to allow your Virtual Machines to access
the host filesystem.  Your system appears to already be set up with usernames

Then I checked to make sure that my home directory didn't already contain
a .vmware directory, created one, then put into it the license that I got
sent to me under separate cover by VMware.

drwxr-xr-x   5 root     root         4096 Jan 26 12:08 ../
-rw-------   1 brian    brian         115 Jan 29 16:14 .Xauthority
-rw-r--r--   1 brian    brian        1899 Jan 26 12:08 .Xdefaults
-rw-------   1 brian    brian         336 Jan 28 21:05 .bash_history
-rw-r--r--   1 brian    brian          24 Jan 26 12:08 .bash_logout
-rw-r--r--   1 brian    brian         230 Jan 26 12:08 .bash_profile
-rw-r--r--   1 brian    brian         559 Jan 26 12:08 .bashrc
-rw-r--r--   1 brian    brian        4044 Jan 26 12:08 .emacs
drwxr-xr-x   4 brian    brian        4096 Jan 26 12:08 .kde/
-rw-r--r--   1 root     root         2096 Jan 26 12:09 .kderc
-rw-r--r--   1 brian    brian         185 Jan 26 12:08 .mailcap
drwxr-xr-x   5 brian    brian        4096 Jan 29 16:24 .netscape/
-rw-r--r--   1 brian    brian        3730 Jan 26 12:08 .vimrc
-rw-r--r--   1 brian    root            4 Jan 29 16:14 .wmrc
-rw-------   1 brian    brian         524 Jan 29 16:27 .xsession-errors
-rw-r--r--   1 brian    brian         598 Jan 26 12:08 .zshrc
drwxr-xr-x   4 brian    brian        4096 Jan 27 18:18 Desktop/
-rw-r--r--   1 brian    brian     3580853 Jan 29 16:19 VMware-1.1.2-364.tar.gz
-rw-r--r--   1 brian    brian     6039887 Jan 29 16:20 VMware-2.0-444.tar.gz
-rw-r--r--   1 brian    brian         660 Jan 29 16:32 license-2.0.beta
drwx------   2 brian    brian        4096 Jan 27 18:45 nsmail/
drwxr-xr-x   2 brian    brian        4096 Jan 28 20:54 perldev/
drwx------   2 brian    brian        4096 Jan 26 12:08 tmp/

[brian@grinch brian]$ mkdir .vmware
[brian@grinch brian]$ mv license-2.0.beta .vmware/.    

Orb Home   Index (& Links) Here   
Back to VM Beta 2 main page

All Content Copyright © 1999, 2000 Brian P. Bilbrey. All Rights Reserved.