Hi Alkis,
On Mon, Apr 25, 2016 at 01:15:26PM +0300, Alkis Georgopoulos wrote:
> Unfortunately, testing showed that replacing:
> # Default-Start: S
> with:
> # Default-Start: 2 3 4 5
> doesn't solve the issue.
>
> One workaround is to change instead:
> # Required-Start: $network $local_fs
> with:
> # Required-Start: $local_fs
>
> This solves the ordering cycle by starting nbd-client a little later.
>
> Should we use that until a proper fix is committed?
> Does anyone have any better immediate workarounds?
...at risk of stating the obvious:
One workaround is to not combine NetworkManager and nbd-client on the
same system. If you're going to try to run an important filesystem (say,
the root filesystem) on something that lives somewhere on the network,
giving the user the ability to play with network connections at will
seems like a bad idea.
At any rate, the prerequisites for fixing this properly have now landed
in Debian, so a proper fix should be forthcoming soonishly :-)
--
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
people in the world who think they really understand all of its rules,
and pretty much all of them are just lying to themselves too.
-- #debian-devel, OFTC, 2016-02-12
