From owner-freebsd-questions@FreeBSD.ORG Fri Oct 13 02:40:04 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2DFB16A412 for ; Fri, 13 Oct 2006 02:40:04 +0000 (UTC) (envelope-from snagit@cbpratt.prohosting.com) Received: from n126.sc0.cp.net (smtpout1106.sc0.he.tucows.com [64.97.144.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C8AD43D6E for ; Fri, 13 Oct 2006 02:40:04 +0000 (GMT) (envelope-from snagit@cbpratt.prohosting.com) Received: from [192.168.1.100] (67.47.213.85) by n126.sc0.cp.net (7.2.069.1) (authenticated as eagletree@hughes.net) id 452EC8430000D425 for freebsd-questions@freebsd.org; Fri, 13 Oct 2006 02:39:58 +0000 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <200610130132.k9D1WgwY005831@banyan.cs.ait.ac.th> References: <302F75DC2739FB43B236373398A8C5992988@saturnus.intra.socruel.nu> <0779903C-A01F-4CF0-AF1F-3DA317511598@cbpratt.prohosting.com> <200610130132.k9D1WgwY005831@banyan.cs.ait.ac.th> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chris Date: Thu, 12 Oct 2006 19:39:49 -0700 To: FreeBSD Questions X-Mailer: Apple Mail (2.752.2) Subject: Re: Prevent process in disk wait X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 02:40:04 -0000 On Oct 12, 2006, at 6:32 PM, Olivier Nicole wrote: >> While installing the Ruby port on a 6.1-Release system (uname -a >> ... >> 37788 p0 DL+ 39:43.11 ./ruby18 ./bin/rdoc --all --ri --op >> /usr/local/share/ri/1.8/system . >> >> The system is an old Pentium 5 with a standard IDE drive. Is there a > > I got hit bit that a couple of times too. > > For some reason, Ruby at some stage tries to browse the complete hard > disk in order to find things like libraries. > > At least that's what I guessed. > > Anser was: get a better/newer hardware. > Yes, I wasn't clear in trying to answer the original post. Inadequate memory that led to swapping seemed to be the source of that port being a slow upgrade. I thought that might explain the problem described. With the methods as described in the previous post, perhaps one could get by with antiquated hardware though for testing purposes and playing.