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 the default action when no other action is
43 specified by command line switches. Thus running `novaboot myos` (or
44 `./myos` as described above) will run Qemu and make it boot the
45 configuration specified in the `myos` script.
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) and the
75 corresponding options follows.
77 ## Configuration reading phase
79 After starting, novaboot reads configuration files. Their content is
80 described in section ["CONFIGURATION FILE"](#configuration-file). By default,
81 configuration is read from multiple locations. First from the system
82 configuration directory, second from the user configuration file and
83 third from `.novaboot` files along the path to the current directory.
84 Alternatively, a single configuration file specified with the **-c**
85 switch or with the `NOVABOOT_CONFIG` environment variable. The latter
86 read files override settings from the former ones.
88 The system configuration directory is determined by the content of
89 NOVABOOT\_CONFIG\_DIR environment variable and defaults to
90 `/etc/novaboot.d`. Files in this directory with names consisting
91 solely of English letters, numbers, dashes '-' and underscores '\_'
92 (note that dot '.' is not included) are read in alphabetical order.
94 Then, the user configuration file is read from
95 `$XDG_CONFIG_HOME/novaboot`. If `$XDG_CONFIG_HOME` environemnt
96 variable is not set `~/.config/novaboot` is read instead.
98 Finally, novaboot searches for files named `.novaboot` starting from the
99 directory of the novaboot script (or working directory, see bellow)
100 and continuing upwards up to the root directory. The found
101 configuration files are then read in the opposite order (i.e. from the
102 root directory downwards). This allows to have, for example, a project
103 specific configuration in `~/project/.novaboot`.
105 Note the difference between `~/.config/novaboot` and `~/.novaboot`.
106 The former one is read always, whereas the latter only when novaboot
107 script or working directory is under the `$HOME` directory.
109 In certain cases, the location of the novaboot script cannot be
110 determined in this early phase. This happens either when the script is
111 read from the standard input or when novaboot is invoked explicitly as
112 in the example ["4."](#4) above. In this case the current working
113 directory is used as a starting point for configuration file search
114 instead of the novaboot script directory.
116 - -c, --config=_filename_
118 Use the specified configuration file instead of the default one(s).
120 ## Command line processing phase
124 Dump the current configuration to stdout end exit. Useful as an
125 initial template for a configuration file.
129 Print short (**-h**) or long (**--help**) help.
131 - -t, --target=_target_
133 This option serves as a user configurable shortcut for other novaboot
134 options. The effect of this option is the same as the options stored
135 in the `%targets` configuration variable under key _target_. See
136 also ["CONFIGURATION FILE"](#configuration-file).
138 ## Script preprocessing phase
140 This phases allows to modify the parsed novaboot script before it is
141 used in the later phases.
143 - -a, --append=_parameters_
145 Append a string to the first `load` line in the novaboot script. This
146 can be used to append parameters to the kernel's or root task's
147 command line. This option can appear multiple times.
151 Use `bender` chainloader. Bender scans the PCI bus for PCI serial
152 ports and stores the information about them in the BIOS data area for
155 - --chainloader=_chainloader_
157 Specifies a chainloader that is loaded before the kernel and other
158 files specified in the novaboot script. E.g. 'bin/boot/bender
163 Print the modules to boot and their parameters after this phase
164 finishes. Then exit. This is useful for seeing the effect of other
165 options in this section.
167 - -k, --kernel=`file`
169 Replace the first word on the first `load` line in the novaboot
172 - --scriptmod=_perl expression_
174 When novaboot script is read, _perl expression_ is executed for every
175 line (in $\_ variable). For example, `novaboot
176 \--scriptmod=s/sigma0/omega6/g` replaces every occurrence of _sigma0_
177 in the script with _omega6_.
179 When this option is present, it overrides _$script\_modifier_ variable
180 from the configuration file, which has the same effect. If this option
181 is given multiple times all expressions are evaluated in the command
184 ## File generation phase
186 In this phase, files needed for booting are generated in a so called
187 _build directory_ (see ["--build-dir"](#build-dir)). In most cases configuration
188 for a bootloader is generated automatically by novaboot. It is also
189 possible to generate other files using _heredoc_ or _"<"_ syntax in
190 novaboot scripts. Finally, binaries can be generated in this phases by
191 running `scons` or `make`.
193 - --build-dir=_directory_
195 Overrides the default build directory location.
197 The default build directory location is determined as follows: If the
198 configuration file defines the `$builddir` variable, its value is
199 used. Otherwise, it is the directory that contains the first processed
202 See also ["BUILDDIR"](#builddir) variable.
204 - -g, --grub\[=_filename_\]
206 Generates grub bootloader menu file. If the _filename_ is not
207 specified, `menu.lst` is used. The _filename_ is relative to the
208 build directory (see **--build-dir**).
210 - --grub-preamble=_prefix_
212 Specifies the _preable_ that is at the beginning of the generated
213 GRUB or GRUB2 config files. This is useful for specifying GRUB's
218 Specifies _prefix_ (e.g. `/srv/tftp`) that is put in front of every
219 file name in generated bootloader configuration files (or in U-Boot
222 If the _prefix_ contains string $NAME, it will be replaced with the
223 name of the novaboot script (see also **--name**).
225 If the _prefix_ contains string $BUILDDIR, it will be replaced with
226 the build directory (see also **--build-dir**).
230 Alias for **--prefix**.
232 - --grub2\[=_filename_\]
234 Generate GRUB2 menu entry in _filename_. If _filename_ is not
235 specified `grub.cfg` is used. The content of the menu entry can be
236 customized with **--grub-preamble**, **--grub2-prolog** or
237 **--grub\_prefix** options.
239 In order to use the the generated menu entry on your development
240 machine that uses GRUB2, append the following snippet to
241 `/etc/grub.d/40_custom` file and regenerate your grub configuration,
242 i.e. run update-grub on Debian/Ubuntu.
244 if [ -f /path/to/nul/build/grub.cfg ]; then
245 source /path/to/nul/build/grub.cfg
248 - --grub2-prolog=_prolog_
250 Specifies text that is put at the beginning of the GRUB2 menu entry.
252 - -m, --make\[=make command\]
254 Runs `make` to build files that are not generated by novaboot itself.
258 Use the name _string_ instead of the name of the novaboot script.
259 This name is used for things like a title of grub menu or for the
260 server directory where the boot files are copied to.
264 Do not run external commands to generate files (i.e. "<" syntax and
265 `run` keyword). This switch does not influence generation of files
266 specified with "<<WORD" syntax.
268 - -p, --pulsar\[=mac\]
270 Generates pulsar bootloader configuration file named `config-_mac_`
271 The _mac_ string is typically a MAC address and defaults to
274 - --scons\[=scons command\]
276 Runs `scons` to build files that are not generated by novaboot
281 Strip _rom://_ prefix from command lines and generated config files.
282 The _rom://_ prefix is used by NUL. For NRE, it has to be stripped.
286 Exit novaboot after file generation phase.
288 ## Target connection check
290 If supported by the target, the connection to it is made and it is
291 checked whether the target is not occupied by another novaboot
294 - --amt=_"\[user\[:password\]@\]host\[:port\]_
296 Use Intel AMT technology to control the target machine. WS management
297 is used to powercycle it and Serial-Over-Lan (SOL) for input/output.
298 The hostname or (IP address) is given by the _host_ parameter. If
299 _password_ is not specified, environment variable AMT\_PASSWORD is
300 used. The _port_ specifies a TCP port for SOL. If not specified, the
301 default is 16992. Default _user_ is admin.
303 - --iprelay=_addr\[:port\]_
305 Use TCP/IP relay and serial port to access the target's serial port
306 and powercycle it. The IP address of the relay is given by _addr_
307 parameter. If _port_ is not specified, it default to 23.
309 Note: This option is supposed to work with HWG-ER02a IP relays.
311 - -s, --serial\[=device\]
313 Target's serial line is connected to host's serial line (device). The
314 default value for device is `/dev/ttyUSB0`.
316 The value of this option is exported in NB\_NOVABOOT environment
317 variable to all subprocesses run by `novaboot`.
321 Specifies settings passed to `stty` invoked on the serial line
322 specified with **--serial** option. If this option is not given,
323 `stty` is called with `raw -crtscts -onlcr 115200` settings.
327 Command that mediates connection to the target's serial line. For
328 example `ssh server 'cu -l /dev/ttyS0'`.
330 - --remote-expect=_string_
332 Wait for reception of _string_ after establishing the the remote
333 connection before continuing.
335 ## File deployment phase
337 In some setups, it is necessary to copy the files needed for booting
338 to a particular location, e.g. to a TFTP boot server or to the
343 Turns your workstation into a DHCP and TFTP server so that the OS can
344 be booted via PXE BIOS (or similar mechanism) on the test machine
345 directly connected by a plain Ethernet cable to your workstation.
347 The DHCP and TFTP servers requires root privileges and `novaboot`
348 uses `sudo` command to obtain those. You can put the following to
349 _/etc/sudoers_ to allow running the necessary commands without asking
352 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
353 your_login ALL=NOPASSWD: NOVABOOT
357 Starts a TFTP server on your workstation. This is similar to
358 **--dhcp-tftp** except that DHCP server is not started.
360 The TFTP server require root privileges and `novaboot` uses `sudo`
361 command to obtain those. You can put the following to _/etc/sudoers_
362 to allow running the necessary commands without asking for password.
364 Cmnd_Alias NOVABOOT = /usr/sbin/in.tftpd --listen --secure -v -v -v --pidfile tftpd.pid *, /usr/bin/pkill --pidfile=tftpd.pid
365 your_login ALL=NOPASSWD: NOVABOOT
369 Port to run the TFTP server on. Implies **--tftp**.
373 Generates the ISO image that boots NOVA system via GRUB. If no filename
374 is given, the image is stored under _NAME_.iso, where _NAME_ is the name
375 of the novaboot script (see also **--name**).
377 - --server\[=\[\[user@\]server:\]path\]
379 Copy all files needed for booting to another location. The files will
380 be copied (by **rsync** tool) to the directory _path_. If the _path_
381 contains string $NAME, it will be replaced with the name of the
382 novaboot script (see also **--name**).
384 - --rsync-flags=_flags_
386 Specifies which _flags_ are appended to `rsync` command line when
387 copying files as a result of _--server_ option.
391 If **--server** is used and its value ends with $NAME, then after
392 copying the files, a new bootloader configuration file (e.g. menu.lst)
393 is created at _path-wo-name_, i.e. the path specified by **--server**
394 with $NAME part removed. The content of the file is created by
395 concatenating all files of the same name from all subdirectories of
396 _path-wo-name_ found on the "server".
400 Use Intel AMT technology for IDE redirection. This allows the target
401 machine to boot from novaboot created ISO image. Implies **--iso**.
403 The experimental `amtider` utility needed by this option can be
404 obtained from https://github.com/wentasah/amtterm.
406 ## Target power-on and reset phase
408 At this point, the target is reset (or switched on/off). There is
409 several ways how this can be accomplished. Resetting a physical target
410 can currently be accomplished by the following options: **--amt**,
411 **--iprelay**, **--reset-cmd**.
415 Switch on/off the target machine and exit. The script (if any) is
416 completely ignored. Currently it works only with **--iprelay** or
419 - -Q, --qemu\[=_qemu-binary_\]
421 Boot the configuration in qemu. Optionally, the name of qemu binary
422 can be specified as a parameter.
424 - --qemu-append=_flags_
426 Append _flags_ to the default qemu flags (QEMU\_FLAGS variable or
427 `-cpu coreduo -smp 2`).
429 - -q, --qemu-flags=_flags_
431 Replace the default qemu flags (QEMU\_FLAGS variable or `-cpu coreduo
432 \-smp 2`) with _flags_ specified here.
436 Command that resets the target.
438 - --no-reset, --reset
440 Disable/enable resetting of the target.
442 ## Interaction with the bootloader on the target
444 - --uboot\[=_prompt_\]
446 Interact with U-Boot bootloader to boot the thing described in the
447 novaboot script. _prompt_ specifies the U-Boot's prompt (default is
448 "=> ", other common prompts are "U-Boot> " or "U-Boot# ").
449 Implementation of this option is currently tied to a particular board
450 that we use. It may be subject to changes in the future!
454 Command(s) to send the U-Boot bootloader before loading the images and
455 booting them. This option can be given multiple times. After sending
456 commands from each option novaboot waits for U-Boot _prompt_.
458 If the command contains string _$NB\_MYIP_ then this string is
459 replaced by IPv4 address of eth0 interface. Similarly _$NB\_PREFIX_ is
460 replaced with prefix given by **--prefix**.
462 See also `uboot` keyword in ["NOVABOOT SCRIPT SYNTAX"](#novaboot-script-syntax)).
464 - --uboot-addr _name_=_address_
466 Load address of U-Boot's `tftpboot` command for loading _name_,
467 where name is one of _kernel_, _ramdisk_ or _fdt_ (flattened device
470 The default addresses are ${_name_\_addr\_r}, i.e. U-Boot environment
471 variables used by convention for this purpose.
473 - --uboot-cmd=_command_
475 Specifies U-Boot command used to execute the OS. If the command
476 contains strings `$kernel_addr`, `$ramdisk_addr`, `$fdt_addr`,
477 these are replaced with the addresses configured with **--uboot-addr**.
481 bootm $kernel_addr $ramdisk_addr $fdt_addr
483 or the `UBOOT_CMD` variable if defined in the novaboot script.
485 ## Target interaction phase
487 In this phase, target's serial output is redirected to stdout and if
488 stdin is a TTY, it is redirected to the target's serial input allowing
489 interactive work with the target.
493 When _string_ is sent by the target, novaboot exits. This option can
494 be specified multiple times, in which case novaboot exits whenever
495 either of the specified strings is sent.
497 If _string_ is `-re`, then the next **--exiton**'s _string_ is
498 treated as regular expression. For example:
500 --exiton -re --exiton 'error:.*failed'
502 - --exiton-re=_regex_
504 The same as --exiton -re --exiton _regex_.
506 - --exiton-timeout=_seconds_
508 By default **--exiton** waits for the string match forever. When this
509 option is specified, "exiton" timeouts after the specifies number of
510 seconds and novaboot returns non-zero exit code.
514 Setup things for interactive use of target. Your terminal will be
515 switched to raw mode. In raw mode, your system does not process input
516 in any way (no echoing of entered characters, no interpretation
517 special characters). This, among others, means that Ctrl-C is passed
518 to the target and does no longer interrupt novaboot. Use "~~."
519 sequence to exit novaboot.
523 When _string_ is received from the target, send the string specified
524 with the subsequent **--send\*** option to the target.
526 - --expect-re=_regex_
528 When target's output matches regular expression _regex_, send the
529 string specified with the subsequent **--send\*** option to the target.
531 - --expect-raw=_perl-code_
533 Provides direct control over Perl's Expect module.
537 Send _string_ to the target after the previously specified
538 **--expect\*** was matched in the target's output. The _string_ may
539 contain escape sequences such as "\\n".
541 Note that _string_ is actually interpreted by Perl, so it can contain
542 much more that escape sequences. This behavior may change in the
545 Example: `--expect='login: ' --send='root\n'`
547 - --sendcont=_string_
549 Similar to **--send** but continue expecting more input.
551 Example: `--expect='Continue?' --sendcont='yes\n'`
553 # NOVABOOT SCRIPT SYNTAX
555 The syntax tries to mimic POSIX shell syntax. The syntax is defined
556 with the following rules.
558 Lines starting with "#" and empty lines are ignored.
560 Lines that end with "\\" are concatenated with the following line after
561 removal of the final "\\" and leading whitespace of the following line.
563 Lines of the form _VARIABLE=..._ (i.e. matching '^\[A-Z\_\]+=' regular
564 expression) assign values to internal variables. See ["VARIABLES"](#variables)
567 Lines starting with `load` keyword represent modules to boot. The
568 word after `load` is a file name (relative to the build directory
569 (see **--build-dir**) of the module to load and the remaining words are
570 passed to it as the command line parameters.
572 When the `load` line ends with "<<WORD" then the subsequent lines
573 until the line containing solely WORD are copied literally to the file
574 named on that line. This is similar to shell's heredoc feature.
576 When the `load` line ends with "< CMD" then command CMD is executed
577 with `/bin/sh` and its standard output is stored in the file named on
578 that line. The SRCDIR variable in CMD's environment is set to the
579 absolute path of the directory containing the interpreted novaboot
582 Lines starting with `run` keyword contain shell commands that are run
583 during file generation phase. This is the same as the "< CMD" syntax
584 for `load` keyboard except that the command's output is not
585 redirected to a file. The ordering of commands is the same as they
586 appear in the novaboot script.
588 Lines starting with `uboot` represent U-Boot commands that are sent
589 to the target if **--uboot** option is given. Having a U-Boot line in
590 the novaboot script is the same as passing an equivalent
591 **--uboot-init** option to novaboot. The `uboot` keyword can be
592 suffixed with timeout specification. The syntax is `uboot:Ns`, where
593 `N` is the whole number of seconds. If the U-Boot command prompt does
594 not appear before the timeout, novaboot fails. The default timeout is
599 #!/usr/bin/env novaboot
600 load bzImage console=ttyS0,115200
601 run make -C buildroot
602 load rootfs.cpio < gen_cpio buildroot/images/rootfs.cpio "myapp->/etc/init.d/S99myapp"
604 Example (NOVA User Land - NUL):
606 #!/usr/bin/env novaboot
607 WVDESC=Example program
608 load bin/apps/sigma0.nul S0_DEFAULT script_start:1,1 \
609 verbose hostkeyb:0,0x60,1,12,2
610 load bin/apps/hello.nul
611 load hello.nulconfig <<EOF
612 sigma0::mem:16 name::/s0/log name::/s0/timer name::/s0/fs/rom ||
613 rom://bin/apps/hello.nul
616 This example will load three modules: `sigma0.nul`, `hello.nul` and
617 `hello.nulconfig`. sigma0 receives some command line parameters and
618 `hello.nulconfig` file is generated on the fly from the lines between
623 The following variables are interpreted in the novaboot script:
627 Novaboot chdir()s to this directory before file generation phase. The
628 directory name specified here is relative to the build directory
629 specified by other means (see ["--build-dir"](#build-dir)).
633 Assigning this variable has the same effect as specifying ["--exiton"](#exiton)
638 Parameters passed to hypervisor. The default value is "serial", unless
639 overridden in configuration file.
643 The kernel to use instead of the hypervisor specified in the
644 configuration file with the `$hypervisor` variable. The value should
645 contain the name of the kernel image as well as its command line
646 parameters. If this variable is defined and non-empty, the variable
647 HYPERVISOR\_PARAMS is not used.
651 If this variable is 1, the system is not booted. This is currently
652 only implemented for U-Boot bootloader where it is useful for
653 interacting with the bootloader without booting the system - e.g. for
658 Use a specific qemu binary (can be overridden with **-Q**) and flags
659 when booting this script under qemu. If QEMU\_FLAGS variable is also
660 specified flags specified in QEMU variable are replaced by those in
665 Use specific qemu flags (can be overridden with **-q**).
669 See ["--uboot-cmd"](#uboot-cmd).
673 Description of the WvTest-compliant program.
677 The timeout in seconds for WvTest harness. If no complete line appears
678 in the test output within the time specified here, the test fails. It
679 is necessary to specify this for long running tests that produce no
684 Novaboot can read its configuration from one or more files. By
685 default, novaboot looks for files in `/etc/novaboot.d`, file
686 `~/.config/novaboot` and files named `.novaboot` as described in
687 ["Configuration reading phase"](#configuration-reading-phase). Alternatively, configuration file
688 location can be specified with the **-c** switch or with the
689 NOVABOOT\_CONFIG environment variable. The configuration file has Perl
690 syntax (i.e. it is better to put `1;` as the last line) and should set
691 values of certain Perl variables. The current configuration can be
692 dumped with the **--dump-config** switch. Some configuration variables
693 can be overridden by environment variables (see below) or by command
696 Supported configuration variables include:
700 Build directory location relative to the location of the configuration
705 Default target (see below) to use when no target is explicitly
706 specified on command line with the **--target** option.
710 Hash of target definitions to be used with the **--target** option. The
711 key is the identifier of the target, the value is the string with
712 command line options. For instance, if the configuration file contains:
714 $targets{'mybox'} = '--server=boot:/tftproot --serial=/dev/ttyUSB0 --grub',
716 then the following two commands are equivalent:
718 ./myos --server=boot:/tftproot --serial=/dev/ttyUSB0 --grub
721 # ENVIRONMENT VARIABLES
723 Some options can be specified not only via config file or command line
724 but also through environment variables. Environment variables override
725 the values from configuration file and command line parameters
726 override the environment variables.
730 Name of the novaboot configuration file to use instead of the default
733 - NOVABOOT\_CONFIG\_DIR
735 Name of the novaboot configuration directory. When not specified
736 `/etc/novaboot.d` is used.
740 Defining this variable has the same meaning as **--bender** option.
744 Michal Sojka <sojka@os.inf.tu-dresden.de>