From owner-freebsd-current Thu Jul 6 12:19: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 7BF0437BA9E for ; Thu, 6 Jul 2000 12:18:57 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 64A70A06; Thu, 6 Jul 2000 12:18:56 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id MAA13964; Thu, 6 Jul 2000 12:18:55 -0700 (PDT) Message-ID: <3964DB9F.2D9E86D3@cup.hp.com> Date: Thu, 06 Jul 2000 12:18:55 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Rahul Dhesi Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP: /etc/rc.shutdown calls local scripts now References: <20000706185810.8EECB7D33@yellow.rahul.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rahul Dhesi wrote: > > >> Can we have little green "[ OK ]"s as well? :) > > >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. I don't like the Linux/HP-UX/whatever way simply because it's non-unix in the sense that normally output is generated only in case of failure or in exceptional conditions. It's "telling" me things I don't want to "hear". The same applies to having "N/A" or "FAIL" emitted for services that aren't enabled/configured (in which case printing "FAIL" is plain wrong). > 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. Which means that if the daemon is down and the script doesn't know about it, you have to remove pid files and whatnot to use the script again to get the daemon running, right? > 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. You mean the irritating pop-up that asks you questions everytime the bloody machine boots? :-) -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message