diff options
| author | Lyndon Brown <jnqnfe@gmail.com> | 2020-03-11 18:43:12 +0000 |
|---|---|---|
| committer | Luca Boccassi <bluca@debian.org> | 2020-03-12 10:31:39 +0000 |
| commit | 1e0339a4e36f85f468ecbdc21c645541f51e5e56 (patch) | |
| tree | 81e7fc69a6fa84b42ae1efa19a2fa6a3957ee6a9 /manpages | |
| parent | 9930ce1ea542516dabdce9ce9b2bb297b437483a (diff) | |
| download | vyos-live-build-1e0339a4e36f85f468ecbdc21c645541f51e5e56.tar.gz vyos-live-build-1e0339a4e36f85f468ecbdc21c645541f51e5e56.zip | |
remove obsolete loop-aes-utils related losetup hack
677415f6d7efc1e5b888570d70af311d2900c69c (2007) in v1.0~a2-1 added a hack
relating to the loop-aes-utils package and losetup. this commit bundled
a bunch of changes, it was not specific to the hack, and so info about the
hack is limited to a brief comment included within the related change in
defaults:
```
# Workaround for loop-aes-utils divertion
# (loop-aes-utils' losetup lacks features).
```
though it is very similar to the removed fdisk hack in that it seems that
one package may replace a binary from another, moving the original to a
new location, and this hack gives the user the opportunity to select the
original instead of the one put in its place, for use in LB.
the comment mentions a package called loop-aes-utils as being the package
that performs such a diversion, and that the need for the hack was that
losetup itself lacked features, presumably encryption support, and it is
clear that it is the losetup binary that is the focus of the diversion.
looking into the history of loop-aes-utils a little, this package was
dropped from debian back in 2012 (#680748), favouring encrytion support of
dm-crypt/cryptsetup.
double checking file contents of packages, only the mount package carries
an /sbin/losetup file, so presumably this means that dm-setup/cryptsetup
do not perform such a diversion of losetup (i.e. their use is exclusively
done directly).
since the possible diversion is simply gone, that completely removes any
point in having the hack of giving users choice between losetup and the
diverted one. so let's remove this obsolete hack...
Diffstat (limited to 'manpages')
| -rw-r--r-- | manpages/en/lb_config.1 | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/manpages/en/lb_config.1 b/manpages/en/lb_config.1 index 8282973ca..76148435e 100644 --- a/manpages/en/lb_config.1 +++ b/manpages/en/lb_config.1 @@ -152,8 +152,6 @@ .br [\fB\-\-loadlin\fR true|false] .br - [\fB\-\-losetup\fR losetup|losetup.orig] -.br [\fB\-\-memtest\fR memtest86+|memtest86|none] .br [\fB\-\-mirror\-binary\fR \fIURL\fR] @@ -395,8 +393,6 @@ sets the kernel flavours to be installed. Note that in case you specify more tha sets the internal name of the kernel packages naming scheme. If you use debian kernel packages, you will not have to adjust it. If you decide to use custom kernel packages that do not follow the debian naming scheme, remember to set this option to the stub of the packages only (for debian this is linux\-image\-2.6), so that \fISTUB\fR-\fIFLAVOUR\fR results in a valid package name (for debian e.g. linux\-image\-686\-pae). Preferably you use the meta package name, if any, for the stub, so that your configuration is ABI independent. Also don't forget that you have to include stubs of the binary modules packages for unionfs or aufs, and squashfs if you built them out-of-tree. .IP "\fB\-\-loadlin\fR true|false" 4 sets loadlin. Defaults to false, except when the debian-installer is included for x86_64 or i386. -.IP "\fB\-\-losetup\fR losetup|losetup.orig" 4 -sets the filename of the losetup binary from the host system that should be used. This is autodetected and does generally not need any customization. .IP "\fB\-\-memtest\fR memtest86+|memtest86|none" 4 defines if memtest, memtest86+ or no memory tester at all should be included as secondary bootloader configuration. This is only available on amd64 and i386 and defaults to memtest86+. .IP "\fB\-\-mirror\-binary\fR \fIURL\fR" 4 |