HDTenEightyP/NetNews huggingface dataset:
From: hm329@rrz.uni-koeln.de (Thomas Scheunemann)
Subject: Re: [Q] x8514 with SLS?
Organization: Regional Computing Center, University of Cologne, F. R. Germany
Distribution: comp
Date: Fri, 16 Oct 92 22:26:47 GMT


I have just compiled the x8514 Xserver for SLS 0.98p1 and except that it
took about three hours there were no major problems.
j
The problem is that i cannot run this Xserver. There are at least two
quirks and any help would be greatly appreciated.

1. my ATI-Busmouse isn't recognized by the X-Server. As this seems to be a
common problem, i hope that there is someone who can tell me how exactly
i have to configure X11 to recognize this mouse.

2. the Xserver says that he couldn't set the default font-path and therefore
he can't load the fixed font. I believe that someone did have the same problem
but i have not seen any answer to it.

If someone is interested in the binaries I could upload them possibly to
tsx-11.mit.edu.

Hope anyone can help me
Thomas Scheunemann

Newsgroups: comp.os.linux
From: lcd@ais.org (Leon Dent)
Subject: Re: Smail (from Mailpak 1.3) won't compile
Organization: UMCC
Distribution: comp
Date: Sat, 17 Oct 1992 00:51:13 GMT

In article <1992Oct16.134339.8762@aw2.fsl.ca.boeing.com> vds7789@aw2.fsl.ca.boeing.com (Vincent D. Skahan) writes:
>
>well, last night I put together the long rumored (threatened?) 'newspak 1.0'
>which I'll try to upload this weekend to tsx-11 and sunsite.  At this time
>it contains the following:
>
>	- Cnews 
>	- tin1.1pl4
>	- trn2.2
>

I, for one, am hoping these are individual files rather than one multi-meg
file.  A "newspak" directory with a README indicating the last update of
each file can't take much more space than one large file.

Leon Dent
lcd@ais.org
From: dcs11@cl.cam.ac.uk (D.C. Strawson)
Newsgroups: comp.os.linux
Subject: Bizzare crashes with SLS
Keywords: 486
Date: 16 Oct 92 16:22:28 GMT
Reply-To: dcs11@cl.cam.ac.uk (D.C. Strawson)
Organization: U of Cambridge, England

A friend and I are a bit concerned (to say the least) about the
bahaviour of the Linux
OS on his PC. I have helped several other people install either Linux or
SLS with
few problems.

First, the hardware:

	486 - 33 MHz 126K Cache EISA motherboard 
	8M System RAM
	Adaptec 1542 SCSI card (ISA)
	Orchid Prodesigner IIs 1M crd + Philips 4CM2799 20" monitor

	The partitioning on the disk is 51M Linux plus 3 x 50M DOS	

	Award BIOS - This has a BETA marked on the initial screen

For those in the UK, the machine was baught from MJN.

The software:
	
	Linux 0.98 SLS distribution

OK. We booted up and after a bit of hassle, made the partition. Then SLS, which
did not want to install at all. It first managed to install about the
first disk
and then came to the conclusion that it had finished. Every time we ran
doinstall this
happened, in various ways. I suspect that sub-processes were dying and
causing it to
terminate early.

In the end I installed most of the system by copying all the DOS disks onto the
DOS area and using a small shell script to untar them.

All through this, bash kept dying, roughly every 5-20 commands entered. Often
sub-processes of it died, such as ls or more, all processes dump core.

However, on a brighter note we now have X running - almost happily, the
big problem
seems to be that bash or similar exits, so the X server shuts down prematurely.

We have tried zsh instead of bash, and have had similar problems, but
nowhere near
as bad. We even managed to go through a whole load of the demos - great!


We are both really impressed with the system - we cannot wait to get going with
something useful. At the moment, however, it is not really helping if
the system
crashes once every five mins.

I stress that the kernel has very rarely crashed - init (almost) always
has managed
to recover. Only once did the system have to be reset - I bet this was
that each new shell
created by init died immediately, and a loop was created.


By the way, does anyone have monitor settings for the above mentioned
screen...?


We would be most grateful to anyone who can help. 

	

-------------------------------------------------------------------------------
Daniel Strawson & Tim Mills  CST 1B                e-mail : dcs11@uk.ac.cam.phx
-------------------------------------------------------------------------------
From: ajh@uk.co.gec-mrc (Andrew Haylett)
Newsgroups: comp.os.linux
Subject: Performance problems with driving LP?
Date: 13 Oct 92 10:36:12 GMT
Organization: GEC-Marconi Research Centre, Great Baddow, UK
X-Newsreader: TIN [version 1.1 PL6]

Has anyone else experienced this? I have a Deskjet 500 hanging off a
parallel port, which can be driven quite happily by Linux in text
mode.  However, when dumping graphics, for example from gs 2.5.2, it
prints the first few lines at full speed, then slows right down to
about one line every five seconds or so. Driving the printer directly
from emTeX under DOS works at just about full speed. I've seen this
phenomenon before when using a software printer cache under DOS, so
suspect it's not specific to Linux; but can anyone help?

Machine: humble 386SX/16, 8Mb.
-- 
Andrew Haylett (ajh@gec-mrc.co.uk) GEC-Marconi Research, Great Baddow, Essex.
Newsgroups: comp.os.linux
From: chad@eng.umd.edu (R Michael McMahon)
Subject: Re: Dos Emulator: PAUSE (dir/p) fixed
Reply-To: chad@eng.umd.edu (R Michael McMahon)
Organization: College of Engineering, Maryversity of Uniland, College Park
Date: Tue, 13 Oct 1992 14:22:10 GMT

In article <1992Oct12.231012.4906@cseg02.uark.edu>, tep@cseg02.uark.edu (Tim Peoples) writes:
> chad@src.umd.edu (R Michael McMahon) writes:
> 
> >	Those of you using the DOS emulator have noticed that commands
> >which use the DOS PAUSE routine crash the process. A simple 1 line patch
> >to emu.c can solve this problem:
> >
> >in ms_dos() add		case 0: /* divide by 0 */  break;
> >
> >
> >	After enabling debugging and watching a simple PAUSE command 
> >result in INT 0 being called, I decided to investigate. After an hour
> >of tracing through COMMAND.COM with CodeView, I found the following
> >code:
> >
> >	MOV	AX,0c08		<- no problem: standard DOS keyboard
> >	INT	21		   flush/wait for keypress sequence
> >	MOV	AX,0c00		<- what? Call interrupt 0? Thats a 
> >	INT	21		   floating point/divide by 0 routine!
> >
> 
> [ Discussion of INT 0 deleted ]
> 
>    From what you supplied above, this is not INT zero but FUNCTION
> zero if INT 21.  Advanced MSDOS Programming from Microsoft Press
> states:
> 
>    Int 21H
>    Function 00H
>    Terminate process
> 
>    I don't know why it's there but it's deffinately not a divide
> by zero interrupt call.
> 
> -- 
> 
> +--------------------------------------+-------------------------------------+
> | Tim Peoples                          | The time has come the hacker said   |
> | tep@engr.uark.edu                    | to talk of many things,             |
> | Dept. of Computer Systems Engineering| of simms and sockets and semaphores |
> | University of Arkansas, Fayetteville | of processes and pings....          |
> +--------------------------------------+-------------------------------------+
> |    I need no disclaimer; nobody listens to what I have to say anyway!!     |
> +----------------------------------------------------------------------------+
> 


Yes, Tim, you are right, and that's what I coded (by putting the patch
in as function 0 of INT 21), but definitely not what I said. In the 
future, I guess you should trust my code more than my explanations-
typical engineer.

Mike McMahon	chad@src.umd.edu
Newsgroups: comp.os.linux
From: mmh@mercury.analog.com (Marc M. Hoffman)
Subject: CSCHEME!!
Organization: Analog Devices Inc, Norwood MA, USA
Distribution: comp
Date: Thu, 8 Oct 1992 20:04:44 GMT


I got cscheme running if anyone is interested send me mail and I will
post it..  This includes the compiler...

--
-----------------------
marc.hoffman@analog.com
From: briana@tau-ceti.isc-br.com (Brian W. Antoine)
Newsgroups: comp.os.linux
Subject: Re: SCSI hangs up after ident on boot
Date: 16 Oct 92 20:58:02 GMT
Organization: ISC - Bunker Ramo, Spokane, WA
X-Newsreader: Tin 1.1 PL3

drew@kinglear.cs.colorado.edu (Drew Eckhardt) writes:
: In article <1992Oct16.171826.14638@den.mmc.com> keng@den.mmc.com (Ken Garrido) writes:
: >
: >
: >Don't know if this is FAQ.
: >I am brand-new to this, just subscribed to the group.
: >If I breach netiquette, please email me a FAQL.
: >
: >HELP !
: >
: >As I boot, I get a message that reads :
: >
: >SCSI : detected 1 SCSI disk 0 tapes total
: >SCSI host 2 timed out - aborting command 
: >
: 
: The factory configuration for the Seagate SCSI boards is for DOS - 
: ie interrupts are disabled.  Needless to say, this doesn't work
: in a real operating system that's expecting interrupts when 
: a SCSI command is done.
: 
: Jumper your board for IRQ5, and things should be fine.
: 

  This works fine as long as you don't have a busmouse installed also.  The
mouse driver is hardcoded for IRQ5 and the STXX isn't gonna like sharing
the interrupt.  The way I got around that on the one system that uses the
Seagate controller was to patch the driver to not allow the device to
disconnect from the bus.  The interrupt line is only used to signal the
reconnection attempt.  I don't have the code in front of me, but look for
the call to internal_command() and change the last arg to NO_RECONNECT.
This lets you use with card without needing interrupts.  Of course this
is gonna be VERY slow because the kernel will loop getting the data from
the drive and ignore everything else until the transfer completes.
-- 
Brian Antoine    |                                 | "Where are we going?"
ISC-Bunker Ramo  | ...uunet!isc-br!tau-ceti!briana |               "PLANET 10!"
Spokane, WA      |  or briana@tau-ceti.isc-br.com  | "When?"
                 |  or briana@miniop.spk.wa.us     |               "REAL SOON!"
Newsgroups: comp.os.linux
From: tthorn@daimi.aau.dk (Tommy Thorn)
Subject: Re: XFM 1.1: not work at all
Organization: DAIMI: Computer Science Department, Aarhus University, Denmark
Date: Fri, 9 Oct 92 21:20:43 GMT

Ching-Hsiang Chen <chchen@stat.fsu.edu> writes:

>I've tried XFM 1.1, from old X version 1.1 to current Xfree86, including
>both binary and source version. I could compile it w/o any problem
>at all but each time I ran it, it gave me a core dump. This happened
>when I still got a 386SX/16 to current 386DX/33. I got 5 mb RAM.
>Kind of frustrating. Anyone succeeds?

>Steve Chen             chchen@stat.fsu.edu

I had no problem, but I deleted my copy due to lack of diskspace.

I'll consider compiling it again when time permits.
--
/Tommy Thorn, another LPF member. Terminate software patents.
Join The League for Programming Freedom, mail league@prep.ai.mit.edu.
XT350 '88 - You either make dust, or you eat it.
From: pmacdona@tadpole.bcsc.gov.bc.ca (Peter MacDonald)
Newsgroups: comp.os.linux
Subject: SLS update
Date: 15 Oct 92 14:02:31 GMT
Reply-To: pmacdona@tadpole.bcsc.gov.bc.ca
Organization: The Internet

This is not really an update, but rather just a couple of 
comments.

If you were one of the prudent people to wait for SLS .98
to settle down, it should be ok to download it now.  Most
of the problems seem fixed.

If you already have SLS, just do a "ls -lt ??/*" to see which
packages have changed.  Of special interest are the "z?fix.taz"
files, located if present on the last disk of a distribution.
This contains the fixes either as replacement files, or as a 
shell script that does the work for you.  When the fully
corrected packages are uploaded, the "z?fix.taz" files will
mysteriously dissappear.  Until then, one-off installation
may not get permissions right.

Also note, although SLS is so easy to install, that even an
non administrator can do it, it still presumes that you are
an administrator.   And part of an administrators job is making
sure that files have the correct permissions :-) :-).

Seriously, thanks to all who have provided input.

Peter
pmacdona@sanjuan.uvic.ca
Newsgroups: comp.os.linux
From: davem@extro.ucc.su.OZ.AU (David Monro)
Subject: TeX under linux
Summary: TeX utils required
Keywords: TeX
Organization: arbritray
Date: Thu, 8 Oct 1992 09:45:10 GMT

Before I buy a 386 motherboard for home, there are some things I need to
know.

1. Is there a dvi screen previewer avaliable for hercules cards?
	I am using emtex dviscr under dos and I like it. I
	would like to get it running under linux - does anybody
	have source and some idea how to patch for hercules under
	linux? (I suspect the autodetect code will go a bit haywire.)
	However, anything that works will do.

2. Will it read the font libraries used by emtex stuff?
	These save a lot of space - I need this if I am
	going to do anything else meaningful with linux.

3. I already have a copy of dvilj2p, which works very nicely.
	Again, I need a version which supports the font
	libraries, if possible. Has anybody managed to get
	a copy of emtex dvi2hplj working? (This should be
	fairly easy, but I don't have the source or know
	where to get it.)

I already have access to a 486 running a full installation of
the mcc 0.97.2.12 release so I can compile things and hack them
around if I need to.

The emtex font library stuff is not absolutely essential, but
I do need something to cut down the space used by all the fonts
used on my ( 40M ) home machine. (Under emtex, huge numbers of
fonts can be packed into a single file - this can save very
large amounts of space.) If there is an equivalent storage
mechanism I'd like to know about it too. If anybody has
documentation on the format I could try and add it to one of the
more readily availiable packages, so if you have it, please send it.

If I can get that lot working, I'll buy a 386 board and ditch dos.

Thanks very much people,


-- 
David Monro
e-mail: davem@extro.ucc.su.OZ.AU
Newsgroups: comp.os.linux
From: jayh@ms.uky.edu (Jay Hofacker)
Subject: Re: Use of zip instead of compress
    <Bw4p36.Eoz.2@cs.cmu.edu>
Date: Wed, 14 Oct 1992 22:31:39 GMT
Organization: University Of Kentucky, Dept. of Math Sciences

ddj+@cs.cmu.edu (Doug DeJulio) writes:


>I've been using zoo as a compresser, because it gives much better
>compression ratios than compress does.  However for archival, I tar
>files first and then zoo the tarfile.  That's because all of the
>PC-based archivers I've seen do nothing to preserve the ownership and
>mode of the files in the archive.  That's fine if it's a directory of
>source code, but if for example there's a shellscript, the script
>won't work anymore once you take it back out of the archive (because
>the executable bit was stripped off by the archiver).  Similarly, if
>you back up your home directory and then unpack it, all of your mail
>files would suddenly be world-readable!  For this reason I'll always
>use tar or some other Unix based archiver at the lowest level, and
>then some other compressor.

Info-ZIPs zip 1.9 and unzip 5.0 preserve all Unix permissions, including
storing symbolic links as links instead of files (-y option).  
(hmm.. Do they store the suid/sgid permissions too?...)

One thing zip/unzip doesn't seem to do is store devices as major/minor
numbers instead of accessing the device. ie 'zip -9ry devices /dev' attempted
to compress all of memory via "/dev/mem" instead of making a backup of
all the devices.  Is there a way around this?
-- 
Jay Hofacker
Email: jayh@ms.uky.edu                  --- "Hailing frequencies closed sir."
Newsgroups: comp.os.linux
From: hlu@yoda.eecs.wsu.edu (H.J. Lu)
Subject: Re: Termcap question
Organization: Washington State University
Date: Thu, 8 Oct 92 07:15:49 GMT

In article <BvsCyK.AHH@ux1.cso.uiuc.edu> Upholder@uiuc.edu (THE Upholder of Truth) writes:
>davison@borland.com (Wayne Davison) writes:
>
>>Did you read anything in my article after the opening sentence?  In it I
>>explained exactly why the termcap standard *requires* you to output the
>>sequence im-ic-ei when both are defined.  This is NOT an option.
>
>>Here's the reasoning:
>
>>  1.   If your terminal has only insert mode, you define im & ei.
>>  2.   If your terminal has only insert char, you define ic.
>>  3.   If your terminal requires insert mode to be turned on and then
>>       a character sequence output for each inserted character you
>>       define BOTH im/ei and ic.
>>  4.   If your terminal has both an insert mode and an insert character
>>       sequence that does not fall into category 3, you must choose one
>>       of the two.  The usual choice is insert mode.
>>  5.   If your terminal has a multi-character insert sequence, you define
>>       IC regardless of whether im/ei or ic is defined.
>
>
>So here'e the question your average Linux user has...
>
>	HOW DO WE FIX IT? 
>
>or alternately, 
>
>	Does anyone have a "fixed" termcap for the linux std consoles?
>	If you do, either post it if it's small or put it up for FTP
>	somewhere or have it put on the new rootdisks...
>
>-- 

Get my bootable rootdisk under pub/linux/GCC/rootdisk or
Linux Base System under pub/linux/GCC/basedisk on tsx-11.
Then copy /etc/termcap and /usr/bin/elvis to your hd.

H.J.
From: al198723@academ01.mty.itesm.mx (Jesus Eugenio Sanchez Pena)
Newsgroups: comp.os.linux
Subject: Distributing Linux
Date: 16 Oct 92 19:56:07 GMT

rms@gnu.ai.mit.edu (Richard Stallman) writes:

>The FSF could distribute a system containing Linux
>if someone would like to undertake the work of putting
>the distribution together and maintaining it.

>If you want to volunteer for overall responsibilty for this (which
>probably means doing much of the work yourself), please send me mail.
From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
Newsgroups: comp.os.linux
Subject: Bug in tcp/ip code included with 0.98
Date: 7 Oct 1992 15:48:34 -0500
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

I have a customized system as far as linux goes, so I had to pull the
stock 98.1 sources off of nic to compile it. Then when I attempted to
run some things that used tcp/ip, such as rpcinfo they wouldn't work at
all. I got a network unreachable error. I recompiled the 98.1 kernal with
the base tcpip.0.8.1 stuff from nic, and now it works with no problems. I
went ahead and diffed to two version of the tcp/ip code and found a handful
of differences. So I was wondering if anyone knows which version of the tcp/ip
code is in the base distribution, as it doesn't appear to be the same as the
tcpip.0.8.1 release. 

James
From: widmer@zzz.pe.u-tokyo.ac.jp (Thomas Widmer)
Newsgroups: comp.os.linux
Subject: Re: At last: the media woke up
Date: 15 Oct 92 08:23:17 GMT
	<1992Oct15.020946.5978@ee.eng.ohio-state.edu>
Organization: Dept. of Precision Machinery Eng., The University of Tokyo,
	Japan.



>> In article <1992Oct14.181622.16550@fwi.uva.nl>, stolk@fwi.uva.nl (Bram) writes:
>> > However, in the November issue of another german mag. C'T, there is
>> > an article on Linux. C'T is a very popular magazine of high scientific
>> > quality, and available all over Europe. The article was pretty
>>
>> Finally someone on the outside has recognized Linux!!!!!!

In SuperASCII (japanese magazine), VOL.3 #10 October 1992, there is an
article comparing BSD, Mach, Linux and others. The part about linux is
***8*** pages long and has also an instruction how to get it and install
it.

take care
    tom

--
---------------------------------------------------------------------
Thomas Widmer  (widmer@zzz.pe.u-tokyo.ac.jp)
Yoshikawa & Tomiyama Lab.
Department of Precision Machinery Engineering, Faculty of Engineering
The University of Tokyo, Hongo 7-3-1, Bunkyo-ku, Tokyo 113, Japan
---------------------------------------------------------------------
From: torvalds@klaava.Helsinki.FI (Linus Torvalds)
Newsgroups: comp.os.linux
Subject: Re: Kernel panic!?
Date: 15 Oct 92 09:34:27 GMT
Organization: University of Helsinki

In article <1biei2INN2mc@crcnis1.unl.edu> mchapin@cse.unl.edu (Mark Chapin) writes:
>In attempting to install the SLS package, I partioned my hard drive several
>times using fdisk from Linux, DOS and even OS/2.  After every attempt I use
>mkfs -c /dev/hda2 57344 (with or without the -c) . No matter what I do I
>get Kernel Panic:  Trying to write bad sector.
>Wassup?  I have an ESDI 660 MB Seagate.

The "trying to write bad sector" panic can happen if linux finds a drive
it simply doesn't know how it might possibly read/write.  The harddisk
driver is unable to cope with more than 2 drives and/or more than 16
heads.  The reason is that the st-506 programming interface only has one
bit for drive identification, and 4 bits for head info.  So if linux
sees a disk that has more heads than 16, linux gives up with the above
panic. 

If somebody knows how >16 heads are handled on the IO register level,
I'd be interested to know.

>					  I have partitioned it several
>different ways.  I am putting the Linux/Minix partition in a primary slot. 
>I have tried the turbo on/off.  Any suggestions on what to try.  I guess I
>could try putting Linux as hda1, but I don't see how this would solve
>the problem.  Please HELP!!!

No, using hda1 shouldn't make any difference.  If your controller allows
different sector translations, you might want to re-configure the drive
using fewer heads, although that might then be a problem for the BIOS if
the number of cyliders grow beyond 1024 (linux hasn't got this
particular problem). 

		Linus
Newsgroups: comp.os.linux
From: S_WIEZORKE@iravcl.ira.uka.de (Hans B. Wiezorke)
Subject: XLoadImage: has someone ported it yet?
Organization: University of Karlsruhe (FRG) - Informatik Rechnerabt.
Date: Fri, 16 Oct 1992 09:54:35 GMT
X-News-Reader: VMS NEWS 1.23

has someone ported xloadimage (or sth. similar)?

i really would like to have a nice .gif file as desktop picture :-)

keep hackin'

hans



 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I                  __     I   Hans Bernhard Wiezorke  (at Uni. of Karlsruhe)  I
I /opus\    _____(@  \    I   E-Mail :  S_WIEZORKE@iravcl.ira.uka.de          I
I \sndo/   /.         !   I          or UK9K@DKAUNI2.bitnet (for large mails) I
I          ------)    !   I- - - - - - - - - - - - - - - - - - - - - - - - - -I
I                X~~~~!   I                    W A N T E D                    I
I- - - - - - - - - - - - -I                 Schroedinger's Cat                I
I std. disclaimers apply  I                   dead or alive                   I
 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Newsgroups: comp.os.linux
From: dperry@ringer.cs.utsa.edu (Dave Perry)
Subject: lpd, and spooling
Keywords: PRINTING!
Organization: University of Texas at San Antonio
Date: Sun, 11 Oct 1992 01:06:39 GMT

Hello,

I am in the process of installing SLS 0.98 on my home PC, and having
had previous linux experience with the mcc releases, I was curious
as to the availability of a printer daemon to spool print jobs.  Also,
I'd like to be able to print makeshift TeX documents (makeshift becuase
I only have a cheap little panasonic dot-matrix) from linux...  Any
info would be helpful!

-Dave
-- 
"...and everything under the sun." | *Not Windows | dave@lil-stat.tamu.edu
                         -floyd    |  compatible  | dperry@ringer.cs.utsa.edu
Newsgroups: comp.os.linux
From: djr48312@uxa.cso.uiuc.edu (X X)
Subject: X11R5V1.1 man files
Organization: University of Illinois at Urbana
Date: Fri, 9 Oct 1992 03:51:41 GMT

I set the manpath varialbe in my .bashrc file to point to /usr/man/mann
but the man pages for x are still not working.  Anyone have the correct
implementation to share with me?  Also if you have a libc.so.4 could
you uuencode it and mail it to me?  I erased mine.
From: stuartajc@cix.compulink.co.uk (Stuart Cockman)
Newsgroups: comp.os.linux
Subject: X11v2 in mono on TVGA8900C
Date: 16 Oct 92 22:04:00 GMT
Reply-To: stuartajc@cix.compulink.co.uk

Hi.

Newbie to X11 question:

Anyone help me to get X11v2 working in mono on a TVGA 8900C?
I have tried the timing examples for Xconfig, and also adjusted them 
according to the instructions.

I get a screen displayed,  but cannot read it. 

Thanks...Stuart
Newsgroups: comp.os.linux