3 novaboot - Boots a locally compiled operating system on a remote
10 **novaboot** \[option\]... \[--\] script...
12 **./script** \[option\]...
16 This program makes booting of a locally compiled operating system (OS)
17 (e.g. NOVA or Linux) on remote targets as simple as running a program
18 locally. It automates things like copying OS images to a TFTP server,
19 generation of bootloader configuration files, resetting of target
20 hardware or redirection of target's serial line to stdin/out. Novaboot
21 is highly configurable and it makes it easy to boot a single image on
22 different targets or different images on a single target.
24 Novaboot operation is controlled by command line options and by a so
25 called novaboot script, which can be thought as a generalization of
26 bootloader configuration files (see ["NOVABOOT SCRIPT SYNTAX"](#novaboot-script-syntax)).
27 Typical way of using novaboot is to make the novaboot script
28 executable and set its first line to _#!/usr/bin/env novaboot_. Then,
29 booting a particular OS configuration becomes the same as executing a
30 local program - the novaboot script.
32 Novaboot uses configuration files to, among other things, define
33 command line options needed for different targets. Users typically use
34 only the **-t**/**--target** command line option to select the target.
35 Internally, this option expands to the pre-configured options.
36 Configuration files are searched at multiple places, which allows to
37 have per-system, per-user or per-project configurations. Configuration
38 file syntax is described in section ["CONFIGURATION FILE"](#configuration-file).
40 Simple examples of using `novaboot`:
42 1. Run an OS in Qemu. This is can be specified with the **--qemu** option.
43 Thus running `novaboot --qemu myos` (or `./myos --qemu` as described
44 above) will run Qemu and make it boot the configuration specified in
46 2. Create a bootloader configuration file (currently supported
47 bootloaders are GRUB, GRUB2, ISOLINUX, Pulsar and U-Boot) and copy it
48 with all other files needed for booting to a remote boot server. Then
49 use a TCP/IP-controlled relay/serial-to-TCP converter to reset the
50 target and receive its serial output.
52 ./myos --grub2 --server=192.168.1.1:/tftp --iprelay=192.168.1.2
54 3. Run DHCP and TFTP server on developer's machine to boot the target
59 This is useful when no network infrastructure is in place and
60 the target is connected directly to developer's box.
62 4. Create bootable ISO image.
64 novaboot --iso -- script1 script2
66 The created ISO image will have ISOLINUX bootloader installed on it
67 and the boot menu will allow selecting between _script1_ and
68 _script2_ configurations.
72 Novaboot performs its work in several phases. Each phase can be
73 influenced by several command line options, certain phases can be
74 skipped. The list of phases (in the execution order) is as follows.
76 - 1. [Configuration reading](#configuration-reading-phase)
77 - 2. [Command line processing](#command-line-processing-phase)
78 - 3. [Script preprocessing](#script-preprocessing-phase)
79 - 4. [File generation](#file-generation-phase)
80 - 5. [Target connection](#target-connection-check)
81 - 6. [File deployment](#file-deployment-phase)
82 - 7. [Target power-on and reset](#target-power-on-and-reset-phase)
83 - 8. [Interaction with the bootloader](#interaction-with-the-bootloader-on-the-target)
84 - 9. [Target interaction](#target-interaction-phase)
86 Each phase is described in the following sections together with the
87 command line options that control it.
89 ## Configuration reading phase
91 After starting, novaboot reads configuration files. Their content is
92 described in section ["CONFIGURATION FILE"](#configuration-file). By default,
93 configuration is read from multiple locations. First from the system
94 configuration directory (`/etc/novaboot.d/`), second from the user
95 configuration file (`~/.config/novaboot`) and third from `.novaboot`
96 files along the path to the current directory. Alternatively, a single
97 configuration file specified with the **-c** switch or with the
98 `NOVABOOT_CONFIG` environment variable is read. The latter read files
99 override settings from the former ones.
101 The system configuration directory is determined by the content of
102 NOVABOOT\_CONFIG\_DIR environment variable and defaults to
103 `/etc/novaboot.d`. Files in this directory with names consisting
104 solely of English letters, numbers, dashes '-' and underscores '\_'
105 (note that dot '.' is not included) are read in alphabetical order.
107 Then, the user configuration file is read from
108 `$XDG_CONFIG_HOME/novaboot`. If `$XDG_CONFIG_HOME` environemnt
109 variable is not set `~/.config/novaboot` is read instead.
111 Finally, novaboot searches for files named `.novaboot` starting from the
112 directory of the novaboot script (or working directory, see bellow)
113 and continuing upwards up to the root directory. The found
114 configuration files are then read in the opposite order (i.e. from the
115 root directory downwards). This allows to have, for example, a project
116 specific configuration in `~/project/.novaboot`.
118 Note the difference between `~/.config/novaboot` and `~/.novaboot`.
119 The former one is read always, whereas the latter only when novaboot
120 script or working directory is under the `$HOME` directory.
122 In certain cases, the location of the novaboot script cannot be
123 determined in this early phase. This happens either when the script is
124 read from the standard input or when novaboot is invoked explicitly as
125 in the example ["4."](#4) above. In this case the current working
126 directory is used as a starting point for configuration file search
127 instead of the novaboot script directory.
129 - -c, --config=_filename_
131 Use the specified configuration file instead of the default one(s).
133 ## Command line processing phase
137 Dump the current configuration to stdout end exit. Useful as an
138 initial template for a configuration file.
142 Print short (**-h**) or long (**--help**) help.
144 - -t, --target=_target_
146 This option serves as a user configurable shortcut for other novaboot
147 options. The effect of this option is the same as specifying the
148 options stored in the `%targets` configuration variable under key
149 _target_. See also ["CONFIGURATION FILE"](#configuration-file).
151 When this option is not given, novaboot tries to determine the target
152 to use from either **NOVABOOT\_TARGET** environment variable or from
153 **$default\_target** configuration file variable.
155 ## Script preprocessing phase
157 This phases allows to modify the parsed novaboot script before it is
158 used in the later phases.
160 - -a, --append=_parameters_
162 Append a string to the first `load` line in the novaboot script. This
163 can be used to append parameters to the kernel's or root task's
164 command line. This option can appear multiple times.
168 Use `bender` chainloader. Bender scans the PCI bus for PCI serial
169 ports and stores the information about them in the BIOS data area for
172 - --chainloader=_chainloader_
174 Specifies a chainloader that is loaded before the kernel and other
175 files specified in the novaboot script. E.g. 'bin/boot/bender
180 Print the modules to boot and their parameters after this phase
181 finishes. Then exit. This is useful for seeing the effect of other
182 options in this section.
184 - -k, --kernel=`file`
186 Replace the first word on the first `load` line in the novaboot
189 - --scriptmod=_perl expression_
191 When novaboot script is read, _perl expression_ is executed for every
192 line (in $\_ variable). For example, `novaboot
193 \--scriptmod=s/sigma0/omega6/g` replaces every occurrence of _sigma0_
194 in the script with _omega6_.
196 When this option is present, it overrides _$script\_modifier_ variable
197 from the configuration file, which has the same effect. If this option
198 is given multiple times all expressions are evaluated in the command
201 ## File generation phase
203 In this phase, files needed for booting are generated in a so called
204 _build directory_ (see ["--build-dir"](#build-dir)). In most cases configuration
205 for a bootloader is generated automatically by novaboot. It is also
206 possible to generate other files using _heredoc_ or _"<"_ syntax in
207 novaboot scripts. Finally, binaries can be generated in this phases by
208 running `scons` or `make`.
210 - --build-dir=_directory_
212 Overrides the default build directory location.
214 The default build directory location is determined as follows: If the
215 configuration file defines the `$builddir` variable, its value is
216 used. Otherwise, it is the directory that contains the first processed
219 See also ["BUILDDIR"](#builddir) variable.
221 - -g, --grub\[=_filename_\]
223 Generates grub bootloader menu file. If the _filename_ is not
224 specified, `menu.lst` is used. The _filename_ is relative to the
225 build directory (see **--build-dir**).
227 - --grub-preamble=_prefix_
229 Specifies the _preable_ that is at the beginning of the generated
230 GRUB or GRUB2 config files. This is useful for specifying GRUB's
235 Specifies _prefix_ (e.g. `/srv/tftp`) that is put in front of every
236 file name in generated bootloader configuration files (or in U-Boot
239 If the _prefix_ contains string $NAME, it will be replaced with the
240 name of the novaboot script (see also **--name**).
242 If the _prefix_ contains string $BUILDDIR, it will be replaced with
243 the build directory (see also **--build-dir**).
247 Alias for **--prefix**.
249 - --grub2\[=_filename_\]
251 Generate GRUB2 menu entry in _filename_. If _filename_ is not
252 specified `grub.cfg` is used. The content of the menu entry can be
253 customized with **--grub-preamble**, **--grub2-prolog** or
254 **--grub\_prefix** options.
256 In order to use the the generated menu entry on your development
257 machine that uses GRUB2, append the following snippet to
258 `/etc/grub.d/40_custom` file and regenerate your grub configuration,
259 i.e. run update-grub on Debian/Ubuntu.
261 if [ -f /path/to/nul/build/grub.cfg ]; then
262 source /path/to/nul/build/grub.cfg
265 - --grub2-prolog=_prolog_
267 Specifies text that is put at the beginning of the GRUB2 menu entry.
269 - -m, --make\[=make command\]
271 Runs `make` to build files that are not generated by novaboot itself.
275 Use the name _string_ instead of the name of the novaboot script.
276 This name is used for things like a title of grub menu or for the
277 server directory where the boot files are copied to.
281 Do not run external commands to generate files (i.e. "<" syntax and
282 `run` keyword). This switch does not influence generation of files
283 specified with "<<WORD" syntax.
285 - -p, --pulsar\[=mac\]
287 Generates pulsar bootloader configuration file named `config-_mac_`
288 The _mac_ string is typically a MAC address and defaults to
291 - --scons\[=scons command\]
293 Runs `scons` to build files that are not generated by novaboot
298 Strip _rom://_ prefix from command lines and generated config files.
299 The _rom://_ prefix is used by NUL. For NRE, it has to be stripped.
303 Exit novaboot after file generation phase.
305 ## Target connection check
307 If supported by the target, the connection to it is made and it is
308 checked whether the target is not occupied by another novaboot
311 - --amt=_"\[user\[:password\]@\]host\[:port\]_
313 Use Intel AMT technology to control the target machine. WS management
314 is used to powercycle it and Serial-Over-Lan (SOL) for input/output.
315 The hostname or (IP address) is given by the _host_ parameter. If
316 _password_ is not specified, environment variable AMT\_PASSWORD is
317 used. The _port_ specifies a TCP port for SOL. If not specified, the
318 default is 16992. Default _user_ is admin.
320 - --iprelay=_addr\[:port\]_
322 Use TCP/IP relay and serial port to access the target's serial port
323 and powercycle it. The IP address of the relay is given by _addr_
324 parameter. If _port_ is not specified, it default to 23.
326 Note: This option is supposed to work with HWG-ER02a IP relays.
328 - -s, --serial\[=device\]
330 Target's serial line is connected to host's serial line (device). The
331 default value for device is `/dev/ttyUSB0`.
333 The value of this option is exported in NB\_NOVABOOT environment
334 variable to all subprocesses run by `novaboot`.
338 Specifies settings passed to `stty` invoked on the serial line
339 specified with **--serial** option. If this option is not given,
340 `stty` is called with `raw -crtscts -onlcr 115200` settings.
344 Command that mediates connection to the target's serial line. For
345 example `ssh server 'cu -l /dev/ttyS0'`.
347 - --remote-expect=_string_
349 Wait for reception of _string_ after establishing the remote
352 - --remote-expect-silent=_string_
354 The same as **--remote-expect** except that the remote output is not
355 echoed to stdout while waiting for the _string_. Everything after the
356 matched string is printed to stdout, so you may want to include line
357 end characters in the _string_ as well.
359 ## File deployment phase
361 In some setups, it is necessary to copy the files needed for booting
362 to a particular location, e.g. to a TFTP boot server or to the
367 Turns your workstation into a DHCP and TFTP server so that the OS can
368 be booted via PXE BIOS (or similar mechanism) on the test machine
369 directly connected by a plain Ethernet cable to your workstation.
371 The DHCP and TFTP servers requires root privileges and `novaboot`
372 uses `sudo` command to obtain those. You can put the following to
373 _/etc/sudoers_ to allow running the necessary commands without asking
376 Cmnd_Alias NOVABOOT = /bin/ip a add 10.23.23.1/24 dev eth0, /bin/ip l set dev eth0 up, /usr/sbin/dhcpd -d -cf dhcpd.conf -lf dhcpd.leases -pf dhcpd.pid, /usr/sbin/in.tftpd --listen --secure -v -v -v --pidfile tftpd.pid *, /usr/bin/touch dhcpd.leases, /usr/bin/pkill --pidfile=dhcpd.pid, /usr/bin/pkill --pidfile=tftpd.pid
377 your_login ALL=NOPASSWD: NOVABOOT
381 Starts a TFTP server on your workstation. This is similar to
382 **--dhcp-tftp** except that DHCP server is not started.
384 The TFTP server require root privileges and `novaboot` uses `sudo`
385 command to obtain those. You can put the following to _/etc/sudoers_
386 to allow running the necessary commands without asking for password.
388 Cmnd_Alias NOVABOOT = /usr/sbin/in.tftpd --listen --secure -v -v -v --pidfile tftpd.pid *, /usr/bin/pkill --pidfile=tftpd.pid
389 your_login ALL=NOPASSWD: NOVABOOT
393 Port to run the TFTP server on. Implies **--tftp**.
397 Generates the ISO image that boots NOVA system via GRUB. If no filename
398 is given, the image is stored under _NAME_.iso, where _NAME_ is the name
399 of the novaboot script (see also **--name**).
401 - --server\[=\[\[user@\]server:\]path\]
403 Copy all files needed for booting to another location. The files will
404 be copied (by **rsync** tool) to the directory _path_. If the _path_
405 contains string $NAME, it will be replaced with the name of the
406 novaboot script (see also **--name**).
408 - --rsync-flags=_flags_
410 Specifies which _flags_ are appended to `rsync` command line when
411 copying files as a result of _--server_ option.
415 If **--server** is used and its value ends with $NAME, then after
416 copying the files, a new bootloader configuration file (e.g. menu.lst)
417 is created at _path-wo-name_, i.e. the path specified by **--server**
418 with $NAME part removed. The content of the file is created by
419 concatenating all files of the same name from all subdirectories of
420 _path-wo-name_ found on the "server".
424 Use Intel AMT technology for IDE redirection. This allows the target
425 machine to boot from novaboot created ISO image. Implies **--iso**.
427 The experimental `amtider` utility needed by this option can be
428 obtained from https://github.com/wentasah/amtterm.
430 ## Target power-on and reset phase
432 At this point, the target is reset (or switched on/off). There is
433 several ways how this can be accomplished. Resetting a physical target
434 can currently be accomplished by the following options: **--amt**,
435 **--iprelay**, **--reset-cmd**.
439 Switch on/off the target machine and exit. The script (if any) is
440 completely ignored. Currently it works only with **--iprelay** or
443 - -Q, --qemu\[=_qemu-binary_\]
445 Boot the configuration in qemu. Optionally, the name of qemu binary
446 can be specified as a parameter.
448 - --qemu-append=_flags_
450 Append _flags_ to the default qemu flags (QEMU\_FLAGS variable or
451 `-cpu coreduo -smp 2`).
453 - -q, --qemu-flags=_flags_
455 Replace the default qemu flags (QEMU\_FLAGS variable or `-cpu coreduo
456 \-smp 2`) with _flags_ specified here.
460 Command that resets the target.
462 - --no-reset, --reset
464 Disable/enable resetting of the target.
466 ## Interaction with the bootloader on the target
468 - --uboot\[=_prompt_\]
470 Interact with U-Boot bootloader to boot the thing described in the
471 novaboot script. _prompt_ specifies the U-Boot's prompt (default is
472 "=> ", other common prompts are "U-Boot> " or "U-Boot# ").
473 Implementation of this option is currently tied to a particular board
474 that we use. It may be subject to changes in the future!
478 Disable U-Boot interaction previously enabled with **--uboot**.
482 Command(s) to send the U-Boot bootloader before loading the images and
483 booting them. This option can be given multiple times. After sending
484 commands from each option novaboot waits for U-Boot _prompt_.
486 If the command contains string _$NB\_MYIP_ then this string is
487 replaced by IPv4 address of eth0 interface. Similarly _$NB\_PREFIX_ is
488 replaced with prefix given by **--prefix**.
490 See also `uboot` keyword in ["NOVABOOT SCRIPT SYNTAX"](#novaboot-script-syntax)).
492 - --uboot-addr _name_=_address_
494 Load address of U-Boot's `tftpboot` command for loading _name_,
495 where name is one of _kernel_, _ramdisk_ or _fdt_ (flattened device
498 The default addresses are ${_name_\_addr\_r}, i.e. U-Boot environment
499 variables used by convention for this purpose.
501 - --uboot-cmd=_command_
503 Specifies U-Boot command used to execute the OS. If the command
504 contains strings `$kernel_addr`, `$ramdisk_addr`, `$fdt_addr`,
505 these are replaced with the addresses configured with **--uboot-addr**.
509 bootm $kernel_addr $ramdisk_addr $fdt_addr
511 or the `UBOOT_CMD` variable if defined in the novaboot script.
513 ## Target interaction phase
515 In this phase, target's serial output is redirected to stdout and if
516 stdin is a TTY, it is redirected to the target's serial input allowing
517 interactive work with the target.
521 When _string_ is sent by the target, novaboot exits. This option can
522 be specified multiple times, in which case novaboot exits whenever
523 either of the specified strings is sent.
525 If _string_ is `-re`, then the next **--exiton**'s _string_ is
526 treated as regular expression. For example:
528 --exiton -re --exiton 'error:.*failed'
530 - --exiton-re=_regex_
532 The same as --exiton -re --exiton _regex_.
534 - --exiton-timeout=_seconds_
536 By default **--exiton** waits for the string match forever. When this
537 option is specified, "exiton" timeouts after the specifies number of
538 seconds and novaboot returns non-zero exit code.
542 Setup things for interactive use of target. Your terminal will be
543 switched to raw mode. In raw mode, your system does not process input
544 in any way (no echoing of entered characters, no interpretation
545 special characters). This, among others, means that Ctrl-C is passed
546 to the target and does no longer interrupt novaboot. Use "~~."
547 sequence to exit novaboot.
549 - --no-interaction, --interaction
551 Skip resp. force target interaction phase. When skipped, novaboot exits
552 immediately when boot is initiated.
556 When _string_ is received from the target, send the string specified
557 with the subsequent **--send\*** option to the target.
559 - --expect-re=_regex_
561 When target's output matches regular expression _regex_, send the
562 string specified with the subsequent **--send\*** option to the target.
564 - --expect-raw=_perl-code_
566 Provides direct control over Perl's Expect module.
570 Send _string_ to the target after the previously specified
571 **--expect\*** was matched in the target's output. The _string_ may
572 contain escape sequences such as "\\n".
574 Note that _string_ is actually interpreted by Perl, so it can contain
575 much more that escape sequences. This behavior may change in the
578 Example: `--expect='login: ' --send='root\n'`
580 - --sendcont=_string_
582 Similar to **--send** but continue expecting more input.
584 Example: `--expect='Continue?' --sendcont='yes\n'`
586 # NOVABOOT SCRIPT SYNTAX
588 The syntax tries to mimic POSIX shell syntax. The syntax is defined
589 with the following rules.
591 Lines starting with "#" and empty lines are ignored.
593 Lines that end with "\\" are concatenated with the following line after
594 removal of the final "\\" and leading whitespace of the following line.
596 Lines of the form _VARIABLE=..._ (i.e. matching '^\[A-Z\_\]+=' regular
597 expression) assign values to internal variables. See ["VARIABLES"](#variables)
600 Lines starting with `load` keyword represent modules to boot. The
601 word after `load` is a file name (relative to the build directory
602 (see **--build-dir**) of the module to load and the remaining words are
603 passed to it as the command line parameters.
605 When the `load` line ends with "<<WORD" then the subsequent lines
606 until the line containing solely WORD are copied literally to the file
607 named on that line. This is similar to shell's heredoc feature.
609 When the `load` line ends with "< CMD" then command CMD is executed
610 with `/bin/sh` and its standard output is stored in the file named on
611 that line. The SRCDIR variable in CMD's environment is set to the
612 absolute path of the directory containing the interpreted novaboot
615 Lines starting with `run` keyword contain shell commands that are run
616 during file generation phase. This is the same as the "< CMD" syntax
617 for `load` keyboard except that the command's output is not
618 redirected to a file. The ordering of commands is the same as they
619 appear in the novaboot script.
621 Lines starting with `uboot` represent U-Boot commands that are sent
622 to the target if **--uboot** option is given. Having a U-Boot line in
623 the novaboot script is the same as passing an equivalent
624 **--uboot-init** option to novaboot. The `uboot` keyword can be
625 suffixed with timeout specification. The syntax is `uboot:Ns`, where
626 `N` is the whole number of seconds. If the U-Boot command prompt does
627 not appear before the timeout, novaboot fails. The default timeout is
632 #!/usr/bin/env novaboot
633 load bzImage console=ttyS0,115200
634 run make -C buildroot
635 load rootfs.cpio < gen_cpio buildroot/images/rootfs.cpio "myapp->/etc/init.d/S99myapp"
637 Example (NOVA User Land - NUL):
639 #!/usr/bin/env novaboot
640 WVDESC=Example program
641 load bin/apps/sigma0.nul S0_DEFAULT script_start:1,1 \
642 verbose hostkeyb:0,0x60,1,12,2
643 load bin/apps/hello.nul
644 load hello.nulconfig <<EOF
645 sigma0::mem:16 name::/s0/log name::/s0/timer name::/s0/fs/rom ||
646 rom://bin/apps/hello.nul
649 This example will load three modules: `sigma0.nul`, `hello.nul` and
650 `hello.nulconfig`. sigma0 receives some command line parameters and
651 `hello.nulconfig` file is generated on the fly from the lines between
656 The following variables are interpreted in the novaboot script:
660 Novaboot chdir()s to this directory before file generation phase. The
661 directory name specified here is relative to the build directory
662 specified by other means (see ["--build-dir"](#build-dir)).
666 Assigning this variable has the same effect as specifying ["--exiton"](#exiton)
671 Parameters passed to hypervisor. The default value is "serial", unless
672 overridden in configuration file.
676 The kernel to use instead of the hypervisor specified in the
677 configuration file with the `$hypervisor` variable. The value should
678 contain the name of the kernel image as well as its command line
679 parameters. If this variable is defined and non-empty, the variable
680 HYPERVISOR\_PARAMS is not used.
684 If this variable is 1, the system is not booted. This is currently
685 only implemented for U-Boot bootloader where it is useful for
686 interacting with the bootloader without booting the system - e.g. for
691 Use a specific qemu binary (can be overridden with **-Q**) and flags
692 when booting this script under qemu. If QEMU\_FLAGS variable is also
693 specified flags specified in QEMU variable are replaced by those in
698 Use specific qemu flags (can be overridden with **-q**).
702 See ["--uboot-cmd"](#uboot-cmd).
706 Description of the WvTest-compliant program.
710 The timeout in seconds for WvTest harness. If no complete line appears
711 in the test output within the time specified here, the test fails. It
712 is necessary to specify this for long running tests that produce no
717 Novaboot can read its configuration from one or more files. By
718 default, novaboot looks for files in `/etc/novaboot.d`, file
719 `~/.config/novaboot` and files named `.novaboot` as described in
720 ["Configuration reading phase"](#configuration-reading-phase). Alternatively, configuration file
721 location can be specified with the **-c** switch or with the
722 NOVABOOT\_CONFIG environment variable. The configuration file has Perl
723 syntax (i.e. it is better to put `1;` as the last line) and should set
724 values of certain Perl variables. The current configuration can be
725 dumped with the **--dump-config** switch. Some configuration variables
726 can be overridden by environment variables (see below) or by command
729 Supported configuration variables include:
733 Build directory location relative to the location of the configuration
738 Default target (see below) to use when no target is explicitly
739 specified with the **--target** command line option or
740 **NOVABOOT\_TARGET** environment variable.
744 Hash of target definitions to be used with the **--target** option. The
745 key is the identifier of the target, the value is the string with
746 command line options. For instance, if the configuration file contains:
748 $targets{'mybox'} = '--server=boot:/tftproot --serial=/dev/ttyUSB0 --grub',
750 then the following two commands are equivalent:
752 ./myos --server=boot:/tftproot --serial=/dev/ttyUSB0 --grub
755 # ENVIRONMENT VARIABLES
757 Some options can be specified not only via config file or command line
758 but also through environment variables. Environment variables override
759 the values from configuration file and command line parameters
760 override the environment variables.
764 Name of the novaboot configuration file to use instead of the default
767 - NOVABOOT\_CONFIG\_DIR
769 Name of the novaboot configuration directory. When not specified
770 `/etc/novaboot.d` is used.
774 Name of the novaboot target to use. This overrides the value of
775 **$default\_target** from the configuration file and can be overriden
776 with the **--target** command line option.
780 Defining this variable has the same meaning as **--bender** option.
784 Michal Sojka <sojka@os.inf.tu-dresden.de>