On Wed, Aug 3, 2011 at 11:12 AM, Klaus Lichtenwalder <[email protected]> wrote: > Am 03.08.2011 20:07, schrieb Michał Górny: >> On Wed, 03 Aug 2011 20:01:15 +0200 >> Klaus Lichtenwalder <[email protected]> wrote: > [...] >>> And your and other peoples reasons are more than valid. So, I think >>> the most nonintrusive way would be to have a symbolic link to probably >>> /var/run/resolv.conf, which would also work if the file isn't there... >>> It could belong to a group with members that are allowed to write >>> there. Dhcp, MM, ppp probably... >> >> As I mentioned earlier, symlink is no solution but a workaround >> introducing further breakage possibilities. Most importantly it won't >> allow you to have fallback /etc/resolv.conf. And the symlink will be >> invalid if one uses separate /var and /var hasn't been mounted yet. > > Yeah, I've been posting too early for your argument, and you're right. I > don't think /var not being mounted will be a problem (haven't thought it > through, though), because that's so early in the boot process that name > resolution might not yet be a problem. (Network probably isn't up either).
This is exactly what /run was created for, so why not call it /run/resolv.conf instead of /var/run and avoid that problem entirely? _______________________________________________ networkmanager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
