97c01e48ed
Currently we have all our elements and library files in a top-level directory and install them into <root>/share/diskimage-builder/[elements|lib] (where root is either / or the root of a virtualenv). The problem with this is that editable/development installs (pip -e) do *not* install data_files. Thus we have no canonical location to look for elements -- leading to the various odd things we do such as a whole bunch of guessing at the top of disk-image-create and having a special test-loader in tests/test_elements.py so we can run python unit tests on those elements that have it. data_files is really the wrong thing to use for what are essentially assets of the program. data_files install works well for things like config-files, init.d files or dropping documentation files. By moving the elements under the diskimage_builder package, we always know where they are relative to where we import from. In fact, pkg_resources has an api for this which we wrap in the new diskimage_builder/paths.py helper [1]. We use this helper to find the correct path in the couple of places we need to find the base-elements dir, and for the paths to import the library shell functions. Elements such as svc-map and pkg-map include python unit-tests, which we do not need tests/test_elements.py to special-case load any more. They just get found automatically by the normal subunit loader. I have a follow-on change (I69ca3d26fede0506a6353c077c69f735c8d84d28) to move disk-image-create to a regular python entry-point. Unfortunately, this has to move to work with setuptools. You'd think a symlink under diskimage_builder/[elements|lib] would work, but it doesn't. [1] this API handles stuff like getting files out of .zip archive modules, which we don't do. Essentially for us it's returning __file__. Change-Id: I5e3e3c97f385b1a4ff2031a161a55b231895df5b
58 lines
1.3 KiB
Plaintext
58 lines
1.3 KiB
Plaintext
mkdir -p /proc /sys /dev /boot /etc /mnt /lib/modules
|
|
|
|
mount -t proc proc /proc
|
|
|
|
mount -t sysfs none /sys
|
|
|
|
UDEVD=
|
|
if [ -x "/bin/systemd-udevd" ]; then
|
|
UDEVD="systemd-udevd"
|
|
else
|
|
UDEVD="udevd"
|
|
fi
|
|
|
|
# udev versions 176 and newer require a different on-disk setup
|
|
UDEVD_VERSION=$(udevadm --version)
|
|
|
|
if [ "$UDEVD_VERSION" != "" -a $UDEVD_VERSION -gt 175 ]; then
|
|
echo "Using new-style udevd setup"
|
|
mount -t devtmpfs none /dev
|
|
mkdir -p /run
|
|
mount -t tmpfs -o "nosuid,size=20%,mode=0755" tmpfs /run
|
|
mkdir -p /run/{lock,udev}
|
|
else
|
|
echo "Using old-style udevd setup"
|
|
mount -t tmpfs none /dev
|
|
ln -sf /proc/self/fd /dev/fd
|
|
mknod /dev/null c 1 3
|
|
mknod /dev/zero c 1 5
|
|
mknod /dev/random c 1 8
|
|
mknod /dev/urandom c 1 9
|
|
mknod /dev/tty0 c 4 0
|
|
mknod /dev/tty1 c 4 1
|
|
mknod /dev/tty2 c 4 2
|
|
mknod /dev/tty3 c 4 3
|
|
mknod /dev/tty4 c 4 4
|
|
mknod /dev/tty5 c 4 5
|
|
mknod /dev/tty6 c 4 6
|
|
mknod /dev/tty7 c 4 7
|
|
mknod /dev/tty8 c 4 8
|
|
mknod /dev/tty9 c 4 9
|
|
mknod /dev/tty c 5 0
|
|
mknod -m 0600 /dev/console c 5 1
|
|
mknod -m 0666 /dev/ptmx c 5 2
|
|
mkdir -p /dev/.udev/data
|
|
fi
|
|
|
|
echo "starting syslogd"
|
|
|
|
echo '*.* /initlog' > /etc/syslog.conf
|
|
syslogd
|
|
klogd
|
|
|
|
echo "starting udevd"
|
|
$UDEVD --daemon --resolve-names=never
|
|
|
|
echo "load modules"
|
|
load_modules_by_udev
|