[mythtv-users] Double booting again: database issues?

[John Pilkington]

In an attempt to see 0.24 in action on my FE/BE multibooted box without 
overwriting my 0.23-fixes system, and to move away from F12 before its 
EOL, I upgraded first the 0.23/F12 to 0.23/F13 and then the dormant 
F10/0.22 to F12/0.24 - I tried to go to F14 but didn't persevere with 
that after it stalled, perhaps because my partition-identification 
incantation wasn't understood.

So I can now boot into either 0.23 or 0.24, but I see different 
databases.  That's OK if they remain independent, and I would (naively) 
expect that, because each lives in its own /var/lib/mysql folder.  But 
yesterday I rescanned the 0.24 tuners and last night the 0.23 system 
made several 0-byte recordings - and a few that were normal.  Is this 
likely to be a database corruption effect? Is there, for example, a 
cache that survives a reboot?  Or might it perhaps be mismatched or 
uninitialised  tuner firmware?  I've now ensured that the same firmware 
files are in both places and rescanned the tuners in 0.23, and at 
present that seems to be working as normal.

I asked about database transfer on the same box in February this year 
and Mike kindly put me straight.

TIA

John P