HDTenEightyP/NetNews huggingface dataset:
From: ctne_ltd@uhura.cc.rochester.edu (Chris Newbold)
Newsgroups: comp.os.linux
Subject: [BUG REPORT] swapping trouble with 0.98-pl6 ?!?
Date: 14 Dec 92 05:39:57 GMT
Organization: University of Rochester - Rochester, New York

I have been having trouble with 0.98-pl5 and 0.98-pl6 when
running under X. The machine will suddenly lock when I try
and run commands in an xterm window. This happens 1-4
times an hour.

I can reproduce the problem almost consistently by trying
to copies of ghostview simultainously. Other commands that
frequently cause the system to hang are: tar, groff and
make/gcc.

At first I thought that this might be a problem with the
X386-S3 server. However, some experimentation proved this
theory invalid. I have this trouble under pl5 or pl6, with
X386-S3 version 0.2b or 0.3 or the X386mono server.

I stress-tested the system outside of X to see if I could
reproduce the problem, but had no luck. Though I pushed the
load average over 3 with extreme disk activity, nothing
broke. However, I was unable to use up much of the swap
space--which is what I think kills everything.

Is anybody else having troubles like this? This is perhaps
the worst bug I have disovered since the old SCSI code
would trash my disk daily...

My system:

486/33DX, EISA bus
8MB ram
AHA1542 SCSI disks

8MB swap parition

-Chris

-- 
>>>> Chris Newbold <<<< * "If you fool around with a thing for very long you *
University of Rochester	*  		  will screw it up."		     *
Disclaimer: "All warranties expire upon payment of invoice."                
ctne_ltd@uhura.cc.rochester.edu * uhura.cc.rochester.edu!ctne_ltd@uunet
Newsgroups: comp.os.linux
From: wirzeniu@klaava.Helsinki.FI (Lars Wirzenius)
Subject: Re: Faq for 0.95p5...needed!
Organization: University of Helsinki
Date: Mon, 14 Dec 1992 16:57:52 GMT

tfoley@camaro (Tim Foley) writes:
>  Someone should write a faq for converting from 0.98p1 to 0.98p5 and 
>above.

Probably one of the easiest ways is to install the newest SLS.  That
should make it easier for you to stay up to date as well.  I did this
myself, just to see what SLS looks like.  (I'm probably going to start
from scratch _again_ in a while, just for the pleasure of compiling
everything myself; however, I think I know what I do and how most
things work, if you don't you might be better off with SLS).

If you have things that are not in SLS, you should get their sources,
upgrade to SLS, then recompile and install them.  Recompilation is
needed so that the program will not use old versions of system calls,
and such things.  

There are a couple of things that won't be fixed by a simple
recompilation.  I know of two programs: uucp and minicom.  uucp uses a
library function (sigaction, I think) in such a way that it triggers a
bug, and will cause trouble because of that.  This can be fixed by
configuring uucp so that it won't use sigaction.  Minicom has a bug
that causes it to modify a string literal, which is not allowed.  This
can be fixed by replacing the string literal with an array that has
been initialized to the value of the string literal.

I do not know whether the above are fixed in the current versions of
SLS, but if not, they will be.

For people who don't enjoy building their systems from scratch, SLS is
currently the easiest way of installing Linux.  Those of us who prefer
to do it our own way (with our very own bugs :) do it that way.

--
Lars.Wirzenius@helsinki.fi  (finger wirzeniu@klaava.helsinki.fi)
   MS-DOS, you can't live with it, you can live without it.
Newsgroups: comp.os.linux
From: s9100786@cumulus.csd.unsw.oz.au (Matthew Jackson)
Subject: Re: Does bootlin.com work with the new kernel?
Reply-To: M.Jackson@unsw.edu.au
Organization: School of Banking and Finance, University of New South Wales
X-Newsreader: TIN [version 1.1 PL8]
Date: Mon, 14 Dec 1992 23:42:45 GMT

Andrew J. Cosgriff ! (andrewc@aurora.cc.monash.edu.au) wrote:
: joel@wam.umd.edu (Joel M. Hoffman) writes:

: >In article <1992Dec13.193812.6958@tc.cornell.edu> torvalds@cc.helsinki.fi (Linus Torvalds) writes:
: >>Linux version 0.99 is now available at nic.funet.fi, in the directory
: >>pub/OS/Linux/PEOPLE/Linus as both full source and patches against
: >>0.98.6.  It will probably show up on the other major sites soon. 

: >>NOTE!!! Use LILO-0.7 to load the 0.98pl5 and newer kernels: any older
: >>version of lilo is liable to result in weird problems. 

: >What about bootlin.com?  Does that still work?

: I don't see why not...It's just that LILO 0.6 did weird things to 98p6 when
: you booted it (apparently - nothing weird happened to me except I now have a
: 1024 byte ramdisk, but i can live with that - I've got 8MB to play with,
: anyway...)

Bootlin works for me on 0.98pl6 - I used it after the pl6 problem was 
discovered to be lilo until I could download lilo 0.7.

Cheers,

--
Matthew Jackson                       | Computing Officer
M.Jackson@unsw.edu.au                 | School of Banking and Finance
61-2-697-3553                         | University of New South Wales
                                      | Sydney, Australia
From: higgins@mozart.uni-paderborn.de (Frank Westheider)
Newsgroups: comp.os.linux
Subject: Where to find SLIP/PPP, How to get UUCP to work
Date: 18 Dec 1992 13:48:22 +0100
Organization: Universitaet Paderborn, Germany
NNTP-Posting-Host: mozart-bb.uni-paderborn.de
Keywords: PPP,SLIP,UUCP

Hi Linuxer !

I'm looking for the SLIP/PPP distribution. Where can i find them,
how does it work.

Second question : How can i get a UUCP working with a direct
                  serial-cable between 2 Linux-Boxes ??


Thanks
   Frank  (higgins@uni-paderborn.de)
Newsgroups: comp.os.linux
From: ngoh@rintintin.Colorado.EDU (NGO HIEN D)
Subject: Re: why does telnet sometimes lock up X????
Summary: update your kernel and tcp binaries.
Organization: University of Colorado, Boulder
Date: Sun, 13 Dec 1992 11:17:28 GMT

I've had this problem in the past, with telnets locking up my machine
forcing a reboot.  Usually ends up in a kernel panic or locked up X
server with no diagnostic info.  From 0.97pl6 -> 0.98pl4 or so
actually.  I think it's been a combination of many factors; old telnet
binaries, broken config, problems with tcpip, etc.  But I am happy to
report that my system runs flawlessly now.  Using 0.98pl6 + suite of
tcpip patches and the new telnet[d], ftp[d], and nfs I have not had a
problem.  That would be my only suggestion to you... just update the
kernel and your binaries.  I am just ecstatic that I have a completely
stable system with all of the tools/toys that I use.  

On another note, I have crossfire compiled for Linux if anyone is
interested.  I think it is the latest version (0.87.something), in
case you haven't heard 'bout it, crossfire is a cross between
Gauntlet and hack/moria.  Only real problem I had was that xmkmf
would get hung up on one line in the Imakefile.

+--------------------------------------------------------------------------+
| Hien D. Ngo                                        ngoh@rtt.colorado.edu |
| Computer Science Undergraduate                                           |
| University of Colorado at Boulder                                        |
\--------------------------------------------------------------------------/
Newsgroups: comp.os.linux
From: minyard@crchh7b9 (Corey Minyard)
Subject: 0.99 general protection error
Organization: Bell-Northern Research, Richardson, Tx
X-Newsreader: TIN [version 1.1 PL8]
Date: Mon, 14 Dec 1992 18:42:08 GMT

The default 0.99 kernel gave me a general protection at startup.  The kernel
was crashing in wake_up().  After some creative debugging (I added a stack
trace-back to the exception handler) I found the bug was coming from iput().
It turns out that the inode_wait variable was not being initialized to NULL.

Make the following change the following in fs/inode.c to fix the problem.
This is not really a diff, but you should get the idea:
***
  static struct inode inode_table[NR_INODE];
  static struct inode * last_inode = inode_table;
! static struct wait_queue * inode_wait;
  
  void inode_init(void)
  {
***
  static struct inode inode_table[NR_INODE];
  static struct inode * last_inode = inode_table;
! static struct wait_queue * inode_wait = NULL;
  
  void inode_init(void)
***

Corey
minyard@bnr.ca

Newsgroups: comp.os.linux
From: wirzeniu@klaava.Helsinki.FI (Lars Wirzenius)
Subject: Re: How stable is extended filesystem?
Organization: University of Helsinki
Date: Wed, 16 Dec 1992 19:51:52 GMT

Steve.Harrington@f34.n343.z1.fidonet.org (Steve Harrington) writes:
>Actually the efs author has also mentioned that he will release
>a program to convert to the new file system.  A backup and restore
>won't be necessary.

A backup is still very, very, very advisable.  Backing up before doing
anything dramatic is always a good idea.  (What if the conversion
program has a subtle bug that only manifests itself on your machine?)

--
Lars.Wirzenius@helsinki.fi  (finger wirzeniu@klaava.helsinki.fi)
   MS-DOS, you can't live with it, you can live without it.
Newsgroups: comp.os.linux
From: erc@unislc.uucp (Ed Carp)
Subject: Re: Linux 0.99 FPU question
X-Newsreader: TIN [version 1.1 PL6]
Organization: Unisys Corporation SLC
Date: Fri, 18 Dec 1992 17:00:26 GMT

Gary Faulkner (garyf@uts.amdahl.com) wrote:

: Even better, does anyone have an idea about why I am having to have
: FPU emulation in my kernel? I realize that not many people (guessing
: here) have 486's running linux, but if so, has anyone else tried NOT
: including the FPU-emu stuff in their kernel?

I'm running a 486/25, and I didn't have to build FPU into the kernel...
-- 
Ed Carp			erc@apple.com, erc@saturn.upl.com	801/538-0177

Who and what would you be if you went beyond your deepest fears?
Newsgroups: comp.os.linux
From: marks@sci.kun.nl (Mark Stoutjesdijk)
Subject: SLIP
Summary: Who's got any experience with slip?
Keywords: Serial Line IP
Organization: University of Nijmegen, The Netherlands
X-Newsreader: NN version 6.4.19
Date: Fri, 18 Dec 1992 17:09:53 GMT

Hi there folks!

Who's got any experience with SLIP?

Would this enable me to use my Linux as if connected by TCP/IP, thus
being able to telnet and ftp directly from home? (As far as telnet
and ftp are direct, of course)

Mark Stoutjesdijk
marks@sci.kun.nl


Newsgroups: comp.os.linux
From: "William L. Mullica" <p00192@psilink.com>
Subject: TO ALL THOSE WHO THINK THE VOLUME IN comp.os.linux IS TOO HIGH
Organization: Performance Systems Int'l
Date: Sat, 12 Dec 1992 13:15:09 GMT
X-Mailer: PSILink-DOS (3.3)

I've asked a number of questions on comp.os.linux and almost always get 
replies/answers back by mail. I think this is good in order to keep the 
number of news articles to a manageable level. However, once "the 
answer" has been tested and proven to work, I think that the person who 
asked the original question should post "the answer" to the news group. 
This would, hopefully, prevent others from asking the same question over 
and over and would further reduce the volume in comp.os.linux.

Comments?

Bill, N6CKM

Newsgroups: comp.os.linux
From: bhenning@wimsey.bc.ca (Bill Henning)
Subject: Re: Modem control (was Re: uucico not hanging up the telephone line)
Organization: Wimsey Information Services
Date: Sun, 20 Dec 1992 06:31:42 GMT

Thanks, will disable text responses...
From: eekim@husc10.harvard.edu (Eugene Kim)
Newsgroups: comp.os.linux
Subject: Working Linux!/Suggestions
Date: 18 Dec 92 01:33:22 GMT
Article-I.D.: husc3.1992Dec17.203324.18642
Organization: Harvard University Science Center

Hi.  After following this newsgroup for about two months, I finally downloaded
Linux and successfully installed it a couple of weeks ago.  It is great!  The
installation was successful with very few glitches (I used the SLS 0.98 pl5)
and everything, including the alpha S3 server, works very nicely.  It is also
extremely fast, the most impressive thing of all.

Anyway, I just had a couple of thoughts.  My main trouble with the installation
was hard disk partitioning.  After I figured out how much space and how many
blocks my partitions should be, partitioning was fairly easy.

The most difficult aspect was understanding the organization of the file
structure.  I had trouble with this mainly because I have only limited
experience with Unix, and zero as a system administrator.  I think what would
be useful in future distributions (maybe this is being done with the
documentation?) is explain the directory structure, and talk about where files
generally go and how much customization you should do.

Just as a side note, I wrote an article for the Harvard Computer Review about
Linux.  It will be coming out in the February issue.  Unfortunately, the HCR
is not really an established publication at Harvard yet, but I hope the few
people who do read it will spread the word about Linux and try it out.

Once again, I love Linux and am looking forward to porting as many programs
as possibly, perhaps even writing a few of my own :)

Thanks Linus et al.

-- 
Eugene Kim '96                     |   "If we do not succeed, then we run the
INTERNET: eekim@husc.harvard.edu   |    risk of failure."        --Dan Quayle
From: cyberman@exucom.com (Stephen R. Phillips)
Newsgroups: comp.os.linux
Subject: Suggestion Spliting Group
Date: 12 Dec 92 04:47:02 GMT
Organization: ExuCom MultiMedia Inc.
X-Newsreader: TIN [version 1.1 PL7]


In hopes that this will prevent the 99-300 message per day from
SWAMPING most poeple.  I suggest this group be split.

how about
comp.os.linux.announce
comp.os.linux.help
comp.os.linux.discussion
comp.os.linux.x

This is a suggestion perhaps it's not worth doing but I can't keep up
with 152 threads and 192 articles (per DAY).  

perhaps adding
comp.os.linux.flame would be good to? :)
Cyberman
-- 
This is my sig file!
Read rec.games.programer!
From: eekim@husc11.harvard.edu (Eugene Kim)
Newsgroups: comp.os.linux
Subject: Porting gnuplot to Linux
Date: 16 Dec 92 22:14:40 GMT
Organization: Harvard University Science Center

Hi.  I've been trying to port gnuplot to Linux.  Everything was compiling
nicely until the very end, when the Makefile tried to compile the file
plot.c with the directive -lplot.

I searched my whole hard drive, and could not find the file "libplot.a"
Does anyone know what directive I should use?  I'm using makefile.unx.

Please reply by e-mail.  Thanks in advance.

-- 
Eugene Kim '96                     |   "If we do not succeed, then we run the
INTERNET: eekim@husc.harvard.edu   |    risk of failure."        --Dan Quayle
From: ail8070@tamuts.tamu.edu (Andy I. Liaw)
Newsgroups: comp.os.linux
Subject: Olvwm won't run...  Help!!
Date: 13 Dec 1992 02:06:56 GMT
Organization: ~/lib/organization
NNTP-Posting-Host: tamuts.tamu.edu

Can someone with olvwm working tell me why it doesn't work for me?
I got olvwm-bin.t.Z from sunsite, unpacked it, and did what where_to_put
said.  I then change the twm line to olvwm -3d in my  .xinitrc, and
then startx.  The mouse pointer showed up for about 30 sec. and then
I'm back in text mode with some message saying can't open display.
This happens whether I set DISPLAY to :0 or not.

Am I missing something?  Someone give me some hints please!!

andy
aliaw@stat.tamu.edu
From: wilsont@rahul.net (Timothy Wilson)
Newsgroups: comp.os.linux
Subject: I'm a newcomer, i have problems! please help.
Keywords: ]
Date: 16 Dec 92 07:25:25 GMT
Organization: a2i network

Here's my story:
I'm a C programmer from a unix/motorola background.
I hate ms-dos
I found linux.
I DL'ed linux boot and root.
it booted 3 times.
I read instructions and FAQ's saying i need to partition my drive.
I partitioned my drive.
I discovered some wierdo CMOS setup thingy. 
i tried telling this CMOS thingy about my HD.
I tried to boot linux.
it hasnt worked since.
after "Linux version xxxx" it just sits there
(it used to give me a shell, but not now!)

I use a 386sx-16  4MB ram. and a 40 meg HD, math coprocessor. paradise vga card.

vt's 2-4 don't work either.

I've been around computers for a long time, and have never scene anything so
twisted as this clone i work on. I'm not a IBMer, i'm a unix guy.

replies to email would be cool, but not neccesary.

thank you!.//oh and thank you!
-- 
Timothy Wilson <wilsont@rahul.net>
Newsgroups: comp.os.linux
From: mopar@uxa.cso.uiuc.edu (Mopar Mike)
Subject: xwindows/et4000
Organization: University of Illinois at Urbana
Date: Fri, 18 Dec 1992 08:24:58 GMT

Hello Fellow linuxers!  I grabbed the SLS version of X and installed 
it onto my drive.  When I run startx the monitor goes into fits of
gray and white.  I've got a tseng labs svga card with an et4000 chip
set, linux .99, a 386dx-40 w 16 meg.  Has anyone seen this problem 
before?  Any help would be appreciated.

					mopar@uxa.cso.uiuc.edu

Newsgroups: comp.os.linux
From: drew@ophelia.cs.colorado.edu (Drew Eckhardt)
Subject: Re: SPLIT #$%&%$ THIS GROUP NOW!!!!!!!
Organization: University of Colorado at Boulder
Date: Mon, 14 Dec 1992 03:52:14 GMT

Net news has more than just comp.os.linux*.  There are a number of other 
hierchies, such as comp.windows.x, comp.unix, etc that are better suited 
to many linux questions.  

If people would use these, and then post to comp.os.linux only after 
reading the various FAQ's, info sheets, and TFM, maybe we wouldn't 
have any traffic problems.

 
In article <BCR.92Dec12201153@hfl3sn02.cern.ch> bcr@cernapo.cern.ch (Bill Riemers) writes:
>
>I'm not sure why .bugs failed, but it is clear why .questions and .misc failed.
>What is the difference?  Also what would be the point of posting to .questions,

The FAQ, TFM, and comp.os.unix.questions probably cover 99% of the traffic 
that would end up in this group.  The other 1% of this traffic shouldn't
make a significant impact on comp.os.linux.

>when the experts would probably just read .bugs and .misc.

> .x11

Try

comp.windows.x.announce
comp.windows.x.motif
comp.windows.x.pex
comp.windows.x.apps
comp.windows.x.intrinsics

For general questions, you'll reach a much wider audience that is
knowledgeable about X.

There shouldn't be any real linux specific issues for X (You could
make an argument for -pn (no tcp-ip support), but some commercial
vendors have unbundled tcp/ip and -pn would apply for them)

comp.windows.x.i386unix should catch all of the Xfree stuff, this
will benefit the BSD crowd and everybody with a commercial x86
unix that wants an R5 server and clients.


> .dosemulation

Try comp.unix.dos-under-unix.  Technical issues should go to the 
mailing list where they won't be lost in the noise.

> .graphics

Outside of a few X related posts, and an anouncement for shared libraries
handling jpeg, etc, I haven't seen any recent graphics related posts on 
comp.os.linux.  

> .install

Read the FAQ.

Read the instructions that come with the SLS distribution.

No problem.

>
>This is hardly intended to be a complete list, but merily the obvious ones
>that came to mind.

Please drop the split discussions.  More sub groups weren't created because
people didn't want them, or didn't care enough to participate in the 
RFD or CFVs.  If you still feel the same way in six months, start a 
new RFD.  
-- 
Boycott AT&T for their absurd anti-BSDI lawsuit. | Drew Eckhardt
Condemn Colorado for Amendment Two.		 | drew@cs.colorado.edu
Use Linux, the fast, flexible, and free 386 unix |  
Newsgroups: comp.os.linux
From: jliddle@rs6000.cmp.ilstu.edu (Jean Liddle)
Subject: Re: A proposal for organizing comp.os.linux. [NEW-CHANNELS]
Date: Sun, 13 Dec 1992 23:37:05 GMT
Organization: Illinois State University

I have been dilligently trying to avoid this, but felt I had to respond to
this post.

In article <1992Dec13.204007.17189@reed.edu> nelson@reed.edu (Nelson Minar) writ
es:
>
>However, if a few of the louder voices on comp.os.linux really wanted
>to, we could still split comp.os.linux this week. Instead of splitting
>it according to the normal Usenet voting procedures, split it into the
>alt groups. Alt groups don't require a vote - a week's discussion on
>alt.config seems to be sufficient.
>
>There are some good reasons not to do this. For one thing, it's fairly
>sleazy.

This is a very *B A D* idea.  It is inappropriate to circumvent usenet
policies because we disagree with the results.  Such a move would be
very detrimental to the whole climate of the linux community, and would
be very asocial to boot.

Now please, please, lets keep the bandwidth clean of this stuff 'till 
next May or so.

Jean.

BTW - I have been reading c.o.s (formerly a.o.s) since April.  I missed
the call for votes, as probably did others.  Such is life.  I am speaking
as one who probably would have voted for a split, and will do so next time
this comes up.  Nevertheless, it is time for those of us who disagree with
the results of the last vote to take our lumps gracefully and shut-up.
-- 
Jean Liddle                                 
Computer Science, Illinois State University  
e-mail:  jliddle@ilstu.edu                  
--------------------------------------------
Newsgroups: comp.os.linux
From: ujlh@pool.info.sunyit.edu (James Henrickson)
Subject: Re: A little linux xmas success story
Organization: State University of New York -- Institute of Technology
Date: Tue, 15 Dec 1992 04:14:22 GMT

In article <1992Dec12.195027.5890@sol.UVic.CA> pmacdona@sanjuan (Peter MacDonald) writes:
>
>From the readme:
>] to boot from your harddrive.  Note that if you have less than 4 Meg of RAM,
>] you will need to make and activate a 4 Meg swap partition, prior to installation.
>] For example, using /dev/hda3 for swap: "mkswap /dev/hda3 4096; swapon /dev/hda3"
>

I had a short (very short!) experience running Linux on a 386SX-25 with
2 MB, and I would like to add a little advice.

Be sure you have "swapon" in your /etc/rc file before doing an "fsck".
Otherwise, you'll probably run out of memory.

(I experienced this with an older distribution of Linux that had "swapon"
 after "fsck".  This may have already been corrected.)

-- 
Jim H.
*
* James L. Henrickson  |  "I don't need a signature, I need a job!"
* ujlh@sunyit.edu      |  BSCS, December 1992
From: nation@dopey.sanders.lockheed.com (Robert Nation)
Newsgroups: comp.os.linux
Subject: Re: keyboard problems - v.99
Date: 16 Dec 92 22:09:57 GMT
Organization: Lockheed Sanders, Inc.
In-reply-to: ammo@cc.gatech.edu's message of 15 Dec 92 02:27:27 GMT

I also had the keyboard lockup when I first compiled 0.99, but
the problem went away when I completely removed the sound card support
and its stub. Are these events related? I don't know.

Note: my machine is a 486DX-33 no-name laptop, 4M memory.

			Rob Nation
			Lockheed Sanders
			Merrimack, NH
From: jars@carson.u.washington.edu (Juan Rodriguez-Sero)
Newsgroups: comp.os.linux
Subject: Problems compiling fstat
Summary: Can't compile fstat, make says "SYS_mmap undefined"
Keywords: fstat, ps
Date: 15 Dec 92 18:12:32 GMT
Organization: University of Washington, Seattle

After compiling and installing version 0.99, I tried to run ps -U
and got a message telling me to recompile.  I tried that, and most
of the programs in ps-0.98.tar+patch compile uneventfully; but com-
pilation of fstat aborts in the mmap step; I get a message saying
that "SYS_mmap undefined."  I haven't been able to fix this.  Has
anybody else had this problem? Is there any fix for it?

Thanks in advance for any help.


Juan Antonio Rodriguez-Sero; jars@u.washington.edu
(School of Oceanography; University of Washington, WB - 10)
-------------------------------------------------------------
Reality is what refuses to go away
when I stop believing in it.
				     Philip K. Dick
Newsgroups: comp.os.linux