Re: [PATCH] Fancy rc startup style RFC


On Apr 19, 2006, at 2:07 PM, Eric Anderson wrote:


Ok - first, let me remind everyone that this is for startup/ shutdown of scripts and such, not for ls and other things. I'd also like to remind everyone that the default for the whole thing can be OFF, so you won't even know the option exists if you don't want to know about it. If it is on, then the default is b/w like the current setup is, and currently no information is suppressed so there is no loss of helpful information on boot, only additional information (OK, FAILED, SKIP, etc).

If someone doesn't like the colors, doesn't like the 'fancy' bootup, then they merely have to do nothing at all.

This is a similar feature as rc_info is, and there's no issue there, because it's off by default. Same with the color daemon at the boot menu.

I think it should be off by default, until enough people demand it on (if that happens at all), and then it should be b/w by default, with the option to make it color. My main goal was to implement this with as little reworking of the current system as possible, yet still reap rewards of easy readability when the system boots.


I hate to even suggest this, but perhaps we should add a desktop vs server option when installing freebsd. It wouldn't effect packages used, but might change a few defaults such as this new fancy startup. People using terminals and such would still get their black and white startup and everyone else would get the nice color startup. Anyone using a desktop or sys admins who have video cards in their servers and never tend to debug anything would like it. I think PC-BSD and DesktopBSD show there is a demand for FreeBSD on the desktop. It might be time we acknowledge that. Adding color doesn't minimize the "power to serve." As much as I love FreeBSD, sometimes its difficult to get others to try it simply because the project is so difficult about desktop usage. People often try out a new OS on a desktop before using it on production servers. Few people just risk it like I did a few years ago. In my case, I just didn't want linux.


Lucas Holt
Luke@xxxxxxxxxxxxxxxx
________________________________________________________
FoolishGames.com (Jewel Fan Site)
JustJournal.com (Free blogging)
FoolishGames.net (Enemy Territory site)


_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: boot banner project
    ... So, having found that FreeBSD ... > naturally chose it for those servers. ... While what I propose for the boot scrn ... there, that might use FreeBSD, that use Linux, because they haven't even ...
    (freebsd-current)
  • Servers Crash every few days
    ... I have six servers running FreeBSD 6.2 and all of them have the same config. ... Memory for the servers are ... 1000 connection and sometimes when the connections is more 10000. ...
    (freebsd-questions)
  • Re: Windows client - internet connection sharing
    ... >> ADSL line to provide internet access via LAN to a ... > This is all about how you interface your FreeBSD ... > servers and so forth. ... This enables you to set up a 'DMZ' network, ...
    (freebsd-questions)
  • Re: Changing Hardware Platform
    ... Some folks will find these two Kbs informative on troubleshooting related startup issues: ... The boot manager searches for and starts IA64ldr.efi. ... >> You can't expect PnP to solve your boot controller issue. ... >> that means that the driver is effectively preinstalled, ...
    (microsoft.public.windows.server.sbs)
  • Re: computer problem
    ... really have to be run at Startup. ... and you can't boot into Normal Mode to put ... aren't networking, the system wastes time during boot looking for network ... network adapter will list beneath that heading. ...
    (microsoft.public.windowsxp.general)