From owner-freebsd-hackers Sun Jan 11 18:26:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA08637 for hackers-outgoing; Sun, 11 Jan 1998 18:26:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA08313 for ; Sun, 11 Jan 1998 18:23:03 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id MAA00815; Mon, 12 Jan 1998 12:46:03 +1030 (CST) Message-Id: <199801120216.MAA00815@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: mika ruohotie cc: hackers@FreeBSD.ORG Subject: Re: Splash screen (splashkit) for 3.0 systems... In-reply-to: Your message of "Sun, 11 Jan 1998 16:02:18 +0200." <199801111402.QAA02310@shadows.aeon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Jan 1998 12:46:02 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > > Mike Smith: > > I'm also interested in seeing if a few things I found in the 2.2 version > > were/will be addressed. E.g.: > > > > - Splash should auto-dismiss itself when booting gets to the syscons > > login prompt (i.e. not running xdm) > > why not make it a user selectable? That'd be pretty straightforward; I'd suggest an rc.conf option to change the "running" splash, either "NO" (do nothing), "CLEAR" (remove the splash) or the path of a new splash to put up once the system was up. > so that a user would be able to choose an option where the splash is > left after the boot complites, maybe even putting on another image > all together, and until some special key combination (user definable) > is pressed, leave it at that. the key combination would drop it to the > normal syscons login. wouldnt hurt having that key comb being predefined. It is already; any VT switch will clear the splash, and there's a keymap token for toggling it back. I was considering the "window" key, actually, although that leaves out a lot of people with older keyboards... > that would be _very_ usefull for me for those customer firewall setups, > all the customer needs to know is if the system is up and running or > not, they dont need to be able to log in. to many people nowadays a > nice image on screen looks more "convincing" than a black login screen, > i'd assume many people considering "non gui" looking somewhat "old". Sure. Colour cycling will happen post-boot as well, as there are timers available at that point. > yes, i'd do that myself if i'd know how, maybe i know, it just sounds > too complicated for me. Not really. Syscons is a bit of a monster, but not *that* bad. I'm certainly more than open to suggestions, diffs, whatever. > pssss. yes, i can test things in at least one of my current machines Please do, if you get a chance. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\