<br><br><div class="gmail_quote">On Fri, Jun 5, 2009 at 9:18 PM, Brian Wood <span dir="ltr"><<a href="mailto:beww@beww.org">beww@beww.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On Friday 05 June 2009 19:57:00 Nick F wrote:<br>
> On Fri, Jun 5, 2009 at 1:29 PM, Douglas Wagner <<a href="mailto:douglasw0@gmail.com">douglasw0@gmail.com</a>> wrote:<br>
> > Did a double network upgrade (8.04 -> 8.10 -> 9.04). The upgrade got<br>
> > hung up in the 8.10 ->9.04 side with some symbolic links to NFS shares<br>
> > and didn't install correctly. Removing and adding a few packages<br>
> > (basically a readd of the mythbuntu consolidated package) fixed the issue<br>
> > and has the machine up and running.<br>
> ><br>
> > The root cause seems to be myth being unable to read from NFS. I can<br>
> > unmount but not remount the NFS shares. Restarting NFS-COMMON doesn't<br>
> > seem to help.<br>
><br>
> I had an issue when upgrading one of my frontends from 8.10 to 9.04. The<br>
> network upgrade failed (with an error message about nfs). I mucked around<br>
> for a while - but in the end just wiped the HDD and installed Jaunty from<br>
> scratch using a CD. It didn't bother me too much reinstalling - being a<br>
> frontend I was up and running in a hour or so. I copied back my backed-up<br>
> fstab and everything, including nfs mounts, worked fine. I tend to leave<br>
> this particular frontend on 24x7 and it 's rock-solid and has never dropped<br>
> a nfs mount.<br>
<br>
</div></div>Hey folks, some of us don't run Ubuntu or Mythbuntu, so when you say something<br>
about "upgrading" a Myth frontend, then give a couple of Ubuntu version<br>
numbers, weak-minded people like me tend to get confused.<br>
<br>
We were discussing Myth upgrades, (having wandered off topic from the initial<br>
NFS problem). Do you mean you upgraded the OS without touching anything Myth,<br>
or do you mean you upgraded from one Mythbuntu version to another, which<br>
would seem to include both an OS and a Myth version upgrade? Or did you mean<br>
upgrading the OS, then manually installing an updated Myth version?<br>
<br>
I can see a benefit to Mythbuntu tracking Ubuntu release numbers, Mythdora<br>
moved to a similar scheme with FC version #s, but it means simply mentioning<br>
a version number could mean different things.<br>
<font color="#888888"><br>
--<br>
beww<br>
<a href="mailto:beww@beww.org">beww@beww.org</a><br>
</font><div><div></div><div class="h5">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br>As the OP I'll clarify. <br><br>Mythbuntu tracks with the Ubuntu Version Numbers: 8.04, 8.10 and 9.04 are the three most recent version numbers of Ubuntu.<br><br>A "distribution" (repackage) of Ubuntu specifically for MythTV is Mythbuntu (same as MythDora / Fedora). What probably got confusing was that Mythbuntu is also a PACKAGE that can be installed in a Ubuntu (base) system to provide myth capability. All of this has NOTHING to do with the MythTV Release (0.21.xxxx) version shipping within the Mythbuntu system.<br>
<br>--Doug<br>