Hello, The Beastie menu makes it convenient choosing boot options. The Beastie decorating space right to the menu reflects the preference of the majority or all of the FreeBSD developers. Their opinion is documented in http://www.freebsd.org/copyright/daemon.html . However there are users which have a different opinion and which don't like the Beastie mascot to be displayed during boot time. However there are users which have a different opinion and which don't like the Beastie mascot to be displayed during boot time. The question is: are such users - welcome - tolerated - disliked. In case they are more or less tolerated what should they do in order to switch the Beastie splash screen? - renounce of the Beastie menu (beastie_disable="YES") ? - spend some hours to dig in mailing lists or dig in http://www.forth.org/tutorials.html ? - or have an convenient flag in loaders.conf that allows to run Beastie menu but display some other decoration? The patch 74577 offers a convenient flag to disable the display of the Beastie while being compatible with the majority of the FreeBSD developers. http://www.freebsd.org/cgi/query-pr.cgi?pr=74577 There were talks that the FreeBSD logo will change anyway. But so far this has not affected 5.4-RC1. -Hanspeter
(Changing the subject since its not reflective of the tone of the message. Apologies to the poster, but since this is a touchy subject I'm going to make this a more technical discussion.) On Mon, 11 Apr 2005, Hanspeter Roth wrote:> - or have an convenient flag in loaders.conf that allows to > run Beastie menu but display some other decoration?I I have an idea and the patch in PR 74577 is about halfway there. I suggest providing a script that forth-ifies a provided ASCII logo, and a loader option to load a banner file from disk. This way, if, say, an OEM wanted to put contact information in there, they could put in loader.conf: banner_enable="YES" banner_file="/boot/oem.banner" and have that displayed instead of the beastie. The forthifier script would turn the file into a forth function definition and then it can be included with standard routines in the loader. Then your banner function would just call it. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
On Apr 14 at 10:13, Doug White spoke:> I I have an idea and the patch in PR 74577 is about halfway there. I > suggest providing a script that forth-ifies a provided ASCII logo, and a > loader option to load a banner file from disk. This way, if, say, an OEM > wanted to put contact information in there, they could put in loader.conf: > > banner_enable="YES" > banner_file="/boot/oem.banner" > > and have that displayed instead of the beastie.Is it acceptable that the banner_file is just an include file or should the program open the banner_file itself? -Hanspeter