After freebsd-update - all went wrong.

[Marwan Sultan]

Dear Poly,

 

  /etc/resolv.conf and /etc/hosts and /etc/rc.conf

  are untouched.

 

  The only problem that freebsd ignores the "defaultrouter" line in /etc/rc.conf

  and just for the archives, kernel has been restored to default,

  but i have recompiled my kernel and its okay.

 

  I will today use the ordiary freebsd update (csup) and see if this will fix what

  freebsd-update broke- and will update this list.

 

  This is a lesson for me and everyone to never run freebsd-update on a custom kernel

  system, however It shouldnot produce such problem. (i think)

 

 Thank you

 

- Marwan Sultan

  System Administrator
 
> Date: Thu, 24 Dec 2009 15:35:44 +0100
> From: freebsd at edvax.de
> To: dead_line at hotmail.com
> CC: freebsd-questions at freebsd.org
> Subject: Re: After freebsd-update - all went wrong.
> 
> On Thu, 24 Dec 2009 14:06:48 +0000, Marwan Sultan <dead_line at hotmail.com> wrote:
> > well, I have fixed problem two by installing back my custom kernel.
> > but the system still ignores the "defaultroute" command in rc.conf
> > this is why we have manuly added to the rc.local
> 
> Is this possibly a spelling error? The setting in rc.conf
> is defaultrouter="..." - routeR.
> 
> 
> 
> > But eventho it shouldnot touch rc.conf right?
> 
> Correct. The rc.conf file is one of the few ones that
> shouldn't be in the scope of freebsd-update or mergemaster
> (if you update by source).
> 
> 
> > my rc.local now has
> > 
> > route add default 66.xx.x.x
> > ifconfig em0 66.xx.x.x netmask 255.255.255.255 alias
> 
> 
> 
> > If i take it off, system will not have any defaultroute
> > anymore although its in rc.conf
> > 
> > defaultrouter="66.xx.x.x"
> > hostname="xxxxxx.com"
> > ifconfig_em0="inet 66.xx.x.x netmask 255.255.255.0"
> 
> Your setting in rc.conf is spelled correctly (see above).
> 
> Could you try what happens if you start the inet subsystem
> manually (/etc/rc.d/netif and /etc/rc.d/routing)? The
> last one reads defaultrouter="..." from rc.conf.
> 
> As far as I see, the settings in rc.conf are completely
> valid, and should work. If this is still the "old" rc.conf
> (that worked before), the services activated in there
> should be started, too...
> 
> You could additionally check /etc/resolv.conf and /etc/hosts
> for any malformed entries. I think /etc/hosts could be
> altered / overwritten by freebsd-update?
> 
> 
> 
> 
> -- 
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
 		 	   		  
_________________________________________________________________
Hotmail: Powerful Free email with security by Microsoft.
http://clk.atdmt.com/GBL/go/171222986/direct/01/