From owner-freebsd-current Tue Nov 10 10:24:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26835 for freebsd-current-outgoing; Tue, 10 Nov 1998 10:24:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA26830 for ; Tue, 10 Nov 1998 10:24:46 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zdISQ-0002P9-00; Tue, 10 Nov 1998 10:24:02 -0800 Date: Tue, 10 Nov 1998 10:24:00 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: The Hermit Hacker cc: Mike Smith , Paul Saab , current@FreeBSD.ORG Subject: Re: 18gig drive's supported? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Nov 1998, The Hermit Hacker wrote: > Surprisingly, I did...when I upgraded the system to its currently > level...:( Now I've got sysinstall upgraded and installed, but when I go > to 'label' or 'fdisk', it auto-presents me with da0, but doesn't give me > the old choices of working with any of the other drives...did I miss a new > command line switch her or something like that? Have read man pages, have > built a new libdisk.a *just in case*... Give up and use fdisk, disklabel, and newfs directly. I think it was a mistake to re-invent the whell and re-develop all these functions and call it sysinstall. sysinstall has problems with large DPT disks too, but disklable and newfs work fine directly. > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message