From owner-freebsd-hackers Tue Nov 7 12:42:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 0932F37B479 for ; Tue, 7 Nov 2000 12:42:32 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id eA7Kg3w16327; Tue, 7 Nov 2000 14:42:03 -0600 (CST) (envelope-from dan) Date: Tue, 7 Nov 2000 14:42:02 -0600 From: Dan Nelson To: Dag-Erling Smorgrav Cc: Graham Wheeler , freebsd-hackers@FreeBSD.ORG Subject: Re: Help writing a screen saver module Message-ID: <20001107144202.B4569@dan.emsphone.com> References: <3A06B7A7.7665C46A@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from "Dag-Erling Smorgrav" on Tue Nov 7 18:03:39 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 07), Dag-Erling Smorgrav said: > Graham Wheeler writes: > > I am trying to write a screen saver module that, when it kicks in, > > will switch to the first console, and then, if a key is pressed, > > will switch back to the one that was previously active. The idea is > > that the first console has something useful running on it, > > typically a tail -f of the logs. > > Switching consoles causes syscons to stop the screensaver, which > causes your code to try to switch back to the original console, which > causes syscons to stop the screensaver since seems to be running. In > other words, Don't Do That. Sorry. You can make it look like you're switched to vty 0, by making your screen_saver() function simply copy the contents of vty 0 to screen memory on every update. Just make sure both vtys are the same size first... -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message