From owner-freebsd-questions Fri Sep 15 16:41:48 2000 Delivered-To: freebsd-questions@freebsd.org Received: from technet.tjhsst.edu (technet.tjhsst.edu [151.188.14.120]) by hub.freebsd.org (Postfix) with ESMTP id DB53B37B422 for ; Fri, 15 Sep 2000 16:41:43 -0700 (PDT) Received: from lan.tjhsst.edu (lan.tjhsst.edu [151.188.14.12]) by technet.tjhsst.edu (8.9.3/8.9.3) with ESMTP id TAA01248 for ; Fri, 15 Sep 2000 19:41:31 -0400 Received: from TJHSST_SCIENCE/SpoolDir by lan.tjhsst.edu (Mercury 1.47); 15 Sep 00 19:38:53 EST Received: from SpoolDir by TJHSST_SCIENCE (Mercury 1.47); 15 Sep 00 19:38:32 EST Received: from Kevathlon (24.168.212.214) by lan.tjhsst.edu (Mercury 1.47); 15 Sep 00 19:38:28 EST Message-ID: <000a01c01f6e$80f86540$a300a8c0@Kevathlon> From: "Kevin Caffrey" To: Subject: Compatability Date: Fri, 15 Sep 2000 19:41:43 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C01F4C.F9A3A1C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C01F4C.F9A3A1C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have a machine with BSDI disk slices that we would like to upgrade to = another OS, and I am wondering if FreeBSD will read BSDI disk slices so = that we could transfer the data. Thanks, Kevin Caffrey ------=_NextPart_000_0007_01C01F4C.F9A3A1C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I have a machine with BSDI disk slices = that we=20 would like to upgrade to another OS, and I am wondering if FreeBSD will = read=20 BSDI disk slices so that we could transfer the data.

Thanks,

= Kevin=20 Caffrey

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