God, I was hoping I wouldn't have to go through that again. What a nightmare. Is there a way to export a channels.conf to import in to the new one or something?

Noob Question here sorry.

It seems that in a few weeks, the two options will be available:
1. Upgrade to next version of Knoppmyth (R5Fx)
2. Build mythtv and plugins svn from source and install.

I currently have R5F1, but made many minor tweaks / script additions (mainly in /usr/bin dir or with mythweb).
Am I correct in that by performing either of these options, I will lose my tweaks?

Additionally, I needed to do a lot of small setup stuff (getting sound card working with ALSA updates, etc.) Is it likely I will lose these settings?

For an upgrade it depends on how well you prepare. The standard backup script has hooks to automatically backup and restore additional files. All you need to do is know what those files are and add them to the appropriate lists.

For the build from source, it depends on what you build and install. For example, upgrading MythTV and XMLTV from source won't mess with your Alsa settings.

Either way the real secret is to do the prep work ahead of time. If you haven't already got good notes on what you changed, do a find for stuff newer than the /etc/.epoch file and figure out which are incidental (log files, recordings, ...) and which represent real changes that you made. Being a pro and someone who does a _lot_ of upgrades, I tend to keep my "notes" as scripts and diff patches. That way after an upgrade/downgrade/sidegrade it takes all of 2 minutes to log in and run them. The RF1 Hints contain a lot more information on this general theme.

Thanks!
With some recommendations in the past, I am using mondo to back up (wiki)
I am guessing this has those hooks for additional files you mentioned. I haven't done much more than create the backups.
As for logging, I haven't been keeping diffs, but a general excel sheet with a high-level description of all the files changed / functionality added. So hopefully that will be enough to get prepped well for the upgrade.
Anyway...didn't mean to hijack the thread with this topic. Back to SD.

I did the upgrade this morning and everything seems to be working fine including the weather. Thanks for the detailed instructions. The only thing that seems to be missing is the knoppmyth menu in the frontend. How do I go about restoring that?

Thanks

I've read in the posts that following Cecil's instructions today will leave you unable to get schedule data until SD opens up accounts. So is it possible to get and install the latest -fixes now and still work with the old xmltv or is there some code dependency between the current -fixes and new xmltv?


Assuming I can get the latest myth fixes without breaking Zap2It; would it save time later, or will I just have to recompile myth again once SD is ready for me to switch?

If I can do myth without breaking Z2I, and it's going to save time later; Am I correct that, this would mean doing everything after the "cd .." line in the CODE section of the first post.

Finallly, in the CODE section of the first post what was the initial working directory? "~" ?

Thanks

When I ran this my "current working directory" was one I created called "/myth/tmp/xml".

Marc

The Knoppmyth menu is part of the mainmenu.xml that gets overwritten when you install the new -fixes. Before you run the above you should make a copy to restore later. Then after the install just copy the mainmenu.xml back.

Since you have already upgraded here is the mainmenu.xml from R5F1.

Britney

UPDATE: My bad! I'm actually still getting listings from Z2L after updating myth to svn - when I first ran mythfilldatabase I could not connect to Z2L (401 Unauthorized) but a later scheduled run the next day ran fine and my listings are up-to-date. So you should be able to update to svn 0.20-fixes and still get the old listings until you are ready to switch to SD.

As marc posted, I've seen a post on the myth-users list that indicates that if your lineups are the same on SD, you should not have to delete your old listing sources and create new ones in mythtv-setup - you update XMLTV and myth per cecil's instructions here, then run mythtv-setup and update your existing source to SD, get the new lineups, and run mythfilldatabase afterwards.

FYI, SD is allowing registration currently. I was able to sign-up, and set up. Looks nice.

Now I'm ready for the update and I can go live!

I am wondering what the odds are that KM will have an upgrade release out before 1 Sep? I am willing to perform the upgrade myself, but if I can leave this in the qualified hands of the people who make KM, I'd just as soon do that

I followed Cecil's directions and almost everything appears to be back to normal using SD (thanks by the way, very painless). The only problems that I'm having involve channel names/icons. I imagine the icons can't be solved without getting the correct channel names, so let's start with that.

I tried to scan for channels using SD and it would not do anything. I tried it three or four times, it would pause and then stop. I could only scan using the tuner itself which meant I have "adding channel 2" "adding channel 3" etc for all of my channel names. Stdout for mythtv-setup shows it connecting to SD and it appears as though it works properly, no errors.

(edit) Solved my own problem by actually following the directions better by NOT scanning for any channels as I used to with zap2it.

Next version per Cecil
http://mysettopbox.tv/phpBB2/viewtopic.php?t=16190

_________________
-Roseville, Michigan USA
LinHES R8: FE/BE, FE (x2)

I've just "upgraded" my Knoppmyth box to R5F1, and I'm hesitant to try the instructions (even though I'm on the newest build now). Has anyone tried it on that version? Is it straightforward enough? (Sorry if this is a newb question, rather unfamiliar with the guts of Knoppmyth and I've already broken my mythbox once today...hence the upgrade... )

Moreover, has anyone tried to actually pull data from schedulesdirect using the update cecil published now that the service is live?

Yes, I have. His code example will take care of steps 1 and 2, and it took about 35 minutes for me to finish everything (2 of the steps took a while to perform, the make commands). I also switched restarted the backend before step 8 so that the mythfilldatabase could connect to it.

It's worked well although see my post above for the problems I've had with channel names.