HAL update, OM2008.8

roguemoko at roguewrt.org roguemoko at roguewrt.org
Mon Sep 1 06:23:31 CEST 2008


Nishit Dave wrote:
> On Sat, Aug 30, 2008 at 1:06 PM, Matt <matt.joyce at gmail.com 
> <mailto:matt.joyce at gmail.com>> wrote:
> > Nishit Dave wrote:
> >> Hi,
> >>
> >> The current upgrade of hal from 0.5.9-r6 to 0.5.11-r0 today through
> >> the official repository led to the following exit message (relating to
> >> haldaemon):
> >> Cannot create link over existing -/etc/resolv.conf-.
> >> which would be the case because of the earlier resolvconf problem
> >> being solved manually by creating a real /etc/resolv.conf file.  Now,
> >> should that file be replaced again with a link, and how?
> >>
> >>
> >
> > Move resolv.conf to /var/run/resolv.conf and then link /etc/resolv.conf
> > to it.
> > maybe.
> >
> Found an update on the wiki:
> http://wiki.openmoko.org/wiki/Om_2008.8#Known_Issues
>
>     NOTE: Solusion: Steps to add missing scripts:
>
>     touch /etc/resolvconf/run/enable-updates
>     cd /etc ; rm resolv.conf ; ln -s /etc/resolvconf/run/resolv.conf .
>     mkdir /lib/resolvconf/ ; cd /lib/resolvconf/
>     wget http://kopparv34.mine.nu/list-records
>     Edit /etc/network/interfaces and remove the lines:
>     network 192.168.0.0 <http://192.168.0.0>
>     gateway 192.168.0.200 <http://192.168.0.200>
>     If we need to use the usb network more then just locally from the
>     computer in the other end of the USB-cable, login with ssh and add
>     a default route like this:
>     route add default gateway 192.168.0.200 <http://192.168.0.200>
>
>
> I haven't tried it so far.

That's looking pretty ugly. The way I see it, everything should be 
querying /etc/resolv.conf as per standard with /etc/resolv.conf 
symlinked to volatile so that you're not continually writing to flash.

Anything else just looks ugly and would require some awareness that does 
not exist.

 From what I can tell, this is how it should work. Why other core 
packages are breaking this convention I have no idea. It seems there is 
merely a communication breakdown between devs when it comes to dns 
resolving.

Sarton




More information about the community mailing list