Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 May 1998 21:31:11 +0200
From:      Eivind Eklund <eivind@yes.no>
To:        Tom <tom@sdf.com>, Simon Shapiro <shimon@simon-shapiro.org>
Cc:        freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG
Subject:   Re: DPT install problem
Message-ID:  <19980522213111.03467@follo.net>
In-Reply-To: <Pine.BSF.3.95q.980522103909.20211C-100000@misery.sdf.com>; from Tom on Fri, May 22, 1998 at 10:41:41AM -0700
References:  <XFMail.980522140943.shimon@simon-shapiro.org> <Pine.BSF.3.95q.980522103909.20211C-100000@misery.sdf.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 22, 1998 at 10:41:41AM -0700, Tom wrote:
>   Yes, it seems to be a sysinstall interaction.  If I leave the space
> unallocated, and then disklabel and newfs it later, it works fine.
> 
>   Currently it is pretty hard to bootstrap a new DPT system.  You have to
> be able to build a kernel somewhere else as sysinstall will install a
> non-DPT kernel, and you can't use sysinstall to allocate large DPT
> partitions.  I fear for the new user.

sysinstall doesn't do this anymore.  The DPT driver is activated as
part of the standard sysinstall now.

As for large arrays: I think that will have to be left to you that
actually have those large arrays - it is kind of difficult for us
others to find out where the problem is.  I suspect libdisk might be
the culprit; it interact with the slice code using different IOCTLs
than disklabel, IIRC.

Eivind.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980522213111.03467>