Am 03.08.2011 10:29, schrieb Michał Górny: > Hello, > > AFAIK NetworkManager is the most common tool which keeps writing > to /etc/resolv.conf file during runtime. Such a solution makes it hard > to support configurations where rootfs in read-only most of the time. > > That's why I'm considering moving the resolv.conf file to /var. I'm not > sure about the exact location there but /var seems much better for > non-static resolver configs. > > I think that the best solution would be to patch glibc so it will first > try to load 'dynamic' resolv.conf from /var, and then fallback to > static configs in /etc. > > I'd really appreciate any kind of feedback on that idea. > Hi, my first impression was, no way, this has always been this way :-) But then, this may be the exact reason to look at change. 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... Klaus -- ------------------------------------------------------------------------ Klaus Lichtenwalder, Dipl. Inform., http://www.lichtenwalder.name PGP Key fingerprint: BF52 72FA 1F5A 1E29 C0F8 498C C4C6 633C 2821 97DA
Attachment:
signature.asc
Description: OpenPGP digital signature