Difference between revisions of "Self-install-existing"

From Amahi Wiki
Jump to: navigation, search
Line 53: Line 53:
 
5. Start the Amahi installer.
 
5. Start the Amahi installer.
 
  service amahi-installer start
 
  service amahi-installer start
6. And last but not least, get the installer going by accessing it with a browser at <nowiki>http://localhost:2000</nowiki></code>
+
6. And last but not least, get the installer going by accessing it with a browser at <nowiki>http://localhost:2000</nowiki>
  
Note: If after starting the install via the web interface (<code><nowiki>http://localhost:2000</nowiki></code>) you accidently kill the terminal window in which you started the 'service ' from, it does appear to complete OK.
+
 
 +
Note: If after starting the install via the web interface (<nowiki>http://localhost:2000</nowiki>) 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:
 
From time to time this method may miss some dependencies. At the end, try this as root:

Revision as of 16:07, 7 November 2010

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 :)
  • Installer takes a few minutes to download the packages.
  • Warning about GPG keys appears after download:
 ...
 (64/65): samba-3.5.6-69.fc14.i686.rpm                                           | 5.0 MB     00:03     
 (65/65): wol-0.7.1-4.fc12.i686.rpm                                              |  38 kB     00:00     
 -------------------------------------------------------------------------------------------------------
 Total                                                                  253 kB/s |  56 MB     03:48     
 warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 97a1071f: NOKEY

fedora/gpgkey | 3.2 kB 00:00 ...

 Importing GPG key 0x97A1071F:
 Userid : Fedora (14) <fedora@fedoraproject.org>
 Package: fedora-release-14-1.noarch (@anaconda-InstallationRepo-201010211814.i386)
 From   : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-i386
 Is this ok [y/N]:
6. Select y to accept.  "Installing: ...." will appear for each package.
7. Install takes a few minutes, ends with a Complete! message.

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 at 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,