Mark_Racicot
April 29th, 2015, 12:04 AM
Host system:
Intel i5/3.4MHz, 32GB RAM, Win7 (x64) Ultimate -- running VMWare Player
Created new VM for Ubuntu 15.04, allocated a 30GB drive space for it. Installed. During first post-install boot, I see:
[FAILED] Failed to start /etc/rc.local Compatibility.
I'm new to Linux generally and Ubuntu specifically... When I 'ls' the etc directory, rc.local shows up as a green filename, and I've not a single clue what that color code means. I can see that it is owned by root, so it's something the system created during install. The error message is also the only error message I see when I start this VM.
On this same host, I have an Ubuntu 14.04LTS installation (x64), and the only error message I see in that boot is that the VMWare Tools aren't running or starting. I can live without that for now, but it is different that the previous version of Ubuntu I had installed (version unknown), in which the VMWare tools ran correctly and there were no errors/fails during boot.
In neither case does this error/fail message appear to have any bearing on the operation of the system, but I don't like 'fail' messages during boot.
Any ideas?
Mark
Intel i5/3.4MHz, 32GB RAM, Win7 (x64) Ultimate -- running VMWare Player
Created new VM for Ubuntu 15.04, allocated a 30GB drive space for it. Installed. During first post-install boot, I see:
[FAILED] Failed to start /etc/rc.local Compatibility.
I'm new to Linux generally and Ubuntu specifically... When I 'ls' the etc directory, rc.local shows up as a green filename, and I've not a single clue what that color code means. I can see that it is owned by root, so it's something the system created during install. The error message is also the only error message I see when I start this VM.
On this same host, I have an Ubuntu 14.04LTS installation (x64), and the only error message I see in that boot is that the VMWare Tools aren't running or starting. I can live without that for now, but it is different that the previous version of Ubuntu I had installed (version unknown), in which the VMWare tools ran correctly and there were no errors/fails during boot.
In neither case does this error/fail message appear to have any bearing on the operation of the system, but I don't like 'fail' messages during boot.
Any ideas?
Mark