HDTenEightyP/NetNews huggingface dataset:
From: k2@bl.physik.tu-muenchen.de (Klaus Steinberger)
Newsgroups: comp.os.linux
Subject: Re: ghostscript/ghostview errors
Date: 27 Aug 92 19:39:17 GMT
Organization: Leibniz-Rechenzentrum, Muenchen (Germany)

davidsen@ariel.crd.GE.COM (william E Davidsen) writes:

>In article <1992Aug27.035346.16159@rs6000.cmp.ilstu.edu>, jliddle@rs6000.cmp.ilstu.edu (Jean Liddle) writes:
>| Hi,
>| 
>| Both ghostview 1.3 and ghostscript 2.5 (from gatekeeper.3com.com) compiled
>| flawlessly under linux 0.97.1 and gcc 2.2.2.  (linux 0.97.1 was installed
>| over the SLS 0.96 installation).  When trying to display some files, such

>  Beward 2.5. If you've been reading the bug group you will know that
>there are performance problems and problems with the laserjet. Bad
>problems to the point that 2.5.1 is promised in about 6 weeks.

Yeah, but for both problems there are fixes posted in the bug group,
and both are really simple. A more annoying problem is that the
magnifying window with ghostview didn't work. (It pops up, but will be
empty).

Anyway, none of these problems are killers, so if you need some of the
new features, get it. At least the new cdjcolor driver for the Deskjet 500c
is a real step forward.

Sincerely,
Klaus
--
Klaus Steinberger               Beschleunigerlabor der TU und LMU Muenchen
Phone: (+49 89)3209 4287        Hochschulgelaende
FAX:   (+49 89)3209 4280        D-8046 Garching, Germany
Internet: Klaus.Steinberger@Physik.Uni-Muenchen.DE
Newsgroups: comp.os.linux
From: dhirvela@icaen.uiowa.edu (Dave Hirvela)
Subject: Re: ATI graphics ULTRA? Will it work?
Date: Mon, 31 Aug 1992 19:40:13 GMT
Organization: University of Iowa, Iowa City, IA, USA

djr48312@uxa.cso.uiuc.edu (X X) writes:

>WIll the ATi graphics ULTRA work with linux?  Any onr know if the mosue
>will work?  Is the card compatible with Xwindows?


Yes, it sure will, I'm using it right now.  To run x you need the 8514/a
x server (at least I think you do, I'm still working on getting the binaries
on my system) and then you can use the accellerated modes.

Get the file Xlinux8514.T.Z, it's on the major site, got mine from the
finland site...

Dave

p.s.  The bus mouse wasn't tested by the author, so you might have a
problem with that, but hopefully not...


?
-- 
Any opinions expressed are obviously wrong.  * dhirvela@icaen.iowa.edu
Save Ferris !  Use only optical media !      * dhirvela@umaxc.weeg.uiowa.edu
Try Telemate-PC and save feeping creatures ! * Booster Gold in mail on:
"I don't think that word means what you      * bbs.isca.uiowa.edu login:
 think it does." _The Princess Bride_        * iscabbs - Try it today !!!
Newsgroups: comp.os.linux
From: bboerner@novell.com (Brendan B. Boerner)
Subject: Re: problem with header files and gcc2.2.2d
Keywords: gcc signal.h
Organization: Novell, Inc. --Austin
Date: Fri, 28 Aug 1992 13:41:18 GMT

In article <6038@pdxgate.UUCP> moyerg@rigel.cs.pdx.edu (gary a moyer) writes:
>Well, I got around the build.c problems by simpling omitting the
>header file(s) that were giving me problems -- most notably signal.h.
>
>I am now trying to implement some _simple_ signal catching and this header
>file is beginning to become a big problem.  Heres what I get:
>Parse error before `SignalHandler'
>Parse error before `signal'
>Parse error before `__sighandler_t'
>...etc...

You need the header files from at least 0.97 Pl #1.  I got 0.92 Pl
#2 and everything is allright.

Brendan
-- 
Brendan B. Boerner		Phone: 512/346-8380
Internet: bboerner@novell.com	MHS: bboerner@novell
Please use ^^^^^^^^^^^^^^^^^ if replying by mail.
From: adam@soda.berkeley.edu (Adam J Richter)
Newsgroups: comp.os.linux
Subject: Re: Adaptec AHA1542B hangs when booting 0.97-0.97.2
Date: 1 Sep 92 22:26:34 GMT
Organization: University of California, Berkeley
NNTP-Posting-Host: soda.berkeley.edu


	When I boot Linux with my Adaptec 1542B (revision J) SCSI
controller, Linux recognizes that there is an Apaptec controller,
prints something like "SCSI: 1 host found", and then waits forever.
With debugging turned on under 0.97.2, I get the following messages:

aha1542_detect:
aha1542_detect: enable interrupt channel 11
aha1542_detect: enabling interrupts
	*** READ CAPACITY ***
aha1542_command: ..calling 1542_queuecommand
aha1542_queuecommand: dev 0 cmd 25 pos -1 len 8 aha1542_queuecommand: dumping scsi cmd 25 00 00 00 00 00 00 00 00 00
aha1542_queuecommand: now waiting for interrupt


	Characters still echo when I type them, but I can't do anything
to get the kernel to proceed beyond this point.  I get the same
behavior with my CDROM attached to the SCSI bus and with nothing
on the SCSI bus.  It also does not matter whether or not I remove
my serial/parallel card and modem.  I have tried booting 0.97, 0.97.1
and 0.97.2.


	The FAQ on tsx-11.mit.edu mentions that the version of the SCSI
code rolled into the standard Linux distribution is not the latest
version available, when when I checked headreast.colorado.edu, all of
the distribution files had version numbers in the .95-.96 range, suggesting
that they actually correspond to earlier versions of linux.

	Thanks in advance for any input that anyone can offer.


-- 
Adam J. Richter				409 Evelyn Avenue, Apt. 312
richter@cerf.net			Albany, CA 94706
					(510)528-3209
Another member of the League for Programming Freedom (league@prep.ai.mit.edu).
From: cmetz@thor.tjhsst.edu (Craig Metz)
Newsgroups: comp.os.linux
Subject: Ethernet drivers
Date: 28 Aug 92 11:48:07 GMT
Reply-To: cmetz@thor.tjhsst.edu (Craig Metz)
Organization: The Internet


	I have to put in a good vote here - 3Com 3C503 (Etherlink II) 
and 3Ccom 3C505B (Etherlink Plus) cards. There are numerous packet
drivers out there for DOS that use these cards, many of which you
can get source to, as well. And my school has close to a hundred
cards, all either a 3C505B or a 3C503 (many were donated by 3COM...
okay, well, 3COM was going to donate a lot, but they've only come
up with six. Anybody from 3Com out there? Your people here have
nixed a good PR opportunity...). 

	Seeing also as there are so many of these in use, I think
that somebody should write one. I'm not going to be like 90% of the
people on this group now and whine and argue that this is what people
should do (ie somebody ELSE should do), if nobody does start doing
one soon, then I'll step forward and do it. Just somebody definitely
needs to support these cards.

						-Craig
From: magyar@hss.caltech.edu (Ted Turo'cy)
Newsgroups: comp.os.linux
Subject: Problem w/ shoelace
Date: 31 Aug 92 10:20:22 GMT
Organization: California Institute of Technology, Pasadena

G'day -

	I've just finished installing linux on my new 386 compat, and I'm
pleased to say I love it.  (In fact, I've already made one other convert...)
However, I've run into one small problem: Following the instructions in
shoelace.doc from tsx, when I attempt to boot from the HD, it gets as far
as the "Load Image" message, the hard drive continues to work for a few
seconds, then stops moving, while the drive light remains on.  I've had
no trouble booting from floppy using the file system on the hard drive;
also, shoelace will happily boot my DOS partition.  All the printout from
shoelace agrees with the example given in the docs...  So, I'm somewhat
puzzled.  Anyone have any ideas?

Thanks greatly,

Ted Turo'cy
magyar@hss.caltech.edu
Newsgroups: comp.os.linux
From: d88-jwn@dront.nada.kth.se (Johan W}hlin)
Subject: Re: Next major release of the Linux C library
Keywords: gcc jump table link
Organization: Royal Institute of Technology, Stockholm, Sweden
Date: Mon, 31 Aug 1992 08:45:14 GMT


Will programs compiled with -jump work with the new libs. Or should they
be recompiled with the jumptable-scheme ?
Thanks a <some arbitrary _very_ large number> times for you effort ..
/Johan
-- 
/Johan W}hlin (.. where the } really is an a with a ring above it.. 8))
Newsgroups: comp.os.linux
From: hlu@yoda.eecs.wsu.edu (H.J. Lu)
Subject: MM code in 0.97 pl2 (Re: BUG with bash and Linux-0.97 pl 2)
Organization: Washington State University
Date: Sun, 30 Aug 92 18:28:05 GMT

In article <5725@mccuts.uts.mcc.ac.uk> LeBlanc@mcc.ac.uk writes:
>In article <1992Aug29.054016.28156@athena.mit.edu> tytso@ATHENA.MIT.EDU (Theodore Ts'o) writes:
>>I just recently upgraded to Linux 0.97 patchlevel 2, and after I did,
>...
>>If you type the following at bash under 0.97 PL2:
>
>>unset SHLVL
>>exec /bin/sh
>
>>The existing shell will core dump without managing to exec the prgram
>>you ask it to exec.
>...
>>This behavior can be duplicated using either the MCC 0.96c /bin/bash, or
>>the /bin/bash on the 0.97 rootimage disk.
>
>This problem disappears if you recompile bash under 0.97p2; at least it
>does not exhibit itself with the bash supplied with MCC interim 0.97p2.
>

I think something is wrong with signals with bash. When I do a make,
I can type ^c to stop it under zsh. But under bash, the make is
stopped. However, those makes in subdirs continue.

BTW, something is very strange with mm in 0.97 pl2. Some
binaries, mount and tools/build, linked with static or
old shared libs die with segmentation fault. mount and build
linked with jump table 3.0 work fine.

H.J.
From: wirzeniu@klaava.Helsinki.FI (Lars Wirzenius)
Newsgroups: comp.os.linux
Subject: Re: questions: vi problem, make dep, filenames, libraries
Date: 4 Sep 92 15:11:11 GMT
Organization: University of Helsinki

mal11@po.CWRU.Edu (Matthew A. Lewis) writes:
>Second, I finished the GCC install script and it told me to do
>a make dep with the kernel Makefile. What does make dep mean? Will
>this recompile the kernel for me? How do I implement the patches in this?

Doing a make dep means, basically, this:

	cd /usr/src/linux
	make dep

Change the directory name on the first line to whatever directory you
use to store the kernel sources.

>Next, what are the limitations on filename lengths and is there a way
>to change it????

The Minix filesystem has 14 chars max per filename.  This is the default
filesystem, and the only one in production use.  There is also an
extended filesystem, extfs, that has a maximum of 256 chars per
filename, but this filesystem is still in a testing phase, and unless
you enjoy having problems and solving them, you probably want to stay
away from it.

--
Lars.Wirzenius@helsinki.fi
Xref: sparky comp.os.linux:9086 alt.cd-rom:2734
From: ericy@hal.gnu.ai.mit.edu (Eric Youngdale)
Newsgroups: comp.os.linux,alt.cd-rom
Subject: Re: What is a good PC CD-ROM drive for me?
Date: 25 Aug 92 22:58:50 GMT
Article-I.D.: mintaka.1992Aug25.225850.8501
Organization: /etc/organization

In article <RUSSELL.92Aug25150134@csd475a.erim.org> russell@csd475a.erim.org (John Russell) writes:
>	>   Keep in mind that the real cheap drives can have seek times on the
>        >order of 800ms.  If this is acceptable to you, then go ahead.
>   
>   I have seen software advertised that speeds these slow access units up.
>   Has anyone tried this software? Do you get a noticeable performance 
>   increase?  I don't remember the name/manufacturer of the software.
>   The price was quite reasonable.

	I do not know anything about this software.  My guess is that this
is nothing more than a cache of some kind, and with linux we use the same
buffer cache that the regular disk drives use.  Also, many drives have a 64k
track buffer, which also helps to reduce I/O time, but would obviously not do
very much for the seek times.

-Eric
Newsgroups: comp.os.linux
From: cummings@tiger1.prime.com (Kevin J. Cummings)
Subject: Re: Beta TCP/IP 
Organization: Prime Computer, Inc.
Date: Fri, 28 Aug 1992 18:31:20 GMT

In article <714839549snx@crynwr.com>, nelson@crynwr.com (Russell Nelson) writes:
> In article <1992Aug25.233806.11161@morrow.stanford.edu> bir7@leland.Stanford.EDU writes:
> 
>    Currently only the Western Digital Ethercard Plus and compatibles
>    are supported (wd80[01]3 boards).  If you have a different ethernet
>    board you will either have to write your own driver or wait until
>    someone else does (There is someone who claims to be working on
>    drivers for many different ethernet boards.)
> 
> Yes.  I'm going to get a NE2000 driver going first, because they're
> so ubiquitious and cheap.  Any votes for what comes after that?
> 3Com's brand new 3c509 is a pretty high-tech card...

Could someone tell me where SL/IP support fits into this picture so I don't
have to keep using KA9Q for it?
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Newsgroups: comp.os.linux
Subject: Re: getting "bogus do_no_page"; strange vi behavior
Date: 31 Aug 92 19:58:05 GMT
Organization: University of Helsinki

In article <1992Aug31.145123.20915@novell.com> bboerner@novdpd.uucp (Brendan B. Boerner) writes:
>Hello, using Linux 0.97 and later 0.92 Pl#2, when compiling (among
>other things) on a (386/16 w/a tad under 5MB of RAM) I start getting
>spurious "bogus do_no_page" messages.  These don't appear on my
>girlfriend's computer (486/33 w/8MB RAM).

The "bogus do_no_page" error seems to happen on older 386 chips: they
sometimes give spurious page-faults.  The linux approach is just to
print the warning message and return: it seems to work, and the 386 will
happily do the page translation correctly the next time around.  You
should be able to safely uncomment the printk() that prints the message:
especially if linux doesn't seem to mind, and you have no other
problems. 

>Also, after upgrading to 0.97, I noticed that vi has been acting
>funny.  While inserting into a line, it starts adding spaces.  Using ^L
>will redraw the screen and show that the spaces really don't exist.

I think this is due to an incorrect /etc/termcap: the correct fix is
naturally just to dump 'vi' and start using some emacs-like editor :-)
If that isn't possible, try getting a new termcap from a newer rootdisk,
and the problem should hopefully disappear. 

		Linus
Newsgroups: comp.os.linux
From: drew@ophelia.cs.colorado.edu (Drew Eckhardt)
Subject: Re: SLS is awesome and getting larger
Organization: University of Colorado at Boulder
Date: Thu, 27 Aug 1992 15:51:24 GMT

In article <cebB_7a00WCX0E5HxD@andrew.cmu.edu> "Brian E. Gallew" <geek+@CMU.EDU> writes:
>>Actually, Linux also supports several other SCSI controllers, the
>>ST01/2 (Seagate) being among them, and those are s'posed to be dirt
>>cheap.
>
>As the proud owner of an ST01, my advice is:
>Spend the extra bucks to get a real controller!
>
>I tried to plug a Wang SCSI tape drive into it last night, but the
>ST01 only talks to hard drives (and probably Seagate ones at that).

Wrong.  The Seagate talks to anything you have a driver for - 
note that there is no publically available tape driver for 
Linux.  There is a Seagate tape driver for DOS though, you
might check the FTP sites for it.

>Also, the nicer cards give a lot better performance.

Agreed.

>
>Don't get me wrong, the ST01 is completely function (for what it
>does), but I think that in the long run you will be disappointed.

Of course, if cost is the only criteria, $20 is a drop in the 
bucket compared to an Adaptec.
-- 
Microsoft is responsible for propogating the evils it calls DOS and Windows, 
IBM for AIX (appropriately called Aches by those having to administer it), but 
marketing's sins don't come close to those of legal departments.
Boycott AT&T for their absurd anti-BSDI lawsuit.
Newsgroups: comp.os.linux
From: fh8n@uvacs.cs.Virginia.EDU (Frank Houston)
Subject: SLS is awesome and getting larger
Originator: fh8n@opal.cs.Virginia.EDU
Organization: University of Virginia Computer Science Department
Date: Wed, 26 Aug 1992 12:51:43 GMT

Hello linux hackers

I have just finished installing the SLS distribution of linux 
over the weekend. Congratulation to linus and the authors 
of sls. You guys give hackers a good name. The points is 
SLS is now 15 disk and growing to morw than 20. Time to 
go CDROM. On that subject DAK sells a CDROM with controller
for $199. I alspo received a compuadd catalog on Aug 20
that has a Cdrom and card for $169. So the price isn't 
as steep. I know that there is a SCSI cdrom driver in development
, but they seem a lot more expensive. 
	
	$150 for the Adaptec board supported.
	$250 for the cheapest scsi cdrom.

How about the linus community agree upon one of the minimaly 
priced cdrom unix about and create drivers it. This would
create a defacto common linux cdrom drive.

I have just started playing with linux, maybe one I look 
at the code dor the current SCSI cdrom driver I can consider
trying to make my own. But I know writing unix device drivers
is not for the fain of hear :)



-- 
From murdoch!uvaarpa!haven!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!swrinde!ucsd!nosc!crash!pro-graphics.cts.com!pierre Thu Sep 20 16:34:49 EDT 1990
Article 65663 of comp.sys.amiga:
>From: pierre@pro-graphics.cts.com (Pierre Altamore)
From: danielce@mullian.ee.mu.OZ.AU (Daniel AMP Carosone)
Newsgroups: comp.os.linux
Subject: install/strip corrupts filesystem ?
Date: 4 Sep 92 03:01:37 GMT
Organization: Computer Science, University of Melbourne, Australia

I would have put this down to random wierdness, but after discussions
on #linux (IRC) it seems I'm not the only one experiencing this.


A couple of days ago, I recompiled gdb 4.6 from scratch. When it was
done, make install used /usr/bin/install (which I assume came from the
binutils package from gcc 2.2.2d) to copy the executable to
/usr/local/bin/gdb. I mv'ed it to /usr/bin, and stripped it.

Gdb seemed to work fine, at least for the minimal use I gave it over
the last day or so.

The filesystem saw some more use, a few more files written, deleted, etc.

Next reboot, fsck -a /dev/hda2 (the /usr partition) spewed out
hundreds of lines like:

  Block has been used before. Now in file `/bin/gdb'

followed by a largish number of similar lines for other files in the
filesystem.

Repeated applications of `fsck -a /dev/hda2' reported `File system has
been changed' but didn't seem to clear up the problem.

It looked to me like two files seemed to be claiming to own the same
block. A very quick check showed that gdb still loaded and read the
symbols from a file (ie, wasn't obviously corrupted, but with a 770k
static demand-paged executable, you might not see corruption for a
while) Picking some of the other files in the list at random, they
seemed okay also.

This is a fairly new minix filesystem, made only a couple of weeks ago
when I reinstalled on a new machine.


Anyway, I flicked over to #linux and asked if anyone else had seen
this sort of behaviour from the filesystem/fsck before. Sure enough,
someone had (Thanks, Matt) and usually after having run `install'
(possibly with the -s flag to invoke strip). After some discussion, I
deleted /usr/bin/gdb, and was greeted with a bunch of kernel messages:

  free block (0302:nnnnn): bit already cleared

Another fsck -a complained about blocks owned by all the other files
in the list being marked free, fixed that, and now the filesystem
*seems* to be sane and consistent, again with fairly cursory checks.


So: how does `strip' do it's stuff? I assume it's not directly
manipulating the filesystem (ugh, only DOS would do that) but could
something in the way it removes symbol information from a file
exercise a bug in the filesystem code? Perhaps leaving the `holes'
marked free (to be claimed by other files), yet owned by gdb? Some of
the files in the list were *older* than the gdb binary, so this isn't
a particularly satisfactory hypothesis. Any better ideas?

_______________________________________________________________________________
Daniel AMP Carosone.      email: danielce@ee.mu.oz.au     snail: 37 Wandin Road
Computer/Software Eng,      IRC: Waftam                         Camberwell 3124
University of Melbourne.    Vox: +61 3 882 8910                       Australia
Newsgroups: comp.os.linux
From: schli@cs.tu-berlin.de (Wolfram Schlickenrieder)
Subject: Linux TeX / dvi2epson anywhere?
Organization: Technical University of Berlin, Germany
Distribution: comp
Date: Fri, 4 Sep 1992 13:48:16 GMT


	Hi...

	I think of (finally) getting rid of the gaddawful DOS and
	switch to Linux. One of the things I want to continue using is
	TeX, but -- as I'm unfortunately far away from being
	especially rich and therefore forced to stick with the Epson
	printer at home -- I can't find a dvi driver for it.  I'm sure
	there must be one around somewhere -- you can't all have LJ2Ps
	sitting around, can you ;-) ?

	Any pointer is much appreciated...

	...Wolfram
From: hurtta@cs.Helsinki.FI (Kari E. Hurtta)
Newsgroups: comp.os.linux
Subject: Re: gcc compiler bug involving <linux/ctype.h>?
Date: 26 Aug 92 11:34:44 GMT
	<HURTTA.92Aug26131805@plootu.Helsinki.FI>
Organization: Department of Computer Science, University of Helsinki, Finland

In article <HURTTA.92Aug26131805@plootu.Helsinki.FI> hurtta@cs.Helsinki.FI (Kari E. Hurtta) wrote:
> In article <1992Aug26.020845.15618@watson.ibm.com> derek@watson.ibm.com (Derek Lieber) wrote:
>> The problem seems to be due to the toupper macro defined in <linux/ctype.h>.
>> The macro looks fine to me, but changing it from...
>> #define toupper(c)          (_ctmp=c,islower(_ctmp)?_ctmp-('a'-'A'):_ctmp)
> 
> So error is in macro.

Or you use that macro (or header file) in place where isn't meant to use.
Well, I don't know anything about sources of Linux or gcc.

- K E H
Newsgroups: comp.os.linux
From: vesseur@fwi.uva.nl (Joep JJ Vesseur)
Subject: Re: clearing SUID bit on writes
Organization: FWI, University of Amsterdam
Date: Tue, 1 Sep 1992 23:50:18 GMT

Frank T Lofaro <fl0p+@andrew.cmu.edu> writes:

>	Linux should definitely un-setuid and un-setgid files on any
>modification (such as an append). Otherwise it could prove to be a very
>nasty security hole. 
>[...] doesn't belong in a secure (well,
>as secure as UN*X can reasonably be) environment.

   well, i don't know to what extend linux _is_ secure (anyone out there
cares to make any correctness proofs?) and whether anyone uses it
as a real multiple user (read: different users) system at the moment,
but no doubt this will happen in the future.
   i only don't think it should clean the bit on all modifications, only
those initiated by users with a different real-uid than the owner of
the file, in contrast to sysV.

joep.

---
joep vesseur     ---     email: vesseur@fwi.uva.nl
Newsgroups: comp.os.linux
From: drew@ophelia.cs.colorado.edu (Drew Eckhardt)
Subject: Re: SCSI Card:Procom woes
Organization: University of Colorado at Boulder
Date: Mon, 31 Aug 1992 06:49:11 GMT

In article <1992Aug31.044201.961@cs.uow.edu.au> u9050728@cs.uow.edu.au (Shane Kelvin Richards) writes:
>
>	I own a scsi card a "Procom" (its 8bit). Now for this to run on my
>dos system it needs a dos driver, I am just looking at the manual and it
>says the driver is only needed to allow DOS to access more than 2 non-floppy
>disk drives and so that DOS can handle removable scsi-media.

>	Is there any way at all Linux can be made to "see" the scsi card
>and thus my scsi HD. I have a 330meg scsi hard drive which I would love to
>be able to use with linux (at the moment I have had to partition off a
>40meg ide drive - so that linux only has about 20meg at the moment).

If you have the motivation, you could write a low level SCSI driver
for it.  This would amount to 400-1000 lines of kernel code, and 
if you can't get docs, reverse engineering the SCSI BIOS.  

An easier solution would be to run a different SCSI controller, 
although you may have to reformat the drive because of different
mapping conventions.







-- 
Microsoft is responsible for propogating the evils it calls DOS and Windows, 
IBM for AIX (appropriately called Aches by those having to administer it), but 
marketing's sins don't come close to those of legal departments.
Boycott AT&T for their absurd anti-BSDI lawsuit.
Newsgroups: comp.os.linux