From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 17 Feb 2002 21:32:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 17 Feb 2002 21:32:44 -0500 Received: from smtp.cogeco.net ([216.221.81.25]:53449 "EHLO fep1.cogeco.net") by vger.kernel.org with ESMTP id ; Sun, 17 Feb 2002 21:32:34 -0500 Subject: Non-root IPX From: "Nix N. Nix" To: acme@conectiva.com.br Cc: linux-kernel@vger.kernel.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 17 Feb 2002 21:32:26 -0500 Message-Id: <1013999547.19674.1.camel@tux> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org This might be a dupe - sorry. >>From Transgaming (makers of WineX): > The problem is not WineX, it's the Linux kernel, it only allows root > to create IPX sockets. Probably something to do with security, but I > don't know what. Is this true ? If so, what can I do to allow regular users to make IPX sockets ? Is that a wise thing to do ? I'm interested in running a Windows game (Starcraft) as a normal user. WineX has gotten to the point where that is possible, minus IPX. Thanks for your help.