*BSD News Article 4754


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!darwin.sura.net!wupost!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!ira.uka.de!math.fu-berlin.de!zrz.tu-berlin.de!cs.tu-berlin.de!engel
From: engel@opal.cs.tu-berlin.de (Christian Engel)
Subject: X386 xdm with crypt, other tools, printer EXPERIENCES
Message-ID: <1992Sep9.122332.22785@cs.tu-berlin.de>
Summary: xdm compiled with crypt.cgd code available 
Keywords: xdm X386 crypt lpt.c
  
Sender: news@cs.tu-berlin.de
Organization: Techn. University of Berlin, Germany
Date: Wed, 9 Sep 1992 12:23:32 GMT
Lines: 81

ftp.cs.tu-berlin.de

Directory:

pub/os/386BSD/386bsd-0.1/unofficial/local/xdm-crypt.engel.Z


Btw, I was able to compile the following software:

gnu find3.7
gnu make3.62
gnu gcc2.2.2
gnu libg++2.2 (libg++.a, iostream, stdio++)
gnu emacs18.58
gnu epoch4.1pl0
gnu texinfo2.15
gnu readline1.1
gnu bison1.18
xdviPl15
bricons
xtexcad1.2
xfig
xmenu


Kernel Patches
==============

I patched my kernel with the Unofficial Buglist (patches.tar.Z), new.com.cgd,
crypt.cgd, lptWithoutInterrupts, BusmouseV2, dmaFix, GreenmanFix (w/out no 5, I
think), ttyFix, ...
Since then I have no problems with crashing kernels anymore.


Printer Support
===============

I had many problems using the original lpt.c driver although patched with
lpt-haugh and the lp.c drivers.
Printing of normal ascii files was ok using the lp.c driver. But when I tried to
print a .dvi-djc file (Deskjet 500 output from dvi), character losses and even
crashes (lpt.c) occurred.
Switching off the printer caused a reboot.
I could solve the problem for lpt.c using an output filter, that flushed the
output and waited for a while (usleep) after a certain amount of characters were
sent to the printer.
I didn't need to use this filter for the new version of lpt.c that does busy
waiting.


X386
====

I am using one of the binary versions that were supplied. In the beginning I
used a serial mouse. In the beginning the mouse wasn't read properly. I worked a
bit on this problem using a mouse-test programme supplied with X11 for Linux,
that I had to change  a bit and figured out, that the terminal
characteristics weren't set properly.
The same seemed to occur with the X386 kernel.
Therefor I included an ``stty cs7 ...'' line into my .xinitrc and
/usr/lib/X11/xdm/Xsetup_0 and then the mouse worked fine. 




I hope these remarks help others to solve some of there problems with 386bsd.
If you want to have more information or other binaries made available, feel free
to contact me.


	Christian  (engel@cs.tu-berlin.de)





--
Christian Engel, TU-Berlin 	             mail: engel@cs.tu-berlin.de
TFS, dept of theoretical computer science,  formal specifications
address:   TU-Berlin, FR6-1, Franklinstr. 28/29, 1000 Berlin 10, Germany