You can disable eMAC with 1.4.0 (and you should because 1.4.0/eMAC results in bug known as vampire cores).
1.4.1 with patch 1 is unstable ... do not use it ... we call this 188.8.131.52 although the splash screen still says 1.4.1
1.4.1 with patch 2 ... call it 184.108.40.206 although the splash screen still says 1.4.1 ... do not disable eMAC ... the MCPC reboots when you load SCC Linux on the cores.
1.4.1 with patch 3 ... call it 220.127.116.11 although the splash screen still says 1.4.1 ... do not disable eMAC ... the MCPC reboots when you load SCC Linux on the cores.
1.3.0 does not have eMAC enabled and cannot have it so.
We are running 18.104.22.168 (marc041). Does this mean that it is not possible to disable eMAC?
Would it be possible to downgrade us to 1.4.0 and then disable it? How is it disabled at all? Thanks!
If with 22.214.171.124 you disable eMAC, the MCPC will panic. The system becomes unuseable.
Disabling eMAC requires root privilege. As a summary ...
On the MCPC, edit /etc/exports, /etc/network/interfaces, /opt/sccKit/systemSettings.ini, /etc/bind/*.zone, /etc/bind/named.*, /etc/ssh/ssh_conifg, /etc/hosts.
We need to be careful to update the serial numbers in the zone files. We powercycle everything .. basically we want to restart bind and networking.
Dropping to 1.4.0 would require the above as well. In addition 1.4.0 has a different SCC Linux.
Message was edited by: Ted Kubaska .. typo