[mythtv-users] Best options/howto for diskless frontends

Ross Boylan RossBoylan at stanfordalumni.org
Mon Feb 25 16:32:09 UTC 2013


On Fri, 2013-02-22 at 11:19 +0000, Paul Gardiner wrote:
> > iface eth0 inet dhcp
> >
> > so if-up leaves it alone. You may have to run
> >
> > echo "nameserver 192.168.0.1" | resolvconf -a eth0
> >
> > afterward if you want to access the internet (replace 192.168.0.1
> with
> > the IP address of your router).
> 
> You genius. That was it. I got around it in a slightly different way.
> I
> stuck the disk back in and ran yast2 to perform the change from dhcp
> to
> static. That way I could set up dns and default route in an
> environment
> that I was more familiar with. I then rsync'd again and noticed just
> a file in /etc/sysconfig had changed. It had the same effect: no
> longer
> did it deadlock.
> 
> Then my one remaining problem was that, out of the two kernels on my
> system, I'd picked the wrong one for mkinitrd (I'd assumed it would be
> the one that had a soft link called vmlinuz). It mostly worked with
> the
> wrong kernel, but the nvidia module wouldn't load, presumably because
> I'd built it for the other kernel.
> 
> Anyway, now it works. Thank you.
> 
> I'm not sure I completely understand the exact nature of the deadlock.
> I know the nfs mount was operational before that stage. Would the
> execution of if-up have temporarily disconnected it?
> 
I set the interface to manual in /etc/network/interfaces.
If you bring the network that supplies root down it will hose your
system, as you saw.  I think it will do so even if you bring the
interface right back up.

Bringing the network up also configures the nameserver, router, etc, and
so you need to arrange for those things to happen through other
channels, at least on Debian.  It sounds as if you've taken care of
that.

Ross Boylan



More information about the mythtv-users mailing list