Re: Upgrading to 5.3

On 2005-02-18 Andrew L. Gould wrote: On Thursday 17 February 2005 11:18 pm, Joachim Dagerot wrote: >> I just cvsuped to freebsd-stable and buildworld. No problems. >> >> Now I want to build the kernel with the same conf as I used for the >> last years (5.x), but I ran into problems. device "p

Re: Upgrading to 5.3

On Thursday 17 February 2005 11:18 pm, Joachim Dagerot wrote: > I just cvsuped to freebsd-stable and buildworld. No problems. > > Now I want to build the kernel with the same conf as I used for the > last years (5.x), but I ran into problems. device "pcm" is unknown. > > Is this a 'common' problem,

Upgrading to 5.3

I just cvsuped to freebsd-stable and buildworld. No problems. Now I want to build the kernel with the same conf as I used for the last years (5.x), but I ran into problems. device "pcm" is unknown. Is this a 'common' problem, or am I in deep sh*t? //Joche

Re: ntpd problems since upgrading to 5.3 - found the problem!

On Sat, 22 Jan 2005 02:32, Lowell Gilbert wrote: > Ian Moore <[EMAIL PROTECTED]> writes: > > On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote: > > > Ian Moore <[EMAIL PROTECTED]> writes: > > > > I've just realised I'm not running a name server at all on my 5.3 > > > > system. I have 4.9 installed on

Re: ntpd problems since upgrading to 5.3 - found the problem!

Ian Moore <[EMAIL PROTECTED]> writes: > On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote: > > Ian Moore <[EMAIL PROTECTED]> writes: > > > I've just realised I'm not running a name server at all on my 5.3 system. > > > I have 4.9 installed on this computer too & I'd set up the caching server > > > o

Re: ntpd problems since upgrading to 5.3 - found the problem!

On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote: > Ian Moore <[EMAIL PROTECTED]> writes: > > I've just realised I'm not running a name server at all on my 5.3 system. > > I have 4.9 installed on this computer too & I'd set up the caching server > > on it, I guess I forgot that step when I installed

Re: ntpd problems since upgrading to 5.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 January 2005 23:14, John wrote: > On Tue, Jan 18, 2005 at 04:04:30PM -0600, John wrote: > > On Tue, Jan 18, 2005 at 07:23:41AM -0600, John wrote: > > > On Tue, Jan 18, 2005 at 07:26:16AM +0100, Christian Hiris wrote: > > > > -BEGIN PG

Re: ntpd problems since upgrading to 5.3

On Tue, Jan 18, 2005 at 04:04:30PM -0600, John wrote: > On Tue, Jan 18, 2005 at 07:23:41AM -0600, John wrote: > > On Tue, Jan 18, 2005 at 07:26:16AM +0100, Christian Hiris wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA1 > > > > > > On Tuesday 18 January 2005 01:09, John wrote: > >

Re: ntpd problems since upgrading to 5.3

On Tue, Jan 18, 2005 at 07:23:41AM -0600, John wrote: > On Tue, Jan 18, 2005 at 07:26:16AM +0100, Christian Hiris wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On Tuesday 18 January 2005 01:09, John wrote: > > > > > This is what goes into the log: > > > Jan 17 18:04:29 pear

Re: ntpd problems since upgrading to 5.3 - found the problem!

Ian Moore <[EMAIL PROTECTED]> writes: > I've just realised I'm not running a name server at all on my 5.3 system. I > have 4.9 installed on this computer too & I'd set up the caching server on > it, I guess I forgot that step when I installed 5.3. > I'll set it up & see that makes any difference

Re: ntpd problems since upgrading to 5.3

On Tue, Jan 18, 2005 at 07:26:16AM +0100, Christian Hiris wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tuesday 18 January 2005 01:09, John wrote: > > > This is what goes into the log: > > Jan 17 18:04:29 pearl ntpd[838]: ntpd 4.2.0-a Sun Jan 9 10:58:59 CST 2005 > > (1) Jan 17

Re: ntpd problems since upgrading to 5.3 - found the problem!

On Tue, 18 Jan 2005 17:13, Christian Hiris wrote: > On Tuesday 18 January 2005 07:19, Ian Moore wrote: > > Now I'm not sure what the best way to get around this would be. I run a > > caching name server on the machine, so I guess I can tweak it to force > > localhost.foo.com resolve to 127.0.0.1 >

Re: ntpd problems since upgrading to 5.3 - found the problem!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 January 2005 07:19, Ian Moore wrote: > > Now I'm not sure what the best way to get around this would be. I run a > caching name server on the machine, so I guess I can tweak it to force > localhost.foo.com resolve to 127.0.0.1 I'm runnin

Re: ntpd problems since upgrading to 5.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 January 2005 01:09, John wrote: > This is what goes into the log: > Jan 17 18:04:29 pearl ntpd[838]: ntpd 4.2.0-a Sun Jan 9 10:58:59 CST 2005 > (1) Jan 17 18:04:29 pearl ntpd[838]: bind() fd 7, family 2, port 123, addr > 0.0.0.0,in_clas

Re: ntpd problems since upgrading to 5.3 - found the problem!

On Tue, 18 Jan 2005 12:50, Christian Hiris wrote: > On Tuesday 18 January 2005 01:09, John wrote: > > On Mon, Jan 17, 2005 at 12:49:00PM -0600, John wrote: > > > On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote: > > > > On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote: > > > > > Ian Moore wr

Re: ntpd problems since upgrading to 5.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 January 2005 05:23, Rob wrote: > Christian Hiris wrote: > > On the server ntp.matrix.net I run ntpd with the following config files > > (This machine still runs 5.3-BETA-4): > > > > # cat /etc/rc.conf | grep ntp > > ntpdate_flags="-b cloc

Re: ntpd problems since upgrading to 5.3

Christian Hiris wrote: On the server ntp.matrix.net I run ntpd with the following config files (This machine still runs 5.3-BETA-4): # cat /etc/rc.conf | grep ntp ntpdate_flags="-b clock.netcetera.dk tick.keso.fi" ntpdate_enable="YES" ntpd_enable="YES" - - No need for "ntpdate -b"

Re: ntpd problems since upgrading to 5.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 January 2005 01:09, John wrote: > On Mon, Jan 17, 2005 at 12:49:00PM -0600, John wrote: > > On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote: > > > On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote: > > > > Ian Moore wrote: > > > >

Re: ntpd problems since upgrading to 5.3

On Mon, Jan 17, 2005 at 12:49:00PM -0600, John wrote: > On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote: > > On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote: > > > Ian Moore wrote: > > > > Hi, > > > > Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been > > > > getting the

Re: ntpd problems since upgrading to 5.3

On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote: > On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote: > > Ian Moore wrote: > > > Hi, > > > Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been > > > getting the > > > following error on boot: > > > ntpd[380]: bind() fd 7, famil

Re: ntpd problems since upgrading to 5.3

On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote: > Ian Moore wrote: > > Hi, > > Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been getting > > the > > following error on boot: > > ntpd[380]: bind() fd 7, family 28, port 123, addr fe80:1 > > ::204:61ff:fe46:be89, in6_is_addr_mu

Re: ntpd problems since upgrading to 5.3

Ian Moore wrote: Hi, Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been getting the following error on boot: ntpd[380]: bind() fd 7, family 28, port 123, addr fe80:1 ::204:61ff:fe46:be89, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address ntpd seems to be worki

ntpd problems since upgrading to 5.3

Hi, Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been getting the following error on boot: ntpd[380]: bind() fd 7, family 28, port 123, addr fe80:1 ::204:61ff:fe46:be89, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address ntpd seems to be working from what I ca

Re: upgrading to 5.3-Beta7 problem

Benzi Mizrahi <[EMAIL PROTECTED]> writes: > Hi, > > I am in a middle of upgrading to Beta7 (from 5.3-beta5) > I builtworld builtkernel did installkernel > rebooted as single user did mergemaster. > Now I am having a working 5.3-beta7. > I did make installworld and it stopped in a middle,