On 9/6/05, <b class="gmail_sendername">Josh Owen</b> <<a href="mailto:josh_o_1@yahoo.com">josh_o_1@yahoo.com</a>> wrote:<div><span class="gmail_quote"></span><div><br>
I'm running FC3, but I assume these parts should still be relevant:<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">1.) in Fedora Core 4 there is no dhcp.conf in the /etc<br>directory. If I create a new one my dhcp server will
<br>not start. Where is this file located or what am I<br>doing wrong here</blockquote><div><br>
The file should be called /etc/dhcpd.conf. If you can't find
that, try ls -l /etc/dhcp* and see what files show up. Failing
that, stop and restart your dhcp server and look in /var/log/messages
for output from the server. That might give you some hints as to
where it's looking for a config file. If that still doesn't help,
try 'man dhcpd' or 'man dhcp'.<br>
<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2.) Fedora always sets the tftp server to be a default<br>of off. Where is the file to turn the default to "on"
</blockquote><div><br>
If you installed tftp from an rpm I believe it gets set up to run under
xinetd. Look in /etc/xinetd.d. There should be a file
called tftp (maybe tftpd). There should be several lines in this
file that set various things. One of those lines should look like
this:<br>
<br>
disabled = yes<br>
<br>
Change that yes to a no and restart xinet (/etc/rc.d/init.d/xinetd restart)<br>
<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">3.) I have both the donble.bin and the dongle.bin.conf<br>in the /tftpboot directory so if my tftp server is
<br>running I should have to configure anything else.<br>Correct?</blockquote><div><br>
Correct, that should be all you need to do assuming that your DHCP and tftp servers are set up correctly. <br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">4.) Which dongle.bin.conf way are you using<br> NFS configuration:<br> rdate -s
<a href="http://192.168.10.50">192.168.10.50</a><br> mkdir /var<br> mkdir /var/myth/<br> mount -t nfs -o<br>nolock,rsize=4096,wsize=4096,nfsvers=3<br>192.168.10.50:/var/myth/ /var/myth/<br>
mvpmc -f /etc/helvR10.fnt -s <a href="http://192.168.10.50">192.168.10.50</a><br>-r /var/myth/video &<br><br> Or standard configuration:<br> rdate -s <a href="http://192.168.10.50">192.168.10.50
</a><br> mvpmc -f /etc/helvR10.fnt -s <a href="http://192.168.10.50">192.168.10.50</a><br>&</blockquote><div><br>
I'm using the standard configuration. My reasoning for this is
that I read somewhere that mvpmc sometimes has A/V sync issues during
playback and I believe it mentioned something about this being related
to NFS. So I figured I'd just avoid the NFS mount and stream the
video straight from the backend. I haven't been using it long
enough to tell if it's having A/V sync issues or not so YMMV.<br>
<br>
</div></div>Brad Benson<br>
<br>