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

Tom Rhodes trhodes at
Thu Jul 3 16:40:10 UTC 2003

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

From: Tom Rhodes <trhodes at>
To: Michael Smith <msmith at>
Cc: siegbert.baude at, freebsd-gnats-submit at
Subject: Re: docs/54009: Clarify the location of the splash image in the
 splash man page
Date: Thu, 3 Jul 2003 12:10:18 -0400

 From the loader.conf(5) manual page:
                      (``NO'') If set to ``YES'', a bitmap will be loaded to be
                      displayed on screen while booting.
                      (``/boot/splash.bmp'') Name of the bitmap to be loaded.
                      Any other name can be used.
 I think that is quite explicit on using splash images.  If we read down
 a little further, we come across:
      /boot/defaults/loader.conf  default settings -- do not change this file.
      /boot/loader.4th            defines the commands used by loader to read
                                  and process loader.conf.
      /boot/loader.conf           user defined settings.
      /boot/loader.conf.local     machine-specific settings for sites with a
                                  common loader.conf.
      /boot/loader.rc             contains the instructions to automatically
                                  process loader.conf.
 The one I'm interested in is /boot/loader.conf which is described as 'user defined
 settings.', which I think is self explainatory.  Now, loader.conf works similar
 to rc.conf and a few other files in FreeBSD where the user defined settings
 should exist in another file which overrides the default.  My personal feeling
 here is that the proper method would be to:
 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.
 Tom Rhodes
 On Thu, 3 Jul 2003 09:19:00 -0700
 Michael Smith <msmith at> wrote:
 > Don't screw with the module path.  Either fix the documentation to 
 > reflect
 > reality, or change the code to search for the splash elsewhere.
 >   = Mike
 > On Thursday, July 3, 2003, at 9:16 AM, Siegbert Baude wrote:
 > > Tom, but you have an absolute path to the image in your loader.conf, 
 > > right?
 > >
 > > I checked the docu now once again, and every piece of it including the 
 > > splash
 > > mini-FAQ says, the splash image should go into /boot. I found the 
 > > solution in
 > > /boot/defaults/loader.conf, where it is said that the image must be 
 > > located
 > > somewhere in the module_path. The default for this however is
 > > "/boot/kernel;/boot/modules/" so a splash image in /boot isn't found.
 > >
 > > I think there are two solutions:
 > >
 > > 1) Add /boot to the module_path in /boot/defaults/loader.conf like
 > > "/boot/kernel;/boot/modules/;/boot"
 > >
 > > 2) Remove all examples of images in the documentation, which use 
 > > relative
 > > paths and substitute the absolute paths.
 > >
 > > Mike, do you think there might be some problems with solution #1? It 
 > > would be
 > > easier to correct, but maybe #2 is the cleaner way. I would create the 
 > > diffs
 > > for the man pages and conf-files, so you only had to commit them.
 > >
 > > Ciao
 > > Siegbert
 > >
 > >
 > >
 > --
 > Where am I, and what am I doing in this handbasket?

More information about the freebsd-doc mailing list