From owner-freebsd-hackers Wed Mar 20 13: 9:58 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (pop-be-15-1-dialup-238.freesurf.ch [194.230.14.238]) by hub.freebsd.org (Postfix) with ESMTP id 828BE37B435 for ; Wed, 20 Mar 2002 13:09:38 -0800 (PST) Received: from beerswilling.netscum.dyndns.dk (dcf77-zeit.netscum.dyndns.dk [172.27.72.27] (may be forged)) by dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (8.11.6/8.11.6) with ESMTP id g2KJ4lJ03919 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified FAIL) for ; Wed, 20 Mar 2002 20:04:51 +0100 (CET) (envelope-from bounce@netscum.dyndns.dk) Received: (from root@localhost) by beerswilling.netscum.dyndns.dk (8.11.6/8.11.6) id g2KJ4lF03918; Wed, 20 Mar 2002 20:04:47 +0100 (CET) (envelope-from bounce@netscum.dyndns.dk) Date: Wed, 20 Mar 2002 20:04:47 +0100 (CET) Message-Id: <200203201904.g2KJ4lF03918@beerswilling.netscum.dyndns.dk> From: BOUWSMA Beery Subject: Silly splash! questions To: hackers@freebsd.org Organization: Men not wearing any pants that dont shave X-Hacked: via telnet to your port 25, what else? X-Internet-Access-Provided-By: Slow Dial-in Modem X-NetScum: Yes X-One-And-Only-Real-True-Fluffy: No Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message