Does upstream know about this issue? What would be the real fix to solve this timing problem?
Are there commands, such as: - 'kpartx --wait-until-ready' that waits as long as required or, - 'kpartx --is-ready' that exits 0 or 1 accordingly. Or would implementing those up to 'kpartx' or another project? Cheers, Patrick -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
