From owner-freebsd-ports Fri Feb 15 19:47: 1 2002 Delivered-To: freebsd-ports@freebsd.org Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.8.210.226]) by hub.freebsd.org (Postfix) with ESMTP id 1E87637B400 for ; Fri, 15 Feb 2002 19:46:58 -0800 (PST) Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id g1G3jn751596; Fri, 15 Feb 2002 22:45:49 -0500 (EST) (envelope-from alane) Date: Fri, 15 Feb 2002 22:45:49 -0500 From: Alan Eldridge To: kstailey@surfbest.net Cc: FreeBSD Ports List Subject: [ade@FreeBSD.org: suggests installing in a USER's HOME dir] Message-ID: <20020216034549.GA51544@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.26i X-message-flag: Magic 8-Ball says "Outlook not so good." I'll ask it about Exchange next. Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ----- Forwarded message from Ade Lovett ----- On 02/15/02 21:21, "Alan Eldridge" wrote: > But nobody ever did chime in with an idea of where the best place to put > a 200-400MB *writable* file, installed by a port, is. And that, of course, > was the whole point in cc'ing portmgr. So, any thoughts on that? There is no precedent for this. The closest port (and its aways away by a long shot) is vmware, when it creates its disk images, usually within the users home directory. Hmm. Perhaps instead of using a hardcoded location, you fix0r the code to dig up the users home directory getpwuid(geteuid()), and use/create a klh (or even .klh) subdirectory for the writable stuff? Store a gzipped copy somewhere in ${PREFIX}, and provide an "initialize" script to do the necessary magic. -aDe ----- End forwarded message ----- So, to follow onto this, here's a suggestion: 1. Store the compressed PI disk image in /usr/local/share/whatever. 2. Create an "install as user" script. This creates a custom set of .ini files and copies them, along with an uncompressed disk image, to a directory that a user specifies. IOW, basically what he said, and which was also one of my earlier suggestions. Bottom line is, there's just no reliable way to pick a place that will fit the requirements of (1) unique to local machine (2) big enough (3) writable. -- Alan Eldridge "Dave's not here, man." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message