HDTenEightyP/NetNews huggingface dataset:
From: ah200@cleveland.Freenet.Edu (Randy Beiter)
Newsgroups: comp.os.linux
Subject: mush/mud binary, need source
Date: 2 Jan 1993 22:04:51 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Reply-To: ah200@cleveland.Freenet.Edu (Randy Beiter)
NNTP-Posting-Host: slc12.ins.cwru.edu


I'd like to thank the person who uplaoded the binary for tinymush, and I
was wondering if they had uploaded iether the source code or the diffs for
the changes to get it to run on linux - I'd like to play with the source
code. Thanks much in advance!
-- 
         __  __      ___              _ _ _ _ _ _ _           __________
I I\ /I (_  I__) I    I  I\ I on the I - - - - - -  // I  o) /  Ah200   \ (o  I
I I V I (__ I \, I__ _I_ I \I  IRC   I  O n l y \\ //  I (X  Randy Beiter  X) I
I_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-I A m i g a \X/   I / \ \__________/ / \ I
Newsgroups: comp.os.linux
From: andrewc@aurora.cc.monash.edu.au (Andrew J. Cosgriff !)
Subject: Re: MUDS on a Linux?
Keywords: Linux, MUDS
Organization: Monash University, Melb., Australia.
Date: Sat, 26 Dec 1992 08:59:39 GMT

dhoelzer@hal.gnu.ai.mit.edu (David Hoelzer) writes:


>Has anyone succeeded in compiling and running ANY Mud or have a clue as to
>what my problem could be.

Well, there's at least 3 or 4 different ones that have been ported to linux
 - The Lambda-MOO sources at parcftp.xerox.com compile with few problems,
   so there's no binary distribution for it (this is what I'm using, so if
   anyone wants binaries, let me know and I'll put em up)
 - TinyMUSH has recently been binaried and put up at sunsite and tsx-11
 - I think Diku and LP muds have been binaried also, but mentioned at the
   very least on this group...

 I can't be of much help with regards to TinyMUSH, LP or Diku muds, as I've
never even looked at them (I grabbed Lambda 'cause I heard it compiled cleanly)
so best of luck and happy new year !

Cos !
-- 
-------------------------------------------------------------------------------
 * Andrew J. Cosgriff ! *                   #include <std_witty_quote.h>
#define HERE cc.monash.edu.au               #include <std_disclaimer.h>
Hassle me at :      andrewc@aurora.HERE ; andrewc@lindblat.HERE ; cos@yoyo.HERE
From: lmfken@lmf.ericsson.se (Kenneth Osterberg)
Newsgroups: comp.os.linux
Subject: Re: 2 X problems (.xinitrc and Xview)
Date: 1 Jan 93 17:17:09 GMT
Organization: Oy LM Ericsson Ab, Jorvas, Finland

STDN%MARIST.bitnet@YaleVM.YCC.Yale.Edu (Dan Newcombe) writes:
>HI all...  I am having two problems with X.  The first is that
>X will not come up if I have a .xinitrc.   Without it, I have no
>problems, but as soon as I create one I get the following error.

>xinit:  Interrupted system call (errno 4):  Client error.

>But this happens even if I comment out all of the lines in
>.xinitrc   My .xinitrc looks like...
>OPENWINHOME=/usr/openwin; export OPENWINHOME
>PATH=$PATH:$OPENWINHOME/bin
>HELPPATH=$OPENWINHOME/help; export HELPPATH
>if  -z "$MANPATH" |; then
>MANPATH=/usr/local/man:/usr/man; export MANPATH
>fi
>MANPATH=$MANPATH:$OPENWINHOME/man
>twm &

>I don't understand as all except for the last line was taken
>straight from the README for XView, which is my next problem.

The README also states that you probably lose if you use Xview apps
without running an OpenLook compliant WM. Use olwm or olvwm.
The OPENWINHOME stuff in your .xinitrc is needed for Xview apps, if
you use twm you won't need any of the above. Xview apps won't work,
of course.

>I had this problem before and I did something that made it
>work.  Only problem is I don't know what I did.  Anyway,
>when I enter all the commands in my .xinitrc by hand
>and run olwm instead of twm, XView starts up.  My background
>turns blue and it opens a window that has a width of half the
>screen and seems to go on forever lengthwise.  I can grab the
>handles and window and reposition and resize it, but that's about
>it.  Also, it I click my right mouse button for my control
>panel, all I get is a white line about 1" thick that goes the
>length of the whole screen.  When I ran olwm these are the
>errors I got.  Sorry it's so long but I'd rather be complete.
>any help is very needed.  Thanks, and happy new year...
[errmsgs deleted...]

Probably some kind of configuration error. Check out the .Xdefaults
and .openwin-menu in your home directory, try renaming them (if you
have them). If there is still a problem, look in
/usr/openwin/lib/openwin-menu, get the default ones from the xview package
if necessary. 

The error messages you listed could mean you have a font problem. Try
running mkfontdir in all font directories (/usr/X386/fonts/*).

Hope something of this helps...

/Kenneth
--
Kenneth Osterberg      lmfken@lmf.ericsson.se or lmfken@bluese1.ericsson.fi
From: alex@am.sublink.org (Alex Martelli)
Newsgroups: comp.os.linux
Subject: Re: Video mode problems: Want 80x25 display back
Date: 31 Dec 92 10:11:40 GMT
Organization: Premiata Famiglia Martelli & Figli

dld54032@uxa.cso.uiuc.edu (Dave Dribin) writes:
	...
:>   I have just installed SLS Linux v0.99.  While installing it I used
:>the standard 80x25 display.  Now whenever I boot up, I get sent into
:>some other mode.  The print is a lot smaller.  I think it is 132x43,
:>but I haven't counted.  I was wondering how to change this.  I looked
:>at all previous posts and found no answers.  Thanx in advance.  Any help

I had the same problem.  LILO 0.7's "vga=" parameter fixed it; I had
no luck using rdev's -v switch, which *should* also work.


Alex
-- 
Alex Martelli - alex@am.sublink.org - +39 (51) 250434 - Bologna, Italia

DON'T worry about rutgers' ***"Waiting mail"*** warnings, your mail WILL
get here UNLESS you get a ***"Failed mail"*** message from them!!!
From: loser@clueless.newbie.tyro.org
Newsgroups: comp.os.linux
Subject: Re: lpd needs listen & accept NOT IN SLS
Date: 3 Jan 93 17:45:56 GMT
Article-I.D.: wam.1993Jan3.174556.9868
Organization: Workstations at Maryland, University of Maryland, College Park
X-Newsreader: TIN [version 1.1 PL6]

listen and accept are system calls, not files, and they are part of linux.
Also the lpd daemon is not supposed to stay running.  It is started by lpr,
do its job and then dissappears.
From: rick@ee.uwm.edu (Rick Miller, Linux Device Registrar)
Newsgroups: comp.os.linux
Subject: Re: [Q] Linux fdisk DOS compatible?
Date: 27 Dec 1992 10:30:45 GMT
Organization: Just me.
NNTP-Posting-Host: 129.89.2.33
Summary: Let's get the terminology straight, folks.

mrhoten@cs.stanford.edu (Matt Rhoten) writes:
>okir@monad.swb.de (Olaf Kirch) writes:
>
>> Since DOS fdisk refused to make more than one primary partition, I
>> used Linux fdisk. However, I left one partition for later use with
>> DOS. But now, DOS won't recognize my disk at all!
>
>I ran into this as well. DOS breaks if you have more than one primary
>partition. Since you don't need any of your linux partitions to be
>primary partitions, you could simply remove the "bootable" or primary
>bit from them with linux fdisk, leaving only your DOS partition marked
>primary.

WHOA-THERE!  I think you guys mean "BOOT" partition, not "primary".

A "primary" partition is not a certain partition, but a certain *kind* of
partition.  A "primary" partition is, itself, a single partition... as
opposed to an "extended" partition  which may be divided into several sub-
partitions or "logical" partitions.

You can have up to four physical partitions (Primary/Extended) on any one
hard drive, but the number of partitions you'll see will depend upon how
many logical divisions each (if any) Extended partition is split into.

Now...   As for marking a physical (Primary/Extended) partition as a "boot"
partition (a single-bit flag), you may only do this with *one* physical
partition at a time under DOS.  It only makes sense, since your machine
doesn't come with a built-in boot-selector.  If you use Linux's fdisk to
flag more than one partition as "boot", your machine won't know which to
use (for DOS or for Linux, you're not even in any operating system yet),
and it will crash.

The best option I've seen is LILO... put it on a Primary partition where
some of your Linux is (I've heard that can even sit on the swap partition)
and tell LILO where to find your DOS stuff.  It works for me...

Rick Miller   <rick@ee.uwm.edu> | <rick@discus.mil.wi.us>   Ricxjo Muelisto
Occupation:  Husband, Father, WEPCo. WAN Mgr., Discus Sys0p, and  Linux fan
Newsgroups: comp.os.linux
From: pmacdona@sanjuan (Peter MacDonald)
Subject: Re: Question and Observations
Organization: University of Victoria, Victoria B.C. CANADA
Date: Tue, 29 Dec 92 00:52:00 GMT

>	the thing that I would honestly like to know is...from
>peter mcdonald (I think)...have you ever set up the SLS distribution
>under a multi-user environment?  From the way I see things running,
>and permissions set, I don't see how...unless what is being distributed
>is not the same?


What you fail to understand is that SLS is not a snapshot like 386BSD.
It is a collection of packages.  Some packages get updated occasionally
and other new ones appear.  If a later package happens to contain
a duplicate copy with the wrong perms (or say a man page, or just
another copy of a directory, which changes it's permissions), bang
another permission gets hosed.

I have repeatedly asked someone to volunteer to write a script to set
permissions, but no such luck.  A real problem is that there is no
real agreement on what the correct permissions/ownerships should be.
How about you Marc?  Care to put your money where your mouth (or fingers) are?

Peter.
Newsgroups: comp.os.linux
From: alovell@kerberos.demon.co.uk (Anthony Lovell)
Subject: Re: Dead Keyboard and 0.99 
Distribution: world
Organization: The Home for Three Headed Canines
Reply-To: alovell@kerberos.demon.co.uk
X-Mailer: Simple NEWS 1.90 (ka9q DIS 1.18)
Date: Thu, 24 Dec 1992 01:10:28 +0000

Thank for the help ,fitted a cheap keyboard and it now works

-- 

anthony

------------------------------------------------------------------------------
alovell@kerberos.demon.co.uk          |   If at first you don't succeed
                                      | 
alovell@cix.compulink.co.uk           |   Get a Bigger Hammer 
------------------------------------------------------------------------------
Newsgroups: comp.os.linux
From: pmacdona@sanjuan (Peter MacDonald)
Subject: Permissions in SLS
Organization: University of Victoria, Victoria, BC, CANADA
Date: Tue, 29 Dec 92 21:45:48 GMT

Here is how I want to handle permission setting in SLS.
Like just about all other administration, I want to use
a shell script.  So I intend to modify/extend install
to allow it to modify files in place, plus a few other
goodies documented briefly below in the very simple
example I cobbled together.

I intend to hook into rc.local to run this after the
install is complete, and a reboot has occured.
What I would like is feedback in the form of please 
add the following lines ...

Here it is:

Peter
---perms.sh------------------------------------------------
#
# Set the permissions in the system using a modified install
# adding option -i for in place mods of files, and allowing
# character mode specs (u+r) like in chmod.  The -r option 
# specifies recursive behaviour.  Also take multiple 
# directories on the command line.  The advantage of a shell
# script is that it allows extended semantics where needed.
#
install -d -o root -g root -m 755 bin
install -d -o root -g root -m 755 usr
install -d -o root -g root -m 755 lib
install -d -o root -g root -m 755 home
install -d -o root -g root -m 755 user
install -d -o root -g root -m 755 mnt
install -i -o root -g root -m 755 lib/*
install -d -o root -g root -m 1777 tmp
install -d -o root -g root -m 1777 usr/tmp
install -d -o root -g root -m 755 usr/bin
install -d -o root -g root -m 755 usr/lib
install -r -i -o root -g root -m a+r usr/lib/*
install -r -d -o root -g root -m a+rx usr/lib/*
install -d -o root -g root -m 755 usr/man
install -d -o root -g root -m 755 usr/man/*
install -i -o root -g root -m 644 usr/man/*
install -i -o root -g root -m 755 usr/man/*/*
install -d -o root -g root -m 755 usr/spool
install -d -o root -g root -m 755 usr/spool/mail
install -d -o root -g root -m 755 usr/spool/uucp
install -d -o root -g root -m 755 usr/adm
for i in home/*; do
	install -d -o `basename $i`  -g user -m 755 $i
	install -i -o `basename $i`  -g user -m 755 $i/*
	touch usr/spool/mail/`basename $i`
	install -i -o `basename $i`  -g mail -m 660 usr/spool/mail/`basename $i`
done
Newsgroups: comp.os.linux
From: mph@plasma.apana.org.au (Martin Peter Howell)
Subject: Re: 0.99 directory bug?
Organization: APANA site, Melbourne, Australia
Date: Tue, 22 Dec 1992 23:54:51 GMT

roberts@cray.com (Michael Roberts  {67000 CF/DEV}) writes:

>My recent upgrade to 0.99 from 0.98.5 has yielded a bug involving
>floppy disks. When I mount a floppy disk with a minix filesystem
>on it and I change directories to the floppy disk, I get errors
>using "pwd" and "du". "pwd" gives the error:

>	pwd: No such file or directory

>but it works fine when my current working directory is on a hard
>drive partition. "du" works fine on floppy directories, but if I'm
>in a floppy directory and "du" a hard disk directory, like "du /",
>I get the error:

>	du: cannot get current directory: No such file or directory

I have found that trying to mount an extended or minix fs on a
directory that is not in the root (eg. /usr/mountpoint) always gives
these errors.  Whereas mounting to a directory in the root is no problem.
I noticed this a while ago (0.98.[12]) but haven't tried it since
so I don't know if it has been fixed.

-Martin.
mph@plasma.apana.org.au
Newsgroups: comp.os.linux
From: miranda@hitchcock (Johann Miranda)
Subject: Re: Advice on organizing linux users locally
Date: Sun, 3 Jan 1993 06:54:00 GMT
Reply-To: miranda@eng.uiowa.edu
Organization: Department of Elect. and Comp. Engr., University of Iowa, USA.

In article <93Jan2.021018ast.52@ug.cs.dal.ca> pitzel@ug.cs.dal.ca (brad John pitzel) writes:
>Hello,
>
>I have put out a posting locally at my university asking
>people who are using linux or interested in doing so to
>send me email. I am interested in getting local linux
>users together to share info/files/etc, increasing the
>'linux awareness' of the community, and maybe
>setting up a mirror of the SLS package for FTP.
>
>I am certain this have been done in many other
>institutions around the world, so I am asking
>for people's advice on what sort of activites
>are popular to local linux groups.  Any 
>success/failure stories would help!
>
>Thanks in advance,
>Brad Pitzel
>pitzel@ug.cs.dal.ca
>
 
I just did the same for the state of Iowa (yes, we have computers here, to 
helps count the corn kernels :).

Obviously, I am _very interested_ in the type of activities that linux
users/hackers can appreciate. although not a hacker myself, I LIKE this
OS. So, please, leep this thread going and contribute if you have something 
to say. thanks.  Adios.			-JEM-
>


Newsgroups: comp.os.linux
From: Alex Nemirovsky <AN72958%LTUVAX.BITNET@mitvma.mit.edu>
Subject: Diamond Speedstar 24X {I know I know..please dont kill me}
Reply-To: AN72958%LTUVAX.BITNET@mitvma.mit.edu
Organization: The Internet
Date: Mon, 4 Jan 1993 05:06:46 GMT

I hate to ask this but one of my friends need at 24 bit card to handle
full color...  They have an Orchid Pro II now and want to upgrade.
I know some people have figured out the clocks for the Speedstar 24X
....and a was wondering.. if it would possible to mail me your
Xconfig???  please..?????    dont kill me... ok??
I am doing it for a friend.

I am also told that the Genoa card (dont know model) is also 24 bit but
has less support on the Dos side and I haven't seen it in stores.

h.... and one tiny little thing... I dont suppose the the Xconfigs for
the Speedstar 24X let X windows use and recognize that the card can do
the full 16.7 million colors??


-bye...

thanks in advance.. i hope.

                                        - Alex Nemirovsky
                                          Larry Tech University
                                          Southfield, Mi.
From: andreas_reimer@solaris.hamm.sub.org (ANDREAS REIMER)
Newsgroups: comp.os.linux
Subject: recompiled kernel crashes...
Date: 3 Jan 93 02:45:07 GMT

I have a problem with SLS 0.99-47:
 
After I had installed Linux I re-compiled the kernel because I
wanted to use my German Keyboard. (Searching for keys can be very
annoying... )
Everything worked fine until I rebooted.
Linux displayed some normal installation messages and after that, it
DIED with the following strange message:
 
general protection: 0000
EIP: 0008: 0000B694
EFLAGS: 00010286
fs: 0017
base: C0000000, limit: 000A0000
pid: 1, process nr: 1
8b 13 d2 74 27 83 3a 02 74
 
I have done some debugging by inserting 'printk("I am here!");'
into the kernel-sources and I think the system crashes just after
mounting the root-device and during opening TTY1.
 
Another strange thing is the fact, that 'ps' seems to fail:
 
  PID TT STAT  TIME COMMAND
lseek kmem: Unknown error 186956107
 
My system configuration is:
Mainboard: 386DX 40Mhz (AMD)
Harddisk:  Maxtor 7213A (212MB, IDE)
(I do not use strange or exotic hardware)
 
Can anybody help me ???
Newsgroups: comp.os.linux
From: dinn@ug.cs.dal.ca (Michael 'Moose' Dinn)
Subject: Re: Wanted: a tar.Z of someone's /usr/lib/uucp/* files.
Organization: Math, Stats & CS, Dalhousie University, Halifax, NS, Canada
X-Newsreader: TIN [version 1.1 PL6]
Distribution: na
Date: Sun, 3 Jan 1993 15:04:27 GMT

Ed Carp (erc@unislc.uucp) wrote:
: There are sample config files included with mailpak.  Have you run this?
: 
: "uucico -r1 -f -s<site>"
: 
: then looked in /usr/spool/uucp/.Admin/audit.local?

Nothing is there. And nothing happens. Nothing at all. Even with -x9,
nothing happens.

: Or you could do "/usr/lib/uucp/uuchk"...

Which seems to report everything as OK.

--
 Michael Dinn, CS Student * dinn@ug.cs.dal.ca * Use your modem! (902) 461-4773
 "make lots of money",  "enjoy the work",  "operate within the law":  choose 2
Newsgroups: comp.os.linux
From: marcf@nexus.yorku.ca (Marc G Fournier)
Subject: Re: [Q]Upgrading libc.so.
Keywords: libc.so linux Library
Organization: York University
Date: Mon, 28 Dec 1992 16:04:29 GMT

KIRSCH@ps1.iaee.tuwien.ac.at (Rainer Kirsch) writes:

>Hello Linux Fans!
>Working with Linux 0.99p1 is great pleasure!

>1.Upgrading libc.so (How to do really?)
>To maximize functionality I got libc.so.4.2 per ftp. But ...
>Upgrading from libc.so.4.1 to 4.2 isn't that easy. (The numbers apply to the 
>actual situation, but I ask for the principal algorithm)
>My binaries (which are from SLS 0.98p1 distribution) look for libc.so.4 (not 
>trailing zero!) - so I had made a symbolic link
>libc.so.4 -> libc.so.4.1
>In order to make a new link, I removed the old one and uups ... I could not 
>do anything else. Of course! I installed a small system by usage of a1 and 
>a2 floppies of the SLS distribution, mounted my normal root-partition, 
>installed the new link and rebooted from the normal root.
>My question is: Have I overseen some simpler possibility of procedure?

	But of course...why not just do 'ln -fs libc.so.4.2 libc.so.4'? :)

Marc
From: STDN%MARIST.bitnet@YaleVM.YCC.Yale.Edu (Dan Newcombe)
Newsgroups: comp.os.linux
Subject: Most recent GCC and libs and how to update to them?
Date: 3 Jan 1993 04:02:03 -0600
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu

Hi all... (again :)
 What are the most recent (reliable) libraries and stuff for GCC and
so on?  I am using GCC 2.2.2d and my libraries are 4.1.  I tried
putting lib4.2 stuff on my system and had just a few big errors.  So...
What are the most recent versions and what do I need to do to update
to them?

  -Dan  (thanx)

Dan Newcombe
stdn@vm.marist.edu                        kk4d@maristb.marist.edu
dnewcomb@cybernet.cse.fau.edu             And others...
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
- Real programmers like vending machine popcorn.  Coders pop it in the
  microwave oven.  Real programmers use the heat given off by the cpu.
  They can tell what job is running just by listening to the rate of popping.

Newsgroups: comp.os.linux
From: marc@r-node.gts.org (Marc Fournier - Admin)
Subject: Re: password problems
Organization: R-node Public Access UNIX Information System (416-249-5366)
Date: Thu, 31 Dec 1992 17:30:06 GMT

In article <1992Dec31.123659.13483@athena.mit.edu> kambis@asdsun.larc.nasa.gov writes:
>
>hello all. happy new year!
>
>I am having '...password expires in 0 days...' problems.  I know this was
>going around earlier, but I don't remember the solution.  (I have the SLS
>release of about 2 weeks ago.)  If any of you kind folks could help me out
>of this one, I'd greatly appreciate it.
>

	passwd -x XXXX

Marc
-- 
Marc G. Fournier      | R-node Public Access Unix running UnixBBS 1.10
Etobicoke, Ontario    | 416-249-5366   24hrs 7 days/week   network email
voice: 249-4230       | shell accounts available  2500+ newsgroups  FREE
marc@r-node.pci.on.ca | Telebit WorldBlazer/SupraModem2400/Cardinal 2400 
Newsgroups: comp.os.linux
From: sno@ais.org (Stephen Opal)
Subject: Re: Linux raw beginner question.
Organization: UMCC
Date: Tue, 22 Dec 1992 17:57:37 GMT

Thanks to the several emails I received for showing me the way.

Points:

1)  SLS is designed to be installed to a HD rather than used as a floppy
set-up.  I didn't realize that.  However, it is the distribution I *will*
be using when my HD controller comes in on the next delivery.

2)  Floppies must be formatted by DOS first, before Linux will acknowledge
them.

3)  The correct format for mounting a new floppy device is:
	# mkdir <pathname>
	# mount </dev/whatever> <pathname>

Thank you to the constructive suggestions.  Now to get the 0.99.1
distribution so that I can get rid of that annoying keyboard lockup prob.

-- 
Stephen N. Opal     sno@umcc.ais.org
Newsgroups: comp.os.linux
From: samuulin@iastate.edu (Steve A Mullinnix)
Subject: Problems 
Organization: Iowa State University, Ames IA
Date: Wed, 30 Dec 1992 04:17:05 GMT

Yesterday I got Linux SLS 0.99-47 (???) from tsx-11.mit.edu and installed
it without any problems.  I then went to get Linux to boot from my hard
drive and it failed.  My next thought was to recompile the kernel to get
a new image to put on my boot partition, I wanted to rebuild the kernel
anyway.  So I went into /usr/src/linux and entered:

/usr/src/linux# make dep

It went fine for a little bit, then died as below: 

gcc -DKERNEL -E -M *.c > .depend
gcc -DKERNEL -E -M *.c > .depend
gcc -DKERNEL -E -M *.c > .depend
inode.c:22: #error The iso9660 filesystem can only be used with CDROM.
make[2]: *** [dep] Error 1
make[1]: *** [dep] Error 1
make: *** [dep] Error 1

I continued anyway to make the kernel by entering:

/usr/src/linux# make

It compiled many of the source files and then died as follows:

make[2]: `ext.o' is up to date.
msdos
make[2]: `msdos.o' is up to date.
proc
make[2]: `proc.o' is up to date.
net
for i in tcp; do (cd $i && echo $i && make) || exit; done
tcp
make[2]: *** No way to make target `/usr/include/sys/cdefs.h'.  Stop.
make[1]: *** [subdirs] Error 1
make: *** [linuxsubdirs] Error 1

Does anyone know what might be going on here.  Linux appears to work fine
if I boot off my boot floppy.  I should be able to build the kernel.  Maybe
someone out there has seen this or can tell what I did wrong.

Thanks for your help.
+------------------------------------------------------------------------+
|   Steve Mullinnix     Iowa State University     Computer Engineering   |  
+------------------------------------------------------------------------+

Newsgroups: comp.os.linux
From: Lou Berger <lberger@BBN.COM>
Subject: Xconfig for LCD screen
Reply-To: lberger@BBN.COM
Organization: The Internet
Date: Wed, 30 Dec 1992 17:51:57 GMT


Does anyone out there have an Xconfig for a mono LCD screen with Cirrus
Logic VGA driver and reported chip type of 'stingray'.  I'm having much
trouble getting the timing parameters right.  (If I only had a spec
sheet....) 

Thanks in advance,

Lou Berger