From owner-freebsd-current@FreeBSD.ORG  Tue Aug 31 02:14:56 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D8E9C16A4CE
	for <current@FreeBSD.org>; Tue, 31 Aug 2004 02:14:56 +0000 (GMT)
Received: from mail.gmx.net (mail.gmx.de [213.165.64.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id DD95843D41
	for <current@FreeBSD.org>; Tue, 31 Aug 2004 02:14:55 +0000 (GMT)
	(envelope-from lists@MHoerich.de)
Received: (qmail 15523 invoked by uid 0); 31 Aug 2004 02:14:54 -0000
Received: from 80.138.86.250 by www8.gmx.net with HTTP;
	Tue, 31 Aug 2004 04:14:54 +0200 (MEST)
Date: Tue, 31 Aug 2004 04:14:54 +0200 (MEST)
From: "Mario Hoerich" <lists@MHoerich.de>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
MIME-Version: 1.0
References: <Pine.BSF.4.53.0408291011481.80509@e0-0.zab2.int.zabbadoz.net>
X-Priority: 3 (Normal)
X-Authenticated: #5114400
Message-ID: <32047.1093918494@www8.gmx.net>
X-Mailer: WWW-Mail 1.6 (Global Message Exchange)
X-Flags: 0001
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
cc: current@FreeBSD.org
Subject: Re: [FIXED] Re: [5.3-B2] PPPoE broken?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Aug 2004 02:14:57 -0000

# Bjoern A. Zeeb:

[ http://docs.FreeBSD.org/cgi/mid.cgi?200408271833.i7RIX8fw068973 ]
> >
> > Manually applying the diffs and rebuilding world+kernel seems
> > to have fixed it. Great. Thanks for the really fast help. :)
> 
> this doesn't make much sense at all.
>
> Are you sure you had a complete and clean new RELENG_5
> world and kernel before ?

Hm. I think so. I can't claim to actually understand what the 
above commit does, but I didn't expect it to affect my system 
either. Rebuilding solved the problem however, so I just blamed
it on the diffs. ;)

Giving it some second thought, I recently read about -j4 being
considered safe for buildworlds. The failing world _was_ built
with that flag, but I'm quite sure I didn't specify it after
merging the diffs into my local source tree. I just didn't
suspect this to result in runtime errors, but I can't recall
anything else I might have varied.

Does that sound like a more probable cause to you?

Cheers,
Mario