Date: Thu, 12 Oct 2006 19:39:49 -0700 From: Chris <snagit@cbpratt.prohosting.com> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Prevent process in disk wait Message-ID: <DD0185F4-3E4A-412C-BB25-D78E4B149033@cbpratt.prohosting.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DD0185F4-3E4A-412C-BB25-D78E4B149033>