freebsd-stable Digest, Vol 72, Issue 2
freebsd-sta...@freebsd.org
freebsd...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-sta...@freebsd.org
You can reach the person managing the list at
freebsd-st...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-stable digest..."
Today's Topics:
1. Re: buildworld fails at sbin/ifconfig (Michael C. Shultz)
2. Re: How to successfully mount /root if not in fstab?
(Charles Swiger)
3. Re: Looking for ntp/PPS setup guide (Jeff W. Boote)
4. [Fwd: PXEboot compile error (missing .h)] (D. Pageau)
5. Re: Looking for ntp/PPS setup guide (Kevin Oberman)
6. Re: buildworld fails at sbin/ifconfig (Ruslan Ermilov)
----------------------------------------------------------------------
Message: 1
Date: Mon, 2 Aug 2004 06:15:45 -0700
From: "Michael C. Shultz" <ring...@inbox.lv>
Subject: Re: buildworld fails at sbin/ifconfig
To: "jeev" <je...@charter.net>
Cc: freebsd...@freebsd.org
Message-ID: <200408020615....@inbox.lv>
Content-Type: text/plain; charset="utf-8"
On Friday 30 July 2004 10:13 am, you wrote:
> http://www.pasteme.com/paste/794?tx=on&submit=Format+it%21
hey did you ever fix that/ I’m having that problem on releng_4_10
j
cc -O -pipe -DUSE_IF_MEDIA -DINET6 -DUSE_VLANS -DUSE_IEEE80211 -DNS -Wall
-Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wnested-externs -I.. -c
ifconfig.c
ifconfig.c:244: `IFF_STATICARP' undeclared here (not in a function)
ifconfig.c:244: initializer element is not constant
ifconfig.c:244: (near initialization for `cmds[38].c_parameter')
ifconfig.c:245: `IFF_STATICARP' undeclared here (not in a function)
ifconfig.c:245: initializer element is not constant
ifconfig.c:245: (near initialization for `cmds[39].c_parameter')
*** Error code 1
Stop in /usr/src/sbin/ifconfig
Its been a while since I saw this.
the quick fix is to copy:
/usr/src/sys/net/if.h
over
/usr/include/net/if.h
If you want an explanation why this works just ask. FreeBSD folks turned down
my problem report for this although the problem stil exists.... :(
-Mike
------------------------------
Message: 2
Date: Mon, 2 Aug 2004 13:05:12 -0400
From: Charles Swiger <csw...@mac.com>
Subject: Re: How to successfully mount /root if not in fstab?
To: Joel Hatton <jo...@auscert.org.au>
Cc: freebsd...@freebsd.org
Message-ID: <1E281F2D-E4A6-11D8...@mac.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
On Aug 2, 2004, at 2:49 AM, Joel Hatton wrote:
> I've been caught out (twice now - yes, I was stupid enough to do this
> twice!) with mounting /root after removing a hard disk from my system
> and
> would like to know why it wasn't trivial to recover.
The system requires a working root account in order to be repairable in
single-user mode. One consequence of this is that /root needs to be on
the same partition as /, for much the same reasons that /bin or /etc
needs to be on /.
--
-Chuck
------------------------------
Message: 3
Date: Mon, 02 Aug 2004 13:52:32 -0600
From: "Jeff W. Boote" <bo...@internet2.edu>
Subject: Re: Looking for ntp/PPS setup guide
To: Kevin Oberman <obe...@es.net>
Cc: FreeBSD...@FreeBSD.org
Message-ID: <410E9B80...@internet2.edu>
Content-Type: text/plain; charset=us-ascii
Kevin Oberman wrote:
> The problem is that polling mode and PPS don't work properly together,
> so I have found that the TrueTime format provides the best results.
> ctime=off
> emul=truetime
> ctime=on
Specifically, If I remember correctly... the binary format used by the
palisades driver uses the same pin as PPS making them incompatible
(DCD?).
> I am still looking at the best choice for PPS setup...PPS_SYNC (flag3 1"
> or software PPL "flag3 1". Both do very well. I suspect that the absolute
PPL would be "flag3 0", right?
> time is closest with PPS_SYNC but the stability is often better with PLL
> discipline. If PLL proves the more stable, I will use a fudge of time1
> to correct for the offset. (In my last message bnl-owamp was running
> PPS_SYNC and the system I queries was running PLL. Note the 51
> microsecond offset. I don't know yet if that's real or an artifact of
> network delays.
That is an interesting idea. I have not tried that yet. I may try "flag3
0" on one or two of our systems and see if the stability improves. (We
have 11 of these in service at the moment... The places we have real
stability problems now is where we tend to loose CDMA service for
portions of a day.)
One thing we have noticed is that the TrueTime output seems to have a
fairly large offset relative to the PPS output of the device. (i.e. The
two outputs of the exact same device seem to have a non-trivial offset
from each other.) This causes a fair bit of instability. To compensate
for this, we have been using a fudge of time1 to correct the TrueTime
output. (11 msec's is what we have found works but I suspect this is PC
hardware and OS dependent.) I am not sure how much of this delay is due
to the polling nature of the TrueTime NTP driver verses the more event
driven PPS implementation in the kernel. To determine the 11 msec value,
we used the enable calibrate mode of NTP and waited for the offset to
stabilize for a couple of days.
(Another thing of note if you are using this EndRun device: Make sure
you set "flag2 1" for the PPS device. It is the "clear" of the PPS
signal that is synchronized.)
jeff
------------------------------
Message: 4
Date: Mon, 02 Aug 2004 16:49:39 -0400
From: "D. Pageau" <dpa...@infodev.ca>
Subject: [Fwd: PXEboot compile error (missing .h)]
To: sta...@freebsd.org
Message-ID: <410EA8E3...@infodev.ca>
Content-Type: text/plain; charset="us-ascii"
Still no answer. Is that off topic? Should I post somewhere else?
Thanks
*Repost*
-------------- next part --------------
An embedded message was scrubbed...
From: "D. Pageau" <dpa...@infodev.ca>
Subject: PXEboot compile error (missing .h)
Date: Fri, 30 Jul 2004 09:29:50 -0400
Size: 11361
Url: http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040802/11b876e4/PXEbootcompileerrormissing-0001.mht
------------------------------
Message: 5
Date: Mon, 02 Aug 2004 15:23:32 -0700
From: "Kevin Oberman" <obe...@es.net>
Subject: Re: Looking for ntp/PPS setup guide
To: "Jeff W. Boote" <bo...@internet2.edu>
Cc: FreeBSD...@FreeBSD.org
Message-ID: <200408022223...@ptavv.es.net>
> Date: Mon, 02 Aug 2004 13:52:32 -0600
> From: "Jeff W. Boote" <bo...@internet2.edu>
>
> Kevin Oberman wrote:
> > The problem is that polling mode and PPS don't work properly together,
> > so I have found that the TrueTime format provides the best results.
> > ctime=off
> > emul=truetime
> > ctime=on
>
> Specifically, If I remember correctly... the binary format used by the
> palisades driver uses the same pin as PPS making them incompatible
> (DCD?).
>
> > I am still looking at the best choice for PPS setup...PPS_SYNC (flag3 1"
> > or software PPL "flag3 1". Both do very well. I suspect that the absolute
>
> PPL would be "flag3 0", right?
Yes, PLL (I typed PPL about 5 or 6 times) would be "flag3 0". I am a
truly terrible typist and spell check does not catch these things.
> > time is closest with PPS_SYNC but the stability is often better with PLL
> > discipline. If PLL proves the more stable, I will use a fudge of time1
> > to correct for the offset. (In my last message bnl-owamp was running
> > PPS_SYNC and the system I queries was running PLL. Note the 51
> > microsecond offset. I don't know yet if that's real or an artifact of
> > network delays.
>
> That is an interesting idea. I have not tried that yet. I may try "flag3
> 0" on one or two of our systems and see if the stability improves. (We
> have 11 of these in service at the moment... The places we have real
> stability problems now is where we tend to loose CDMA service for
> portions of a day.)
>
> One thing we have noticed is that the TrueTime output seems to have a
> fairly large offset relative to the PPS output of the device. (i.e. The
> two outputs of the exact same device seem to have a non-trivial offset
> from each other.) This causes a fair bit of instability. To compensate
> for this, we have been using a fudge of time1 to correct the TrueTime
> output. (11 msec's is what we have found works but I suspect this is PC
> hardware and OS dependent.) I am not sure how much of this delay is due
> to the polling nature of the TrueTime NTP driver verses the more event
> driven PPS implementation in the kernel. To determine the 11 msec value,
> we used the enable calibrate mode of NTP and waited for the offset to
> stabilize for a couple of days.
I've been using 10 ms. on mine, but 11 may be better.
Time will tell which approach is better. Based on testing over the
weekend, I suspect that I will be switching back to PPS, but I'll let
things run a bit longer before making a final decision.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: obe...@es.net Phone: +1 510 486-8634
------------------------------
Message: 6
Date: Tue, 3 Aug 2004 09:53:12 +0300
From: Ruslan Ermilov <r...@FreeBSD.org>
Subject: Re: buildworld fails at sbin/ifconfig
To: "Michael C. Shultz" <ring...@inbox.lv>
Cc: jeev <je...@charter.net>
Message-ID: <20040803065...@ip.net.ua>
Content-Type: text/plain; charset="us-ascii"
On Mon, Aug 02, 2004 at 06:15:45AM -0700, Michael C. Shultz wrote:
> On Friday 30 July 2004 10:13 am, you wrote:
> > http://www.pasteme.com/paste/794?tx=on&submit=Format+it%21
> hey did you ever fix that/ I???m having that problem on releng_4_10
>
>
>
>
>
> j
>
> cc -O -pipe -DUSE_IF_MEDIA -DINET6 -DUSE_VLANS -DUSE_IEEE80211 -DNS -Wall
> -Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wnested-externs -I.. -c
> ifconfig.c
> ifconfig.c:244: `IFF_STATICARP' undeclared here (not in a function)
> ifconfig.c:244: initializer element is not constant
> ifconfig.c:244: (near initialization for `cmds[38].c_parameter')
> ifconfig.c:245: `IFF_STATICARP' undeclared here (not in a function)
> ifconfig.c:245: initializer element is not constant
> ifconfig.c:245: (near initialization for `cmds[39].c_parameter')
> *** Error code 1
>
> Stop in /usr/src/sbin/ifconfig
>
> Its been a while since I saw this.
> the quick fix is to copy:
>
> /usr/src/sys/net/if.h
>
> over
>
> /usr/include/net/if.h
>
> If you want an explanation why this works just ask. FreeBSD folks turned down
> my problem report for this although the problem stil exists.... :(
>
>
/usr/include isn't used at all in the main build stage of buildworld.
Is it possible that you just ran ``make'' rather than the supposed
``make buildworld'' from under /usr/src?
Also, what is the PR number you're referring to?
Cheers,
--
Ruslan Ermilov
r...@FreeBSD.org
FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040803/4b1b7781/attachment-0001.bin
------------------------------
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
End of freebsd-stable Digest, Vol 72, Issue 2
*********************************************