I just tried to install nbd-server and nbd-client in unstable when dependency based boot sequencing was enabled, and it failed to install because of the dependency loop. Further testing demonstrated that it is only nbd-client that have the loop problem. nbd-server installs just fine.
insserv now report a bit more information about the loop, claiming it involves networking->nbd-client->umountfs. This make me believe that this is a fake loop, only present when both the start and stop dependencies are taken into account. In the latest version of insserv I implemented support in check-initd-order to draw the combined dependency graph for both start and stop dependencies. Use -g -c to extract it in dotty format. Anyway, just wanted to let you know that this issue is a fatal problem when trying to use nbd-client on a machine with dependency based boot system is enabled. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
