6 changes: 3 additions & 3 deletions mythtv/docs/mythtv-HOWTO-4.html
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
<H2><A NAME="Setting_up_paths"></A> <A NAME="s4">4.</A> <A HREF="mythtv-HOWTO.html#toc4">System Configuration Requirements for Compiling MythTV. </A></H2>

<P>Before you compile MythTV from the current source tarball or from
<B>subversion</B>, you may need to modify your system configuration in a
<B>git</B>, you may need to modify your system configuration in a
few ways.</P>
<P>In general, if you install MythTV from pre-packaged binaries for your Linux
distribution/version, you don't need to be too concerned about the issues in
Expand Down Expand Up @@ -46,11 +46,11 @@ <H3><A NAME="modifying_ld.so.conf"></A> Modifying /etc/ld.so.conf </H3>
<P>The runtime manager for shared libraries, <B>/lib/ld.so</B>, gets
information about the locations and contents of shared libraries from
<CODE>/etc/ld.so.cache</CODE>, a file created by <B>ldconfig</B> from
information in <CODE>/etc/ld.so.conf</CODE>. Because MythTV installs
information in <CODE>/etc/ld.so.conf</CODE>. Because MythTV installs
shared libraries in <CODE>/usr/local/lib</CODE>, that directory needs to be
added to the list of directories for <B>ld.so</B> to search when doing
runtime linking of programs, if it is not already there. You do this, as
root, by editing <CODE>/etc/ld.so.conf</CODE>, then running <B>ldconfig</B>.
root, by editing <CODE>/etc/ld.so.conf</CODE>, then running <B>ldconfig</B>.
There are many ways to do this; to determine the way that your distribution
is configured, type:</P>
<P>
Expand Down
38 changes: 18 additions & 20 deletions mythtv/docs/mythtv-HOWTO-5.html
Original file line number Diff line number Diff line change
Expand Up @@ -22,16 +22,16 @@ <H2><A NAME="DownloadAndCompile"></A> <A NAME="s5">5.</A> <A HREF="mythtv-HOWTO.
tarball is a static file and won't include any fixes for issues discovered
after the tarball was created.</P>
<P>The recommended solution is to download the source using
<B>subversion</B> to ensure that you've got the latest fixes.</P>
<P>When using subversion, there are some other choices that need to be made:
<B>git</B> to ensure that you've got the latest fixes.</P>
<P>When using git, there are some other choices that need to be made:
<UL>
<LI>Do you want to run the stable release of MythTV? If yes, download from the "release-0-23-fixes" branch.</LI>
<LI>Do you want to run the stable release of MythTV? If yes, use "git checkout 0.24"</LI>
<LI>Do you want to run the absolute latest developer code? If yes, you <EM>must</EM>
join the
<A HREF="http://www.mythtv.org/mailman/listinfo/mythtv-commits/">http://www.mythtv.org/mailman/listinfo/mythtv-commits/</A> and
<A HREF="http://www.mythtv.org/mailman/listinfo/mythtv-dev/">http://www.mythtv.org/mailman/listinfo/mythtv-dev/</A> mailing lists to
keep up to date with the current status of the code. Code obtained from
subversion has no guarantees regarding stability, etc. The latest code will be in "trunk".</LI>
git has no guarantees regarding stability, etc. The latest code will be in "master".</LI>
</UL>
</P>
<P>If you are in North America you will use the Schedules Direct grabber which is
Expand Down Expand Up @@ -60,38 +60,36 @@ <H2><A NAME="ConfigureSD"></A> <A NAME="ss5.1">5.1</A> <A HREF="mythtv-HOWTO.htm
<H2><A NAME="ss5.2">5.2</A> <A HREF="mythtv-HOWTO.html#toc5.2">Manually building MythTV</A>
</H2>

<P>If you are going to use <B>subversion</B>, execute the following
instructions to obtain the latest <EM>trunk</EM> version of MythTV.</P>
<P>To use the <EM>release</EM> version, you can execute the following. You are
strongly encouraged to use the release version.</P>
<P>If you are going to use <B>git</B>, execute the following
instructions to obtain the latest version of MythTV.</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
$ svn co http://svn.mythtv.org/svn/branches/release-0-23-fixes/ mythtv-0.23
$ cd mythtv-0.23
$ git clone https://github.com/MythTV/mythtv.git
</PRE>
</CODE></BLOCKQUOTE>
</P>
<P>To download trunk:</P>
<P>To use the <EM>release</EM> version, you can execute the following after
completing the previous command. You are strongly encouraged to use the
release version.</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
$ svn co http://svn.mythtv.org/svn/trunk/ mythtv-trunk
$ cd mythtv-trunk
$ git checkout 0.24
</PRE>
</CODE></BLOCKQUOTE>
</P>
<P><B>NOTE</B>: Using a svn version of the code allows you to stay
up-to-date with changes. So, if there's an update to the 0.23 release and
you originally obtained it using svn, you could enter the
mythtv-0.23 directory and type "svn up", which will update your copy
<P><B>NOTE</B>: Using a git version of the code allows you to stay
up-to-date with changes. So, if there's an update to the 0.24 release and
you originally obtained it using git, you could enter the
mythtv directory and type "git pull", which will update your copy
with the fixed version from the website. You would then recompile and
install the updated 0.23 code.</P>
install the updated 0.24 code.</P>
<P>If you are using the tarball, then unpack it:
<BLOCKQUOTE><CODE>
<PRE>
$ tar -xjf mythtv-0.23.tar.bz2
$ cd mythtv-0.23
$ tar -xjf mythtv-0.24.tar.bz2
$ cd mythtv-0.24
$ ./configure
</PRE>
</CODE></BLOCKQUOTE>
Expand Down
2 changes: 1 addition & 1 deletion mythtv/docs/mythtv-HOWTO-6.html
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ <H3><A NAME="modify_perm_mysql"></A> Modifying access to the MySQL database for
<CODE>mc.sql</CODE> script is only granting access to the local host.</P>
<P>To allow other hosts access to your master database, you can either
configure MySQL database access with no security or with additional
granularity. </P>
granularity.</P>
<P>
<FIGURE>
<EPS FILE="stop.eps">
Expand Down
50 changes: 25 additions & 25 deletions mythtv/docs/mythtv-HOWTO-8.html
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ <H2><A NAME="s8">8.</A> <A HREF="mythtv-HOWTO.html#toc8">Setting up a remote con

<P>MythTV does not have native remote control receiver and decoder software
built-in. Instead, remote control functions are implemented by cooperating
with <B>lirc</B>, the Linux Infrared Remote Control program.
with <B>lirc</B>, the Linux Infrared Remote Control program.
<B>lirc</B> handles the IR hardware and passes keystrokes to MythTV, which
then acts as if the user had pressed the keys on the keyboard. The file
<CODE>keys.txt</CODE> describes the keys used to control MythTV.</P>
Expand All @@ -33,7 +33,7 @@ <H2><A NAME="s8">8.</A> <A HREF="mythtv-HOWTO.html#toc8">Setting up a remote con
receiver senses the pulses and sends them to the lirc daemon. The lircd
loads a file called <CODE>lircd.conf</CODE> which instructs it how interpret the
IR pulses that it received and convert them to a human-readable name.</P>
<P>For example, the hardware may receive pulses may correlate to "Channel Up".
<P>For example, the hardware may receive pulses may correlate to "Channel Up".
The <CODE>lircd.conf</CODE> file will then contain a line that looks something
like this:</P>
<P>
Expand All @@ -44,18 +44,18 @@ <H2><A NAME="s8">8.</A> <A HREF="mythtv-HOWTO.html#toc8">Setting up a remote con
</CODE></BLOCKQUOTE>
</P>
<P>The <CODE>lircd.conf</CODE> file can have multiple remote controls defined.</P>
<P>The second part is <CODE>lircrc</CODE>, which takes the name of the button which
<P>The second part is <CODE>~/.lircrc</CODE>, which takes the name of the button which
was pressed ("ChannelUp") in the above example, and associates that to an
action to be performed by a program using the remote control. So in MythTV,
ChannelUp means one thing, while in <B>mplayer</B> it means something
different. <CODE>lircrc</CODE> gives you the flexibility of taking the name of
different. <CODE>~/.lircrc</CODE> gives you the flexibility of taking the name of
the button and having it perform different actions depending on which
program you're using at the time.</P>
<P><B>NOTE</B>: The definitions in <CODE>lircd.conf</CODE> come from the user
community, and there is no standard for the common button names. One
<CODE>lircd.conf</CODE> file may contain a definition for a button called
"ChannelUp", while another may contain a definition for "Chan+". Your
<CODE>lircrc</CODE> file must therefore be configured appropriately, or it won't
<CODE>~/.lircrc</CODE> file must therefore be configured appropriately, or it won't
work.</P>
<P>Look for pre-made lircd.conf configuration files at
<A HREF="http://lirc.sourceforge.net/remotes/">http://lirc.sourceforge.net/remotes/</A>. If you find one of your remotes
Expand Down Expand Up @@ -95,22 +95,22 @@ <H2><A NAME="s8">8.</A> <A HREF="mythtv-HOWTO.html#toc8">Setting up a remote con
<P>The next step is to convert those signals into something that can be used
to control MythTV. MythTV now includes native support for lirc and can
interact directly with it.</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
$ cd mythtv/contrib/config_files/lirc
$ cp lircrc.example ~/.lircrc
</PRE>
</CODE></BLOCKQUOTE>

or
<P>Example <CODE>~/.lircrc</CODE> files for configuring remote controls for MythTV are
available in the
<A HREF="http://www.mythtv.org/wiki/Category:LIRC_Configuration_Files">LIRC Configuration Files</A> category of the MythTV wiki. There are also
many pages providing details for specific remote controls in the
<A HREF="http://www.mythtv.org/wiki/Category:Remote_Controls">Remote Controls</A> category of the wiki.</P>
<P>After browsing the available configuration files,
you may copy/paste the desired configuration information into
<CODE>~/.lircrc</CODE> or download it from the wiki.
<BLOCKQUOTE><CODE>
<PRE>
$ cp lircrc.example.pinnaclestudiopctv ~/.lircrc
$ mythwikiscripts
</PRE>
</CODE></BLOCKQUOTE>

if you've got a Pinnacle Studio PCTV remote.
Follow the on-screen prompts to download the configuration file.</P>
<P>Once you've put the desired configuration into <CODE>~/.lircrc</CODE>, test it.
<BLOCKQUOTE><CODE>
<PRE>
$ irw
Expand Down Expand Up @@ -141,11 +141,11 @@ <H2><A NAME="s8">8.</A> <A HREF="mythtv-HOWTO.html#toc8">Setting up a remote con
<H2><A NAME="ss8.1">8.1</A> <A HREF="mythtv-HOWTO.html#toc8.1">Additional information for lirc</A>
</H2>

<P>Take a look at the lircrc.example files in the <CODE>contrib/configfiles/</CODE>
directory. In my case, (Pinnacle Studio card) the channel up and down functions
weren't working, due to the fact that the button names were different than
the default <CODE>lircrc.example</CODE> file that came with MythTV.</P>
<P>The <CODE>lircrc.example</CODE> file has this:
<P>Take a look at the example <CODE>~/.lircrc</CODE> files in the
<A HREF="http://www.mythtv.org/wiki/Category:LIRC_Configuration_Files">MythTV wiki</A>. In my case, (Pinnacle Studio card) the channel up and
down functions weren't working, due to the fact that the button names were
different from the example <CODE>~/.lircrc</CODE> I used to start my configuration.</P>
<P>The example file had this:
<BLOCKQUOTE><CODE>
<PRE>
begin
Expand Down Expand Up @@ -192,14 +192,14 @@ <H2><A NAME="ss8.1">8.1</A> <A HREF="mythtv-HOWTO.html#toc8.1">Additional inform
</CODE></BLOCKQUOTE>

which took care of basic functionality. Because the PCTV Studio remote
has additional buttons, look at the
<CODE>contrib/config_files/lirc/lircrc.example.pinnaclestudiopctv</CODE> for an example of how
has additional buttons, look at the
<A HREF="http://www.mythtv.org/wiki/Lircrc_-_Pinnacle_Studio_PCTV">lircrc - Pinnacle Studio PCTV</A> page for an example of how
to define additional buttons, and how to debug potential button name
conflicts between the <CODE>lircrc.example</CODE> file and how <B>your</B>
conflicts between your <CODE>~/.lircrc</CODE> file and how <B>your</B>
remote defines the button names.</P>
<P>By examining the button names defined in <CODE>/etc/lircd.conf</CODE> and using
the <B>irw</B> program to make sure that your remote is working, you can
create the appropriate mappings in <CODE>.lircrc</CODE> to get excellent remote
create the appropriate mappings in <CODE>~/.lircrc</CODE> to get excellent remote
functionality with MythTV.</P>
<P>Note the <B>repeat =</B> parameter. This informs the <CODE>irxevent</CODE>
program to pass through every third keypress. By default, <CODE>lirc</CODE>
Expand Down
7 changes: 4 additions & 3 deletions mythtv/docs/mythtv-HOWTO-9.html
Original file line number Diff line number Diff line change
Expand Up @@ -360,7 +360,7 @@ <H3>How to use Storage Groups.</H3>
go into the Default Storage Group where they'll be the first programs
eligible for expiration if the system needs free space for recordings.</P>
<P>Usage information for all Storage Group directories is visible on the
mythfrontend status screen as well as the mythbackend status webpage.
mythfrontend status screen as well as the mythbackend status webpage.
MythTV is smart enough to determine which directories are on shared
filesystems so it should not count free or used space multiple times if you
have more than one directory on the same filesystem.</P>
Expand Down Expand Up @@ -575,8 +575,9 @@ <H2><A NAME="ss9.5">9.5</A> <A HREF="mythtv-HOWTO.html#toc9.5">Grabbing channel
</P>
<P>If you do not have XMLTV software installed and do not want to install it
for the sake of this minor task, there is a generic
<CODE>contrib/master_iconmap.xml</CODE> which you can copy and use but this may
not be as complete as using the specific information for your service.</P>
<CODE>contrib/icons/master_iconmap/master_iconmap.xml</CODE> which you can copy
and use but this may not be as complete as using the specific information
for your service.</P>
<P>Once you have an <CODE>iconmap.xml</CODE> file, add the icon information to your
database and grab any new icons with the command:
<BLOCKQUOTE><CODE>
Expand Down
268 changes: 132 additions & 136 deletions mythtv/docs/mythtv-HOWTO-singlehtml.html

Large diffs are not rendered by default.

Binary file modified mythtv/docs/mythtv-HOWTO.pdf
Binary file not shown.
752 changes: 382 additions & 370 deletions mythtv/docs/mythtv-HOWTO.txt

Large diffs are not rendered by default.