From owner-freebsd-hackers Thu Feb 9 09:21:20 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA13540 for hackers-outgoing; Thu, 9 Feb 1995 09:21:20 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA13534 for ; Thu, 9 Feb 1995 09:21:19 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id JAA23073; Thu, 9 Feb 1995 09:21:13 -0800 From: Poul-Henning Kamp Message-Id: <199502091721.JAA23073@ref.tfs.com> Subject: Re: installation problem (2.0): exec failed? To: jcargill@cs.wisc.edu (Jon Cargille) Date: Thu, 9 Feb 1995 09:21:13 -0800 (PST) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <9502090430.AA04848@grilled.cs.wisc.edu> from "Jon Cargille" at Feb 8, 95 10:30:54 pm Content-Type: text Content-Length: 558 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > Has anyone run across this sort of installation problem before? > > Someone I know says he got the following error (followed by a reboot) > after fdisk/disklabelling, and proceeding with the installation: > > exec(stand/newfs) failed code=5888. > This is because his scsi-adapter has the ">1GB" option set. This is fixed (with a measurable speed-increase as side-effect) in the next snapshot. -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-)