From owner-freebsd-hackers Sat May 25 22:55:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA07746 for hackers-outgoing; Sat, 25 May 1996 22:55: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 WAA07735; Sat, 25 May 1996 22:55:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id WAA18630; Sat, 25 May 1996 22:54:55 -0700 (PDT) To: csdayton@midway.uchicago.edu cc: "Matthew N. Dodd" , freebsd-hackers@FreeBSD.org, Dima Ruban Subject: Re: Adduser program in C In-reply-to: Your message of "Sat, 25 May 1996 21:10:01 CDT." <199605260210.VAA23555@woodlawn.uchicago.edu> Date: Sat, 25 May 1996 22:54:55 -0700 Message-ID: <18628.833090095@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Yo, everybody! :-) I don't really care _what_ language it's written in just so long as: 1. It supports a reasonable number of options and home directory organization schemes. For a synopsis of my views on this, search the mailing list archives for "adduser" - I actually spec'd this out awhile back in a mail message to this list. 2. Be designed to be callable by front-ends written in anything from Tk to C. By "callable" I simply mean that adduser(1) should be drivable completely by command-line arguments, only prompting the user for information when it has not been provided thusly. 3. That language be a standard part of the system so we don't need to bring in something like prolog just to get adduser to compile. :-) Jordan