From owner-freebsd-current Thu Jul 6 16:38:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 66DEA37B7EB for ; Thu, 6 Jul 2000 16:38:17 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e66NcGK70125; Thu, 6 Jul 2000 16:38:16 -0700 (PDT) Date: Thu, 6 Jul 2000 16:38:16 -0700 (PDT) From: Doug White To: Rahul Dhesi Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP: /etc/rc.shutdown calls local scripts now In-Reply-To: <20000706185810.8EECB7D33@yellow.rahul.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Jul 2000, Rahul Dhesi wrote: > 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. But guess what, the error messages are eaten. I've had times where errors were not redirected into the log so you have phantom errors. Plus I've had erroneous 'OK' conditions on things that were actually broken (eg missing ethernet interfaces). The current way spews the error all over, but it's plainly obvious what's broken and why. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message