Most recent edit on 2009-05-20 02:26:36 by HarryBo
Additions:
~- After successful filesystem checks (which may involve a further restart), your music files are synchronised (using Rsync) to your MasterLibrary.
- 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 ;)
Deletions:
~- After successfull filesystem checks (which may involve a further restart), your music files are synchronised (using Rsync) to your MasterLibrary.
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!
Edited on 2009-05-20 02:26:01 by HarryBo
Additions:
~2) SlimCar's custom kernel starts the system (detects hardware etc) and then passes control to...
...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.
Deletions:
~2) The bootable partition contains the entire OS, a size of 200-250MB. This includes the kernel, configuration files etc - basically the entire SlimCar system but not the music files.
The kernel executes init, which in turn processes the files in /etc/rc.d/. Many of the Slackware scripts have been modified or removed for SlimCar. It's beyond the scope of this article to fully discuss the Linux boot process but essentially it involves hardware detection, mounting of filesystems (including kernel filesystems like /dev and /sys) and activation of network interfaces. During the normal boot process, fsck is suppressed to ensure that you don't end up waiting for SlimCar to boot when it's in your car.
Edited on 2009-05-20 02:24:07 by HarryBo
No differences.
Edited on 2009-05-20 02:23:55 by HarryBo
No differences.
Edited on 2009-05-20 02:23:38 by HarryBo
Additions:
~- 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 successfull 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.
Deletions:
- 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 successfull filesystem checks (which may involve a further restart), your music files are synchronised (using Rsync) to your MasterLibrary.
Edited on 2009-05-20 02:23:03 by HarryBo
Additions:
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.
The kernel executes init, which in turn processes the files in /etc/rc.d/. Many of the Slackware scripts have been modified or removed for SlimCar. It's beyond the scope of this article to fully discuss the Linux boot process but essentially it involves hardware detection, mounting of filesystems (including kernel filesystems like /dev and /sys) and activation of network interfaces. During the normal boot process, fsck is suppressed to ensure that you don't end up waiting for SlimCar to boot when it's in your car.
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 successfull filesystem checks (which may involve a further restart), your music files are synchronised (using Rsync) to your MasterLibrary.
Depending on settings in /etc/slimcar.conf, SlimCar starts SSHd, Syslog, the WebInterface and SqueezeCenter.
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!
Deletions:
This page provides a quick reference to the boot sequence used by SlimCar. It is very similar to that used by a bare Slackware install, with some things removed and a couple of custom bootscripts to make SqueezeCenter work.
The kernel executes init, which in turn processes the files in /etc/rc.d/. Many of the Slackware scripts have been modified or removed for SlimCar. It's beyond the scope of this article to fully discuss the Linux boot process but essentially it involves hardware detection, mounting of filesystems (including kernel filesystems like /dev and /sys) and activation of network interfaces.
SlimCar calls "/etc/rc.d/music boot". This script s used to synchronise SlimCar's music library with the one your MasterLibrary machine (if you're connected to your home network) and then starts SqueezeCenter. See MusicBootScript for full details.
At this point, the boot process is complete and a "login:" prompt will be displayed - assuming you have a display plugged in, of course.
Edited on 2008-07-01 02:31:32 by HarryBo
Additions:
This page provides a quick reference to the boot sequence used by SlimCar. It is very similar to that used by a bare Slackware install, with some things removed and a couple of custom bootscripts to make SqueezeCenter work.
The bootable partition contains the entire OS, a size of 200-250MB. This includes the kernel, configuration files etc - basically the entire SlimCar system but not the music files.
The kernel executes init, which in turn processes the files in /etc/rc.d/. Many of the Slackware scripts have been modified or removed for SlimCar. It's beyond the scope of this article to fully discuss the Linux boot process but essentially it involves hardware detection, mounting of filesystems (including kernel filesystems like /dev and /sys) and activation of network interfaces.
SlimCar calls "/etc/rc.d/music boot". This script s used to synchronise SlimCar's music library with the one your MasterLibrary machine (if you're connected to your home network) and then starts SqueezeCenter. See MusicBootScript for full details.
Deletions:
This page provides a quick reference to the boot sequence used by SlimCar. It is very similar to that used by a bare LinuxFromScratch install, with some things (ie: logging) removed and a couple of custom bootscripts to make SlimServer work.
The bootable partition contains the entire OS, a size of 100-150MB. This includes the kernel, configuration files etc - basically the entire SlimCar system but not the music files.
The kernel executes init, which in turn processes the files in /etc/rc.d/rcsysinit.d. Most of these scripts are left as standard for an LFS system, but the kernel and system logs have been removed. It's beyond the scope of this article to fully discuss the Linux boot process but essentially it involves hardware detection, mounting of filesystems (including kernel filesystems like /dev and /sys) and activation of network interfaces. SlimCar runs at runlevel 3.
SlimCar uses 2 custom bootscripts (found in /etc/rc.d/init.d) - music (see ConfigFiles) and slim.
The bootable partition contains the entire OS, a size of 100-150MB. This includes the kernel, configuration files etc - basically the entire SlimCar system but not the music files.
Deletions:
~1) Computer goes through Power On Self Test (POST) sequence and passes control to IDE primary master - the CompactFlash card in a CF2IDE adapter.
The CompactFlash card contains SysLinux, a lightweight bootloader designed to work on FAT16 filesystems. This reads the kernel and the compressed filesystem image into RAM, and begins kernel execution. From this point onwards, the entire system "lives" in the system's RAM (known as a ramdisk) and the CompactFlash card is only used for certain configuration files and storage of playlists.
Edited on 2006-09-05 20:58:56 by HarryBo
Additions:
~2) The CompactFlash card contains SysLinux, a lightweight bootloader designed to work on FAT16 filesystems. This reads the kernel and the compressed filesystem image into RAM, and begins kernel execution. From this point onwards, the entire system "lives" in the system's RAM (known as a ramdisk) and the CompactFlash card is only used for certain configuration files and storage of playlists.
Deletions:
~2) The CompactFlash card contains SysLinux, a lightweight bootloader designed to work on FAT16 filesystems. This reads the kernel and the compressed filesystem image into RAM, and begins kernel execution.
Edited on 2006-09-05 20:56:57 by HarryBo
Additions:
~~music is used to synchronise SlimCar's music library with the one your MasterLibrary machine. See MusicBootScript for full details.
slim then starts SlimServer with all appropriate options and paths.
Edited on 2006-09-05 20:56:48 by HarryBo
Additions:
~music is used to synchronise SlimCar's music library with the one your MasterLibrary machine. See MusicBootScript for full details.
slim then starts SlimServer with all appropriate options and paths.
Deletions:
~~The music bootscript is used to synchronise SlimCar's music library with the one your MasterLibrary machine. See MusicBootScript for full details.
The
slim bootscript starts
SlimServer with all appropriate options and paths.
Edited on 2006-09-05 20:56:17 by HarryBo
Additions:
~3) The kernel executes init, which in turn processes the files in /etc/rc.d/rcsysinit.d. Most of these scripts are left as standard for an LFS system, but the kernel and system logs have been removed. It's beyond the scope of this article to fully discuss the Linux boot process but essentially it involves hardware detection, mounting of filesystems (including kernel filesystems like /dev and /sys) and activation of network interfaces. SlimCar runs at runlevel 3.
The music bootscript is used to synchronise SlimCar's music library with the one your MasterLibrary machine. See MusicBootScript for full details.
The slim bootscript starts SlimServer with all appropriate options and paths.
Deletions:
~3) The kernel executes init, which in turn processes the files in /etc/rc.d/rcsysinit.d. Most of these scripts are left as standard for an LFS system, but the kernel and system logs have been removed. It's beyond the scope of this article to fully discuss the Linux boot process but essentially it involves hardware detection, mounting of filesystems (including kernel filesystems like /dev and /sys) and activation of network interfaces.
Oldest known version of this page was edited on 2006-09-05 20:55:13 by HarryBo []
Page view:
Boot Sequence
This page provides a quick reference to the boot sequence used by
SlimCar. It is very similar to that used by a bare
LinuxFromScratch install, with some things (ie: logging) removed and a couple of custom bootscripts to make
SlimServer work.
- Computer goes through Power On Self Test (POST) sequence and passes control to IDE primary master - the CompactFlash card in a CF2IDE adapter.
- The CompactFlash card contains SysLinux, a lightweight bootloader designed to work on FAT16 filesystems. This reads the kernel and the compressed filesystem image into RAM, and begins kernel execution.
- The kernel executes init, which in turn processes the files in /etc/rc.d/rcsysinit.d. Most of these scripts are left as standard for an LFS system, but the kernel and system logs have been removed. It's beyond the scope of this article to fully discuss the Linux boot process but essentially it involves hardware detection, mounting of filesystems (including kernel filesystems like /dev and /sys) and activation of network interfaces.
- SlimCar uses 2 custom bootscripts (found in /etc/rc.d/init.d) - music (see ConfigFiles) and slim.
- The music bootscript is used to synchronise SlimCar's music library with the one your MasterLibrary machine. See MusicBootScript for full details.
- The slim bootscript starts SlimServer with all appropriate options and paths.
- At this point, the boot process is complete and a "login:" prompt will be displayed - assuming you have a display plugged in, of course.
CategoryProject
