From owner-freebsd-stable Tue Dec 18 5: 7:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cache1.hck.carroll.com (cache1.hck.carroll.com [216.44.20.19]) by hub.freebsd.org (Postfix) with ESMTP id 0CE4537B420 for ; Tue, 18 Dec 2001 05:07:29 -0800 (PST) Received: from [216.44.20.5] (HELO carroll.com) by cache1.hck.carroll.com (CommuniGate Pro SMTP 3.2.4) with ESMTP id 7297845 for freebsd-stable@freebsd.org; Tue, 18 Dec 2001 08:07:27 -0500 Received: by carroll.com (CommuniGate Pro PIPE 3.4.6) with PIPE id 1310062; Mon, 17 Dec 2001 14:14:53 -0500 From: damien@carroll.com Received: by carroll.com (CommuniGate Pro PIPE 3.4.6) with PIPE id 1310057; Mon, 17 Dec 2001 14:14:43 -0500 Received: from 50.dhcp.hck.carroll.com ([10.64.0.218] verified) by carroll.com (CommuniGate Pro SMTP 3.4.6) with ESMTP id 1310054; Mon, 17 Dec 2001 14:14:35 -0500 Date: Mon, 17 Dec 2001 14:14:35 -0500 To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Linux compatibility broken in latest 4.4-STABLE? Message-ID: <167570000.1008616475@50.dhcp.hck.carroll.com> X-Mailer: Mulberry/2.1.2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-CNVscan: Virus Scanned by Carroll-Net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, We have found that the Linux version of the Citrix client no longer runs when we upgrade to the latest version of 4.4-STABLE. When we try to connect to a server, the Citrix client displays the following error in an X window: 29: Invalid serial number and also displays the following to stderr: SIOCGIFFLAGS: Invalid argument This problem does not happen in 4.4-RELEASE, or earlier versions of 4.4-STABLE, but happens on every machine that we upgrade to the latest STABLE. We have also tried installing the latest linux-base7, but still had the same errors. Does anyone have any ideas what might be causing this and if there are any kernel settings that I could try using to resolve the problem? Thanks for your help. --- Damien Tougas Systems Administrator Carroll-Net, Inc. http://www.carroll.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message