From owner-freebsd-current@FreeBSD.ORG Sat Mar 5 04:03:01 2005 Return-Path: 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 85F1F16A4CE for ; Sat, 5 Mar 2005 04:03:01 +0000 (GMT) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5329B43D46 for ; Sat, 5 Mar 2005 04:03:01 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) (192.168.1.2) by mail.ambrisko.com with ESMTP; 04 Mar 2005 20:03:01 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.11/8.12.9) with ESMTP id j25431Z9031187; Fri, 4 Mar 2005 20:03:01 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.11/8.12.11/Submit) id j2542IMn031147; Fri, 4 Mar 2005 20:02:18 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200503050402.j2542IMn031147@ambrisko.com> In-Reply-To: <20050305011256.GA1258@NitroPhys.welchsmnet.net> To: Sean_Welch@alum.wofford.org Date: Fri, 4 Mar 2005 20:02:18 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: fixing Vmware 2 port for 5.x and 6.x.. kmem _alloc_pageable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2005 04:03:01 -0000 Sean Welch writes: | On Fri, Mar 04, 2005 at 04:58:20PM -0800, Doug Ambrisko wrote: | > Skip the extra bits and just go for the code. | > make update | > cp vmware.orig | > ./update | > | > Then it should be good to go. | | Thanks for the advice but it is still a no go... | | # ./update /usr/local/lib/vmware/bin/vmware | File mame missing! | | Not sure what is causing this. I'm using version 89 of the patch. They might have changed things. Look at the source to find out. Doug A.