Table of Contents
Advertisement
Notes:
If
sconfig
replies with its usage-information you still have an OS installed, which doesn't support en-
abling/disabling individual
If querying an
autojob
explicit settings for the
shown above.
The possible values of
the functions for different storage media individually. When this extension will be implemented and how
exactly the syntax for this will look like is still to be defined.
4.1.9 Autostart
The autostart service on Garz & Fricke Linux platforms uses nearly the same mechanism as
I
in chapter
[
4.1.8 Autocopy]
The
simply searches for an
autostart
executable files are executed in alphabetic order. Filenames starting with digits are executed before those starting
with letters in numeric order. Files in subfolders of the
The execution of the autostart files is shown in the Linux console during start up:
mount.sh/automount Auto-mount of [/media/sda1] successful
mount.sh/automount Found an autostart folder. Executing files...
mount.sh/automount Executing /media/sda1/autostart/test.sh...
Finished executing autostart files
I
As already stated in
[
4.1.8 Autocopy]
The user may desire to autostart an application from a storage media with command line args. In this case a
start script can be placed in the autostart folder that starts the aplication itself in a subfolder of autostart with the
desired command line args. It is important to place the application itself in a subfolder. Otherwise the
mechanism will try to start this application without the command line args in parallel to the start script.
Example: The user created a Qt application (e.g. myapp) to run on X Server. This makes it necessary to
set the environment variable
/autostart/custom
on the storage media. Consequently, the start script (e.g. myapp.sh) must have the following
contents:
#!/bin/sh
export DISPLAY=:0.0
./custom/myapp
The start script must be placed in the folder
I
is shown in figure
[
Figure
Figure 5: Layout of the storage medium after preperation with the custom files
After plugging the storage media into the target system. The start script and the apllication should start properly.
Enabling/Disabling: Starting with OS Release 33 and newer the
via XML-configuration and the
For backward compatibility the
explicit setting for this function. To be able to configure each of the
to install an XML-configuration file specifying explicit state-settings for the
configuration files are available from Garz & Fricke:
autojob
functions. Please update your OS in this case.
function returns no reply, at all, your XML-configuration probably doesn't contain
autojob
functions, yet. Please install one of the provided XML-configuration files as
all
and
off
have been chosen on purpose to allow future extension to enable/disable
except for the autostart specific part in /etc/udev/scripts/mount.sh.
folder in the root directory of the storage media. If found, the
autostart
autocopy
is executed before autostart.
DISPLAY=:0.0
before calling myapp. The application is placed e.g. in the folder
/autostart
5].
sconfig
tool.
autostart
function is still enabled by default if the XML-configuration contains no
GUF-Yocto-34.0-r5756-0
autostart
are ignored.
on the storage media. The layout of the storage medium
autostart
function may be enabled/disabled
autojob
functions individually, you may have
autojob
VINCELL
User Manual
¡
¡
autocopy
described
autostart
functions. At least two such
19
Advertisement
Table of Contents
