From owner-freebsd-doc@FreeBSD.ORG Mon Dec 1 14:17:36 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A799106564A; Mon, 1 Dec 2008 14:17:36 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (pittgoth.com [205.134.163.206]) by mx1.freebsd.org (Postfix) with ESMTP id 075A88FC19; Mon, 1 Dec 2008 14:17:35 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from localhost.fbsdsecure.org (c-68-83-213-214.hsd1.va.comcast.net [68.83.213.214]) (authenticated bits=0) by pittgoth.com (8.14.3/8.14.3) with ESMTP id mB1EHYpV026358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Dec 2008 09:17:35 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Mon, 1 Dec 2008 09:17:30 -0500 From: Tom Rhodes To: Gabor PALI Message-Id: <20081201091730.0ef555fa.trhodes@FreeBSD.org> In-Reply-To: <49330A66.8040801@FreeBSD.org> References: <493155ED.8020004@FreeBSD.org> <49316309.1050407@gmail.com> <49330A66.8040801@FreeBSD.org> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-doc@FreeBSD.org Subject: Re: RFR: A "Boot Time Splash Screens" Section to the Handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2008 14:17:36 -0000 On Sun, 30 Nov 2008 22:49:26 +0100 Gabor PALI wrote: > Manolis Kiagias wrote: > > Here are a few nits you may want to act on. >=20 > Thank you for your review. I fixed all the problems you pointed out and > created a new version [1][2]. >=20 >=20 > > I can't tell about technical accuracy. >=20 > Hm, it seems I should really test the description myself :) >=20 >=20 > > "Note that, a 320x200 ___splash screen___ image will be displayed as a > > small block in the center of a solid white background screen." =3D> I > > don't understand what you mean by this. Since the resolution at boot > > will be 320x200, the splash screen will still fill the entire screen. > > Do you mean to compare the size of the image to a typical desktop? >=20 > To be honest, it was (blindly) imported from the original text. As far > as I remember (I used splash screens about three years ago), it wants to > tell you something like "if you have a 320x200 image but the resolution > is higher, then it will be put in the middle of the screen". Anyway, I > removed this sentence, since I do not see any clear connection with the > other sentences. >=20 >=20 > > While discussing text mode screensavers, it might be worth mentioning > > that you can get the list of available savers by ls=20 > > /boot/kernel/*saver.ko or something along that line. >=20 > Instead of this, I simply referenced the splash(4) manual page, it > should be enough. >=20 >=20 > > I also feel some longer sentences could use a few commas. >=20 > I tried to insert those commas, and split some longer sentences up into > smaller ones. >=20 >=20 > > I've only peeked at the SGML, but I am sure there is nothing to fix > > there :) >=20 > Thank you for trusting my SGML skills :) >=20 >=20 > Note for native speakers: please, review! You asked. :P Index: chapter.sgml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v retrieving revision 1.65 diff -u -r1.65 chapter.sgml --- chapter.sgml 30 May 2006 23:08:23 -0000 1.65 +++ chapter.sgml 30 Nov 2008 21:53:30 -0000 @@ -507,6 +507,192 @@ + + + + + + Joseph J. + Barbish + Contributed by + + + + + Boot Time Splash Screens + + &os; has a feature to allow the display of a splash + screen in place of showing boot messages. This makes + for a clearer visually experience getting to the legacy What? How about: "The splash screen creates a more visually appealing boot screen comparied to the original boot messages. This screen will be displayed until a console login prompt or X Display Manager offers a login prompt." + virtual console text login prompt and/or the X Display Manager + graphical login screen. + + There are two basic environments available in &os;. The + first is the default legacy virtual console text command line Axe the "text" word here. + environment. After the system finishes booting, a virtual + console text login prompt is presented. The second Probably axe "text" here too - I know you're attempting to describe the look; however, it just sounds odd to me. Similar below. + environment is the X11 Desktop graphical environment. After + X11 and one of the graphical + desktop environments, such as + GNOME, + KDE, or + XFce are installed, the X11 desktop + can be launched from the command line by using the + startx command. + + Some X11 users may select not to stop "may elect" here, but I think this entire bit needs reworded. "Some users prefer the X11 desktop graphical login screen over the traditional text based login prompt." is one example of a better sentence. + at the virtual console login prompt at boot time, but go + directly to the X11 desktop display manager's graphical login + screen. Popular choices are XDM, + the display manager of &xorg;, gdm + for GNOME, and + kdm for + KDE, but any other display manager + found in the Ports Collection could be used. These display Not sure about this sentence either. :( + managers basically provide a graphical login screen in place + of the default legacy virtual console text login prompt. + After a successful login, they present the user with a + graphical desktop. + + In the virtual console text command line environment, the + splash screen would hide all the boot probe messages and task + startup messages before displaying the login prompt. In X11 + environment, the users would get a visually clearer system + start up experience resembling something closer to what a + (µsoft; &windows; or non-unix type system) user would + experience. + + + Splash Screen Function + + The splash screen function only supports + 256-color bitmap (.bmp) or ZSoft + PCX (.pcx) files. + In addition, the splash image files must have a resolution + of 320 by 200 pixels or less to work on standard VGA + adapters. + + To use larger images, up to the maximum resolution + supported by the video card, activate the + VESA support included in &os;. This can + be enabled by loading the VESA module + during system boot, or adding a VESA + kernel configuration option and building a custom kernel + (see ). The + VESA support gives users the ability to + display a splash screen image that fills the + whole display screen. + + While the splash screen is being + displayed during the booting process, it can be turned off + any time by hitting a key. "by hitting any key on the keyboard." + + The splash screen defaults to becoming a + screen saver. After a time period of non-use the screen "also defaults to being a screen saver outside of X11." + will change to the splash screen and cycle + through steps of changing intensity of the image, from + bright intensity to a very dark intensity and over again. + This default splash screen (screen saver) + behavior could be overridden by adding a + saver=3D line to + /etc/rc.conf. Option + saver=3D has several built-in screen savers + to choose from, the full list can be found in the + &man.splash.4; manual page. The default splash + screen screen saver is called warp. + Note that, the saver=3D option specified in "Note that the ..." + /etc/rc.conf only applies to virtual + consoles. It has no effect on X11 display managers. + + At boot time with the splash screen + enabled, a few boot loader messages still could be seen leading + up to and including the boot options menu, and a timed wait + count down prompt before the splash screen is + displayed. This sentence is a bit much. + + Sample splash screen files can be downloaded from the + gallery at . + + + + Enabling the Splash Screen Function + + The splash screen + (.bmp) or (.pcx) + file has to be placed in the /boot directory. + + For default boot display resolution (256-color, 320 by + 200 pixels, or less), edit + /boot/loader.conf, so it contains the + following: + + splash_bmp_load=3D"YES" +bitmap_load=3D"YES" +bitmap_name=3D"/boot/splash.bmp" + + For larger video resolutions up to the maximum of the + video card, edit /boot/loader.conf, so + it contains the following: + + vesa_load=3D"YES" +splash_bmp_load=3D"YES" +bitmap_load=3D"YES" +bitmap_name=3D"/boot/splash.bmp" + + The above assumes that + /boot/splash.bmp + is used for splash screen. When a PCX + file is desired, use the previous statements, plus the + vesa_load=3D"YES" line depending on the + resolution. + + splash_pcx_load=3D"YES" +bitmap_load=3D"YES" +bitmap_name=3D"/boot/splash.pcx" + + The file name is not really restricted to Axe the word "really" here. + splash as shown in the above example. It can + be anything as long as it has type of BMP + or PCX, such as + splash_640x400.bmp + or + blue_wave.pcx. + + There are another two possible interesting + loader.conf options. Not sure about this one. + + + + beastie_disable=3D"YES" + + + This will stop the boot options menu from being + displayed, but the timed wait count down prompt will + still be present. Even with the display of the boot + options menu disabled, entering an option selection at + the timed wait count down prompt will enact the + corresponding boot option. + + + + + loader_logo=3D"beastie" + + + This will replace the default words + &os;, which are displayed to the right + of the boot options menu with the colored beastie logo + like releases in the past had. + + + + + For more information, please see the &man.splash.4;, + &man.loader.conf.5;, and &man.vga.4; manual pages. + + Hope that helps. --=20 Tom Rhodes