[Voyage-linux] dynamic nameserver problem
Kim-man 'Punky' TSE
(spam-protected)
Tue May 4 10:15:49 HKT 2010
Hi Clemens,
resolvconf introduced in 0.6.5 is used to solve this late . I am not
expecting it does not work. At boot before setting network, there
should be a message:
===================================
Reconfiguring resolvconf.
mkdir: created directory `/lib/init/rw/resolvconf'
mkdir: created directory `/lib/init/rw/resolvconf/interface'
Copying /ro to /rw.
Voyage is now setting up tmpfs for changed files...
tmpfs: mount back /lib/init/rw/var/log to /var/log
tmpfs: mount back /lib/init/rw/var/tmp to /var/tmp
Done.
Setting up resolvconf...done.
===================================
If you see these lines this means resolve.conf is kept as in
/etc/resolvconf/run and is symlink to /lib/init/rw/resolvconf, which is
writable.
BTW, /etc/resolv.conf is also be symlink to
/etc/resolvconf/run/resolv.conf as well, that I don't see why it is not
writable. May be you have different environment than me. Otherwise,
please check /etc/init.d/voyage-sync that enable resolvconf part.
- Punky
On 5/3/2010 7:32 PM, Clemens Grünberger wrote:
> On the other hand disabling resolvconf and manually putting in 2
> nameservers in resolv.conf works (remountrw-edit-remountro), but I'd
> rather not rely on the continuous availability of my chosen nameservers.
> I want to use these machines as remote nodes, so I cannot rely on
> fixing nameservers by hand.
>
> Any suggestions how to do this in a neat way? (Some symlinking to /tmp?,
> or should I just mount the fs as read-write every time I make the
--
Regards,
Punky
Voyage Solutions (http://solution.voyage.hk)
* Embedded Solutions and Systems
- Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
- Network Engineering, Development Platform and Consultation
More information about the Voyage-linux
mailing list