From owner-freebsd-hackers  Sat Nov  9 06:49:16 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA01981
          for hackers-outgoing; Sat, 9 Nov 1996 06:49:16 -0800 (PST)
Received: from pdx1.world.net (pdx1.world.net [192.243.32.18])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA01973
          for <hackers@freebsd.org>; Sat, 9 Nov 1996 06:49:13 -0800 (PST)
Received: from suburbia.net (suburbia.net [198.142.2.24]) by pdx1.world.net (8.7.5/8.7.3) with ESMTP id GAA07318; Sat, 9 Nov 1996 06:49:00 -0800 (PST)
Received: (sendmail@localhost) by suburbia.net (8.7.4/Proff-950810) id BAA16030; Sun, 10 Nov 1996 01:48:42 +1100
Received: from profane.suburbia.net(203.4.184.222), claiming to be "profane.iq.org"
 via SMTP by suburbia.net, id smtpd16027aaa; Sun Nov 10 01:48:35 1996
Received: (from smtpd@localhost)
          by profane.iq.org (8.8.2/8.8.2) id BAA12293;
          Sun, 10 Nov 1996 01:48:40 +1100 (EST)
Message-Id: <199611091448.BAA12293@profane.iq.org>
Received: from localhost(127.0.0.1), claiming to be "profane.iq.org"
 via SMTP by localhost, id smtpd012289; Sat Nov  9 14:47:34 1996
To: Darren Reed <avalon@coombs.anu.edu.au>
cc: hackers@freebsd.org
Subject: Re: patches for nice text modes (170x48x16 etc) (syscons.c) 
In-reply-to: Your message of "Sat, 09 Nov 1996 18:39:22 +1100."
             <199611090923.UAA12140@profane.iq.org> 
Date: Sun, 10 Nov 1996 01:47:34 +1100
From: Julian Assange <proff@profane.iq.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


> So how would I use that patch ?

Apply the syscons patch to to syscons.c (against 2.2-current, but
even if it doesn't patch cleanly against earlier code, changes
needed to patch cleanly should only be cosmetic). Rebuild.

Apply the SVGATextMode text mode patches to SVGATextMode-1.4
(see my original message for the url). Compile.

Configuration is the same as with XFree in terms of
setting up mode-lines - just read the SVGATextMode docs, there
is plenty of really good material there, and you should have
a working TextConfig file with less hair pulling than X.

Sync pules are ULF and they re-radiate very poorly.  Creating a
cron which changes mode-lines randomly every half hour or so is a
good way to frustrate all but the most sophsticated automated van
eck monitors. Manned units are a different story, but your opponent
has to invest in lots of personel time.

Since I'm on this issue anyway, you can also choose your colour
palette so equal absolute voltage intensities are used on each
R,G,B line (check by cable merging - sometimes the there are voltage
biases in the colour seperation/generation hardware). Not a substitute
for the old aluminium wall paper and a big fat grounding stake, but
it does increase the cost and required fidelity of the van eck monitor.

If you have already set up X, then you can in many circumstances
use the X modelines under text mode. This can be pretty neat
if your graphics card can pull the character data fast enough
(ET4000's always can. Other cards have lower max dot clocks for
text modes than graphics modes. My S3-trio-64 can do around 87Mhz)
as you can swap back and forth between text mode and X-mode without
any delay for monitor re-syncing.

-Julian