Cincinnerdi Tech Stuff

A mind-numbing read if ever there was one

Setting up Ubuntu web services – twice

leave a comment »

I’m setting up a web server on the Risky LAN and also setting up a VMWare machine to use with VMPlayer for the NetCom 5199 class. I’m using Ubuntu Edgy (6.10) and have installed:

  • minicom
  • Apache 2.0
  • MySQL 5.0 client and server
  • PHP 5 (and php5-cli which is listed for those who are afraid of Perl and Python)

During the installation it says:

  • Setting port 80 to listen. If not desired edit /etc/apache2/ports.conf
  • Could not determin the servers fully qualified domain name, using 127.0.0.1 (Later it forced a restart and got the same message two more times.)

On the last few installs of Ubuntu, I’ve been receiving an intermittant message at boot time:

Internal Error – failed to initialize HAL!

Today I’m getting this from the VM install, but not the real PC install. Rebooting has sometimes worked. It didn’t this morning. I changed the autologon to off and turned off, then restarted the VM. That seemed to work!
Now to install the VMWare tools. It only provides a rpm and a tar.gz version. Support docs say to use the latter and just run it as root and accept the defaults. I did and must have pressed enter over 20 times. It needed to “make” a version and needed a C compiler. I assumed since it’s Ubuntu, I didn’t have the needed development tools installed, but I pressed enter so more, accepted the default screen resolution of 800 x 600 and it seemed to proceed without complaint.
It says I’ll need to run /usr/bin/vmware-toolbox.

Interesting observation on the VMWare support site follows. I don’t think this should be a problem since I’m running on a P4 and I’d bet the PCs at Cincinnati State use Intel:

Known Issues -Migration to a Different Processor

VMware recommends you do not migrate a Linux virtual machine between hosts when one host is running on an AMD processor and the other is running on an Intel processor.

During installation, many distributions of Linux choose a kernel that is optimized for the specific processor on which it is being installed, and some distributions install a generic kernel by default, but provide architecture-specific kernels that the user can choose to install. The kernel might contain instructions that are available only on that processor. These instructions can have adverse effects when run on a host with the wrong type of processor.

Thus, a Linux virtual machine created on a host with an AMD processor might not work if migrated to a host with an Intel processor. The reverse is also true: a Linux virtual machine created on a host with an Intel processor might not work if migrated to a host with an AMD processor.

This problem is not specific to virtual machines and also occurs on physical computers. For example, if you move a hard drive with a Linux installation from an AMD machine to an Intel machine, you are also likely to experience problems trying to boot from that drive.

Advertisements

Written by scottledyard

2007, February 13th at 4:47 am

Posted in Apache, Linux, Minicom, MySQL, PHP

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: