vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 9cf3a2d30dc15853ff9c230840dfb94a5ae9d601
Merge: 9d732c4 b55d060
Author: Luca Boccassi <bluca@debian.org>
Date: Fri Jan 3 23:39:47 2025 +0000
Merge branch 'zeha/readonly-nvme' into 'master'
0020-read-only: iterate over all devices + improve console message layout
See merge request live-team/live-boot!60
commit 9d732c47e730156a1eb91dd0d667392edaf95287
Merge: 5af574c 5be6189
Author: Luca Boccassi <bluca@debian.org>
Date: Fri Jan 3 23:38:14 2025 +0000
Merge branch 'zeha/findiso-features' into 'master'
fromiso features
See merge request live-team/live-boot!59
commit b55d06044c82d77b43e5d3752625dc7f79dbebdb
Author: Michael Prokop <mika@grml.org>
Date: Fri Jul 10 08:57:19 2020 +0200
0020-read-only: iterate over all devices + improve console message layout
There might be block devices other than /dev/sd* + /dev/vd* (like
/dev/nvme0n*). Instead of hardcoding a static list, let's iterate over
all of them, and then ignore all symlinks (pointing to the actual
devices) and consider only actual block devices.
Also ensure that the device exists (checked via `blockdev --getsz ...`)
before executing `blockdev --setro ...` on it.
Reworked the according console message: using printf with field width
allows us to make this look a bit nicer and better integrate into the
boot sequence look-alike.
JFTR: it would be nice to send output also to `/boot.log` (which ends up
as `/var/log/live/boot.log` on the booted system), but if we do this
then the output is visible twice during startup, as `/boot.live` is sent
to console via `tail -f`. If changing this to only list it via
`/boot.live` it might not be always guaranteed to be visible on screen,
so we didn't change this yet.
This work was funded by Grml-Forensic.
[zeha@d.o: forward upstream]
commit 5af574cdb0fecf04d9efff8706cd4447071085de
Merge: cb107a9 0cc0263
Author: Luca Boccassi <bluca@debian.org>
Date: Fri Jan 3 23:02:45 2025 +0000
Merge branch 'zeha/fix-lvm' into 'master'
Activate LVM volumes if needed
See merge request live-team/live-boot!58
commit 5be6189688414b279912a0b74af5c4d9a656b194
Author: Mihai Moldovan <ionic@ionic.de>
Date: Thu Mar 25 06:15:28 2021 +0100
fromiso: support lvm/mdadm as sources
Previously, it wasn't possible to use fromiso with a Linux software RAID
or LVM device.
The code handling lvm/mdadm devices has been moved around and the
fromiso feature split up, so that lvm/mdadm devices are now started as
necessary even when fromiso has been passed.
The usual caveats apply: if you start from an lvm/mdadm device *without*
using the toram feature, the original volume will be kept mounted, so
it's not safe to mount the volume containing the grml image after
booting it.
With the toram feature, this is not an issue, since all the data is read
into a ramdisk and the original volume unmounted.
[zeha@d.o: rebase, forward upstream]
commit 25bac8666d8e2cf7b3e1b5c30f664bfca7aab631
Author: Mihai Moldovan <ionic@ionic.de>
Date: Mon Mar 8 06:30:50 2021 +0100
fromiso: allow overriding fstype
The overriding feature can be turned on/used by prefixing the file
system type to the path, separated from the device node with a colon.
Example (good override): ext4:/dev/vda49/path/to/grml.iso
If the file system specification contains any non-alphanumerical
characters other than '-' or '_', it will be treated as part of the
actual path, since, at least currently, all known file systems match
this rule.
Example (no override): cra$$$yf§:/dev/sr0/another_path/to/grml.iso
In the former example, no file system type override is detected, which
means that the code will eventually search for a device called
'cra$$$yf§:/dev/sr0' (which, granted, doesn't make a lot of sense).
Sometimes it's necessary or at least handy to specify the file system
used for mounting the fromiso backing device directly.
For instance, putting the ISO file on a RAID1-backed device will fail to
mount it through autodetection (which, really, in most cases is a good
thing to not corrupt the array).
This change also mounts the backing device read-only, which should
enable safe usage and mounting even on RAID1 devices. Note, though, that
read-only mounts are not really very much "read-only", since they
actually sometimes still change on-disk file system metadata, like the
last time the device was mounted).
This said, it should be safe enough and users can easily re-sync the
array to ensure consistency later on.
[zeha@d.o: rebase, forward upstream]
commit cb107a9079efbdd45e0ed411735c7a8a11f6e3cd
Merge: 52ba499 9cdbf41
Author: Luca Boccassi <bluca@debian.org>
Date: Fri Jan 3 22:47:24 2025 +0000
Merge branch 'zeha/findiso-mdadm' into 'master'
Fix RAID detection for findiso
See merge request live-team/live-boot!57
commit 0cc0263a889ac60533555efb57bf4d653ada1956
Author: Michael Laß <bevan@bi-co.net>
Date: Thu Aug 31 20:03:38 2023 +0200
9990-main.sh: activate LVM volumes if needed.
An update to the Debian lvm2 package removed a script in the initrd that
would activate any LVs that are required to access the root volume. Due
to this change, grml failed to find its live media when it was stored on
an LVM volume.
Add an explicit activation of any LVs mentioned in the `live-media` or
`bootfrom` kernel arguments, so that the live media can be found again.
Reference: https://github.com/grml/grml/issues/200
[zeha@d.o: forward upstream]
commit 52ba499b676303a2d02c2faec723d2a8e9764e8d
Merge: 60a921f b187626
Author: Luca Boccassi <bluca@debian.org>
Date: Fri Jan 3 22:35:24 2025 +0000
Merge branch 'zeha/bootlog' into 'master'
9990-misc-helpers.sh: append to boot.log, do not overwrite it
See merge request live-team/live-boot!56
commit 60a921f3423ed9cc4cec6a393482ef16633c49a1
Merge: 9ed98df fd5a152
Author: Luca Boccassi <bluca@debian.org>
Date: Fri Jan 3 22:34:22 2025 +0000
Merge branch 'zeha/netdev-mac' into 'master'
live-netdev: accept a MAC address for picking device
See merge request live-team/live-boot!55
commit 9cdbf4142c2150d33bb0f29ac0b5fb2fd478796f
Author: Mihai Moldovan <ionic@ionic.de>
Date: Wed Mar 24 12:31:29 2021 +0100
Fix RAID detection for findiso
mdadm 3.4-2 (Debian stretch) dropped the local-top mdadm script, and
replaced it with a local-block script and some systemd parts.
Use the "new" local-block mdadm script instead.
This one won't allow us to select a specific device to assemble, so just
let it start all of them and hope for the best.
Reference: https://github.com/grml/grml/issues/125
[zeha@d.o: forward upstream, reword]
commit b187626948c5f10eca0885f97658a41c96b5054e
Author: Michael Prokop <mika@grml.org>
Date: Fri Jul 10 09:05:19 2020 +0200
9990-misc-helpers.sh: append to boot.log, do not overwrite it
boot.log might exist already when try_mount fails. Append the log
message instead of truncating it.
commit fd5a152ea5241373ceab02f606e4af597f593179
Author: ThomasToka <117008525+ThomasToka@users.noreply.github.com>
Date: Tue Jul 4 12:27:21 2023 +0200
live-netdev: accept a MAC address for picking device
Have live-netdev accept a MAC address to pick the network device to use.
Correct format is: "live-netdev=xx:xx:xx:xx:xx:xx"
[mika@d.o: use tabs, drop noop assignment]
[zeha@d.o: improve commit message and log messages, forward upstream]
commit 9ed98df6bcf1cf6fba0150d96437536e7e52ab98
Merge: 47b0c06 3be63e6
Author: Luca Boccassi <bluca@debian.org>
Date: Fri Jan 3 21:55:34 2025 +0000
Merge branch 'zeha/rm-old-location' into 'master'
Remove support for legacy live location
See merge request live-team/live-boot!54
commit 47b0c06704efb0c5506af608bde62d56497afaef
Merge: 68c4637 45f68c4
Author: Luca Boccassi <bluca@debian.org>
Date: Fri Jan 3 21:46:45 2025 +0000
Merge branch 'zeha/memdisk' into 'master'
Avoid executing memdiskfind under Secure Boot
See merge request live-team/live-boot!53
commit 3be63e6a3fbae358992a9ceaf9839ca5a524ddd2
Author: Chris Hofstaedtler <zeha@debian.org>
Date: Fri Jan 3 22:38:03 2025 +0100
Remove support for legacy live location
Remove code that was supposed to go away before the bullseye release.
Finalize the migration started in
c6a17c7b41bab36c8445e05fcd60e1e7a0a703a3.
Keeping the old path around breaks running update-initramfs *on* a live
system, where backend/initramfs-tools/live.hook will copy
libnss_dns.so.*, libnss_files.so.* from both /usr/lib and
/usr/lib/live/mount/... into the initramfs.
commit 45f68c40f584f2b836ebb9b178d2da0d14651d8c
Author: Michael Prokop <mika@grml.org>
Date: Sat Jul 18 17:00:46 2020 +0200
Avoid executing memdiskfind under Secure Boot
memdiskfind displays an ugly error message when running under Secure
Boot where access to /dev/mem is restricted:
| cannot open /dev/mem: Operation not permitted
If reading from /dev/mem fails, skip memdiskfind and instead display a
warning message.
commit 3ecb59af4c9e71e2314f956e385036a3f19cc287
Author: Chris Hofstaedtler <zeha@debian.org>
Date: Fri Jan 3 22:13:56 2025 +0100
components/3050-memdisk.sh: flip ifs, unindent
commit 8373e285fa7ca2b2469239307f541101601f977a
Author: Chris Hofstaedtler <zeha@debian.org>
Date: Fri Jan 3 22:12:46 2025 +0100
Extract Setup_Memdisk out of components/9990-main.sh
Same code, just in a new file.
commit 68c46378782d037d426dd67d2ca0ad336c49deea
Author: Thomas Goirand <zigo@debian.org>
Date: Tue Nov 12 12:44:22 2024 +0100
d/changelog:
* Non-maintainer upload.
* Add fix to get DHCP from all nics, not only the first one seen with link
up (Closes: #1069048).
commit a96646e5978c111bf422c558602c1957fe95e4ab
Author: Thomas Goirand <zigo@debian.org>
Date: Mon Apr 15 15:40:46 2024 +0200
Do DHCP on multiple interfaces
The current behavior of live-boot is to search 5 times for network
interfaces with the carrier link up. If there is more than one
interface, but only one is found during a run, then it currently
gives-up searching for other interfaces and exits.
This works if one is lucky, or if only the interfaces with DHCP
have an actual ethernet link. For cases where there is more than
one interface with the link up, but only one is connected to a
DHCPd server, it is possible that it will fail (depending which
card will have the link first).
This patch changes the behavior: it makes sure that all cards
with a link that is up are reported in /conf/param.conf before
exiting, so that live-boot will try to get an IP address from
all cards with link up. Each card continues to have a 15 seconds
timeout (by default) to get the IP address from DHCP.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/l/live-boot.png){kind=link}