From owner-freebsd-current Fri Mar 17 7:11:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id D6E4437BA32 for ; Fri, 17 Mar 2000 07:11:53 -0800 (PST) (envelope-from forrie@forrie.com) Received: from Forrest (getbent@forrie.ne.mediaone.net [24.147.129.124]) by forrie.net with id e2HFBoj01842; Fri, 17 Mar 2000 10:11:51 -0500 (EST) Message-Id: <4.3.1.2.20000317100803.00b52120@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 17 Mar 2000 10:10:04 -0500 To: Brian Dean From: Forrest Aldrich Subject: Re: Streamlining FreeBSD Installations Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200003171453.JAA43008@dean.pc.sas.com> References: <4.3.1.2.20000317074445.00b60d90@216.67.12.69> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Another issue here, at least in our application of it, is about adding users and setting passwords. With well over 100 machines, we want to also have installed user accounts for our engineers. Again, nightmareish to consider doing manually. Such a script used at startup could contain also the account name and perhaps the "crypted" form of the password, and some other utility would need to do the magic from there. _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message