Hi Martyn...
Martyn Bright wrote:
> Can anyone suggest how I can arrange to boot a different
> dongle.bin on each of my 3 x H3 MVP's. I've tried using a
> different filename for each one in the dhcp configuration. The
> dongle.bin.config is happily retrieved from a seperate folder
> for each device, but it appears to be hardcoded somewhere to
> pick up the dongle.bin from the the tftpboot root directory.
>
> The reason I wish to do this is so that I can test any new
> install on my test device without trashing the ones that are in
> use by the family.
>
> dhpcd.conf.
> -----------
> option domain-name "trml.co.uk";
> option routers 192.168.0.205;
> option domain-name-servers 192.168.0.205;
> allow booting;
> allow bootp;
> default-lease-time 600;
> max-lease-time 7200;
> ddns-update-style ad-hoc;
> subnet 192.168.0.0 netmask 255.255.255.0 {
> range 192.168.0.225 192.168.0.232;
> }
> option option-150 code 150 = text ;
> group {
> host mvp1 {
> hardware ethernet 00:0d:fe:0c:47:a0;
> fixed-address 192.168.0.235;
> next-server 192.168.0.1;
> filename "/mvp1/dongle.bin";
> option root-path
> "/home/mvp1,rsize=4096,wsize=4096,nolock";
> }
> host mvp2 {
> hardware ethernet 00:0d:fe:23:72:78;
> fixed-address 192.168.0.234;
> next-server 192.168.0.1;
> filename "mvp2/dongle.bin";
> option root-path
> "/home/mvp2,rsize=4096,wsize=4096,nolock";
> }
> host mvp3 {
> hardware ethernet 00:0d:fe:23:72:64;
> fixed-address 192.168.0.233;
> next-server 192.168.0.1;
> filename "mvp3/dongle.bin";
> option root-path
> "/home/mvp3,rsize=4096,wsize=4096,nolock";
> }
> }
>
>
>
> dongle.bin.config.
> ------------------
> rdate -s 193.120.10.3
> TZ=UTC+0UTCDST,M4.1.0/2,M10.5.0/2; export TZ
> echo "TZ=UTC+0UTCDST,M4.1.0/2,M10.5.0/2; export TZ" >>
> /etc/shell.config
> mkdir /var
> mkdir /var/myth/
> echo 192.168.0.1 tvserver >> /etc/hosts
> echo 192.168.0.235 mvp1 >> /etc/hosts
> echo 192.168.0.234 mvp2 >> /etc/hosts
> echo 192.168.0.233 mvp3 >> /etc/hosts
> hostname mvp1
> mount -t nfs -o hard,tcp,nolock,rsize=4096,wsize=4096,nfsvers=3
> 192.168.0.1:/mnt/store/ /var/myth/
> cp /var/myth/mvpmc/themes/easy* /tmp/themes
> mvpmc -f /etc/helvB18.pcf -m pal -a 4:3 -o composite -S 0 -R
> 192.168.0.1 -s 192.168.0.1 -t /var/myth/mvpmc/themes/easy.xml
> --startup mythtv -F /var/myth/mvpmc/mvp1.cfg &
>
>
> TIA
>
> Martyn
I believe the trick is to name the dongles differently which causes the
associated dongle config to be used. What I use is the same dongle for
3 different mvpmcs. I have one real dongle file and "ln -s" the 2
others w/slightly different names. In the dhcpd.conf use the different
dongle names for different mvpmc boxes (I would get rid of the
directories and make it all flat). Then, the dongle config w/the
similar name should be used.
i.e.:
A dongle called dongle.bin.mvpmc001 will load the config file
dongle.bin.mvpmc001.config. And a dongle called dongle.bin.mvpmc002
will load the config file dongle.bin.mvpmc002.config.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Mvpmc-users mailing list
Mvpmc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/
