Thanks Curtis, 

I submitted the guide in the Useful Articles section in


On Tue, Oct 9, 2012 at 9:23 AM, Curtis Olson <> wrote:
On Tue, Oct 9, 2012 at 11:16 AM, Ash Charles wrote:
The /etc/init.d is empty because this image uses systemd
( as its
initialization system rather than sysvinit.  Among other things,
systemd offers the possibility of really quick boot times.  That said,
it can still read classic sysvinit scripts.

Just to back that up, I've seen an 8 second boot here on an earthstorm (based on the kernel boot timing messages.)  My open embedded image (self built) that I was running before took close to a minute to boot.

systemd is weird and complicated if you are used to the old init system which was complicated compared to what came before it, but onwards and upwards I guess. :-)

If anyone is interested in setting up autologin on the new 3.5 kernel + systemd based system I whipped together a quick howto based on my own hacking:


Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
gumstix-users mailing list