When installing/upgrading packages (e. g. a kernel and initramfs-tools),
the same initrd is generated twice:
```
$ apt-get install --no-install-recommends -y zstd initramfs-tools linux-image-generic
[...]
Setting up initramfs-tools-core (0.145) ...
Setting up initramfs-tools (0.145) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-6.12.16-amd64 (6.12.16-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.12.16-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.12.16-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.12.16-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.12.16-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.12.16-amd64
Setting up linux-image-amd64 (6.12.16-1) ...
Processing triggers for libc-bin (2.40-7) ...
Processing triggers for initramfs-tools (0.145) ...
update-initramfs: Generating /boot/initrd.img-6.12.16-amd64
```
Add a `-s` parameter to `update-initramfs` to set a Unix time stamp
(seconds since 1970) for the update mode. An existing initramfs will
only be updated if it is not newer than the specified Unix time stamp.
This feature is the first step to avoid generating the initrd twice.
LP: #1466965
"update-initramfs -c -k all" used to re-create initramfs images if
they had been deleted without using "update-initramfs -d", as it used
the state directory to determine which kernel versions should have
them.
Since commit f39625a "update-initramfs: Make "-k all" take over other
initramfs images", it ignores the state directory and is almost
equivalent to "update-initramfs -u -k all".
Change it to operate on all installed kernel versions. This will
ignore which kernel versions suppressed initramfs generation, but
I think it's reasonable to assume users won't use these options
if they have installed such kernels.
Closes: #926401
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Describe the new behaviour introduced by commit f39625afd6ba
"update-initramfs: Make "-k all" take over other initramfs images".
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
* Don't use angle brackets around parameters
* Show all options in manual page synopses if possible
* Make the usage summary line match the manual page synopsis,
excluding the -h option
* List all options in usage messages
* Refer to manual pages from usage messages
* Include one blank line at start and end of usage messages
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
The regular/bold formatting are applied to the wrong things on this
line. We also need braces to show where the alternate options start
and ends.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
When using inline markup, all whitespace is significant, so these
options had an extra space in front of them.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
In Debian, update-initramfs has always refused to overwrite or delete
an initramfs image that it didn't create, unless the -t option is
used. On Ubuntu, this check is apparently disabled. The commit log
doesn't provide much of a clue as to why. Looking at the the state of
Debian and the linux-2.6 package at the time, I think the reasoning
must have been something like:
(1) Multiple initramfs/initrd generators were available and could be
coinstalled. The configuration file /etc/kernel-img.conf specified
which one kernel packages should invoke ("ramdisk" variable).
(2) Packages that hooked into initramfs-tools would always run update-
initramfs if it existed, and it would immediately update the
initramfs, because triggers hadn't yet been invented.
(3) To keep the alternate initramfs generators working, update-
initramfs therefore had to either (a) check the configuration file to
find out whether initramfs-tools was meant to be used, or (b) keep
track of which initramfs images it created and therefore "owned".
At this point, (1) is no longer true; the "ramdisk" variable is not
honoured and the initramfs generator to be invoked is chosen by
installing one of several conflicting packages. I think this means
that (3) no longer follows, and whichever of the automatic initramfs
generator packages is currently installed should be considered to
"own" /boot/initrd.img-<version> for all kernel versions.
This commit only disables the checks. The state directory and the
state updates are retained for now, in case it becomes necessary to
revert this change.
Closes: #765750, #804295
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Set the .TH source parameter for all pages to "initramfs-tools".
Set the .TH manual parameter to a commonly used name for the man page
section.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Set each page's date to the date of the last substantive
change, i.e. excluding cross-reference updates and spelling fixes.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
The text in the manual page implies that -b needs an argument
but the usage summaries don't say that.
While we're at it, remove the brackets in '-k [version]', as
these suggest the version argument is optional.
Closes: #762768
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
- add myri10ge, smc911x and hptiop modules
- fix check_minkver() logic
- escape resume variables
- fix SEE ALSO section in all manpages
- source /usr/share/initramfs-tools/conf.d/*
- check against modules.dep before running depmod
- more verbose output
- open console with -i for dash interactive
- fix resume param by LABEL or UUID
- lvm has new prereq mdadm
- update-initramfs fix -v calling
- functions/scripts replace basename usage with shell expansion
