Bug#985255: Systemd initiates fsckd for no apparent reason
biebl at debian.org
Tue Mar 16 10:41:36 GMT 2021
Am 16.03.21 um 11:37 schrieb Michael Biebl:
> As you can see, the kernel switched the ordering of sdb with sdd.
> Hardware probing is no longer asynchronous, so you can't rely on
Sorry, this was confusing. I meant:
Hardware probing by the kernel is nowadays asynchronous. So you can't
rely on the kernel provided names.
The same is btw true as well for ethernet devices. If you have multiple
ones, you can't rely on eth0, eth1 names being stable. They can be
assigned randomly during boot.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 840 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers