<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Startup &amp; System Settings | GoboLinux Documentation</title><link>https://wiki.gobolinux.org/Usage/Startup-and-System-settings/index.html</link><description>Since we felt like we were “starting from scratch” and we really wanted to make a system where everything just made sense for us, we also took the time to rethink the boot scripts. I felt the two historical models (System V and BSD) were overkill for our common desktop-machine setup. GoboLinux uses a simpler system: two scripts, Init and Done, do most of the job. Additional scripts, such as Multi and Single, take care of the runlevels. These files are simply sequences of commands, prepended by the word Exec and a message string. Here’s an excerpt of Init:</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://wiki.gobolinux.org/Usage/Startup-and-System-settings/index.xml" rel="self" type="application/rss+xml"/><item><title>Configuring the Boot Process</title><link>https://wiki.gobolinux.org/Usage/Startup-and-System-settings/Configuring-the-boot-process/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://wiki.gobolinux.org/Usage/Startup-and-System-settings/Configuring-the-boot-process/index.html</guid><description>This page describes the boot process and how to configure your GoboLinux system by editing the configuration files used for startup.
General architecture The BootDriver script (/Programs/BootScript/&lt;version&gt;/bin/BootDriver) manages boot-related tasks. The init program (from the Sysvinit package) running as PID 1 calls BootDriver as specified in /System/Settings/inittab.
BootDriver first loads the boot theme file specified in /System/Settings/BootOptions. Then BootDriver runs the appropriate boot script for the task at hand (startup, shutdown, etc.)</description></item><item><title>Boot Script Tasks</title><link>https://wiki.gobolinux.org/Usage/Startup-and-System-settings/Boot-script-tasks/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://wiki.gobolinux.org/Usage/Startup-and-System-settings/Boot-script-tasks/index.html</guid><description>Your boot scripts can make use of “boot tasks”, which are little service scripts that can be shipped by programs. A program includes its tasks under Resources/Tasks, and they’re linked in /System/Tasks. This is roughly equivalent to the /etc/init.d scripts found in many distributions.
You can launch or stop tasks from the command line, using StartTask and StopTask. For example, the following command will load the SSH daemon:
StartTask OpenSSH Within boot scripts, you don’t need to use these launchers, but you have to add a parameter indicating whether the task is being started or stopped:</description></item><item><title>Boot Themes</title><link>https://wiki.gobolinux.org/Usage/Startup-and-System-settings/Boot-Themes/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://wiki.gobolinux.org/Usage/Startup-and-System-settings/Boot-Themes/index.html</guid><description>GoboLinux is flexible enough to offer you a choice of themes to control how your GoboLinux looks when starting up.
You can select a theme by setting BootTheme=&lt;ThemeName&gt; in /System/Settings/BootOptions. Available themes include:
CheckList - Shows tasks and others that depend on them, then checks them off. Hat - A Red-Hat look-alike: lots of colored [ OK ]s and [FAILED]s are echoed as things are initialized. Progress, Progress-II, or Progress-III - Fancy themes that stress your terminal with tons of escape codes. Quotes - Prints short random quotes to indicate success or failure of every initialized item. Slack - This theme is inspired by the feel of old-school Slackware boots: no distracting messages, no colors, no special effects. Check /Programs/BootScripts/Current/Themes/ to see all the available themes.</description></item></channel></rss>