docs/54009: Clarify the location of the splash image in thesplash man page

[Siegbert Baude]

The following reply was made to PR docs/54009; it has been noted by GNATS.

From: Siegbert Baude <Siegbert.Baude at gmx.de>
To: freebsd-gnats-submit at freebsd.org
Cc: Tom Rhodes <trhodes at freebsd.org>,
	Michael Smith <msmith at freebsd.org>
Subject: Re: docs/54009: Clarify the location of the splash image in the splash
 man page
Date: Sun, 06 Jul 2003 20:56:47 +0200

 > Create the /boot/loader.conf file if it does not exist.  Put in the custom
 > splash information with what is defined above.  That is how I did it on my
 > system.  Now, if you do not define a splash image, then yes I'm sure it
 > would look in the module path (without looking at the code nor any other
 > manual page/documentation besides loader.conf(5)).  Try my suggestion
 > above and let me know if that fixes your problem.  Thanks.
 
 The problem is not, that the splash screen doesn't work; actually it does, either with absolute paths or the image file 
 in the module path. But the splash.4 man page and /boot/defaults/loader.conf don't use absolute paths in their example 
 sections, which is misleading. Look into my diffs, I think they make things clearer.
 
 
 --- splash.4.orig       Sun Jul  6 19:31:28 2003
 +++ splash.4    Sun Jul  6 20:05:51 2003
 @@ -192,11 +192,11 @@
   .Bd -literal -offset indent
   splash_bmp_load="YES"
   bitmap_load="YES"
 -bitmap_name="chuck.bmp"
 +bitmap_name="/boot/chuck.bmp"
   .Ed
   .Pp
   In the above example, the file
 -.Pa chuck.bmp
 +.Pa /boot/chuck.bmp
   is loaded.
   In the following example, the VESA module
   is loaded so that a bitmap file which cannot be displayed in standard
 @@ -205,7 +205,7 @@
   splash_pcx_load="YES"
   vesa_load="YES"
   bitmap_load="YES"
 -bitmap_name="chuck.pcx"
 +bitmap_name="/boot/chuck.pcx"
   .Ed
   .Pp
   If the VESA support is statically linked to the kernel, it is not
 @@ -219,6 +219,13 @@
   only.
   They are not available for the alternative console driver
   .Xr pcvt 4 .
 +.Pp
 +The loader looks for the bitmap file in the kernel module folders as
 +defined by the module_path variable in
 +.Pa /boot/defaults/loader.conf .
 +These folders however are no sensible place for the bitmap file, as
 +they will be renamed by "make world". For the location of the bitmap
 +file absolute paths are therefore recommended.
   .Sh BUGS
   If you load a screen saver while another screen saver has already
   been loaded, the first screen saver will not be automatically unloaded
 
 
 
 --- loader.conf.orig    Sun Jul  6 20:09:26 2003
 +++ loader.conf Sun Jul  6 20:12:45 2003
 @@ -37,8 +37,8 @@
   splash_pcx_load="NO"           # Set this to YES for pcx splash screen!
   vesa_load="NO"                 # Set this to YES to load the vesa module
   bitmap_load="NO"               # Set this to YES if you want splash screen!
 -bitmap_name="splash.bmp"       # Set this to the name of the bmp or pcx file
 -bitmap_type="splash_image_data" # and place it on the module_path
 +bitmap_name="/boot/splash.bmp" # Set this to the name of the bmp or pcx file
 +bitmap_type="splash_image_data"        # Tells loader the image is no kernel module
 
 
   ##############################################################