Writable filesystem in my cases is required only by at/batch, as we have determined. But who knows what configurations could other people have. Certainly, if the interface config has 'up' options with any commands, this should be an indication that it is not to be brought up from udev. Or may be provide an option for the interface config, named like 'noudev', to prevent this explicitly by hand.
Potential resolvconf bug is dependent on these integration chains : chain1 : udev is started at S03, udev runs ifupdown, ifupdown runs resolvconf for dns-* options, resolvconf expects its rundir to be initialized (rm everything, mkdir interface, etc) chain2 : resolvconf rundir is initialized only at S07 . So earlier runs of resolvconf fail due to missing interface dir So, resolvconf rundir initialization should happen before its first run, i.e. before starting udev to be sure. Btw, there is nice bug 340071, just about the opposite matter. It seems the proper order of resolvconf initialization still has to be determined. re: /var/run, I was really wrong and now I have checked by myself that tmpfs /var/run is not cleaned really, so that's not a question now. Network Manager is useful on the desktop, but I have a number of GUI- less servers and routers migrated from Debian to Ubuntu, with advanced enough configuration in interfaces(5) for proper operation of ifupdown and all its integration chains to really matter for me. I don't use NFS much enough, saving aside for diskless booting, so I could not say anything significant on this topic. Hope, ifupdown or resolvconf could be reformed to satisfy user's needs in both ways. -- ifupdown-udev integration should be thought-out more thoroghly https://bugs.launchpad.net/bugs/366967 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
