From owner-freebsd-questions@FreeBSD.ORG Wed Dec 29 05:05:57 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEF4616A4CE for ; Wed, 29 Dec 2004 05:05:56 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63B6343D1F for ; Wed, 29 Dec 2004 05:05:56 +0000 (GMT) (envelope-from matthew.bluestone@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so790281wri for ; Tue, 28 Dec 2004 21:05:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=erhT/7qoyj/6pgQIoRagDp3pOvAbhlSM4XGSVs3Gc61lslqyF/9NAX5F/ZZQynyXGKSM+fSwPM8+qD1o4TSjz8GXKfPcPr0nRzf4zPFy4kt6lp0jZrVhZjRoNalIkd1up9mN1VS0uqHTwjTnQq/Fyt642pHQEWFCRo54vWVe/+g= Received: by 10.54.44.34 with SMTP id r34mr2747wrr; Tue, 28 Dec 2004 21:05:55 -0800 (PST) Received: by 10.54.2.47 with HTTP; Tue, 28 Dec 2004 21:05:55 -0800 (PST) Message-ID: <4e25c614041228210575ad60d2@mail.gmail.com> Date: Wed, 29 Dec 2004 00:05:55 -0500 From: Matthew Bluestone To: freebsd-questions@freebsd.org In-Reply-To: <1104293515l.4925l.0l@BARTON> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <4e25c614041226201361b1a781@mail.gmail.com> <1104124638l.25420l.0l@BARTON> <4e25c6140412280115641d2a3d@mail.gmail.com> <1104293515l.4925l.0l@BARTON> Subject: Re: Wine 20041201 on FreeBSD 5.3-RELEASE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Matthew Bluestone List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 05:05:57 -0000 (I apologize for replying to jason henson rather than the list; either his reply-to was set individually, gmail doesn't correctly respect reply-to (though it seems to in other cases), or I made an error.) Some of my response to jason and his later reply are included. > > (I didn't think that was so clear from the page.) I applied the > > patch, rebuilt, and installed my kernel, and I continue to get the > > same error. [snip] > > # patch > and got normal-looking messages about discarding junk headers and > > footers and applying patches in two spots. I checked the source file > > /usr/src/sys/vm/vm_mmap.c and found the appropriate sections updated. > > I had also edited a custom kernel config file in preparation for > > building a custom kernel anyway, and I did > > # cd /usr/src > > # make buildkernel KERNCONF=MYKERNELNAME > > # make installkernel KERNCONF=MYKERNELNAME > > (substituting the appropriate name, of course). > > The commands finished successfully, and I rebooted and got a > > functioning system without a hitch. > Looks like you did the right patch command. [snip] > Ok, first Kris responded to the thread with "It also clearly states (in > the followup) that the kernel patch is no longer needed." > > Sounds like what Kris was saying was you just needed to cvsup your > ports system and not do the patch anymore. > > "The wine-mmap.patch is no longer needed since that code has been > #ifdef'd=20 out in the wine CVS." > > So you could just rm vm_mmap.c and cvsup your source then update your > system and kernel. Depending on hold old your release is you should > read UPDATING very carefully. As I said in my original post, my ports tree was updated the day before I tried all that (which is well after the bug is listed as being closed). Since I have apparently the latest port of wine and have tried both with and without the kernel patch, I'm at a loss. I thought this may be an issue with common enough components that somebody on this list might have encountered and solved the same problem. I figured that maybe I had misunderstood about the kernel patch no longer being needed; maybe it was merged into CURRENT, but I'd have to do it myself with my 5.3-RELEASE system. Incidentally, if I should *undo* this patch (I'm not a kernel hacker; it intuitively seems that messing with the virtual memory manager, esp. w/ code marked "this is messy; somebody who knows what he's doing should fix it", could be a bad idea), I'd appreciate somebody's letting me know. > Try emailing gerald@FreeBSD.org, he's the port maintainer for wine. I will also email gerald directly. Thank you.