From owner-freebsd-hackers Sat May 15 16:25:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.physics.purdue.edu (galileo.physics.purdue.edu [128.210.67.225]) by hub.freebsd.org (Postfix) with ESMTP id C6BA914D3D for ; Sat, 15 May 1999 16:25:54 -0700 (PDT) (envelope-from jonsmith@physics.purdue.edu) Received: from localhost (jonsmith@localhost) by galileo.physics.purdue.edu (8.9.2/8.9.2) with ESMTP id SAA35910; Sat, 15 May 1999 18:25:51 -0500 (EST) (envelope-from jonsmith@galileo.physics.purdue.edu) Date: Sat, 15 May 1999 18:25:51 -0500 (EST) From: Jon Smith To: Andrew Gordon Cc: freebsd-hackers@freebsd.org Subject: Re: StarOffice command line args In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A million and one thanks + tax. Jon Smith On Sat, 15 May 1999, Andrew Gordon wrote: > Some while ago, Jon Smith wrote: > > > > Has anyone successfully gotten Star Office 5.0 to run multi-user? > > > > I have just solved this. The problem is that StarOffice accesses the > command line arguments (and hence the "/net" flag needed to install > multi-user) using the vile /proc/xxx/cmdline mechanism. The FreeBSD > implementation of this is a hack that only returns argv[0] and therefore > discards any command line arguments. > > The attached patch is still a hack, but is one step closer to the right > answer: it now returns the right answer if the current process reads its > own /proc/xxx/cmdline, but still returns only argv[0] if a process > attempts to read another process' cmdline. This is enough to solve the > StarOffice problem. > > The reason I haven't done the job properly is that I don't know how to > read an address in user-space for a process other than curproc. From the > implementation of /proc/xxx/mem, this seems difficult to do. > > > -- "Everywhere I go, there's Jon Smith!" -- Leah Dunlevy "Cars don't kill people.... People kill people." Jonathan Smith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message