From owner-freebsd-current@FreeBSD.ORG Sun May 11 21:39:01 2003 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 6521837B401 for ; Sun, 11 May 2003 21:39:01 -0700 (PDT) Received: from stargate.northwindcom.net (110-47-237-24.gci.net [24.237.47.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEAAC43FA3 for ; Sun, 11 May 2003 21:38:59 -0700 (PDT) (envelope-from lists@northwindcom.net) Received: from admin (admin.northwindcom.net [192.168.10.2]) by stargate.northwindcom.net (Postfix) with ESMTP id B15213628; Sun, 11 May 2003 20:38:58 -0800 (AKDT) From: "Beech Rintoul" To: "Gerhard Sittig" Date: Sun, 11 May 2003 20:38:48 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: <20030512000531.E26888@shell.gsinet.sittig.org> cc: freebsd-current@freebsd.org Subject: RE: Crossover Office on FreeBSD 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: Mon, 12 May 2003 04:39:01 -0000 -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org]On Behalf Of Gerhard Sittig Sent: Sunday, May 11, 2003 2:06 PM To: freebsd-current@freebsd.org Subject: Re: Crossover Office on FreeBSD On Sun, May 11, 2003 at 12:57 -0800, Beech Rintoul wrote: > > I'm attempting to get Crossover Office to install on 5.1 Beta, but the > script errors with the following: > > chown: 0.0: illegal user name > This installation doesn't support glibc-2.1 on FreeBSD / x86 > > I think it needs the 2.2 libs in /compat/linux, but I have no clue how to > point it there. There are two things to consider here: Is the second error ("doesn't support glibc...") separate from the first one ("illegal user name") or is the "user friendly" print out just the consequence of the failed chown(1) operation (due to a lack of a better classification)? IOW: Is the chown command meant to prepare or check the glibc support? The answer has quite dramatic an influence on the severeness of your problem. :) To catch and squish the first bug: For ages it has been (IIUC) the correct way to specify "user:group" to the chown command (watch the semicolon!). While the "user.group" syntax (with a dot) was supported merely for convenience or compatibility reasons. After a rather long notice the not necessarily legal second syntax was removed and is invalid now (it does not allow for dots in user names and makes the syntax ambigious in this scenario while being unpredictable is a behaviour you cannot accept from an essential system tool). Ask your software vendor to correct the installer (and/or correct it locally yourself and feed back the improvement to the vendor which raises the chance for being accepted and integrated). > Anyone have any suggestions on where to start on this? How do I get the > script to use the linux libs, etc... Codeweavers wasn't very helpful, told > me to install Linux! Do they ship their application with one? Do they support this base system or at least make sure that this combination will work? The problem with "Linux" is that there are so many flavours of it and some of the distributors cannot even handle version numbers correctly (do not label patched version as such or call totally mangled conglomerats(sp?) by their originals' names, which confuses both the users and the service personnel -- since it's hard when you don't know what is really inside from the look on the package/cover). You probably don't want to fight these problems, too, when you actually have some other things to do. Yes, I have seen office packages come with SuSE distros here. And one might assume that the two components cope well with each other when they come in one box from one source -- in contrast to simply having been thrown together by a salesman in the market. This bundling approach isn't even too sick when you simply want to setup an office workstation instead of installing an office suite to an already existing production system. Linux licensing makes the OS shipping even easier than it would be in the Windows world (imagine Windows applications bringing their suggested or required OS with them :] ). VMware can even be cheaper and more space efficient than a second machine. And it definitely is handier than a dual boot setup. But I still assume that you don't really have a library problem but a simple typo/braino (or Linuxism) in the install script. Thanks, I managed to get it installed with no errors using the shell in /compat/linux. However It won't run. When I start the configure utility it spins for a while and just exits with no errors. Since this uses wine as its base I tried installing the wine port and didn't get much farther. Wine seemed to configure ok, but trying to run a windows .exe results in the following: stargate# wine "c:\Program Files\setup.exe" fixme:cdrom:CDROM_GetIdeInterface not implemented for BSD fixme:reg:GetSystemInfo not yet supported on this system err:ntdll:RtlpWaitForCriticalSection section 0x5c0feddc "loader.c: loader_section" wait timed out, retrying (60 sec) tid=000a wine: Unhandled exception, starting debugger... err:ntdll:RtlpWaitForCriticalSection section 0x5c0feddc "loader.c: loader_section" wait timed out, retrying (60 sec) tid=000a err:seh:EXC_DefaultHandling Unhandled exception code c0000194 flags 0 addr 0x5c0c5254 Maybe someone with some wine experience can help me here. Beech