Fedora Linux VM Log Book (CMPSC 210)
( fizzle )
Quick links to some highlights in this log:
2011-02-06
- Began this log today (06 Feb 2011) although I installed
this VM about two weeks ago.
- And I didn't take a whole lot of notes as I went through
this install, mainly because it was sooooooooooo similar
to the Debian install.
- Therefore, beginning this log with these back-entry
details about the installation, which may admittedly be sketchy.
(I'll fill in details little by little as I remember or
re-discover things that I've done so far):
- Hostname: fizzle
- Static IP address will be: 192.168.0.22 (Mask 255.255.255.0)
- Added this to frazzle:/etc/hosts (frazzle is the VM host mochine).
- First regular user account: jay / Password: xdr5******
- root password: The same: xdr5******
- I/O controller: SCSI LSI Logic (as recommended)
- Virtual hard disk: 10 GB, split into multiple pieces
Virtual file name: fizzle.vmdk (et seq.)
- Installation done.
- Reboot. Successful pings in and out.
- Edit /etc/samba/smb.conf -- Set workgroup = DRAGONET
- Shutdown.
2011-02-06
- Fedora Linux VM (fizzle) started.
- Taking some screen shots, as assigned.
- Note, btw, that I can't use Ctrl-Alt-2 to go to a
plain-text mode, much as I might prefer to work that way,
because the host machine intercepts that and I get a
plain-text screen there instead.
- Shutdown.
2011-02-09
- Fedora Linux VM (fizzle) started.
- Change host name from fizzle.localdomain to
fizzle.GollyWhiz.com -- I am moving all my machines
to this. Edit /etc/hosts, add GollyWhiz.com to most
of the host names there.
- Where is network configuration information saved? There
is no /etc/network directory here, and no
/etc/network/interfaces file. Where is the static IP
and related stuff stored?
- Shutdown.
2011-02-17
- Fedora Linux VM (fizzle) started.
- Determined that SQLite IS already installed here, as /usr/bin/sqlite3,
Version 3.6.23.1 (released 30 Mar. 2010).
- Wrote shell script, mkusers.sh, to create SQLite database named cs210class.db
and populate it with our class data. Ran same. Then ran sqlite3 interactively
to view the results. (It helps if you already know some SQL.)
- Shutdown.
2011-02-20
- Having already created a new virtual disk in the Debian
VM, now want to see if same can be used in the
other two (openSUSE and Fedora) VM.
- Installed existing new virtual disk into Fedora VM.
(This is done with VMWare Add Hardware wizard, with
the VM NOT running.)
- Chose “Use existing virtual disk” instead
of “Create new virtual disk”.
- For name of virtual disk file, browsed to existing
file .../vmware/com-disk-2/com-disk-2.vmdk
- Fedora Linux VM (fizzle) started.
- Investigated the visibility and usability of the
new virtual disk here. Ran fdisk -l, created /mnt/sdb2
mount point, mounted /dev/sdb2 there, ran df, verified
that already existing files are visible and readable,
created new file, etc. Conclusion: Everything
works! — I'm not going to bother editing up
and posting the complete transcript because it's substantially
the same as the transcript
for creating the disk in the Debian machine, with just
a few differences:
- Skip running fdisk to create the partitions,
- Skip running mkfs.ext3 to create the file system,
since those steps should not be repeated.
- Did NOT add new disk to /etc/fstab here (yet). May do that
someday, when/if I decide I want that.
- Shutdown.
Note, BTW, that although this shared virtual disk gives me a way
to share files among the three Linux VM's, it's not the best
solution for doing that, since I can't (that I know of) also
share files with the host machine. Instead, I have a shared
folder in the host machine, which all of the VM's can mount
and use, for that purpose (and which my Windows machines can
also use).
Watch this space for further developments.