IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
In a future version of libvolume_id, struct volume_id will be
an opaque data type, which can't be accessed directly.
No interface has changed for now, until all known users are
converted not to access the structure directly.
We see sequences like:
UEVENT[1176966403.907336] add@/block/dasda
UDEV [1176966403.920359] add@/block/dasda
UEVENT[1176966403.964379] add@/block/dasda/dasda1
UEVENT[1176966403.964438] add@/block/dasda/dasda2
UEVENT[1176966403.964483] online@/block/dasda
UEVENT[1176966403.964519] online@/block/dasda/dasda1
UEVENT[1176966403.964555] online@/block/dasda/dasda2
UDEV [1176966403.967413] add@/block/dasda/dasda1
UDEV [1176966403.968719] add@/block/dasda/dasda2
UDEV [1176966403.974750] online@/block/dasda/dasda1
UDEV [1176966403.982241] online@/block/dasda/dasda2
UDEV [1176966403.999847] online@/block/dasda
where the event for the disk (last event) should come before the
events for the partitons. We skipped events for dependency reasons,
but the dependency check for later events did not see the skipped
events.