Page 1 of 2

Minimyth Ram or NFS version

Posted: Tue Sep 04, 2012 4:03 pm
by rdoac
I wrote this on the Myth-Users mailing list, but it was suggested that this would be better place for it.

I thought I'd play around the other day with minimyth, but can't get past mounting /minimyth. As I read it, it seems to be looking for some kind of local storage, which I don't want to use, I'd like everything working via NFS. Am using the 0.25 version of Myth and minimyth, and just want MythFrontend working.

As far as I can tell it's not pulling in the config file from the TFTP server.

Rob

Re: Minimyth Ram or NFS version

Posted: Tue Sep 04, 2012 4:45 pm
by JoeHenley
Rob,

The instructions on the "Documents" page are pretty helpful, ... complex, but helpful. There are also references in there for sources of info on setting up tftpboot, how to get pxelinux going, etc.

I also tend to keep pretty good notes on how I got an installation working; it helps when a year later I need to change something. What you've given us about your problem is pretty thin. If you can provide us more details on what you've done and where the problem arises, I'm sure folks on this site can help.

For example:
-- Are you using ram-minimyth or nfs-minimyth?
-- What are the contents of your /tftpboot directory, both sub-dirs and files?
-- What are the messages in the logs (on the front end, minimyth and messages; on the server, relevant lines from syslog) leading up to the problem?

Joe Henley

Re: Minimyth Ram or NFS version

Posted: Wed Sep 05, 2012 2:15 am
by rdoac
I get the same results on both nfs and ram version. Here is /var/log/messages

Code: Select all

Sep  4 20:09:13 (none) syslog.info syslogd started: BusyBox v1.20.2
Sep  4 20:09:16 (none) daemon.info init: Entering runlevel: 5
Sep  4 20:09:17 (none) local0.info minimyth: starting splash screen
Sep  4 20:09:18 (none) local0.info minimyth: configuring shared libraries ...
Sep  4 20:09:18 (none) local0.info minimyth: starting loopback network interface ...
Sep  4 20:09:18 (none) daemon.err rpcbind: cannot bind 127.0.0.1 on udp: Address already in use
Sep  4 20:09:18 (none) local0.info minimyth: configuring network interface (one shot) ...
Sep  4 20:09:18 (none) local0.info minimyth: running DHCP client command '/sbin/udhcpc -S -o -O subnet -O router -O dns -O logsrv -O hostname -O domain -O broadcast -O ntpsrv -O tcode -p /var/run/udhcpc.pid -s /etc/udhcpc.script -i eth0 -q > /var/log/udhcpc 2>&1'.
Sep  4 20:09:18 (none) daemon.info udhcpc[394]: udhcpc (v1.20.2) started
Sep  4 20:09:18 (none) daemon.info udhcpc[394]: Sending discover...
Sep  4 20:09:18 (none) daemon.info udhcpc[394]: Sending select for 192.168.2.12...
Sep  4 20:09:18 (none) daemon.info udhcpc[394]: Lease of 192.168.2.12 obtained, lease time 21600
Sep  4 15:09:19 (none) local0.info minimyth: fetching configuration file  ...
Sep  4 15:09:19 (none) local0.info minimyth: waiting for directory /minimyth to mount (30 second(s) left) ...
Sep  4 15:09:20 (none) local0.info minimyth: waiting for directory /minimyth to mount (29 second(s) left) ...
Sep  4 15:09:21 (none) local0.info minimyth: waiting for directory /minimyth to mount (28 second(s) left) ...
Sep  4 15:09:22 (none) local0.info minimyth: waiting for directory /minimyth to mount (27 second(s) left) ...
Sep  4 15:09:23 (none) local0.info minimyth: waiting for directory /minimyth to mount (26 second(s) left) ...
Sep  4 15:09:24 (none) local0.info minimyth: waiting for directory /minimyth to mount (25 second(s) left) ...
Sep  4 15:09:25 (none) local0.info minimyth: waiting for directory /minimyth to mount (24 second(s) left) ...
Sep  4 15:09:26 (none) local0.info minimyth: waiting for directory /minimyth to mount (23 second(s) left) ...
Sep  4 15:09:27 (none) local0.info minimyth: waiting for directory /minimyth to mount (22 second(s) left) ...
Sep  4 15:09:28 (none) local0.info minimyth: waiting for directory /minimyth to mount (21 second(s) left) ...
Sep  4 15:09:29 (none) local0.info minimyth: waiting for directory /minimyth to mount (20 second(s) left) ...
Sep  4 15:09:30 (none) local0.info minimyth: waiting for directory /minimyth to mount (19 second(s) left) ...
Sep  4 15:09:31 (none) local0.info minimyth: waiting for directory /minimyth to mount (18 second(s) left) ...
Sep  4 15:09:32 (none) local0.info minimyth: waiting for directory /minimyth to mount (17 second(s) left) ...
Sep  4 15:09:33 (none) local0.info minimyth: waiting for directory /minimyth to mount (16 second(s) left) ...
Sep  4 15:09:34 (none) local0.info minimyth: waiting for directory /minimyth to mount (15 second(s) left) ...
Sep  4 15:09:35 (none) local0.info minimyth: waiting for directory /minimyth to mount (14 second(s) left) ...
Sep  4 15:09:36 (none) local0.info minimyth: waiting for directory /minimyth to mount (13 second(s) left) ...
Sep  4 15:09:37 (none) local0.info minimyth: waiting for directory /minimyth to mount (12 second(s) left) ...
Sep  4 15:09:38 (none) local0.info minimyth: waiting for directory /minimyth to mount (11 second(s) left) ...
Sep  4 15:09:39 (none) local0.info minimyth: waiting for directory /minimyth to mount (10 second(s) left) ...
Sep  4 15:09:40 (none) local0.info minimyth: waiting for directory /minimyth to mount (9 second(s) left) ...
Sep  4 15:09:41 (none) local0.info minimyth: waiting for directory /minimyth to mount (8 second(s) left) ...
Sep  4 15:09:42 (none) local0.info minimyth: waiting for directory /minimyth to mount (7 second(s) left) ...
Sep  4 15:09:43 (none) local0.info minimyth: waiting for directory /minimyth to mount (6 second(s) left) ...
Sep  4 15:09:44 (none) local0.info minimyth: waiting for directory /minimyth to mount (5 second(s) left) ...
Sep  4 15:09:45 (none) local0.info minimyth: waiting for directory /minimyth to mount (4 second(s) left) ...
Sep  4 15:09:46 (none) local0.info minimyth: waiting for directory /minimyth to mount (3 second(s) left) ...
Sep  4 15:09:47 (none) local0.info minimyth: waiting for directory /minimyth to mount (2 second(s) left) ...
Sep  4 15:09:48 (none) local0.info minimyth: waiting for directory /minimyth to mount (1 second(s) left) ...
Sep  4 15:09:49 (none) local0.err minimyth: directory /minimyth failed to mount.
Sep  4 15:09:49 (none) local0.info minimyth: init failed. check '/var/log/messages' for further details.
Sep  4 20:09:49 (none) daemon.info init: no more processes left in this runlevel
Sep  4 15:10:38 (none) auth.info login[672]: root login on 'tty1'

Re: Minimyth Ram or NFS version

Posted: Wed Sep 05, 2012 2:19 am
by rdoac
This is the contents of my /tftpboot/pxeclient directory
/tftpboot/pxeclient $ ls -la
total 6996
drwxr-xr-x 7 root root 4096 Sep 3 09:00 .
drwxr-xr-x 4 root root 4096 Sep 1 20:37 ..
-rw-r--r-- 1 root root 87 Sep 3 12:33 boot.txt
drwxr-xr-x 3 root root 4096 Sep 1 17:42 conf
-rw-r--r-- 1 root root 4087273 Sep 4 18:25 initramfs-genkernel-x86-3.3.8-gentoo
-rw-r--r-- 1 root root 3005584 Sep 1 15:22 kernel-genkernel-x86-3.3.8-gentoo
drwxr-xr-x 4 root root 4096 Sep 1 08:59 nfs-minimyth-0.25.2-81
-rw-r--r-- 1 root root 26460 Jul 22 10:59 pxelinux.0
drwxr-xr-x 2 root root 4096 Sep 1 17:43 pxelinux.cfg
drwxr-xr-x 5 root root 4096 Jul 22 15:50 ram-minimyth-0.25.2-81
drwxr-xr-x 3 root root 4096 Sep 3 08:25 ubuntu


This is pxelinux.cfg/default
DISPLAY boot.txt

DEFAULT ltsp

LABEL ltsp
kernel kernel-genkernel-x86-3.3.8-gentoo
append initrd=initramfs-genkernel-x86-3.3.8-gentoo root=/dev/nfs nfsroot=192.168.2.10:/opt/ltsp/i686 real_init=/sbin/init-ltsp

LABEL minimyth-ram
KERNEL ram-minimyth-0.25.2-81/kernel
APPEND ro root=/dev/ram0 ramdisk_size=192000 initrd=ram-minimyth-0.25.2-81/rootfs

LABEL minimyth-nfs
KERNEL nfs-minimyth-0.25.2-81/kernel
APPEND ro root=/dev/nfs ip=dhcp nfsroot=192.168.2.10:/opt/minimyth/minimyth-0.25.2-81 MM_DEBUG=yes

LABEL ubuntu
kernel ubuntu/i386/linux
append vga=normal initrd=ubuntu/i386/initrd.gz ramdisk_size=16417 root=/
dev/ram rw --

PROMPT 1
TIMEOUT 0

I have two other things on a boot menu..

Tftp is running like this:

/usr/sbin/in.tftpd -l -R 4096:32767 -s /tftpboot/ -vvvv


Nothing in the logs to say it's asking for a conf file.

Re: Minimyth Ram or NFS version

Posted: Wed Sep 05, 2012 2:21 am
by rdoac
Within minimyth-ram is:

/tftpboot/pxeclient/ram-minimyth-0.25.2-81 $ ls -la
total 113688
drwxr-xr-x 5 root root 4096 Jul 22 15:50 .
drwxr-xr-x 7 root root 4096 Sep 3 09:00 ..
drwxr-xr-x 8 root root 4096 Jul 22 15:39 html
-rw-r--r-- 1 root root 2662880 Jul 22 15:39 kernel
-rw-r--r-- 1 root root 3552 Jul 22 15:50 minimyth.md5
-rw-r--r-- 1 root root 113598464 Jul 22 15:50 rootfs
drwxr-xr-x 2 root root 4096 Jul 22 15:39 scripts
drwxr-xr-x 2 root root 4096 Jul 22 15:49 themes
-rw-r--r-- 1 root root 10 Jul 22 15:39 version

Re: Minimyth Ram or NFS version

Posted: Wed Sep 05, 2012 3:31 am
by m_theredhead
What is in your minimyth.conf file?

Do you have a mount point n the file listed at /minimyth?

Re: Minimyth Ram or NFS version

Posted: Wed Sep 05, 2012 5:11 am
by JoeHenley
Rob,

Well, there's certainly alot going on in there!

I have more experience with the nfs-minimyth side of things. When I look at your directory structure and contents, it doesn't look like what is defined in the minimyth documents (at least how I read them). So I'd strongly suggest going back and getting your minimyth directories cleaned up.

I'll pull together a listing of my tftpboot directory and attach it below. That might help you figure out how to fix yours.

Joe Henley
  • .:
    total 48
    drwxr-xr-x 7 root root 4096 Sep 4 22:56 .
    drwxr-xr-x 26 root root 4096 Sep 4 21:02 ..
    drwxr-xr-x 6 root root 4096 Sep 12 2011 conf
    drwxrwxrwx 2 root root 4096 Sep 12 2011 conf-rw
    drwxr-xr-x 7 root root 4096 Sep 9 2010 minimyth-0.23.1-73
    -rw-r--r-- 1 root root 13148 Jan 8 2007 pxelinux.0
    drwxr-xr-x 2 root root 4096 Jun 4 2011 pxelinux.cfg
    drwxr-xr-x 4 root root 4096 Sep 16 2010 temp

    ./conf:
    total 24
    drwxr-xr-x 6 root root 4096 Sep 12 2011 .
    drwxr-xr-x 7 root root 4096 Sep 4 22:56 ..
    drwxr-xr-x 5 root root 4096 Sep 16 2011 Giada
    drwxr-xr-x 3 root root 4096 Apr 8 2011 Sammy
    drwxr-xr-x 3 root root 4096 Mar 25 2011 Theodore

    ./conf/Giada:
    total 96
    drwxr-xr-x 5 root root 4096 Sep 16 2011 .
    drwxr-xr-x 6 root root 4096 Sep 12 2011 ..
    -rw-r--r-- 1 root root 11919 Jun 7 2011 asound.state
    -rw-r--r-- 1 root root 3210 Jan 3 2012 lircd.conf
    -rw-r--r-- 1 root root 6912 Jan 8 2012 lircrc
    -rw-r--r-- 1 root root 13765 Jul 28 11:36 minimyth.conf
    -rw-r--r-- 1 root root 5852 Sep 22 2011 minimyth.pm
    -rw-r--r-- 1 root root 1305 Jun 8 2011 sensors3.conf
    -rwxr-xr-x 1 root root 786 Feb 14 2011 serial.pm
    -rwxr-xr-x 1 root root 3459 Jun 8 2011 status.cgi

    ./conf-rw:
    total 38520
    drwxrwxrwx 2 root root 4096 Sep 12 2011 .
    drwxr-xr-x 7 root root 4096 Sep 4 22:56 ..
    -rwxrwxr-x 1 501 501 11787664 May 26 2010 Giada+libflashplayer.32.so
    -rw-r--r-- 1 500 500 4018176 Sep 6 2011 Giada+themecache.sfs
    -rwxrwxr-x 1 501 501 11787664 May 26 2010 Sammy+libflashplayer.32.so
    -rwxrwxr-x 1 501 501 11787664 May 26 2010 Theodore+libflashplayer.32.so

    ./minimyth-0.23.1-73:
    total 2252
    drwxr-xr-x 7 root root 4096 Sep 9 2010 .
    drwxr-xr-x 7 root root 4096 Sep 4 22:56 ..
    drwxr-xr-x 2 root root 4096 Sep 7 2010 bin
    lrwxrwxrwx 1 root root 13 Sep 9 2010 dev -> rootfs-ro/dev
    -rw-r--r-- 1 root root 2271056 Sep 7 2010 kernel
    lrwxrwxrwx 1 root root 13 Sep 9 2010 lib -> rootfs-ro/lib
    drwxr-xr-x 2 root root 4096 Sep 7 2010 rootfs
    drwxr-xr-x 12 root root 4096 Sep 7 2010 rootfs-ro
    drwxr-xr-x 2 root root 4096 Apr 30 2011 rw
    drwxr-xr-x 2 root root 4096 Sep 7 2010 sbin

    ./minimyth-0.23.1-73/bin:
    total 8
    drwxr-xr-x 2 root root 4096 Sep 7 2010 .
    drwxr-xr-x 7 root root 4096 Sep 9 2010 ..
    lrwxrwxrwx 1 root root 22 Sep 9 2010 mkdir -> ../rootfs-ro/bin/mkdir
    lrwxrwxrwx 1 root root 22 Sep 9 2010 mount -> ../rootfs-ro/bin/mount
    lrwxrwxrwx 1 root root 19 Sep 9 2010 sh -> ../rootfs-ro/bin/sh

    ./minimyth-0.23.1-73/rootfs:
    total 8
    drwxr-xr-x 2 root root 4096 Sep 7 2010 .
    drwxr-xr-x 7 root root 4096 Sep 9 2010 ..

    ./minimyth-0.23.1-73/rootfs-ro: # ----------------------- all the minimyth application files
    total 48 # ---------------------------------------------------------------are in these directories
    drwxr-xr-x 12 root root 4096 Sep 7 2010 .
    drwxr-xr-x 7 root root 4096 Sep 9 2010 ..
    drwxr-xr-x 2 root root 4096 Feb 14 2011 bin
    drwxr-xr-x 2 root root 4096 Sep 7 2010 dev
    drwxr-xr-x 20 root root 4096 Jun 8 2011 etc
    drwxr-xr-x 3 root root 4096 Sep 7 2010 home
    drwxr-xr-x 6 root root 4096 Apr 27 2011 lib
    drwxr-xr-x 2 root root 4096 Sep 7 2010 lib32
    drwxr-xr-x 2 root root 4096 Apr 27 2011 root
    drwxr-xr-x 2 root root 4096 Sep 9 2010 sbin
    drwxr-xr-x 3 root root 4096 Sep 7 2010 srv
    drwxr-xr-x 16 root root 4096 Jul 10 2011 usr

    ./minimyth-0.23.1-73/rw:
    total 8
    drwxr-xr-x 2 root root 4096 Apr 30 2011 .
    drwxr-xr-x 7 root root 4096 Sep 9 2010 ..

    ./minimyth-0.23.1-73/sbin:
    total 12
    drwxr-xr-x 2 root root 4096 Sep 7 2010 .
    drwxr-xr-x 7 root root 4096 Sep 9 2010 ..
    -rwxr-xr-x 1 root root 671 May 2 2010 init
    lrwxrwxrwx 1 root root 26 Sep 9 2010 modprobe -> ../rootfs-ro/sbin/modprobe
    lrwxrwxrwx 1 root root 28 Sep 9 2010 pivot_root -> ../rootfs-ro/sbin/pivot_root

    ./pxelinux.cfg:
    total 20
    drwxr-xr-x 2 root root 4096 Jun 4 2011 .
    drwxr-xr-x 7 root root 4096 Sep 4 22:56 ..
    -rw-r--r-- 1 root root 281 Feb 26 2011 01-00-30-1b-10-39-89
    -rw-r--r-- 1 root root 227 Jan 21 2011 01-00-40-63-d9-19-5e
    -rw-r--r-- 1 root root 263 Aug 28 15:49 01-00-e0-40-68-a6-eb

    ./temp:
    total 24
    drwxr-xr-x 4 root root 4096 Sep 16 2010 .
    drwxr-xr-x 7 root root 4096 Sep 4 22:56 ..
    drwxr-xr-x 2 root root 4096 Sep 9 2010 helper
    drwxr-xr-x 7 root root 4096 Sep 9 2010 html
    -rw-r--r-- 1 root root 2553 May 2 2010 orig-04-minimyth-disk.rules-orig
    -rw-r--r-- 1 root root 10 Sep 7 2010 version

Re: Minimyth Ram or NFS version

Posted: Wed Sep 05, 2012 1:00 pm
by rdoac
I have created a sub directory inside the conf directory with the name of the frontend. Inside of which I have a generic minimyth.conf with practically everything commented.

However, I can't work out how minimyth is supposed to get that config file. TFTP is not showing that it's serving it.

(This is the NFS version).

Sep 5 11:54:39 oac in.tftpd[17090]: sending NAK (1, File not found) to 192.168.2.12
Sep 5 11:54:39 oac in.tftpd[17091]: RRQ from 192.168.2.12 filename /pxeclient/pxelinux.cfg/C0A8020C
Sep 5 11:54:39 oac in.tftpd[17091]: sending NAK (1, File not found) to 192.168.2.12
Sep 5 11:54:39 oac in.tftpd[17092]: RRQ from 192.168.2.12 filename /pxeclient/pxelinux.cfg/C0A8020
Sep 5 11:54:39 oac in.tftpd[17092]: sending NAK (1, File not found) to 192.168.2.12
Sep 5 11:54:39 oac in.tftpd[17093]: RRQ from 192.168.2.12 filename /pxeclient/pxelinux.cfg/C0A802
Sep 5 11:54:39 oac in.tftpd[17093]: sending NAK (1, File not found) to 192.168.2.12
Sep 5 11:54:39 oac in.tftpd[17094]: RRQ from 192.168.2.12 filename /pxeclient/pxelinux.cfg/C0A80
Sep 5 11:54:39 oac in.tftpd[17094]: sending NAK (1, File not found) to 192.168.2.12
Sep 5 11:54:49 oac in.tftpd[17101]: RRQ from 192.168.2.12 filename /pxeclient/nfs-minimyth-0.25.2-81/kernel
Sep 5 06:54:50 oac dhcpd: DHCPDISCOVER from 00:13:d4:4a:cb:00 via eth0
Sep 5 06:54:50 oac dhcpd: DHCPOFFER on 192.168.2.12 to 00:13:d4:4a:cb:00 via eth0
Sep 5 06:54:50 oac dhcpd: DHCPREQUEST for 192.168.2.12 (192.168.2.10) from 00:13:d4:4a:cb:00 via eth0
Sep 5 06:54:50 oac dhcpd: DHCPACK on 192.168.2.12 to 00:13:d4:4a:cb:00 via eth0
Sep 5 06:54:51 oac rpc.mountd[16150]: authenticated mount request from 192.168.2.12:760 for /opt/minimyth/minimyth-0.25.2-81 (/opt/minimyth/minimyth-0.25.2-81)
Sep 5 06:55:25 oac dhcpd: DHCPDISCOVER from 00:13:d4:4a:cb:00 via eth0
Sep 5 06:55:25 oac dhcpd: DHCPOFFER on 192.168.2.12 to 00:13:d4:4a:cb:00 via eth0
Sep 5 06:55:25 oac dhcpd: DHCPREQUEST for 192.168.2.12 (192.168.2.10) from 00:13:d4:4a:cb:00 via eth0
Sep 5 06:55:25 oac dhcpd: DHCPACK on 192.168.2.12 to 00:13:d4:4a:cb:00 via eth0

Re: Minimyth Ram or NFS version

Posted: Wed Sep 05, 2012 5:14 pm
by JoeHenley
Rob,

It still looks to me like your initial directory, dhcp, and tftp set-up are problems. There are tons of lines of code in the MM scripts which assume a specific directory set up. I doubt you're going to get very far until you accomplish that.

I went back and looked at the info in the Documents section of the MM site. The reference there for help in setting up the dhcp and tftp items is no longer correct. I poked around and found a correct url:
http://www.viaarena.com/nothing-but-net ... 1&MCatID=3
...if that one wanders over time, you can just google for "nothing but net" along with "larry matter". Those two together will find the article.

References within the "nothing but net" article may also wander, but you can find the stuff via google.

With that article, Pablo's info in the Documents section on the MM site, and my example of a directory set up which works, you should be able to get started with some success. The next most likely problem you'll encounter is getting the pxelinux.cfg file just right. A couple of hints:
- Be sure to put "01-" at the start of the file name.
- For one of my FE's the file looks like:
-------------------- snip --------------------------------------
# ============== For Giada
PROMPT 1
DEFAULT minimyth-nfs
DISPLAY messages
TIMEOUT 5
LABEL minimyth-nfs
KERNEL minimyth-0.23.1-73/kernel
APPEND ro root=/dev/nfs nfsroot=192.168.1.200:/tftpboot/minimyth-0.23.1-73 ip=dhcp pci=nomsi hpet=disable i8042.noaux
------------------ snip ------------------
The last three items (starting with pci=) on the "append" line are specific to my machine.

Good luck. Keep us posted of your progress.

Joe Henley

Re: Minimyth Ram or NFS version

Posted: Wed Sep 05, 2012 5:29 pm
by rdoac
Be sure to put "01-" at the start of the file name.
- For one of my FE's the file looks like:
-------------------- snip --------------------------------------
# ============== For Giada
PROMPT 1
DEFAULT minimyth-nfs
DISPLAY messages
TIMEOUT 5
LABEL minimyth-nfs
KERNEL minimyth-0.23.1-73/kernel
APPEND ro root=/dev/nfs nfsroot=192.168.1.200:/tftpboot/minimyth-0.23.1-73 ip=dhcp pci=nomsi hpet=disable i8042.noaux
Looking at your setup, you appear to be using 0.23 not 0.25. I will download the kernel and initrd for that later tonight and see if it gets further. Maybe there is something strange about 0.25? It's not a long term solution as my backend is 0.25. I also have LTSP running correctly, so may just stick mythfrontend in that and ticker with it, but it would be nice to get this working.

What to you mean put 01- before the filename? Which filename?

I use tftpboot quite a lot for a bunch of other applications so am quite confident it's probably right, except for minimyth. I don't think it's getting as far as finding minimyth.conf, but as far as I can tell is not asking the tftp server for it (it should say file not found if it's in the wrong place). I may need a command line option for it, or maybe 0.25 assumes local flash storage.

Re: Minimyth Ram or NFS version

Posted: Wed Sep 05, 2012 5:32 pm
by rdoac
Ah OK, I see what you mean. Your pxeconfig directory has individual files based on mac address. If PXEBoot fails to find those it will go to default, which is the one mine is pulling in.

I can try and symlink it and see if that works, maybe minimyth checks which config file it reads, but I don't see that passed to the kernel on the command line, so it seems unlikely.

Re: Minimyth Ram or NFS version

Posted: Thu Sep 06, 2012 12:37 am
by JoeHenley
Rob,

Just a quick reply, I'll be back later with more help.

Don't bother going backwards to 0.23.1. I use that and 0.25.2, they are the same in terms of set-up and structure.

Joe Henley

Re: Minimyth Ram or NFS version

Posted: Thu Sep 06, 2012 1:24 am
by m_theredhead
Hello,

Setting up files for the frontend may make it boot about 1-2 seconds faster because it doesn't search for variations of the Mac address, but it doesn't impact the final boot configuration.

Minimyth doesn't have any way of looking at your pxelinux config files. If the kernel and ramdisk are loaded, then you are past this point. Only the options to the kernel within the config file get passed up.

So, your issue lies elsewhere. I would verify your top level directories match the instructions for installing minimyth.

Re: Minimyth Ram or NFS version

Posted: Thu Sep 06, 2012 4:49 am
by JoeHenley
Rob,

It's getting late, but I think this might work:
Can I assume the contents of the two sub-directories, ram-minimyth-0.25.2-81 and nfs-minimyth-0.25.2-81, under /tftpboot/pxeclient/ have similar contents?
If so then,
(1) Change the append line for nfs-minimyth from "nfsroot=192.168.2.10:/opt/minimyth/minimyth-0.25.2-81" to "nfsroot=192.168.2.10:/opt/minimyth/nfs-minimyth-0.25.2-81"
^^^^
and find a way to mount "/tftpboot/pxeclient/nfs-minimyth-0.25.2-81" at "/opt/minimyth".
OR
(2) Change the append line for nfs-minimyth from "nfsroot=192.168.2.10:/opt/minimyth/minimyth-0.25.2-81" to "nfsroot=192.168.2.10:/tftpboot/pxeclient/nfs-minimyth-0.25.2-81"

You may need to make your browser very wide to see what I'm putting the carets under for emphasis (the "nfs-" insertion).

If it were me, I'd try option 2 first. Both are pretty severe hacks....

Good luck, let us know how it comes out.

Joe Henley

Re: Minimyth Ram or NFS version

Posted: Thu Sep 06, 2012 5:56 am
by m_theredhead
I agree with Rob. The one thing that sticks out to me is your config files are referencing /opt/minimyth/*, but it looks like you have the files actually under /tftpboot