Page 1 of 1

2nd diskless reports minimyth.conf not found

Posted: Wed Jun 13, 2007 2:24 am
by mtnbkr
Just built a second minimyth front end with another VIA EPIA ME6000G Fanless Mini-ITX Mainboard.

My 2nd FE requires that I use the RCA/TV out instead of the VGA out so I need to have multiple minimyth.conf files.

I found in the docs and in irc someone verified that instead of putting minimyth.conf into the default tftproot/PXEClient/conf/default directory, that I should put it into a dir under cont based on the unit's MAC address.

I have tried this using both CAPs and lower case letters and still get the 'miniimyth.conf not found' error during the startup...

Any ideas?

THANKS. And Thanks for minimyth!

--
Bill Arlofski
Reverse Polarity, LLC

Posted: Wed Jun 13, 2007 4:32 am
by Pablo
The directory under the conf directory should be the hostname of the frontend.

Posted: Wed Jun 13, 2007 12:13 pm
by mtnbkr
Pablo wrote:The directory under the conf directory should be the hostname of the frontend.

Hmmm... Actually, I tried that first and thought that since the hostname of the frontend is defined in the minimyth.conf file that that didn't seem to make sense. Chicken/egg scenario. ...And that is when I found a posting saying that the dir should be the MAC address. Since I saw that on a wiki, I guess I should help them out and go back and edit it with the correct information. :)

I am guessing then, that the dir should be the DNS hostname of the frontend. If this is the case, then the minimyth frontend would do a reverse lookup of its IP address to find what directory to look under for it's config file, right?

heh Since I manage and maintain all of this (dhcp, dns etc etc) I 'spose I could find that out by looking at my logs.

Thanks Pablo!

Posted: Wed Jun 13, 2007 12:56 pm
by mtnbkr
I am guessing then, that the dir should be the DNS hostname of the frontend. If this is the case, then the minimyth frontend would do a reverse lookup of its IP address to find what directory to look under for it's config file, right?

heh Since I manage and maintain all of this (dhcp, dns etc etc) I 'spose I could find that out by looking at my logs.
Ok Ok... A little actual thinking helped me this time. It is the host-name DHCP option that tells the frontend what it's hostname is supposed to be, at which point it knows what directory to look in to get its specific config file.

Pablo, I know that you know this, but for anyone building multiple diskless minimyth front ends, you will need a block like this in your dhcpd.conf file defining each frontend:

Code: Select all

host myth1 {
        option host-name "myth1";
        hardware ethernet xx:xx:xx:xx:xx:xx;
        fixed-address 192.168.254.39;
        next-server 192.168.254.1;
        filename "PXEClient/pxelinux.0";


host myth2 {
        option host-name "myth2";
        hardware ethernet xx:xx:xx:xx:xx:xx;
        fixed-address 192.168.254.38;
        next-server 192.168.254.1;
        filename "PXEClient/pxelinux.0";
Remember to change each line above to match your FE's name, and MAC addresses as well as the rest of the network settings of course. Then, the directories under conf will be the same as the "host-name" option above for each frontend.

As always, thanks for minimyth!

--
Bill Arlofski