From owner-freebsd-current Thu Jul 6 11:58:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from yellow.rahul.net (yellow.rahul.net [192.160.13.18]) by hub.freebsd.org (Postfix) with ESMTP id 2E07637BAFF for ; Thu, 6 Jul 2000 11:58:11 -0700 (PDT) (envelope-from dhesi@rahul.net) Received: by yellow.rahul.net (Postfix, from userid 104) id 8EECB7D33; Thu, 6 Jul 2000 11:58:10 -0700 (PDT) To: freebsd-current@freebsd.org Subject: Re: HEADS UP: /etc/rc.shutdown calls local scripts now Newsgroups: a2i.lists.freebsd-current References: X-Newsreader: NN version 6.5.6 (NOV) Message-Id: <20000706185810.8EECB7D33@yellow.rahul.net> Date: Thu, 6 Jul 2000 11:58:10 -0700 (PDT) From: dhesi@rahul.net (Rahul Dhesi) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Linh Pham writes: >> Can we have little green "[ OK ]"s as well? :) >> >> j/k >I hope you are joking... LOL... We don't want Linux emulation to go in >that direction. It's not the green that's important, it's the 'OK'. The way Redhat Linux boots, you can see at a glance which start-up commands failed and which ones succeeded. The way FreeBSD boots, it's all one big blur. Also, in the Linux scheme, there is a standard mechanism to keep track of which boot-time service has already been started, and any accidental re-invocation of the script (without an intervening 'stop') will be detected and rejected. I personally find the 'chkconfig' command to be very convenient to enable, disable, and list boot-time services, without having to manually rename xxx.sh to xxx.sh.DISABLED and back. -- Rahul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message