Date: Mon, 16 Sep 1996 10:13:41 -0700 From: Darryl Okahata <darrylo@hpnmhjw.sr.hp.com> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: hackers@freefall.freebsd.org Subject: Re: fdisk changes, anyone? Message-ID: <199609161713.AA079274022@hpnmhjw.sr.hp.com> In-Reply-To: Your message of "Mon, 16 Sep 1996 02:50:26 PDT." <20503.842867426@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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().
Well, the only real "advantage" is that lines in the config file
can be executed as they are parsed (that, and the fact that I hate
command lines from h*ll ;-). With config files, you don't have to save
the options before executing them. Also, as this is supposed to be used
by scripts and not by real humans, I didn't think that making temporary
files was all that big a deal.
However, I wouldn't mind having these changes added to fdisk. If
you (or someone else) are willing to commit these changes, I'll make it
use command-line options from h*ll. ;-)
-- Darryl Okahata
Internet: darrylo@sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been following him all day.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609161713.AA079274022>