Latest revision as of 07:41, 18 January 2010

Trying out a virtual server for refbase:

Installed ubuntu-server

in a Virtual Machine

• Version ubuntu-9.10-server-i386

  minimal install. After install:

• sudo apt-get update
• sudo apt-get xinit
• sudo apt-get install kubuntu-desktop
• sudo apt-get install mysql-server

  root pw = refbaseufl

• sudo apt-get install apache2
• sudo apt-get install php5-mysql
• sudo apt-get install bibutils
• cd /usr/local/src; sudo wget -nd -np http://downloads.sourceforge.net/project/refbase/refbase/refbase-0.9.5/refbase-0.9.5.tar.gz?use_mirror=voxel
• cd /var/www/
• sudo tar -xzvf /usr/local/src/refbase-0.9.5.tar.gz

http://www.refbase.net/index.php/Installing_refbase

http://www.vmware.com/appliances/directory/1272

This solved the network issue:

Hi,

your problems sound exactly like the problem we ran into when cloning a Debian installation.

The root of the problem at our site was udev's handling of devices. Udev keeps a history of devices attached to the computer. What makes sense for i.e. USB sticks (that is, each USB stick you attach will be recorded and mounted to the same point when attached again at a later point in time), causes problems when systems are cloned.

There is a file /etc/udev/rules.d/z25_persistent-net.rules, where udev memorises, which hardware device should get named eth0. Here it looks like this:
# PCI device 14xx:16xx (tg3)
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", SYSFS{address}=="00:11:xx:xx:xx:xx", NAME="eth0"

When you run the image on another computer, the new network adapter is recognised on the PCI bus and a new entry in the above mentioned file is generated. "eth0" is already given to device 14xx:16xx, so the new device gets named "eth1".

If you delete this file, it will be rebuilt during the next system startup and your problem should go away.

Regards,
Rainer 

Now I can't start X. But this worked:

sudo apt-get update
sudo apt-get install kubuntu-desktop