LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2006-03-25 14:34:04 +00:00
parent 6375328897
commit 5986dc3769
1 changed files with 30 additions and 90 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

120
LDP/howto/docbook/Fedora-Multimedia-Installation-HOWTO.xml
View File

@ -21,12 +21,20 @@
</author>
<revhistory>
<revision>
<revnumber>5.1</revnumber>
<date>2006-03-25</date>
<authorinitials>esr</authorinitials>
<revremark>
Simplified and corrected some FC5 instructions.
</revremark>
</revision>
<revision>
<revnumber>5.0</revnumber>
<date>2006-03-21</date>
<authorinitials>esr</authorinitials>
<revremark>
Update for Fedora Core 5. On the one hand, we can get almost
Update for Fedora Core 5. On the one hand, we can get almost
everything from livna now, which simplifies life. On the other
hand, Totem and Xine are both completely broken.
</revremark>
@ -275,83 +283,14 @@ RPMforge as I advised in previous versions of this FAQ. I say
'theoretically' because, in fact, almost none of the video stuff actually
works in FC5.</para>
<!--
<para>To enable access to the RPMForge repositories, drop the following
into <filename>/etc/yum.repos.d/rpmforge.repo</filename>:</para>
<programlisting>
# RPMForge repositories
[dag]
name=Dag RPM Repository for Fedora Core
baseurl=http://apt.sw.be/fedora/$releasever/en/$basearch/dag/
enabled=1
gpgcheck=1
[freshrpms-core]
name=FreshRPMS-Core
baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/core
enabled=1
gpgcheck=1
[freshrpms-updates]
name=FreshRPMS-Updates
baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/updates
enabled=1
gpgcheck=1
[freshrpms-fresh]
name=FreshRPMS-Fresh
baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/freshrpms
enabled=1
gpgcheck=1
[dries]
name=Extra Fedora rpms dries - $releasever - $basearch
baseurl=http://ftp.belnet.be/packages/dries.ulyssis.org/fedora/linux/$releasever/$basearch/dries/RPMS/
enabled=1
gpgcheck=1
[newrpms.sunsite.dk]
name=Fedora Core 4 i386 NewRPMS.sunsite.dk
baseurl=http://newrpms.sunsite.dk/apt/redhat/en/i386/fc4
enabled=1
gpgcheck=1
</programlisting>
<para>Now you need to import the GPG keys that verify packages from these.
Do this from a root shell: </para>
<programlisting>
rpm &#45;&#45;import http://dag.wieers.com/packages/RPM-GPG-KEY.dag.txt
rpm &#45;&#45;import http://freshrpms.net/packages/RPM-GPG-KEY.txt
rpm &#45;&#45;import http://dries.ulyssis.org/rpm/RPM-GPG-KEY.dries.txt
rpm &#45;&#45;import http://newrpms.sunsite.dk/gpg-pubkey-newrpms.txt
</programlisting>
-->
<para>To enable access to livna, do this:</para>
<programlisting>
rpm -Uvh http://rpm.livna.org/fedora/5/x86_64/livna-release-5-4.noarch.rpm
rpm -ivh http://rpm.livna.org/livna-release-5.rpm
</programlisting>
<para>If this doesn't work, the version number may have changed;
<ulink url='http://rpm.livna.org/fedora/5/'>go to the repo</ulink>,
drop into the directory for your processor type, and see.</para>
<para>This should drop a yum repo configuration file in
<filename>/etc/yum.repos.d/</filename> If that retrieval fails, the livna
people may have bumped the version on the file &mdash; follow the
directions <ulink
url='http://rpm.livna.org/configuration.html'>here</ulink>.</para>
<para>After you do this, I recommended setting the enabled variable on both
entries to 0. This is so you won't do a mass update and get package
clashes between the livna and RPMForge repositories. You can still, when
you need to, use the <option>--enable-repo</option> option of yum to grab a
specific package from livna. Under FC4 or later this key should be
automatically installed the first time you do a retrieval.</para>
<filename>/etc/yum.repos.d/</filename></para>
</sect1>
<sect1><title>Security considerations and other risks</title>
@ -365,10 +304,11 @@ you and a repository.</para>
<para>To control the latter risk, many repositories cryptographically sign
their RPMs. You need to have a local copy of each repository's public key
in order to integrity-check incoming packages. This could be defeated by a
man-in-the-middle attack spoofing the repo site and slipping you bogus keys
as you set up your configuration; while this possibility is extremely
unlikely, you should be aware of it.</para>
in order to integrity-check incoming packages; current versions of yum will
dowmload one for you. This could be defeated by a man-in-the-middle attack
spoofing the repo site and slipping you bogus keys as you set up your
configuration; while this possibility is extremely unlikely, you should be
aware of it.</para>
<para>A long-term risk that you accept by using the proprietary code
referenced in this HOWTO is that of becoming dependent on the whims of a
@ -437,7 +377,7 @@ orignal GPL Flash plugin. Only handles SWF up to level 4.</para>
<listitem>
<para><ulink url='http://gplflash.sourceforge.net/'>gplflash2</ulink>
half-works, with painful amounts of flicker, and frequently crashhes
half-works, with painful amounts of flicker, and frequently crashes
Firefox. This rewrite of gplflash has been abandoned in favor of
gnash.</para>
</listitem>
@ -488,18 +428,18 @@ h263, ac3, asf, avi, real, mjpeg, and flash.</para>
<para>Fedora won't ship MP3-capable software because the Fraunhofer
Institute's patent license terms are not compatible with the GPL.</para>
<para>The default music player in FC5 is Rhythmbox, no longer xmms. I
struggled with Rhythmbox for several hours, but despite its pretty face I
found it unusable. It ignores track numbers &mdash; or, at least, is not
as smart at parsing them out of filenames as xmms is, and doesn't document
its import rules anywhere. Trying to beat it into playing MP3s is a
nightmare so scarifying that at one point I thought I was going to have to
reinstall my entire Linux system just to get the ability to play Oggs back,
because I couldn't figure out what piece of undocumented application state
had gotten scrambled or how to clear it. The documentation is in general a
bad joke &mdash; glossy, superficial, and with no useful content about
troubleshooting problems. The xmms player may not be as featureful or
as nice-looking, but it works better.</para>
<para>The default music player in FC5 is Rhythmbox. I struggled with
Rhythmbox for several hours, but despite its pretty face I found it
unusable. It ignores track numbers &mdash; or, at least, is not as smart
at parsing them out of filenames as xmms is, and doesn't document its
import rules anywhere. Trying to beat it into playing MP3s is a nightmare
so scarifying that at one point I thought I was going to have to reinstall
my entire Linux system just to get the ability to play Oggs back, because I
couldn't figure out what piece of undocumented application state had gotten
scrambled or how to clear it. The documentation is in general a bad joke
&mdash; glossy, superficial, and with no useful content about
troubleshooting problems. The xmms player may not be as featureful or as
nice-looking, but it works better.</para>
<para>To install xmms and make it MP3-capable, start by doing this:</para>
@ -568,7 +508,7 @@ RPM</ulink> and install it.</para>
rpm -e HelixPlayer
</programlisting>
before the 10GOLD version will work. x86_64 FC4 does not
before the 10GOLD version will work. x86_64 FC5 does not
include HelixPlayer.</para>
</sect1>