From owner-freebsd-hackers Mon Sep 16 02:54:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA24394 for hackers-outgoing; Mon, 16 Sep 1996 02:54:18 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA24388 for ; Mon, 16 Sep 1996 02:54:15 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id CAA20505; Mon, 16 Sep 1996 02:50:27 -0700 (PDT) To: Darryl Okahata cc: hackers@freefall.freebsd.org Subject: Re: fdisk changes, anyone? In-reply-to: Your message of "Mon, 16 Sep 1996 00:12:43 PDT." <199609160712.AA113897963@hpnmhjw.sr.hp.com> Date: Mon, 16 Sep 1996 02:50:26 -0700 Message-ID: <20503.842867426@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've just mangled fdisk such that partitioning information can now > be specified via an optional config file. I've been needing a way to > partition a disk from a script (without using expect), and so I mangled > fdisk to do just that. I want to write a perl script for adding SCSI > disks, and a programmatic fdisk was the only piece missing. An example > config file is: Wouldn't it be more flexible to add this as command-line parsing for fdisk? I like the idea, but making it use a config file means that anything driving fdisk programmatically needs to use a temp file, rather than simply forming a complex fdisk commmand and passing it to system(). Jordan