Vratislav Podzimek
Vratislav Podzimek
This function is gross.
We should not have a 600+ lines long function. [1] [1] https://github.com/storaged-project/udisks/blob/master/src/udiskslinuxblock.c#L2870
There's the following rule in *data/80-udisks2.rules*: ``` # Zram devices setup KERNEL=="zram[0-9]", ENV{SYSTEMD_WANTS}="zram-setup@zram%n.service", TAG+="systemd" ``` and this is what the [email protected] does: ``` [Service] Type=oneshot RemainAfterExit=yes EnvironmentFile=-/usr/lib/zram.conf.d/%i-env ExecStart=-/bin/sh -c 'echo...
If a method that results in objects' properties being changed is called, the call finishes while the properties are still being updated by the ["udev feedback loop"](https://github.com/storaged-project/udisks/issues/572#issuecomment-421935724). So in some...
If the promise is being evaluated for the first time (no records in the locks LMDB), it doesn't make sense to check 'ifelapsed' for it.
Goals: - [x] fix potentially unaligned access to LMDB data in *cf-check* - [ ] add `--test-write` to `cf-check repair` - [ ] handle full LMDBs
Now that _libblockdev_ may use DBus for LVM instead of running binaries it may log DBus calls instead of information about spawning processes. Thus `external.log` is a more appropriate name...
For example in #350, new enum values are added. Which means ``BD_NVDIMM_NAMESPACE_MODE_UNKNOWN``, which should logically be last, now is a different integer value which is an ABI change. We should...
This is quite crucial in cases where there are two or more VGs with the same name. Like for example in the case addressed in https://github.com/storaged-project/blivet/pull/652
Instead of the ``dmsetup`` utility.