Red Hat 80 Vmware
Red Hat 80 Vmware
Click on New Virtual Machine, or Select: File | New | New Virtual Machine
Next
Next
I use the virtual machine name and location as specified above instead of the VMware defaults.
Next
You may want to adjust the guest size depending on the amount of physical memory.
Next
If you are on a network with a DHCP server, bridged networking works nicely. I need to
experiment how to switch between bridged networking and “Use host-only networking”.
Next
Next
Finish
Add
Next
Next
Next
OK
Enter
OK
Test
Perform a media check on CD 1 and CD 2, and then returned to CD 1 to start the installation
process. The check for each CD takes about 5 minutes.
Continue
[Mandrake seems to handle the VMware VESA drivers better than Red Hat.]
OK
About 11:00 to this point (assuming only one CD is checked above).
Autopartition
OK
Note that /usr and /home are on virtual drive 2 (sdb). I hope this allows easier migration of /usr
and /home in the future to new virtual systems.
OK
I’ve used LILO in the past but I’ll go with the default GRUB here.
OK
OK
OK
OK
No security for faster VMware virtual machine? What does this selection do? Linux still reports
“High “ for Red Hat Start Icon | System Settings | Security Level
Select a language
OK
OK
Development Tools
Editors
Engineering and Scientific
FTP Server
GNOME Desktop Environment
Graphical Internet
Graphics
KDE Desktop Environment
KDE Software Development
Network Servers
Office/Productivity
Printing Support
SQL Database Server
Server Configuration Tools
Sound and Video
System Tools
Web Server
Windows File Server
X Window System
OK
Prompt for second disk about 49:00 after starting. The estimated times on the screen are not all
that accurate and keep growing during the installation process.
Yes (But often I don’t bother with a boot disk for a VMware machine)
Skip X Configuration until after VMware tools are installed with VMware video drivers.
OK
Login as “root”
Install
yes
cd /etc/X11
cp XF86Config-4.vm XF86Config-4.vm.original
I don't understand the default contents of the file XF86Config-4.vm set by VMware. The default
settings take over my entire screen when I prefer to have Linux work just like another "Window"
under Windows.
Edit /etc/X11/XF86Config-4.vm
Chop out all the "ModeLine" statements above for resolutions that are larger than your physical
monitor. I usually keep the largest as 1152x900 when my physical screen is 1280x1024 or
1400x1050.
A few lines farther down, there are multiple "Display" sections. I delete all the high resolution
ones, and modify the last one to be the resolution I'd like to use when running Linux under
VMware: 1152x900 with Depth 24.
Note above the 1152-by-900 Linux “Window” on 1400-by-1050 Windows Screen on Dell
Inspiron 7500. My Windows toolbars can still be easily accessed at the right and bottom.
Logout as “normal” user. [Click on the Red Hat, and select Logout. In the command window,
enter logout.]
Login as “root”
Another change I make as “root” is to remove the passwords on both root and my “normal” user.
Since I don’t need much security on these machines on private networks.
6. VMware Files
The above is a list of the files that were created in Windows for the RedHat 8.0 virtual machine.
These files can be stored in two ZIPs since a single ZIP would be too large to fit on a single CD.
The largest file, disk2.vmdk, was stored inRedHat80B, while the other files were stored in
RedHat80A.ZIP.
Each of these ZIP files will fit on a CD. These files can then be used to re-create a new RedHat
8.0 box as it exists after installation.
A VMware quirk is that the audio driver is not automatically installed. In VMware, select the
RedHat 8 virtual machine, then Settings and Configuration Editor. Select the Add button.
On my Dell Inspiron 7500 the “ESS Maestro” sound adapter is the correct one.
Finish
8. Using FTP to Transfer Files from Old Virtual Linux Box Via “Network”
Multiple virtual Red Hat Linux machines can be run on the same host PC. These machines can
communicate via the network and files files can be transferred between these machines. Before
doing this, the virtual machines may need to be reconfigured to fit within available memory. In
VMware, select
The Red Hat 8.0 machine and Red Hat 7.2 machines were temporarily reduced to 128 MB so
they both could run. (Note the limit of all virtual machines is 288 MB with only 384 MB of
physical memory on my machine.)
On the “old” Red Hat 7.2 virtual machine I create .tar.gz files to prepare them for the transfer to
the new virtrual machine:
cd ~
tar cpvf - lab/* | gzip > transfer_lab.tar.gz
The files could be transferred directly between machines but I like creating these .gz files since I
also back them up at the time of transfer.
The above screen shows the Red Hat 7.2 machine. Run /sbin/ifconfig to get the IP
address of this Red Hat 7.2 machine, which is 192.168.1.14 in the example above.
Windows 2000 host with Red Hat 7.2 and Red Hat 8.0 virtual machines running
Use command line FTP to copy files to the Red Hat 8.0 box from the Red Hat 7.2 box:
ftp 192.168.1.114
<userid>
<password>
prompt off
mget *.gz
quit
After extracting these transferred files, remember to reconfigure the Red Hat 8.0 machine back to
having 256 MB of virtual memory.
9. Installing Kylix
Login as a “normal” user and start the X-server (“startx”) if necessary.
Open a terminal window. In Red Hat 8: Red Hat Icon | System Tools | Terminal
Insert Kylix 3 CD
cd /mnt/cdrom
sh setup.sh –m (for Kylix 3)
sh.setup.sh (other versions of Kylix)
Press enter many times to view the Kylix license. [Unlike the Mandrake installation, Red Hat
does not seem to recognize the correct graphics environment and uses a text-only installation
scheme.]
Log Out
OK
Create a terminal window and run Kylix (I’m not sure why Kylix is not added to the Red Hat
start menu, like it was with Mandrake 9.0).
Register Now
Next
Enter the Serial Number and Authorization Key from the CD Case.
Next
Next
If you’ve already registered your copy of Kylix, you can avoid the following by selecting
“Register Later” and never registering this copy. Other, enter:
Next
Next
Wait while fonts are generated. This can take several minutes.
The first time Kylix is launched it still shows as “Unregistered”. In subsequent launches, the
splash screen will show the product is registered.
Samba can make the transfer of files between the VMware virtual machine and the Windows
host machine quite easy. Samba is usually installed as part of the RedHat installation. The
following assumes that Samba is installed.
I want to share /home/earl and /home/data from my Red Hat 8.0 virtual machine with the
machines in my GLYNN workgroup. Anyone can read or write to the “data” directory, while
read-only access is granted to the “earl” directory by setting permissions (using the Linux chmod
command):
In my personal Windows network I often connect PCs using a “GLYNN” workgroup with
minimal security considerations (since the network is private). The VMware virtual machine can
share files with this workgroup by configuring the file /etc/samba/smb.conf. First make
a copy the original smb.conf file:
cd /etc/samba
cp smb.conf smb.conf.original
=>cat smb.conf
[global]
netbios name = RH80
workgroup = GLYNN
log level = 2
log file = /etc/samba/samba.log
security = share
[data]
path = /home/data
browseable = yes
guest ok = yes
read only = no
[earl]
path = /home/earl
browseable = yes
guest ok = yes
read only = no
OK
On the Windows 2000 host machine using Windows Explorer, look for “Computers Near Me”
The contents of the RH8 (Red Hat 8) directories are visible from Windows. Files can be
transferred between Windows and Linux quite easily using the Windows Explorer. Some useful
Samba links include:
Configuring Samba
http://www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/custom-guide/s1-samba-
configuring.html