Date: Sun, 13 May 2007 14:29:04 -0500 From: Eric Anderson <anderson@freebsd.org> To: Giorgos Keramidas <keramida@freebsd.org> Cc: Robert Watson <rwatson@freebsd.org>, Kian Mohageri <kian.mohageri@gmail.com>, Dan Nelson <dnelson@allantgroup.com>, freebsd-current@freebsd.org Subject: Re: [PATCH] Fancy rc startup (revisited) Message-ID: <46476700.6010101@freebsd.org> In-Reply-To: <20070513031807.GA6437@kobe.laptop> References: <464464BB.3090100@freebsd.org> <20070511152646.g6n5r7k2tcw00ow4@webmail.leidinger.net> <464476D3.3090001@freebsd.org> <4645173A.2040008@freebsd.org> <fee88ee40705121214ldd26976yd860e9e067d7cb6a@mail.gmail.com> <20070512205110.U24765@fledge.watson.org> <20070513024030.GE2364@dan.emsphone.com> <20070513031807.GA6437@kobe.laptop>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/12/07 22:18, Giorgos Keramidas wrote: > On 2007-05-12 21:40, Dan Nelson <dnelson@allantgroup.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46476700.6010101>