Two small install glitches
I've installed MythDora on two machines -- one backend/frontend and one frontend-only. It works great, and the install and setup were much more seamless than with KnoppMyth.
I did encounter two small glitches, though, that required me to do some manual intervention:
First, although the setup script asked me for a primary DNS server address when using a static IP, this did not get set properly. Consequently, mythsetup was not able to download the lineups from Zap2It on the first try. I had to exit, fix the DNS settting, then rerun mythsetup.
Second, when installing my frontend-only system, mythsetup did not set the backend server address in ~/.mythtv/mysql.txt. Here, too, I had to exit and edit the file manually before the frontend-only box would access the backend server.
Neither of these was a big deal, but might be something to address in the next distribution.
Thanks for the great work on MythDora!
Quote:First, although the
First, although the setup script asked me for a primary DNS server address when using a static IP, this did not get set properly.
I corrected this starting with version 3.1. You should have a copy of resolv.conf in /home/mythtv. This file is there in case resolv.conf has a hiccup. When you fire up mythtvsetup for the first time resolv.conf gets checked for a nameserver and if it's not there then it copies over the one from your home directory.
Second, when installing my frontend-only system, mythsetup did not set the backend server address in ~/.mythtv/mysql.txt.
You always have to do this. I have this stated in the FAQ.
"Please ignore the man behind the curtain"
Dennis
"Please ignore the man behind the curtain"
Dennis
Re: Quote:First, although the
I corrected this starting with version 3.1. You should have a copy of resolv.conf in /home/mythtv. This file is there in case resolv.conf has a hiccup. When you fire up mythtvsetup for the first time resolv.conf gets checked for a nameserver and if it's not there then it copies over the one from your home directory.
I just installed Mythdora 3.2 and had the same problem. Static IP all that and when it was time to use the network during the setup I got nothing. Had to exit MythTV and setup the network then repeat some of it.
Still don't see how that can
Still don't see how that can fail. I have things writing out to a seperate file and then it gets inserted again to make sure. I tested this dozens of times to make it break and it worked everytime. Do you in fact have a file written out to /home/mythtv called resolv.conf? And what are the contents?
"Please ignore the man behind the curtain"
Dennis
"Please ignore the man behind the curtain"
Dennis
Re: Still don't see how that can
Still don't see how that can fail. I have things writing out to a seperate file and then it gets inserted again to make sure. I tested this dozens of times to make it break and it worked everytime. Do you in fact have a file written out to /home/mythtv called resolv.conf? And what are the contents?
# ls /home/mythtv
Desktop install_options resolv.conf
# cat /home/mythtv/resolv.conf
nameserver 207.69.188.185
#
This is the DNS address I entered.
Thats correct. And this is
Thats correct. And this is what gets reinserted back because the nameserver was empty and thats the problem everyone was having. Your problem lies with something else.
"Please ignore the man behind the curtain"
Dennis
"Please ignore the man behind the curtain"
Dennis
Interesting. Looks like
Interesting. Looks like someone else had a similar problem. I could repeat this problem all day. I don't know what happens between the terminal window network setup problems and the real network configuration but it my case it didn't get there, and when I put it there things worked.
Thanks for the reply!That
Thanks for the reply!
That sounds great.