From owner-freebsd-hackers Tue Aug 20 11:24:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA23200 for hackers-outgoing; Tue, 20 Aug 1996 11:24:37 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts9-line6.uoregon.edu [128.223.150.87]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA23195 for ; Tue, 20 Aug 1996 11:24:34 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id LAA00814 for ; Tue, 20 Aug 1996 11:24:43 -0700 (PDT) Date: Tue, 20 Aug 1996 11:24:43 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: hackers@freebsd.org Subject: How about a 'mkdisk' tool? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I don't subscribe to -hackers, but here's something for you guys to chew on if you need a project. I lack the necessary programming expertise, but perhaps someone familiar with sysinstall and the dialog library could do something with it. According to the Unix Sys Admin Handbook, BSDi has a "disksetup" tool that makes it rather easy to fdisk & disklabel a new disk. I was thinking that we could pull out the fdisk and disklabel segments from sysinstall, roll them together into a dialog-driven tool, add a easy-newfs editor, and put them into a 'mkdisk' tool. We are in serious need of a set method to add new disks to the system, a one-stop utility would be the way to go. I don't know how hard it would be to strip out the necessary components from sysinstall, considering what a mess it's in now :-) Just a thought. I'm leaving (again) for a few days so I won't reply immediately. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major