| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
These udev rules were being ignored since we configured Systemd to
install things in /usr/bin and /usr/lib in
0a0da35e1a693fc909d1628f5e81cb3b2693c057.
LVM device nodes weren't being created, and as a result, systems that
had LVM volumes configured in fstab, weren't booting.
Installing the udev rules in /usr/lib fixes the problem.
Change-Id: Ia3372676700c78c655af8721bb8568549eb64666
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was done using the 'indent' tool, which uses a fork of PyYAML named
'ruamel.yaml' to rewrite YAML files without losing comments, ordering,
or certain elements of formatting.
My aim with doing this is to open the door to automated editing of the
reference system definitions using the 'ruamel.yaml' library. This can
be used to implement automated migration when we want to make changes to
the YAML format that we use to represent Baserock system definitions.
Although this looks drastic, remember that it's actually only altered
65 out of 608 .morph files -- the vast majority already pass unchanged
through my version of ruamel.yaml.
Change-Id: I95ec978714b5bd1c02c90183336a9fbb846cb692
|
|
|
|
|
| |
The rules were being put in /lib/lib/udev/rules.d/ because
--with-udev-prefix is the path *containing* ./lib, not ./lib itself.
|
|
|
|
|
|
| |
We now install the necessary LVM systemd units and enable lvmetad
by default. Also, the udev rules are installed to the correct place
so that /dev is correctly populated.
|
|
The LVM tools are generally useful, so they should be available
separately from the huge 'virtualization' stratum.
|