[replies sent directly to me may timeout and bounce, since I'm not online as often as I should be, but I'll check the list archives]
Woo hoo. Splash screens are fun. Is there a way, from the commandline, without rebooting, to unload the already-loaded from /boot/loader.conf splash_image_data file, and load a different one in its place? `kldstat -v' seems to show nothing about the splash image that dmesg reveals as | Preloaded elf module "splash_bmp.ko" at 0xc03b709c. | Preloaded elf module "vesa.ko" at 0xc03b7140. | Preloaded splash_image_data "/boot/LOGOW.SYS" at 0xc03b71dc. Nextly, given that I have a few bitmaps of format 320 x 400 x 8, which seems to be rather far from the available VESA resolutions, I've hacked my splash_bmp.c k0deZ to scale images like /boot/LOGOS.SYS from 320x400 to full-screen, which actually seems to work and looks much better (for some definition of `better'). Is the general consensus that bitmaps should be displayed in their original size, also when less than the full screen is used or when a 320x400 image like /boot/logo.sys is displayed on 640x480 squished to half the `proper' width, or is there a demand for a swell-to-fit type of splash_bmp in addition, or instead? I can see how both are potentially a Good Thing... thanks, barry bouwsma To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
