Ubuntu Wiki

Include(MythTVTeam/Header)

Done

Docs To Be Written

• How users can test their hardware - step by step guide to show users how to download a daily CD, burn it, test hardware, and if needed, report the bug on LP
  • This will be detailed at the Hardware Support page [:MythTVTeam/MythTVHardwareSupport]

Specs to write / Investigations to do

Proposed tasks

Dapper

1. Backport edgy version of mythtv 0.20 to dapper.
2. Update dapper documentation to match edgy documentation and document differences.

Edgy

1. Break edgy documentation into a more modular design allowing pieces to be used for other version directions.

Feisty

1. Move ivtv and lirc modules into linux-restricted-modules.

   • Currently has a bug opened: https://launchpad.net/distros/ubuntu/+source/linux-restricted-modules-2.6.17/+bug/69534

2. Add ivtv firmware to restricted

   • Currently has a bug opened: https://launchpad.net/distros/ubuntu/+source/ivtv/+bug/68676

3. Add metapackages to automatically set up mythtv "profiles" or "roles". See the mythtv edgy documentation to better explain what these roles are.
4. Create a python based lircd.conf parser for writing a .lircrc. This will parse remote information and produce a list of all possible buttons. These will be easily assignable to different applications. A database will be internally maintained in the app for the possible buttons in each app.
5. Create a set procedure for how a user will run a testing version of mythtv to verify hardware/software functionality without sacrificing functionality of their current mythtv network.
6. Create a myth debconf that will automate setting the mysql-server bindaddress and securing mysql-server.
7. Clean up init scripts to use start-stop-daemon instead:
   • There has been a report in the IRC channel (#ubuntu-mythtv) that the init script looks for a PID file rather than checking the process is running - something that start-stop-daemon would be able to check itself. Not knowing enough about the procedure I cannot verify this (Juski).

Feisty + 1

1. Create a ubiquity derived installer to install directly into a mythtv "profile" or "role"

UDEV

1. Do some testing into whether mixed types of tv tuner devices can happily coexist (e.g. ivtv & DVB) AND be relied on to appear at the same device nodes repeatedly. Tuners 'moving around' is a major source of confusion for users (it was for Juski for a while too!).

2. Investigate ways to automate 'manual' (/etc/modprobe list) module loading (and by necessity, blacklisting) - to work around the above?

debconf stuff

1. Ask the user if they want to secure mysql if they do not have a root password. Warn about security issues!

2. Generate the 'random' mythtv user mysql password & display it, and tell the user where it's stored

3. Ask the user if the system is to be a standalone PVR or part of a MythTV network and configure bind-address in my.cnf accordingly

4. Configure the .htaccess file for mythweb so it uses the correct password from the very start.

5. Ask the user if they'd like to secure mythweb (htpasswd?).

6. Possibly check the filesystem on the recording partition & if it's ext3, enable 'gradual file deletes' in MythTV

• (database setting)

.BRBR [:CategoryMythTV]