Ubuntu
ifupdown package

  1. Bug #497299
  2. Comment #61

Comment 61 for bug 497299

Revision history for this message
Alfredo Pironti (alfredo.pironti) wrote :

Maybe there's something I'm missing now. Why is the bug closed? On systems with "different" configurations than having `lo' in /etc/network/interfaces the bug is still present.

If such "different" configurations are wrong, then some policy should avoid the user making such changes to the file (e.g. /etc/sudoers shall be edited with visudo for this purpose)

To put it another way: if this package requires `lo' in /etc/network/interfaces, then it should check for it (or add it, or warn the user) before installing. Just blaming users on this thread for having wrong (or, better, *unexpected*) configurations doesn't solve the bug on itself.