Actual probs with 'ipfw'

2002-10-26 Thread Matthias Schuendehuette
Hi,

I updated my kernel now just like told in the last HEADSUP and hesitate 
to do a 'make installworld' as also mentioned there...

Now, during boot 'ipfw' complaines:

ipfw: size mismatch (have 64 want 1064)
ipfw: size mismatch (have 52 want 40)
ipfw: size mismatch (have 52 want 40)

This happens every time I run 'sh /etc/rc.firewall open'. Not to 
mention, that the firewall is closed perfectly :-/.

I didn't run 'mergemaster' because of no installworld. Is that the 
problem?
-- 
Ciao/BSD - Matthias

Matthias Schuendehuette msch [at] snafu.de, Berlin (Germany)
Powered by FreeBSD 5.0-CURRENT


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Actual probs with 'ipfw'

2002-10-26 Thread Maxime Henrion
Matthias Schuendehuette wrote:
 Hi,
 
 I updated my kernel now just like told in the last HEADSUP and hesitate 
 to do a 'make installworld' as also mentioned there...
 
 Now, during boot 'ipfw' complaines:
 
 ipfw: size mismatch (have 64 want 1064)
 ipfw: size mismatch (have 52 want 40)
 ipfw: size mismatch (have 52 want 40)
 
 This happens every time I run 'sh /etc/rc.firewall open'. Not to 
 mention, that the firewall is closed perfectly :-/.
 
 I didn't run 'mergemaster' because of no installworld. Is that the 
 problem?

No, the problem is that you need to installworld to have an updated
ipfw(8) binary.

Cheers,
Maxime

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Actual probs with 'ipfw'

2002-10-26 Thread Matthias Schuendehuette
On Saturday 26 October 2002 21:48, you wrote:

 No, the problem is that you need to installworld to have an updated
 ipfw(8) binary.

Confirmed! Thanks a lot!

PS: So the HEADSUP-strategy has its limitations... ;-)
-- 
Ciao/BSD - Matthias

Matthias Schuendehuette msch [at] snafu.de, Berlin (Germany)
Powered by FreeBSD 4.7-STABLE


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Actual probs with 'ipfw'

2002-10-26 Thread Bernd Walter
On Sat, Oct 26, 2002 at 10:04:44PM +0200, Matthias Schuendehuette wrote:
 On Saturday 26 October 2002 21:48, you wrote:
 
  No, the problem is that you need to installworld to have an updated
  ipfw(8) binary.
 
 Confirmed! Thanks a lot!
 
 PS: So the HEADSUP-strategy has its limitations... ;-)

You did not reboot to single user mode to installworld.
No need to run ipfw with the new kernel before installworld.
-current readers are expected to know that.

-- 
B.Walter  COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED] Usergroup   [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Actual probs with 'ipfw'

2002-10-26 Thread Matthias Schuendehuette
On Saturday 26 October 2002 22:17, you wrote:
 You did not reboot to single user mode to installworld.
 No need to run ipfw with the new kernel before installworld.
 -current readers are expected to know that.

Right!

What I meant was:
For this reason, you probably want to delay an installworld until you 
are comfortable that your newer kernel builds are satisfactory.
from: Message-ID:  [EMAIL PROTECTED]

But my new kernel build *is* satisfactory now :-)
-- 
Ciao/BSD - Matthias

Matthias Schuendehuette msch [at] snafu.de, Berlin (Germany)
Powered by FreeBSD 4.7-STABLE


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Actual probs with 'ipfw'

2002-10-26 Thread Juli Mallett
* De: Matthias Schuendehuette [EMAIL PROTECTED] [ Data: 2002-10-26 ]
[ Subjecte: Re: Actual probs with 'ipfw' ]
 On Saturday 26 October 2002 22:17, you wrote:
  You did not reboot to single user mode to installworld.
  No need to run ipfw with the new kernel before installworld.
  -current readers are expected to know that.
 
 Right!
 
 What I meant was:
 For this reason, you probably want to delay an installworld until you 
 are comfortable that your newer kernel builds are satisfactory.
 from: Message-ID:  [EMAIL PROTECTED]
 
 But my new kernel build *is* satisfactory now :-)

I think he was referring to a kernel built with dateof(his-patches)-1
sources, rather than much older ones.  There are more obvious version/ABI
skew issues once one updates from so long ago.

juli.
-- 
Juli Mallett [EMAIL PROTECTED]   | FreeBSD: The Power To Serve
Will break world for fulltime employment. | finger [EMAIL PROTECTED]
http://people.FreeBSD.org/~jmallett/  | Support my FreeBSD hacking!

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message