HDTenEightyP/NetNews huggingface dataset:
From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Newsgroups: comp.os.linux
Subject: Re: gcc problems
Date: 6 Apr 92 15:14:55 GMT
Followup-To: LeBlanc@mcc.ac.uk
Organization: Computing Centre, University of Manchester

In article <EdqrFUe00VBCQaMlph@andrew.cmu.edu> aw2t+@andrew.cmu.edu (Alex R.N. Wetmore) writes:
>Linux seems to be missing quite a few
>of the process utils (kill, who, etc).  I assume that this is just
>because of the betaness.

The bash shell actually contains a builtin kill command.  There are
also the following utilities, which might be called 'process' or related
utilities, which have been included in various packages, and
which can be compiled and run under 095a plus patches:

     doshell     start a subprocess attached to a different virtual console
     free        report usage of memory and swap space
     kill        signals other processes
     login       lets you login and can be used instead of 'su -'
     logname     returns the name of the owner of the current process
     nice        starts a background job with low priority
     nohup       starts a background job that should survive parent's logout
     ps          process status reporting utility
     top         usage monitor

     -- Owen
     LeBlanc@mcc.ac.uk
From: wolff@neuron.et.tudelft.nl (Rogier Wolff)
Newsgroups: comp.os.linux
Subject: Re: __ctype undefined symbol error
Date: 10 Apr 92 08:24:08 GMT
Organization: Delft University of Technology, Dept. of Electrical Engineering

knapka@athena.cs.uga.edu (Joseph Knapka) writes:

>Hi, all. I was having trouble compiling ps after applying Linus' and
>H.J.'s patches to the .95a kernel. Turned out I hadn't rooted out all
>traces of gcc-1.40 --- that part of the FAQ is to be taken very seriously!
>Here's H.J.'s message:

>	__ctype is from the header files of gcc 1.40. Please backup and remove
>	any files related to the previous compilers before you install gcc 2.1.
>	There is no __ctype anywhere in the header files for gcc 2.1.
>	
>	BTW, they are in my FAQ. PLEASE READ IT WORD BY WORD AND FOLLOW THE
>	INSTRUCTIONS.
>	
>	Could you please forward my msg to news groups?
>	
>	H.J.
>	-- 
>	School of EECS				Internet: hlu@eecs.wsu.edu
>	Washington State University		BITNET:   60935893@WSUVM1.BITNET
>	Pullman, WA 99164			Phone:    (509) 335-6470 (O)
>	USA						  (509) 334-6315 (H)

>Thanks for your help, H.J. -- the fault was entirely mine.

>For those who are installing 2.1 for the first time, "Remove all other
>compilers" means "rm +recursive /usr/include /usr/lib /usr/local/lib
>(and anything else that looks suspicious)."  Took me a while to catch
>on to that :)

However the __ctype that ps manages to find is the one that comes with
linux kernel sources.  

ps needs a lot of include files from the system, to be able to
read kmem and so forth. However, ctype is also in the kernel
include directory, while the intended ctype is in the /usr/include
directory.

I changed
#include <ctype.h>
to 
#include "/usr/include/ctype.h"
and all managed to compile.

It still crashes though.....

					Roger
-- 
If the opposite of "pro" is "con", what is the opposite of "progress"? 
	(stolen from  kadokev@iitvax ==? technews@iitmax.iit.edu)
EMail:  wolff@duteca.et.tudelft.nl   ** Tel  +31-15-783644 or +31-15-142371
Newsgroups: comp.os.linux
From: david@ods.com (David Engel)
Subject: Re: kernel building problems
Organization: Optical Data Systems, Inc.
Date: Fri, 10 Apr 1992 16:29:06 GMT

news@solitary.Stanford.EDU (System test) writes:
: I've been going crazy trying to get either 0.95c or 0.95c+ to
: compile with gcc 2.1.  Which of these is the "second patch" to
: which H.J.'s patch is to be applied?  

It refers to 0.95c.  Unfortunately, Linus changed the Makefile around 
some in 0.95c+ causing H.J.'s patch and fix for combining the kernel
and gcc 2.1 headers to fail.

: In any event, the makefiles don't seem to work correctly for me and
: I don't know how to fix them.  The include files aren't found
: when the various directories are stepped into.
: 
: I screwed around until I got most everything to compile but can't
: get build to link. ld complains about an invalid offset for _write.
: Does anyone know what might cause this.

I got 0.95c+ to compile with gcc 2.1 by mucking with the Makefiles and
adding some symlinks in /usr/include to /usr/src/linux/include.  The
main thing to make sure of when compiling the kernel is that tools/build
should search /usr/include first and /usr/src/linux/include second, and
be linked with the gcc 2.1 libraries.  Everything else in the kernel
distribution (I'm not including ps) should be self-contained.

Aside to Linus:  Would you mind describing how you have your system set
up?  It might help aleviate problems like this if we knew which compiler
and system libraries you are using.

David
-- 
David Engel                        Optical Data Systems, Inc.
david@ods.com                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081
From: david@csource.oz.au (david nugent)
Newsgroups: comp.os.linux
Subject: smail 3.1.25
Date: Sat, 11 Apr 92 17:12:28 +1000
Reply-To: david@csource.oz.au
Organization: Unique Computing Pty Ltd, Melbourne, Australia

Has anyone got a working smail 3.1.25 for Linux yet? I managed to
get one compiled with a new machine description file and editing
the EDITME file to suit, and it seems to work - mostly. It
consistently traps _after_ delivering mail to local mailboxes,
otherwise it seems quite function.

I haven't been able to track it down further yet due to gdb not
functioning with the new gcc 2.1 beta + kernel + a.out.h, but I
thought I'd post this just in case the problem is known and
someone's already been though this before. If not, then I'll wait
for an updated gdb.

Regards,

  david

..............................................................................
david nugent          Public Access Usenet        "Only Nixon can go to China"
david@csource.oz.au     +61-3-792-3507                - ancient Vulcan proverb
3:632/400@fidonet, 58:4100/1@intlnet, 199:4242/5@rainbownet, 33:300/6@admin
PO Box 260, Endeavour Hills, Victoria, Australia, 3802.
From: UPP200@ibm.rhrz.uni-bonn.de (Guido Kueppers)
Newsgroups: comp.os.linux
Subject: IDE-drive performance with linux
Date: 16 Apr 92 09:02:33 GMT
Organization: RHRZ-Uni-Bonn

Greetings,

don't know whether this belongs here, but I'm experiencing a serious
performance problem with my new IDE-drive under linux:
I'm using a 386DX-20Mhz board with 4 MB of RAM and an unmodified 0.95c+ kernel.
Recently I exchanged my 2 MFM drives for a Rodime (3259A I believe) 200 MB IDE-
drive because the old drives were rather slow and I had been running out of
disk space. With the new drive I noticed that the machine and even the keyboard
sort of froze under heavy disk I/O like running compress or tar.

I then tried to copy a 3 MB file from one partition to another. It took about
2 minutes to complete with the keyboard freezing sometimes! Even copying from
floppy drives isn't much slower. Copying the same 3 MB file under PC-DOS 4.0
on the same drive takes about 20 seconds!
I never had this sort of problem with my old MFM drives (20 MB Fuji and 40 MB
Seagate ST-251 with WD controller). BTW while recompiling the system drive
performance seems to be normal (takes about 20 minutes), at least I don't think
the MFM drives were faster on that.
Does anyone have explanations, hints, experiences? Any feedback is welcome.

Thanks in advance
Guido
From: gt0178a@prism.gatech.EDU (Jim Burns)
Newsgroups: comp.os.linux
Subject: Re: Problems with serial port drivers??
Date: 17 Apr 92 04:12:25 GMT
Organization: Georgia Institute of Technology

in article <1992Apr13.184643.20236@colorado.edu>, drew@caesar.cs.colorado.edu (Drew Eckhardt) says:

>>>You're not *supposed* to be able to do this. The ISA interrupts are level
>>>triggered, which I believe means that after the ICU latches the first

[...]

>>>The MCA interrupts are level triggered, so this is not supposed to be a
>>>problem there.

> 100% false with ISA.  ISA interrupts are edge triggered.  It has nothing

[...]

> You are correct about MCA though - it uses level active IRQ lines,
> and they are open collector. 

Sorry, that was a typo, as you can tell from the contrast in the context.
-- 
BURNS,JIM (returned student)
Georgia Institute of Technology, 30178 Georgia Tech Station,
Atlanta Georgia, 30332            | Internet: gt0178a@prism.gatech.edu
uucp:	  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt0178a
Newsgroups: comp.os.linux
Newsgroups: comp.os.linux

From the FAQ:

> IDE and MFM seem to work with no problem. It works, also, for some
> ESDI drive (Joincom controller with Magtron drive after you have
> commented out the "unexpected hd interrupt"-message from hd.c).

Has anyone gotten linux to run with an Ultrastor Ultra 12F ESDI
controller?

Keith Fries
Hewlett Packard, Spokane Div.
fries@hpspkla.spk.hp.com
From: knapka@athena.cs.uga.edu (Joseph Knapka)
Newsgroups: comp.os.linux
Subject: Re: IDE-drive performance with linux
Date: 16 Apr 92 16:44:24 GMT
Organization: University of Georgia, Athens

In article <92107.36153.UPP200@ibm.rhrz.uni-bonn.de> UPP200@ibm.rhrz.uni-bonn.de (Guido Kueppers) writes:
>Greetings,
>
>don't know whether this belongs here, but I'm experiencing a serious
>performance problem with my new IDE-drive under linux:
>I'm using a 386DX-20Mhz board with 4 MB of RAM and an unmodified 0.95c+ kernel.
>disk space. With the new drive I noticed that the machine and even the keyboard
>sort of froze under heavy disk I/O like running compress or tar.
>

[stuff deleted]

>I then tried to copy a 3 MB file from one partition to another. It took about
>2 minutes to complete with the keyboard freezing sometimes! Even copying from
>floppy drives isn't much slower. Copying the same 3 MB file under PC-DOS 4.0
>on the same drive takes about 20 seconds!
>I never had this sort of problem with my old MFM drives (20 MB Fuji and 40 MB
>Seagate ST-251 with WD controller). BTW while recompiling the system drive
>performance seems to be normal (takes about 20 minutes), at least I don't think
>the MFM drives were faster on that.
>Does anyone have explanations, hints, experiences? Any feedback is welcome.
>
>Thanks in advance
>Guido

My 486 running linux seems zippier in all things than the SPARC 1 I
use at school -- except disk access. Moving big files across
partitions is *deathly* slow, as is waiting for way big swappy jobs to
finish. I didn't realize this wasn't normal -- I thought it was just
'cause the ISA bus is so dang-blamed slow... I don't get HD timeouts
or anything. My drive is a 130M Maxtor IDE.
From: jon@robots.ox.ac.uk (Jon Tombs)
Newsgroups: comp.os.linux
Subject: Sorry Linus
Date: 7 Apr 92 10:45:40 GMT
Organization: Robotics Research Group, Engineering Science Dept, Oxford, UK.
Originator: jon@diomedes.robots

The patch for linux 0.95c Linus probably doesn't want to see...

Apply to /usr/src/linux/include/linux/config.h

*** config.h^	Tue Apr  7 00:09:54 1992
--- config.h	Tue Apr  7 00:09:54 1992
***************
*** 16,22 ****
  #define UTS_SYSNAME "Linux"
  #define UTS_NODENAME "(none)"	/* set by sethostname() */
  #define UTS_RELEASE "0"		/* patchlevel */
! #define UTS_VERSION "0.95a"
  #define UTS_MACHINE "i386"	/* hardware type */
  
  /* Don't touch these, unless you really know what your doing. */
--- 16,22 ----
  #define UTS_SYSNAME "Linux"
  #define UTS_NODENAME "(none)"	/* set by sethostname() */
  #define UTS_RELEASE "0"		/* patchlevel */
! #define UTS_VERSION "0.95c"
  #define UTS_MACHINE "i386"	/* hardware type */
  
  /* Don't touch these, unless you really know what your doing. */


-------
Or should we be updating patch level?

--
 Jon			<jon@robots.ox.ac.uk>
 			"I got in today just as the sun was crashing"
From: ail8070@tamsun.tamu.edu (Andy I. Liaw)
Newsgroups: comp.os.linux
Subject: Re: Patch to preset the SVGA mode
Date: 10 Apr 92 03:10:19 GMT
Organization: Texas A&M University, College Station

In article <1992Apr9.164927.11540@Miles.COM> dennisf@Miles.COM (Dennis Flaherty) writes:
>
>If you are tired of hitting RETURN and selecting the
>same SVGA mode every time you boot Linux, apply this
>patch and rebuild the kernel.  It allows you to preset
>the mode in the Makefile, so that the setup program
>proceeds as if you had hit RETURN and your favorite number.
>
>Dennis
>
Could you please also post the same thing for presetting
the mode to VGA (or EGA)?  Maybe it's trivial, but I'm
not a C programmer and have no idea how this is done.

Thanks!

andy			aliaw@stat.tamu.edu


Xref: sparky comp.os.linux:531 alt.os.linux:2563
Organization: Penn State University
Date: Thursday, 16 Apr 1992 14:16:15 EDT
From: <SAB139@psuvm.psu.edu>
Newsgroups: comp.os.linux,alt.os.linux
Subject: compress/tar problems on SCSI installation

I seem to have a nasty little problem on my hands here.  I'm trying to
install Linux on the second partition of my SCSI drive ( ST01 controller ).
So I FTP'ed the patched 0.95c+ boot image.  This part works fine, it reports
finding the SCSI drive at ID=0 and that it fails read capacity and
everything else.  My problem is that I need the SCSI fdisk to do the
installation and it is a tar file.  I know to rawrite it onto floppy and how
set up the proper dev.  I have two root images, 0.12 and 0.95a, and on both
of them tar is compressed and I keep getting a "ENOSPC" error when I try to
uncompress tar.Z .

What I really need to know is - what does ENOSPC mean and how do I get
around it?

--
  Steve Bairstow

     sab139@psuvm.psu.edu
  or bairstow@vivaldi.psu.edu (NeXT mail ok)
Xref: sparky comp.os.linux:500 alt.os.linux:2546
From: s9100786@csdvax.csd.unsw.edu.au (Matthew Jackson)
Newsgroups: comp.os.linux,alt.os.linux
Subject: How to set the path ?
Date: 15 Apr 92 10:42:26 +1000
Organization: University of New South Wales

First off, thanks to all the work done by everyone to get Linux up and running.
Also, thanks to the writers of the new users and installation pages. I managed
to get 0.95a up and running with only one minor problem (accidentally swapping
the order for the hard disk device numbers).

Now I have a few questions (of course). When I was running the install scripts,
I checked they were flagged as executable, and tried to run them. No go. I then
tried /INSTALL/install and it worked ! OK, I thought Linux doesn't look in the
current directory for a file before searching the path (ala DOS) (is this
meant to work this way ? I am used to DOS and VMS, only just got started with
Unix). OK (he thinks again), why don't I put the current directory in the path ?
I typed set and got a list of the environment variables and there was one called
PATH, so I tried set PATH=....:. and still no go. 

So can someone tell me how to change the path under Linux ?

Thanks in advance,

-- 
Matthew Jackson                       |
Computing Officer                     | Why didn't Noah swat those two
School of Banking and Finance         | mosquitoes ?
University of New South Wales         |
Australia                             |
s9100786@csdvax.csd.unsw.edu.au       |
From: etxlli@eos.ericsson.se (Lars Lindner)
Newsgroups: comp.os.linux
Subject: tar files on floppy.
Date: 13 Apr 92 10:49:34 GMT
Organization: Ericsson Telecom AB

OK here's one more silly question.

When I have both boot and root images installed on HD and i want to
install more SW downloaded as .tar.Z files, in what way vill i get
them on a floppy to be able to install them on my Linux machine.

* Shall i use "rawrite" from DOS to put the files on floppy?

* I rememer reading something like "Do not rawrite compressed files.".
  Whay??

* How to do with files lager than the capasity of my floppy when not compressed?

* Is there another way to install .tar.Z files via floppy?

My Linux machine uses 5 1/4" floppies and the only way for me to write
floppies in that format is to use another DOS machine.

     Thanks in advance from a nowise.


Lars Lindner
Lars.Lindner@eos.ericsson.se
From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger)
Newsgroups: comp.os.linux
Subject: Re: mtools (mcopy) problems
Keywords: mtools mcopy problem help augh
Date: 7 Apr 92 12:54:06 GMT
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH

In article <x3mj=tc.tm@netcom.com> tm@netcom.com (Toshiyasu Morita) writes:
> mcopy does nothing at all - when I type mcopy c:/gcc-1.40/gccinfo.1 gccinfo.1
> nothing happens. I can "mcat" the file and I can view it, but I can't
> copy it to my Linux directory.

If "nothing happens" means that mcopy returns without doing anything,
you've probably forgotten to make links for mread and mwrite. mcopy
execs mread or mwrite to do the transfers, but it doesn't warn when
the exec fails. Fix: chdir to the directory where mtools live and do
a  ln mtools mread; ln mtools mwrite  (or, if you're not using the
merged version, compile mread and mwrite and put them in the approp-
riate directory.)

If "nothing happens" means that mcopy hangs and has to be killed with
^C, you've probably compiled mcopy.c without -DMERGED. mcopy sets
argv[0] of the execed mread/mwrite to "mcopy" if -DMERGED is omitted,
which breaks the merged mtools. Fix: re-compile mcopy.c with -DMERGED

- Werner
-- 
   _________________________________________________________________________
  / Werner Almesberger, ETH Zuerich, CH      almesber@nessie.cs.id.ethz.ch /
 / IFW A44  Tel. +41 1 254 7213                 almesberger@rzvax.ethz.ch /
/_BITNET:_ALMESBER@CZHETH5A__HEPNET/CHADNET:_[20579::]57414::ALMESBERGER_/
From: pthoms@castle.ed.ac.uk (P Thomson)
Newsgroups: comp.os.linux
Subject: swapping continued ?
Date: 12 Apr 92 20:55:40 GMT
Organization: Edinburgh University


Sorry, I should of added the line

      swapon /dev/hda3


to my previous posting


Thanks to the couple of guys whom pointed this out

      Peter
Newsgroups: comp.os.linux
From: S3679988@deimos.ucc.umass.edu (S3679988)
Subject: 0.95a
Organization: University of Massachusetts at Amherst
Date: Fri, 10 Apr 1992 02:04:40 GMT
X-News-Reader: VMS NEWS 1.20

I have recently been trying to upgrade from linux 0.12 to linux 0.95a
(yes, i have taken my time, being a student does that...). Anyhow,
when i boot 0.95, i get hd timeout errors (this is from an unmodified
distribution floppy, that is supposed to go to the floppy device.
This all worked just fine with 0.12, and i am completely baffled as
to why it doesn't work. My system is a 486/33, with a seagate st-225
MFM harddrive.

-- craig hagan

Newsgroups: comp.os.linux,alt.os.linux
From: drew@ophelia.cs.colorado.edu (Drew Eckhardt)
Subject: Re: User's Guide project
Organization: University of Colorado at Boulder
Date: Thu, 16 Apr 1992 09:42:28 GMT

In article <4769@krafla.rhi.hi.is> einari@rhi.hi.is (Einar Indridason) writes:
>In <kuelccINN613@alhena.usc.edu> ajayshah@alhena.usc.edu (Ajay Shah) writes:
>
>>knapka@athena.cs.uga.edu (Joseph Knapka) writes:
>
>And perhaps some co-ordination regarding patches.  Perhaps a few persons
>would take each patch, and compare it to some "standard" source tree.
>
>I have used Minix a bit, but haven't installed Linux (yet), but I'd
>hate to see the "patch-mess", that minix has gotten into, hit Linux as
>well.

It's not that bad - "important" patches do make it back into the standard 
distribution (ie what's necessary for a real ps, faster floppy and 
lp drivers, the virtual consoles, VFS, minor patches in the boot 
sector and hard disk driver, etc) fairly quickly.  

Also, as Linux becomes more stable, kernel patches will become less 
necessary.
From: knapka@athena.cs.uga.edu (Joseph Knapka)
Newsgroups: comp.os.linux
Subject: Hitchhiker's Guide to Linux
Summary: User's Guide volunteers wanted
Date: 14 Apr 92 14:27:44 GMT
Organization: University of Georgia, Athens

Hi, folks. Here's a list of Linux User's Guide chapters, and people
who are writing/compiling them.  Volunteerism is HIGHLY encouraged.

0: Linux overview
I: Installation
IIa:gcc-1.40 
IIb: gcc-2.x (This will be the standard by the time UG is available.
	matthew@cs.uq.oz.au is working on a gcc reference manual.)
III: Communication packages (kermit, etc.)
IV: mtools
V: emacs ...............................Me
VI: groff (& man?)
VII: TeX, LaTeX
------- These next three will involve close cooperation -------
VIII: uucp (Yay!) (Mr. Carp, could you do this one?)
IX: mail 
X: ka9q
----------------------------------------------------------
XI: X11
XII: system administration/security ...Chuck Boyer & me
XIII: configuring and building your Linux kernel
XIV: random gnu software (general porting info)

The first chapter (0, that is) should cover basically what the
INFO-SHEET does.

Chapter I should not only cover the physical installation of Linux,
but should also discuss the standard *nix utilites, what they're for,
and where to get them --- i.e., it should be a guide to putting
together a functional system. johnsonm@stolaf.edu says: 
>	With the ABC release, this chapter should only be a minor 
>	revision of what Iain has already done, in my opinion.  
Yes. But should definitely include a pointer to a good book
on Unix for regular-guy users, IMHO. Also, I think the filesystem
standard document should be here.

The chapters devoted to software packages should cover 1) Where to get
the package; 2) Best-case installation procedure; 3) Typical
installation problems and fixes; 4) When available, a pointer to a
genuine user's manual (i.e., "Lamport, Leslie. LaTeX: a document
preparation system. Addison-Wesley, Reading, MA, 1986"). 

The chapter on GNU software should cover things like appropriate
compiler flags for Linux and so forth. And why they're appropriate.

It's been suggested that "texinfo" be the standard vehicle for this
project. Is this a good idea? I will have to find out about texinfo. 

Comments or (preferably) volunteers?

Bye,
Joseph
Newsgroups: comp.os.linux
From: slowhand@cis.umassd.edu (Chris P. Sullivan)
Subject: Questions from a beginner...
Keywords: 1.44 A: drive, compiling, shells
Organization: University of Massachusetts Dartmouth
Date: Mon, 13 Apr 1992 15:08:08 GMT

Hello everyone,

First, let me applaud everyone who has helped develop and/or document Linux, 
my roommate and I installed it on my machine this weekend, and it went VERY
smoothly (as smooth as Unix-type os's can go, I suppose), this is of course
comparing it to the installation of Minix, which was pure hell.
Now that I have the basic 0.95a system installed, I have a couple of questions.

First, the only thing in the installation process that did not work was the
install, mkdev, mktree scripts, for some reason they would not execute,
it would just respond with a :not found error.  So we ended up printing
the scripts and doing it by hand.  My limited UNIX experience leads me to 
believe it has to do with the wrong shell for these scripts.  WHAT OTHER SHELLS
ARE AVAILIBLE FOR LINUX?  HOW DO YOU INSTALL THEM?  Do you need to re-compile 
the kernal to make them work?

Next,  following the list of MKNOD's in the mkdev script we set up PS0, 
according to the documentation, this makes ps0 an A: drive 1.2MB.  When
we were RAWRITEing to floppies (1.44) to move them to Linux, if the file
was larger than 1.2MB, we would get RESET-FLOPPY CALLED errors.  When we
would mount the floppy, it would work to a point and we would get scattered
RESET-FLOPPY CALLED errors.  HOW WOULD WE MAKE LINUX UNDERSTAND THAT WE HAVE
AND A: DRIVE THAT IS 1.44MB?

Finally, we have access to DECstation 3100s running ULtrix, would it be
for us to compile things on the workstations and then download the executable
to my PC/Linux machine since these machines have far more disk/memory capacity
than mine does?  Or will I run into major incompatability problems?

Any responses will be appreciated.

Chris Sullivan
UMass Dartmouth

slowhand@cis.umassd.edu