So, why not just call it "mkproto", then?

I remember being horribly frustrated with SunOS when I discovered that it
had a mkproto command without the corresponding command to generate the
protofile required by mkproto.  Had to write it in awk due to the lack of
perl.  The mode parser was fun.

On Mon, 29 Oct 2001, Christos Zoulas wrote:

# Date: Mon, 29 Oct 2001 18:38:11 GMT
# From: Christos Zoulas <christos@zoulas.com>
# To: tech-userlevel@netbsd.org
# Subject: Re: CVS commit: basesrc/usr.sbin/makefs
#
# In article <20011029234315.A206@krishna>,
# Bang Jun-Young <junyoung@mogua.com> wrote:
# >On Fri, Oct 26, 2001 at 10:46:22AM +0300, Luke Mewburn wrote:
# >>
# >> Module Name:	basesrc
# >> Committed By:	lukem
# >> Date:		Fri Oct 26 07:46:22 UTC 2001
# >>
# >> Update of /cvsroot/basesrc/usr.sbin/makefs
# >> In directory netbsd.hut.fi:/tmp/cvs-serv17942
# >>
# >> Log Message:
# >> makefs - create a file system image from a directory tree.
# >> It doesn't need any special privileges or kernel devices.
# >>
# >> Only ffs image creation is supported at this time, although makefs has been
# >> designed to allow the addition of other file system formats by writing new
# >> back-ends.
# >>
# >> This program was designed & implemented by Luke Mewburn of Wasabi Systems.
# >
# >Thanks for good work! :)
# >
# >BTW, IMHO, the name 'makefs' is a bit confusing, since it implicits
# >it's used to create new file system on disk as traditional 'mkfs' does.
# >So, how about renaming it to 'mkfsimage', 'makefsimg', or something
# >other that has more appropriate meaning for its purpose?
# >
#
# Historically it has been mkproto I believe. It got removed from 4.4BSD
# because it was AT&T proprietary.
#
# christos
#


				--*greywolf;
--
NetBSD: My Computer Runs!