HDTenEightyP/NetNews huggingface dataset:
From: paoletti@cps.msu.edu (David R. Paoletti)
Subject: Tape drive choices for 386BSD?
Originator: paoletti@pacific.cps.msu.edu
Organization: Dept. of Computer Science, Michigan State University
Date: Sun, 30 Aug 92 08:13:19 GMT

I'm about to upgrade to a 486-50, but don't have an unlimited
amount of money to spend.  I'd like to get a tape drive that is
(will be) compatible with 386BSD.  I've read the "unofficial"
FAQ statement about Wangtek tape drives, but don't want to spend
the money required to purchase a Wangtex 5150 (at least $800
with a SCSI controller).

I'd rather buy a simple QIC-80 such as a Colorado 250 for about
$250.  Is someone working on support for drives of this type?

What about other, less pricey tape drives that will (hopefully)
be supported in the near future?

Thanks,
  Dave Paoletti :)

Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: Where is comp.unix.bsd archived ???
Date:  2 Sep 92 14:58:12 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <1992Sep2.115555.5386@rtpnc.epa.gov> fty@bizarre.rtpnc.epa.gov (Frank Terhaar-Yonkers) writes:

>In article <Btx1G2.4t2@world.std.com>, Stuart J Adams writes:
>Is there an archive site for comp.unix.bsd ???


>I maintain a "culled" archive at: 

>	sunvis.rtpnc.epa.gov:~/pub/386bsd/culled.news


>-- 
>-------------------------------------------------
>Frank Terhaar-Yonkers	fty@bizarre.rtpnc.epa.gov
>Unisys/U.S. EPA		(919)541-2297

ftp.uni-duisburg.de (134.91.4.132) has a subdir, where many patches from the
net community, that were posted to comp.unix.bsd, are stored. This is 
/pub/unix/386bsd-0.1/unofficial/patches/*.* . As the name 'unofficial' suggests,
there is absolutely no warranty, nor is the list complete, bugfree, sorted,
free of conflicts, etc. and not for the casual 386bsd user; with one word: 
dirty ;-)
This host, however, does not save the articles (there has been too much junk
with AT&T and USL in the subject lines :-(

Holger

-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
From: alexei@reef.cis.ufl.edu (Alexei Rodriguez)
Newsgroups: comp.unix.bsd
Subject: BSD help and direction...
Summary: Looking for docs and FAQ
Date: 4 Sep 92 00:28:45 GMT
Organization: Univ. of Florida CIS Dept.

Hello. I have been following the Linux and BSD conferences
for the past week or so and I am desperately in need of 
"direction". I would like to read the FAQ's for both OS's
but have been unable to find either. Could anyone point
out the differences and how they vary? Also, where I may FTP
the code from and any docs that users may have prepared would be more
than helpful. A summary will follow, as usual.

Thanks...

	Alexei


Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Compiling 386bsd-0.1 on < 40Meg ( I've done it)
Organization: Weber State University  (Ogden, UT)
Date: Sun, 30 Aug 92 21:00:15 GMT

In article <colin.715158768@marsh> colin@marsh.cs.curtin.edu.au (Colin Manning) writes:
>	Now that I've compiled the kernel, how do I make a bootable floppy?

	I need to put this in the FAQ.  The procedure is as follows:


1)	Make a copy of dist.fs or fixit.fs, whichever you prefer.
2)	Mount it on /mnt, using:

		mount /dev/fd0a /mnt

3)	Delete the previous kernel on the floppy:

		rm /mnt/386bsd

4)	Make sure you are in the compilation directory (where you made
	your new kernel).
5)	Make sure there is no symbol table on your kernel, or it will be
	too big to fit.  From the compilation directory:

		strip 386bsd

6)	Copy the new kernel to the floppy:

		cp 386bsd /mnt/386bsd

7)	Type sync:

		sync ; # 8-)

8)	Unmount the floppy:

		umount /mnt

9)	You now have a new bootable disk with your new kernel.


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                                       terry@icarus.weber.edu
 "I have an 8 user poetic license" - me
-------------------------------------------------------------------------------
From: guido@gvr.win.tue.nl (Guido van Rooij)
Newsgroups: comp.unix.bsd
Subject: Cgd's boot floppies
Date: 27 Aug 92 19:00:49 GMT
Organization: Guido's home 486 box

I wondered it the boot floppies, e.g dist.fs-noIS, made by CGD also
have tehe patch to allow a second fixed disk to be installed.
If not, is there a fixed kernel out there having both that patch and
all other vital ones in it? 

-Guido
-- 
Guido van Rooij            /        internet: guido@gvr.win.tue.nl
Bisschopsmolen 16          \        phone: ++31-40461433
5612 DS Eindhoven          /
The Netherlands            \
Newsgroups: comp.unix.bsd
From: juengst@boss1.physik.uni-bonn.de (Henry G. Juengst)
Subject: Re: Easy Install for 386bsd with more swap space!
Organization: Universit"at Bonn, Informatikinstitut, R"omerstr 154, W-5300 Bonn 1
Date: Fri, 28 Aug 1992 18:59:41 GMT

In article <1992Aug28.040755.2247@lugb.latrobe.edu.au>, lurch@ee.latrobe.edu.au (Geoffrey Liersch) writes:
> Here is an easier way to install 386bsd with a larger swap space and/or
> a real partitioning scheme.  
> 
> NOTE:  Steps marked with a (*) can be skipped if a separate usr partition
> is not required!
> 

It could be interresting to use the install procedure to get the disktab
values. So I would say:

  0.    Boot install disk, install just to init your hard disk.

> 1.	Boot the fixit.fs floppy.
> 2.	Make the floppy writable:
> 		mount -u /dev/fd0a /
> 3.	Make some space on the floppy:
> 		rm [A-Z]*

  3a.   Make a file with disk parameters:
        disktab -r wd0a >/tmp/disklabel.log
        cat /tmp/disklabel.log

> 4.	Make a disktab entry with a seperate usr partition if needed:
> 		vi /etc/disktab

        Use information found in /tmp/disklabel.log. That makes it a little
        bit easier.

> 5.	Disklabel the hard disk:
> 		disklabel -w -r wd0 "drivename"
> 6.	Prepare the root partition:
> 		newfs /dev/rwd0a
> 7.(*)	Prepare the usr partition if necessary:
> 		newfs /dev/rwd0h		
> 		mount /dev/wd0a /mnt
> 		mkdir /mnt/usr 
> 		mkdir /mnt/sbin
> 		mkdir /mnt/dev
> 		cd /usr/distbin
> 		ls *mount | cpio -pdalmu /mnt/sbin
> 		cd /dev
> 		ls * | cpio -pdalmu /mnt/dev
> 8.	Shutdown and remove the fixit.fs floppy:
> 		shutdown
> 9.	Boot the dist.fs floppy.
> 10.	Mount the root partition:
> 		mount /dev/wd0a /mnt
> 11.(*)	Mount the usr partition if necessary: 
> 		mount /mnt/dev/wd0h /mnt/usr
> 12.	Install the binaries:
> 		zcat /etc/baselist.Z | cpio -pdalmu /mnt	
> 		cd /mnt
> 		zcat /etc/baseutils.cpio.Z | cpio -idalmu
> 13.	Shutdown and remove the dist.fs floppy:
> 		shutdown
> 14.	Boot off the hard disk.
> 15.	Make the root partition writable:
> 		mount -u /dev/wd0a /
> 16.(*)	Mount the usr partition if necessary:
> 		mount /dev/wd0h /usr
> 17.	Read the install notes in the root directory:
> 		zmore INSTALL.NOTES
> 18.	(i)  If you have not got a seperate usr partition the install the 
> 	     binary and other distributions as per the INSTALL.NOTES.
> 	(ii) If you have got a seperate usr partition then install the binary
> 	     distribution as follows:
> 		mkdir /usr/tmp
> 		cd /usr/tmp
> 	     Get the binary distribution to here as per the INSTALL.NOTES.
> 		cd /
> 		cat /usr/tmp/bin01* | uncompress | cpio -idalmu
> 		sh /tmp/install.bin01
> 19.	Create the file /etc/fstab:
> 		vi /etc/fstab
> 	and add the following line(s): 
> 		/dev/wd0a	/	ufs rw 1 1
> 		/dev/wd0h	/usr	ufs rw 1 2 
> 20.	Get to work!
> 
> I hope that this is helpful to someone.
> 
> Lurch
> 
> lurch@ee.latrobe.edu.au

Henry

-- 
juengst@boss1.physik.uni-bonn.de [131.220.221.30]
juengst@saph2.physik.uni-bonn.de [131.220.221.12]
juengst@pib1.physik.uni-bonn.de  [131.220.221.2] (strange particle)

I'm only speaking for myself, but not for anybody else !
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: X386 and Diamond Stealth: not solution
Date: Fri, 04 Sep 92 01:45:55 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

In article <9460@emory.mathcs.emory.edu> sb@next.neuro.emory.edu writes:
>> 
>> I had just made up my mind to buy a Diamond Stealth when I heared about  
>all
>> this trouble. Well, I am looking for cards from other vendors now.
>> So maybe you should give them a list of people who are _not_ going to  
>buy a
>> card from them, unless they change their policy.
>> If you are doing so feel free to put my name on it.
>> -- 
>> Andreas Klingler
>> asklingl@informatik.uni-erlangen.de
>>        I'd love to help you out... Which way did you come in?
>
>
>  I was just about to buy a Diamond Stealth also, but not now that
>I've heard about diamond's uncooperative attitudes.  With the rate
>that technology changes these days, you'd think that companies
>couldn't afford these kinds of policies.
It would help a lot if people would call up Diamond and express
politly their opinion. For instance, I explained to a Diamond
marketing person why I was taking my Stealth back - I can't
write an X11R5 device driver to your card because you use
a propieratory mechanism for setting the clock values on the Stealth.

Also, be aware that future Diamonds svga cards not just the Stealth
will not be supported by X386 due to their new novel way of setting
the clock values.

So call or write to Diamond, if you want to enjoy Diamond products.

From my view, Diamond's strategy poses a bad precedence.

Amancio Hasty

>
>
>
>  Steve Berger (sb@onripx.neuro.emory.edu)


Newsgroups: comp.unix.bsd
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: Re: How download X386 to floppies?
Organization: Nanyang Technological University - Singapore
X-Newsreader: Tin 1.1 PL4
Date: Fri, 28 Aug 1992 01:18:42 GMT

allard@isi.edu (Dennis Allard) writes:
: My goal: create a set of floppies with the X386 distribution on them
:          and then extract that distribution onto my 386BSD.
: 
: My situation:
: 
:   At home: 386BSD binary distribution up and running on a 386-33 clone
:   At work: HP-UX and SunOS workstations, one which has a floppy drive
: 
: I have already ftp'd the files core-{bin,server,fonts,inc,lib,man}-1.0.3.tar.Z
: from agate.berkeley.edu to a fileserver at work.  How can I create a
: multivolume set of floppies which I can then use to install X on my 386 at
: home?
: 
: I cannot use MCOPY to move the files to floppies as each one is far too big
: to fit on a single floppy.  This has GOT to be a simple problem, what am
: I missing (besides a Unix User's guide, something which two decades of
: Unix users have missed)?

Please do read my article on multivolume tar.
: 

In your case, first you need to insall the GNU tar 1.10 . I do not think that
the Sun tar can do multivolume, why don't you check with man tar.

If you have GNU tar 1.10, you do the following commands

tar cvMf /dev/rfd0 {file to archive} 


; note that I forgot Sun floppy device name
; I recommend that you archive each file separately to prevent one error
; affecting all the others

; to verify

tar -tvMf /dev/rfd0


; to extract to 386bsd without copying the files first

tar -xvMOzf /dev/rfd0a | tar xvf -

; warning: I have problems with links


I've not done this personally, I hope you can try and tell us about it.

--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet
From: wjolitz@soda.berkeley.edu (William F. Jolitz)
Newsgroups: comp.unix.bsd
Subject: Re: More on NMI problems.
Date: 4 Sep 1992 18:26:47 GMT
Organization: U.C. Berkeley, CS Undergraduate Association
NNTP-Posting-Host: soda.berkeley.edu

In article <1992Sep2.123248.17492@ponds.uucp> rivers@ponds.uucp (Thomas David Rivers) writes:
>Well, I got much advice on my NMI problems; indicating that I probably
>did, in fact, have a bad memory chip on my machine.
>So; I grabbed testext.exe from SIMTEL20 and let it have at the machine,
>to determine which chip was bad, etc....

I missed your earlier inquiry, but I thought I should post a notice
regarding "trap 19" problems.

In particular, a student in Linkoping University sent me a fax regarding
a problem with booting: he would get a "trap type 19 code..." message
and the system would panic.

Trap type 19 indicates an nmi trap (see trap.h). In this particular
case, the problem was localized to the motherboard (a 486DX 33MHz ISA,
made in Taiwan).

There are two possibilities in this situation:

1. Bad memory parity. This could be a bad memory chip (run memory tests
to confirm). However, it should be noted that some cheap boards have
BIOS's which do not initialize memory correctly. In this case, one must 
clear memory blindly BEFORE touching it. If it is an inadaquate board,
one might want to get a better (in-spec) one and use the other one for
MS-DOS.

2. There is a difference between "expanded" (e.g. LIM) memory and 
"extended" (e.g. above 0x100000) memory. If any memory is allocated
to "expanded" memory, then problems will occur.

A number of people are experiencing 1) and 2) and have written me 
accordingly. I hope this helps isolate a few of those "mystery" problems.

Lynne Jolitz.
Newsgroups: comp.unix.bsd
From: goran@astro.uu.se (Goran Hammarback)
Subject: Re: [386bsd] Virtual memory exhausted. Do I need more swap?
Organization: UDAC, Uppsala, Sweden
Date: Fri, 28 Aug 1992 12:40:24 GMT

In article <david.714981284@mlb.geomechanics.csiro.au>, david@mlb.geomechanics.csiro.au (David Le Blanc) writes:
|> When compiling some programs with GCC, I get the message 'virtual memory
|> exhausted'. I have 40Meg virtual memory, so I am sure that is not the problem.
|> 
|> Is there a setting with GCC which I should raise or what??

You have probably encountered a software limit on memory.

In csh (maybe also in the other shells, but I use csh (well, actually
tcsh 8-) )) there is command named limit.  I'm not at my 386BSD computer
now, so I'm not sure of the names,  but do limit and look for things that
may be called: stacksize, datasize, and memoryuse. 
Increase these values as wanted.

-- 

Goran

------------------------------+---------------------------------
Goran Hammarback              |     goran@astro.uu.se
Astronomiska Observatoriet    |
Uppsala Universitet           |
S-751 20 SWEDEN               |
------------------------------+---------------------------------
From: tj2n+@andrew.cmu.edu (Tao Jiang)
Newsgroups: comp.unix.bsd
Subject: SLIP
Date: 27 Aug 92 12:57:35 GMT
Article-I.D.: andrew.UebI6z200WB_AZuV96
Organization: Doctoral student, Statistics, Carnegie Mellon, Pittsburgh, PA


Hi, neters,

I want to connect my PC (using 386bsd) at home to the computer
at university via slip, which software can I use?  How to use it?

Thanks!
Newsgroups: comp.unix.bsd
From: husemann@camelot.informatik.uni-erlangen.de (Dirk Husemann)
Subject: Re: virtual tty's for 386bsd ?
Organization: CSD., University of Erlangen
Date: Sat, 29 Aug 1992 14:07:03 GMT

nickel@cs.tu-berlin.de (Juergen Nickelsen) writes:
>Since you are in Germany, the best place for getting iScreen should be
>its "home" server, ftp.informatik.uni-erlangen.de. It requires some
>searching though, the directory structure on this server is like they
>want to hide their software. :-)

Sure wanna do that 8=) If it were too easy you'd be missing the sense of adventure, of
searching the unknown, and of finding the unexpected 8=9

Sigh, I'm aware of the sorry state of our directories on ftp.uni-erlangen.de but like many
other things cleaning it up is lingering on my eternal list (maybe after I get X.25/LLC2 for 4.4 
BSD running, get an ISDN driver working, ... 8=)

>Be sure to get the latest version (3.2, if I didn't miss one), since
>scrollback buffers are not in 3.1. (Cut & paste is, but scrollback is
>nice!)  Juergen Weiger seems to put one new feature into each version.
>I like it very much, though I use it only with SunOS and 4.3 BSD, not
>with 386bsd.

It definitely is worth installing --- I've got it running like a charm on BSD/386 right now.

Dirk
---

Newsgroups: comp.unix.bsd
From: mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Subject: How to extract X386
Organization: University of Western Ontario
Date: Fri, 4 Sep 1992 15:51:25 GMT

I am new to bsd.  I have been able to download the file, and create a
working bsd machine on the first try.  The networking works fine also.
The X386 files are named differently than bin01, etc01, ....

How does one extract these files?


mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Western Business School  --  London, Ontario
Newsgroups: comp.unix.bsd
From: u342222@twncu865.ncu.edu.tw
Subject: How to install X386 on 386bsd ?
Organization: Computer Center, NCU, Taiwan, R.O.C.
Date: Wed, 26 Aug 1992 08:41:34 GMT

Dear Sir:
	I install 386bsd on my pc-386, with 8M RAM. But I don't know
how to install X386 server on my PC. Please tell me how to install,
and detail installation guide. I try many times, but I failed.
BTW I use ET-4000 card.
	Thank you very much!

Sheng

Newsgroups: comp.unix.bsd
From: david@mlb.geomechanics.csiro.au (David Le Blanc)
Subject: Re: X386 & Keyboard
Organization: CSIRO DIT (Melb.)
Date:  2 Sep 92 04:55:45 GMT

joergens@snorre.informatik.uni-dortmund.de (Ulrich Joergens (PG211)) writes:

>I have the following problem:

>starting xdm from /etc/rc (as last entry) my keyboard is ignored.

Did you remove the line in your /etc/ttys which specified the console 
(or 'vga' is more correct) as a getty line?

You must remove the 
'console "/usr/bin/getty pc2" on secure'
line to stop the getty grabbing control of your keyboard.


I may be wrong though... :-)
--
David Le Blanc                         :
Email: david@mlb.geomechanics.csiro.au : `Sort of a cross between a Jaguar
CSIRO Division of Geomechanics,	       :  and a freight train.' the Alien
P.O. Box 54 Mt Waverley 3149	       : in Alien^3.
From: goran@astro.uu.se (Goran Hammarback)
Newsgroups: comp.unix.bsd
Subject: Re: whereis /tmp/install.src0?
Date: 28 Aug 92 12:05:13 GMT
Organization: UDAC, Uppsala, Sweden

In article <22278@venera.isi.edu>, allard@isi.edu (Dennis Allard) writes:
|> ==================================
|> Short version of my question:
|> /tmp/install.src0 evaporated.  How can I recreate it?  I still
|> have all the src01.* files in /tmp.  And the extraction went
|> completely through it's first phase.  It now simply needs to
|> execute /tmp/install.src0, I believe.
|> 
|> ==================================
|> (very) Long version of my question:
    [Deleted]

Easy, it's not there!  There is no /tmp/install.???? for either
the src or etc distribution (probably because no extra setup stuff
is needed, for the bin distribution it sets host name and makes devices).

-- 

Goran

------------------------------+---------------------------------
Goran Hammarback              |     goran@astro.uu.se
Astronomiska Observatoriet    |
Uppsala Universitet           |
S-751 20 SWEDEN               |
------------------------------+---------------------------------
Newsgroups: comp.unix.bsd,comp.sys.sun.hardware,comp.protocols.tcpip
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject:  news software
Keywords:  rn nn news inn
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Sun, 30 Aug 92 19:11:06 GMT


Anyone gotten the usenet news directory from agate to work?

I got the whole bunch and tried blue eyed:


Got several problems and finallay gave up.

The most severe problems were:

- test: too may arguments

- lint missing. BTW, is lint still 'encumbered'? Or is there a GNU lint that
   might help?

- /usr/include/sys/resource.h is missing an entry RLIMIT_NOFILE

Anyone got through these weirdnesses ?

--Chris
-----------------------------------------------------------------
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.
From: lwall@netlabs.com (Larry Wall)
Newsgroups: comp.unix.bsd
Subject: Re: backup w/ compression for UN*X?
Date: 3 Sep 92 17:29:07 GMT
Organization: NetLabs, Inc.

In article <dtb.715502483@otto> dtb@otto.bf.rmit.oz.au (David Bath) writes:
: paoletti@cps.msu.edu (David R. Paoletti) writes:
: Remember - very few UNIX commands do everything, but they can be
: hooked together easily.  I guess the exception is perl(1) and
: probably cpio [-alphabet] :-)

Perl can be hooked together easily.  I dunno about cpio...  :-)

Larry Wall
lwall@netlabs.com
Newsgroups: comp.unix.bsd
From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
Newsgroups: comp.unix.bsd
Subject: no screen after X exits
Date: 2 Sep 92 10:10:13
Organization: Kansas State University
NNTP-Posting-Host: maverick.ksu.ksu.edu

I'm having a problem with having no screen after X exits.  This is really
annoying when something is wrong and X doesn't start since one of the first
things it does is set the graphic mode on the card.  I have to reboot to
get the screen back and then I loose any information I had as to why X
didn't start.

My configuration is:

386sx/16
8M RAM
7120A Maxtor IDE
2 com ports
Sigma Legend 1M VGA (ET-4000 chipset)
AOC CM-336 SVGA monitor

I can get X to run fine and can even get at the keyboard by doing a
'startx;sleep 999999' (anyone want to tell me why this works?).  I am
planning on running XDM in the future, but I want to get X to where it
actually works like I want it before doing this.

Is there a program out there that resets the video card to standard
80x25 text mode?

++Brett;
Newsgroups: comp.unix.bsd
From: hsu@pix.com (Dagwood Splits the Atom)
Subject: Re: ecinit on ifconfig
Organization: Pix -- The company with no adult supervision.
Date: Wed, 26 Aug 1992 04:43:34 GMT

In article <BtKCLH.B3o@ibmpcug.co.uk> adrian@ibmpcug.co.uk (Adrian Hall) writes:
>>> Apparently a "scalpel" left in the code (ifconfig or ec-driver). Try
>>> ifconfig with a redirection to /dev/null to identify whether it is in
>>> the driver or in ifconfig.
>>No. You won't see any error message anymore. Try to find the message
>>"ecinit" in the kernel and patch it (e.g. using any DOS disk tool).
>Gee, And I thought 386BSD came with full kernel sources.

It does, of course.  Geez.  The offending code is line 264 of if_ec.c,
and can be easily recognized by its lack of indentation.

And the fact that it says, in its entirety, `printf ("ecinit");'

Is anybody else running X386 with the Keypro (Focus) FC9000 keyboard?
The FC9000 seems to be remarkably buggy, particularly where the pf keys
are concerned.  Programming ctrl-alt-+ results in the following sequence,
according to xev:

	keypress Control-L
	keypress Alt
	keyrelease +	(!)
	keypress +
	keyrelease Alt
	keyrelease Control-L

I may have the last two reversed, but the gist of it is that the plus
key gets its events swapped, defeating the utility of that sequence for
cycling display modes.  My usable workaround is to use Control-R and
Alt-R (actually Meta); the events will then occur in the correct order.

cheers,

-dave

-- 
Dave Hsu                           <hsu@pix.com> -or- <hsu@eng.umd.edu>
Caffeine and Salsa Czar	          "Yeah?  Well there are a lot of people out
Pix Technologies Corporation       there who are full of shit and making money.
Have nerds, will telnet.           And *I'm* not going to be the exception."
Newsgroups: comp.unix.bsd