From owner-freebsd-hackers Tue Jun 30 16:22:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28798 for freebsd-hackers-outgoing; Tue, 30 Jun 1998 16:22:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28736 for ; Tue, 30 Jun 1998 16:21:30 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id QAA10974; Tue, 30 Jun 1998 16:20:55 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Matthew D. Fuller" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Adding a new user interface to FreeBSD administration In-reply-to: Your message of "Tue, 30 Jun 1998 16:33:13 CDT." <19980630163313.49201@futuresouth.com> Date: Tue, 30 Jun 1998 16:20:55 -0700 Message-ID: <10970.899248855@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK, so what's wrong with a simple /etc/rc.conf script that looks > something like: Several reasons. 1. If you want to write a nifty editor for it, you have to now have _rules_ for clumping all the mountd_foo variables together in such a way that all "mountd attributes" are editable in a common block. 2. This does not deal *explicitly* with ordering issues unless it will be very well documented that the order in which startup commands are specified must be maintained (and then, of course, the aformentioned editor has another thing to remember in writing things back out). This would be true in your example since portmap, for one, needs to be run before mountd. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message