Self-install-existing

Installation in an existing Fedora machine

NOTE: this is NOT a recommended method to install, unless it's done on a fairly clean install of the distribution. The reason is that some things that may have been done to the machine that may affect the way Amahi behaves. The recommended method is doing it from scratch.

It is important to note that, Amahi cannot be fully uninstalled in the traditional sense, because the settings affect some subsystems across the machine and the original state of those subsystems is not preserved.

Regardless, here are the install instructions, all of them executed as root.

Fedora 14

See below section for Fedora 12 1. Installed standard FC14, without adding an Amahi repository 2. Create /etc/yum.repos.d/amahi.repo including following text:

 [amahi]
 name=Amahi repository for Fedora $releasever
 baseurl=http://f$releasever.amahi.org/
 gpgcheck=0
 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-amahi

3. run: yum clean all 4. run: yum update - but answer no (N) and don't install the updates 5. run: yum install hda-suite - will ask to install ~173MB/65 packages. Say yes (Y) of course :)

Fedora 12

Install the Amahi release for Fedora 12

1. Install the hda-release

• rpm -Uvh <latest_rpm repo="amahi-f12" rpm="hda-release" arch="noarch" output="url" />

2. Install hdactl (64 or 32bit)

• 32bit - rpm -Uvh --nodeps <latest_rpm repo="amahi-f12" rpm="hdactl" arch="i386" output="url" />
• 64bit - rpm -Uvh --nodeps <latest_rpm repo="amahi-f12" rpm="hdactl" arch="x86_64" output="url" />

3. Now install hda-platform

• rpm -Uvh --nodeps <latest_rpm repo="amahi-f12" rpm="hda-platform" arch="noarch" output="url" />

4. Install dependencies:

• yum -y install rubygems ruby-libs ruby-mysql

5. Start the Amahi installer.

• service amahi-installer start

6. And last but not least, get the installer going by accessing it with a browser:

      http://localhost:2000

Note: If after starting the install via the web interface (http://localhost:2000) you accidently kill the terminal window in which you started the 'service ' from, it does appear to complete OK.

From time to time this method may miss some dependencies. At the end, try this as root:

    rpm -Va  --nofiles

To make sure all the dependecies are met.

In both cases,

• Replace YOURINSTALLCODE with your install code, obviously
• Report bugs in the platform category!
• Save the output and paste it to the bug report.