summaryrefslogtreecommitdiff
path: root/functions/common.sh
diff options
context:
space:
mode:
authorMatthijs Kooijman <matthijs@stdin.nl>2017-08-29 15:04:31 +0200
committerRaphaƫl Hertzog <hertzog@debian.org>2017-09-01 10:07:00 +0200
commit4c229d9449ab5605940bdee28e89166132b1d7e1 (patch)
treea65a6831130f9beba5e0d0bbf7bca44a45ba416c /functions/common.sh
parente8118e8e0a502df4439ffed145942ee1f206bd9d (diff)
downloadvyos-live-build-4c229d9449ab5605940bdee28e89166132b1d7e1.tar.gz
vyos-live-build-4c229d9449ab5605940bdee28e89166132b1d7e1.zip
Pass --partscan to losetup
Recent versions of Linux, parted or some other bit of software cause partition devices, like /dev/loop0p1 to be created when running parted mkpart. However, these devices are not cleaned up when running losetup -d to remove /dev/loop0 later, so they linger around and confuse mkfs (which refuses to make a filesystem, thinking there are partitions): mkfs.fat 4.1 (2017-01-24) mkfs.vfat: Partitions or virtual mappings on device '/dev/loop0', not making filesystem (use -I to override) To prevent this behaviour, pass --partscan to losetup when adding a new partition, to clean up any lingering partitions. It seems losetup does not accept --partscan when deleting a loop device, to clean up at that point, but since binary_hdd mounts the partition last, there should not be any lingering partition devices after live-build is done. The --partscan option is available since util-linux 2.21 (released in 2012), so it should be fairly safe to pass it unconditionally.
Diffstat (limited to 'functions/common.sh')
0 files changed, 0 insertions, 0 deletions