File: flash-kernel.8

package info (click to toggle)
flash-kernel 3.110
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 744 kB
  • sloc: sh: 539; makefile: 36
file content (90 lines) | stat: -rw-r--r-- 3,618 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
.\" -*- nroff -*-
.TH FLASH-KERNEL 8
.SH NAME
flash-kernel \- put kernel and initramfs in boot location
.SH SYNOPSIS
.B flash-kernel [--supported] [--force] [kvers]
.SH DESCRIPTION
flash-kernel is a script which will put the kernel and initramfs in
the boot location of embedded devices that don't load the kernel and
initramfs directly from /boot.  flash-kernel supports devices that
boot from flash memory (hence the name) as well as some devices that
require a special boot image on the disk.
.P
Optionally, it can be passed a version of the kernel to flash; only
the highest version will be flashed and other versions will be
ignored unless the \-\-force option is used. Kernel and initrd are
read from /boot.
.P
Note that when the \-\-force the kernel can be overwritten with the current
version whenever a package is installed which changes the kernel, initramfs
etc. Therefore this is only really useful for one-off testing.
.P
Prior to flashing the kernel, a check is performed to verify that
the subarchitectures of the machine and the image to be flashed
match. Valid filenames for images to flash are suffixed with the
subarchitecture.
.P
If the \-\-supported option is used, flash\-kernel will test to see if
the hardware is supported, and return a true or false value.
.SH ENVIRONMENT VARIABLES

.IP FK_MACHINE
Specify a specific machine, overriding the autodetection, also see the
description of
.B /etc/flash\-kernel/machine
below. Can be set to `none' to disable flash\-kernel. This can be used
when installing flash\-kernel into a chroot, for example while
preparing a filesystem image.
.B WARNING: Take great care when running flash\-kernel in a chroot, since the
.B choice of machine may cause host filesystem partitions to be mounted and 
.B modified.

.IP FK_IGNORE_EFI
Skip EFI detection when this variable is set to `yes'. Normally, flash-kernel
will abort if it detects that the system is running in EFI mode.

.SH FILES
.TP
.B /usr/share/flash-kernel/db/all.db
The database of machines which flash\-kernel knows about. See
.B /usr/share/doc/flash-kernel/README.gz
For information on the database fields.
.TP
.B /etc/default/flash-kernel
may contain the following variables:
.IP
.IR LINUX_KERNEL_CMDLINE ,
which is used by bootscripts to set kernel command line options, overriding the
firmwares defaults (e.g. u-boot's ${bootargs}).
.IP
.IR LINUX_KERNEL_CMDLINE_DEFAULTS ,
which is used by bootscripts to set kernel options which should be overrideable
by the firmware's defaults (e.g. u-boot's ${bootargs}).
.IP
.IR NO_CREATE_DOT_BAK_FILES ,
which if set to "true" or "yes" will prevent flash-kernel from creating backup
".bak" versions of kernel, initrd, and dtb files when installing a new version.
The default is to create such backups to aid in recovery from failed updates.
.IP
.IR MTD_BACKUP_DIR ,
which if set, names a directory to which flash-kernel will write copies of files
which would not normally be accessible in the regular filesystem (either written
to a raw flash partition or to a firmware partition which is not normally
mounted).
If unset defaults to
.I /var/backups/flash-kernel.
Set to "none" to disable.
.TP
.B /etc/flash\-kernel/db
Local overrides to the database of machines
.TP
.B /etc/flash\-kernel/machine
If present this can be used to override the machine autodetection. The
contents must be a string which matches an entry in the database. Or
`none' to disable flash\-kernel.
.B /etc/flash\-kernel/ignore-efi
If present, the contents of this file are used to set the value of the
FK_IGNORE_EFI environment variable.
.SH AUTHOR
Martin Michlmayr <tbm@cyrius.com>