Difference between revisions of "Self-install-existing"
Line 24: | Line 24: | ||
* Installer takes a few minutes to download the packages. | * Installer takes a few minutes to download the packages. | ||
* A Warning about GPG keys appears after download, asnwer '''YES''' here: | * A Warning about GPG keys appears after download, asnwer '''YES''' here: | ||
+ | <div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 0 1em;"> | ||
... | ... | ||
(64/65): samba-3.5.6-69.fc14.i686.rpm | 5.0 MB 00:03 | (64/65): samba-3.5.6-69.fc14.i686.rpm | 5.0 MB 00:03 | ||
Line 37: | Line 38: | ||
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-i386 | From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-i386 | ||
Is this ok [y/N]: | Is this ok [y/N]: | ||
+ | </div> | ||
* Install takes a few minutes, ends with a ''Complete!'' message. | * Install takes a few minutes, ends with a ''Complete!'' message. | ||
* Start the Amahi web installer: | * Start the Amahi web installer: |
Revision as of 16:21, 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
- Installed standard Fedora 14, without adding an Amahi repository
1. Create /etc/yum.repos.d/amahi.repo as root user and include 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
2. We must tell it to use the Amahi repo:
yum clean all
3. Lets make sure its working (Answer NO, we do not want to update all):
yum update
4. Install the Amahi pieces and dependencies (173MB/65 packages; Answer YES):
yum install hda-suite
- Installer takes a few minutes to download the packages.
- A Warning about GPG keys appears after download, asnwer YES here:
... (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]:
- Install takes a few minutes, ends with a Complete! message.
- Start the Amahi web installer:
service amahi-installer start
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
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.