debian-forge/osbuild
Christian Kellner 64addbe2d2 buildroot: allow creating device nodes on s390x
The z Initial Program Loader (zipl) when creating the bootmap in
bootmap_creat (src/zipl/bootmap.c) wants to create a device node
via misc_temp_dev (bootmap_create:1141) for the device that it
is installing the bootloader to[1]. Currently access to loopback
devices is allowed from within the container (it is used to mount
the image), but only read/write access. On s390x also allow the
creation of device nodes, so zipl can do its work and install
the bootloader stages on the "disk".

[1] zipl source at commit dcce14923c3e9615df53773d1d8a3a22cbb23b96
2020-01-13 20:05:10 +01:00
..
__init__.py pipeline: return logs in --json mode 2019-12-14 13:49:24 +01:00
__main__.py osbuild: introduce secrets 2020-01-09 23:55:43 +01:00
api.py osbuild: create API sockets in the thread they're used in 2019-12-25 17:48:26 +01:00
buildroot.py buildroot: allow creating device nodes on s390x 2020-01-13 20:05:10 +01:00
loop.py loop: fix a few typos 2019-12-13 18:15:08 +01:00
objectstore.py objectstore: refer to objects, not trees 2019-09-25 23:50:50 +02:00
pipeline.py osbuild: introduce secrets 2020-01-09 23:55:43 +01:00
remoteloop.py remoteloop: don't use O_DIRECT on s390x 2020-01-13 20:05:10 +01:00
sources.py sources: bump maximum message size to 64k 2020-01-09 23:55:43 +01:00
tmpfs.py osbuild: split package into separate files 2019-08-21 09:56:50 +04:00
treesum.py treesum: don't use dir_fd parameter in os.scandir() 2019-11-29 00:45:14 +01:00