Announcement

Collapse
No announcement yet.

LinuxICE Startup Process

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • LinuxICE Startup Process

    I'm starting a thread to discuss the LinuxICE startup process compared to other systems. This is not a "mine's better than yours" thread. Instead, I hope to discuss why LinuxICE boots faster and what the trade-offs/sacrifices are that you will have to live with if you do choose to use LinuxICE.

    1) Grub, grub bootstraps the kernel
    2) Kernel init - kernel extracts itself off disk and loads itself into memory

    3) Kernel scans hardware and then loads drivers for all devices that it has drivers for.

    4) init - this is handled by "upstart" which is an event based init daemon capable of concurrently spawning boot processes. The following relevant processes are started by upstart:
    - udev - defines rules for devices when they are detected.
    - dbus - facilitates communication between system services like udev, devicekit and others
    - devicekit/hal - hardware abstraction layer so
    - gpsd - handles multiple gps client applications (similar to xport on windows)
    - pulseaudio - handles sound
    - network-manager - handles the network/wifi stuff

    5) X - the X Window server will start and load multiple "session" scripts.

    6) LinuxICE session script - This is the LinuxICE session. It spawns the following:
    - nscan
    - nghost
    - icepanel
    - obdgpslogger
    - window manager
    - gnome-keyring
    - nm-applet - ui for network-manager

    7) nGhost - When nGhost starts, here's what get's loaded:
    A) initialization of the gfx engine and window creation.
    B) initialization of "screen", skin parsing and loading from xml files
    C) loading the main screen images into memory
    D) Event engine initialization, initializes player, loads the database
    E) Player starts playing music
    F) Plugins are loaded:
    1) ncarinfo - obdII display
    2) ng2dbus - exposes nghost's event system over dbus
    3) nvoicesynth - text to voice plugin
    4) nweather - weather plugin
    G) Main event loop entered.
    H) nghost tells nscan to watch the media (usually rescans)

    You should now be ready to go with media, obd, network (including 3g connections and bluetooth), navigation weather, and some other niceties.
    Former author of LinuxICE, nghost, nobdy.
    Current author of Automotive Message Broker (AMB).
    Works on Tizen IVI. Does not represent anyone or anything but himself.

  • #2
    Originally posted by Tidder
    I'm failing to see the comparison.
    I can't compare, I don't know how windows or the other frontends start up or if they even start up at all. That's why I digress to your infinite knowledge tidder
    Former author of LinuxICE, nghost, nobdy.
    Current author of Automotive Message Broker (AMB).
    Works on Tizen IVI. Does not represent anyone or anything but himself.

    Comment


    • #3


      I retract my previous statement.

      *and points to the url ^^*
      Tidder

      Try RevFE
      The best resurrected frontend I've ever used, period.


      I Wish I could ban people

      Comment

      Working...
      X