Boot Sequence

This page provides a quick reference to the boot sequence used by SlimCar. It is similar to that used by a bare Slackware install, with many things removed and a couple of custom bootscripts added to control SlimCar.

1. Computer goes through Power On Self Test (POST) sequence and passes control to SlimCar's boot partition.
2. SlimCar's custom kernel starts the system (detects hardware etc) and then passes control to...
3. ...init, which processes the files in /etc/rc.d/. Many of the Slackware scripts have been modified or removed for SlimCar. During the normal boot process, fsck is suppressed to ensure that you don't end up waiting for SlimCar to check filesystems when it's in your car.
4. SlimCar attempts to ping your MasterLibrary. If there is no reply, skip to step 5. If a response is received, the following occurs:
   • SlimCar "knows" it is on your home network so it creates /etc/slowboot to tell the system to do an extended/full boot next time, then it reboots.
   • Upon reboot, fsck is forced both on the root partition and the music partition.
   • After successful filesystem checks (which may involve a further restart), your music files are synchronised (using Rsync) to your MasterLibrary.
   • /etc/slowboot is removed to allow for normal startup next time.
5. Depending on settings in /etc/slimcar.conf, SlimCar starts SSHd, Syslog, the WebInterface and SqueezeCenter.
6. At this point, the boot process is complete and a "login:" prompt will be displayed - assuming you have a display plugged in, of course! Otherwise, SlimCar is now ready to play music ;)

---

CategoryProject