*BSD News Article 14344


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!usc!elroy.jpl.nasa.gov!nntp-server.caltech.edu!glt
From: glt@cco.caltech.edu (Greg Tanaka)
Newsgroups: comp.os.386bsd.questions
Subject: Re: 386BSD vs Linux
Date: 12 Apr 1993 04:07:04 GMT
Organization: California Institute of Technology, Pasadena
Lines: 30
Message-ID: <1qapt9INNg49@gap.caltech.edu>
References: <1q7ot2$guo@sunb.ocs.mq.edu.au> <1q87cpINNfql@gap.caltech.edu> <1q8bg3$1rju@hal.gnu.ai.mit.edu>
NNTP-Posting-Host: punisher.caltech.edu

mycroft@hal.gnu.ai.mit.edu (Charles Hannum) writes:


>olvwm uses the (free!) `xview' toolkit, which runs on almost any system
>which runs X.
I must be looking in the wrong places, where is olvwm for 386bsd?


>>	a working TCX which compresses the binaries

>Seems to work fine under 386BSD.
Hmm..I tried compiling it but it failed no matter what I did..

>>	Working virtual consoles with automatic vga card recognition.

>I've been using syscons 0.1 for a long time.  Besides fixing one
>egregious bug (it *was* alpha-test software...) it's been working just
>dandy.  Virtual consoles are here.
I am using syscons .2.  For me, the ansi termcaps that came with it seem to
not work at all..  However, I did find that the at386 termcap works a lot 
better..but still not as stable as it would be in NCSA telenet and dos..

>PCFS for 386BSD has been around for a long time, too.
Really? Wow.. I guess I have to look for that also.. 

-Greg Tanaka
glt@ccotech.edu
glt@ugcs.caltech.edu
glt@macross.caltech.edu (My rather unstable 386bsd machine)
p.s.  May be I was wrong about 386bsd