Date: Thu, 30 Jun 2011 12:47:45 +1000 From: Antony Mawer <lists@mawer.org> To: jhell <jhell@dataix.net> Cc: Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no>, freebsd-stable@freebsd.org Subject: Re: kern/143370: splash_txt ASCII splash screen module Message-ID: <BANLkTi=c2B3QghREO1j-cAV9N_RFakU21g@mail.gmail.com> In-Reply-To: <20110630013323.GA41789@DataIX.net> References: <BANLkTikEBa_SKJvOb8-SuNza_Dh158n4gQ@mail.gmail.com> <20110629190431.e03ac76f.torfinn.ingolfsen@broadpark.no> <20110630013323.GA41789@DataIX.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 30, 2011 at 11:33 AM, jhell <jhell@dataix.net> wrote: > Youve been running this in production... How often do these servers > reboot ;=BF and is it to identify what is actually running on the machine > so they are not confused with surrounding equipment ? > > Most admins that I know don't bother with things like splash screens on > 'production' equipment because its irrelevant to the actual server > usage and unneeded overhead since the actual boot messages prove much > more useful than some random ascii or bmp/pcx. They're embedded-style server systems at remote client sites, about 1200 of them. The splash module is just a visual "nicety" which is displayed during startup - at least providing some feedback as to what the system is doing. These are systems aimed at a non-tech audience, so those "niceties" count. The alternative to that was either standard kernel messages during boot, or a silent boot, both of which tend to confuse the crap out of non-tech end users. -- Antony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTi=c2B3QghREO1j-cAV9N_RFakU21g>