From owner-freebsd-current@FreeBSD.ORG Sun May 13 19:29:07 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9CF8516A405; Sun, 13 May 2007 19:29:07 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh2.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 66DFF13C46A; Sun, 13 May 2007 19:29:07 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from neutrino.centtech.com (andersonbox1.centtech.com [192.168.42.21]) by mh2.centtech.com (8.13.8/8.13.8) with ESMTP id l4DJT27h004099; Sun, 13 May 2007 14:29:03 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <46476700.6010101@freebsd.org> Date: Sun, 13 May 2007 14:29:04 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.0 (X11/20070420) MIME-Version: 1.0 To: Giorgos Keramidas References: <464464BB.3090100@freebsd.org> <20070511152646.g6n5r7k2tcw00ow4@webmail.leidinger.net> <464476D3.3090001@freebsd.org> <4645173A.2040008@freebsd.org> <20070512205110.U24765@fledge.watson.org> <20070513024030.GE2364@dan.emsphone.com> <20070513031807.GA6437@kobe.laptop> In-Reply-To: <20070513031807.GA6437@kobe.laptop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/3236/Sun May 13 02:23:27 2007 on mh2.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh2.centtech.com Cc: Robert Watson , Kian Mohageri , Dan Nelson , freebsd-current@freebsd.org Subject: Re: [PATCH] Fancy rc startup (revisited) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 May 2007 19:29:07 -0000 On 05/12/07 22:18, Giorgos Keramidas wrote: > On 2007-05-12 21:40, Dan Nelson wrote: >> In the last episode (May 12), Robert Watson said: >>> Call me old-fashioned, but I actually preferred the much more >>> abbreviated rc output from before rc.d even. :-) We're not going back >>> to hardware devices where all the probed devices add up to fewer than >>> 25 lines, I'm sure, but when daemons generated 8-12 characters >>> without a carriage return each, there was a good chance you could >>> still see the end of the kernel messages by the time you got to >>> login:, and I miss that. I don't object to optional more complex >>> output as long as that complexity is hidden away neatly somewhere in >>> rc.subr, and isn't on by default as shipped. I'd love it if someone >>> could restore the even shorter output we had before. >> Taken to an extreme, you have Solaris 10, where you get the kernel's >> copyright message, smf kicks off all the startup scripts in parallel >> (subject to dependency rules) in the background, their output goes >> into individual logfiles, and all you see is the login: prompt at the >> console :) > > More like Solaris 10 "boot -v", where you still get the kernel messages, > but you have a point there. I am kind of old-fashioned in the Robert > way too, however. If there was a way to minimize the console output > when services are starting, i.e. to print something like: > > [last kernel message] > > Booting FreeBSD: dumpon initrandom fsck root hostid mountcritlocal > var cleanvar random adjkerntz hostname kldxref swap sysctl netif (lo0 > fxp0) pflog pf routing devd nsswitch devfs syslogd ldconfig named > auditd tmp cleartmp dmesg virecover local motd ntpd powerd syscons > sshd sendmail cron securelevel power_profile inetd > > foo login: > > where each rc.d script would only print its name if it *was* enabled > with xxx_enable, optionally followed by a parenthesized list of > single-word status messages for each subscript/component), would be > really neat. > > Is there any easy way we can 'tune' the fancy script to support the > current output style, a very brief style like above, and then a fancy > colorful style, depending on an rc.conf setting? I think the rc_fancy patch could be pretty easily tweaked to do exactly what you say. I might give it a go, and add that as another option to it. Maybe then the variable should change to rc_style_* instead? Eric