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


In article <1992Apr3.160301.19579@athena.cs.uga.edu> knapka@athena.cs.uga.edu (Joseph Knapka) writes:
>In article <1992Apr3.061149.12337@mnemosyne.cs.du.edu> zmbenhal@isis.cs.du.edu (Zeyd M. Ben-Halim) writes:
>>schulte@thp.uni-koeln.de (Martin Schulte) writes:
>>
>>Could somebody post an answer to this question? It has come up at least half
>>a dozen time already. (Un)fortunately I never got these error when I use gcc2.
>>
>>>I took gcc2misc.tar.Z and gcc2lib.tar.Z from tsx-11. I untared them
>>>in /usr.  /usr/gcc2/bin/gcc of a script which only contains the
>>>line "#include <stdio.h>" leads to the error-message:
>>>In file incluced from gcc2test.c:1:
>>>/usr/gcc2/include/stdio.h:99: parse error before '('

This problem is frequently caused by inconsistencies in the include
files, particularly since we have had several versions of the C
compiler with several include file collections.  Imagine that one
include file contains a definition of a macro 'file', while another
contains the word 'file' as the name of a field of a structure.
Either file will work properly, but any program which includes both
must contain the second (with the structure) before the first (the one
with the macro).  This problem actually occurred.

Another problem has occurred in which a macro, e.g., free(a) is
defined in one header file, while the prototype free() occurs in
stdlib.h or unistd.h.  Further problems have occurred when 
include files depend on each other in a manner which is not clear.
I think the people getting these things out have done a marvellous
job.

The whole include file mess should actually get straightened out
only when an official 1.0 release of Linux comes out, and perhaps
not even then.

>I had this problem early on with gcc-2.0. Someone posted about the tar
>on the 0.95a distribution disk corrupting files. I switched to another
>tar (I think from fileutils.tar.Z on tsx-11, but I'm not sure) and
>untarred the gcc-2.x stuff with that, and everything worked after
>that.

Of course, if an include file is actually corrupted, we would
expect the compiler to find syntax errors in it.

     -- Owen
     LeBlanc@mcc.ac.uk
From: moyerg@jove.cs.pdx.edu (gary a moyer)
Newsgroups: comp.os.linux
Subject: problems compiling kernel -- fatal signal 6
Keywords: kernel
Date: 7 Apr 92 23:50:06 GMT

With a little luck and insight from some users, the mystery
surrounding the fatal signal 6 dilemna has been solved.
Evidently the makefile in linux/kernel contains the line
GCC_OPT = -fcombine-regs commented out due to problems (or
possibly a fix) for persons using gcc2.0.  This, however,
makes gcc1.4 choke and die.  Just remove the comment delimiter
and blamo -- it compiles.

                 moyerg@cs.pdx.edu
From: knapka@athena.cs.uga.edu (Joseph Knapka)
Newsgroups: comp.os.linux
Subject: Make dies under gcc2.1
Date: 11 Apr 92 15:22:31 GMT
Organization: University of Georgia, Athens

I've got a terrible problem. I installed gcc-2.1 again today, and
suddenly "make" quit working entirely. It says "No system rules
(/usr/share/mk/sys.mk)". Does anyone know what's going on? It's true
there isn't even a directory /usr/share, but I don't know where such a
directory would come from in the first place. It wasn't in the gcc
distribution. And even my old non-shared-libs version of pmake doesn't
work (same error). Also, my previous four or five installations of
gcc-2.1 went fine, and everything worked.

Thanks for any advice,

Joseph
Newsgroups: comp.os.linux,alt.os.linux
From: jwinstea@jarthur.claremont.edu (Jim Winstead Jr.)
Subject: Re: Problems compiling 0.95c+
Organization: Harvey Mudd College, WIBSTR
Date: Sun, 12 Apr 1992 02:21:13 GMT

In article <1992Apr11.184953.24008@spuddy.uucp> sweh@spuddy.uucp (Stephen Harris) writes:
>Had a few problems compiling the c+ version, patching from 0.95c
>
>These were:
>(1) Lack of include/checkpoint.h, needed in char_dev.c
>    I just "touch"ed this file, to create it, and the compilation worked.
>    What should this include file do????

checkpoint.h is not needed - you're best off removing the references
to it completely.  I think they're in kernel/chr_drv/lp.c and
fs/char_dev.c.

>(2) Boot image finally made recognised my two printer ports then crashed
>    in a similar way to other people have described.
>    I compiled using 1.40 (newgcc.tar.Z)
>    Looking at the stderr from the makefile I found a lot of silly lines
>    "unknown option M%I%" or something like that.

There is a typo in the kernel/Makefile, for the "dep" target - the
line:
	(cd math; $(MAKE) (MFLAGS) dep)
should be:
	(cd math; $(MAKE) $(MFLAGS) dep)

>    Using the gccbin.tar.Z version of 1.40 the error became "unknwon
>    option -O6
>    Removing the "6" and recompiling produced a working bootable kernel.

This is new to gcc 2.0 - you took the right way to fix it.  The best
way to fix it would be to upgrade compilers, of course.  :)

>mknod lp0 c 6 1 / mknod lp1 c 6 2, then my printers both worked.

The minor numbers here are wrong.  lp0 is (6,0), lp1 is (6,1), and lp2
is (6,2).  The root image for 0.96 will have a MAKEDEV that makes
these correctly....
-- 
Jim Winstead Jr. (CSci '95)    | "Catch a fish!"
Harvey Mudd College            |  -Geddy Lee,
jwinstea@jarthur.Claremont.EDU |   San Diego Sports Arena
Disclaimer: Mine, not theirs!  |   January 20, 1992
Newsgroups: comp.os.linux
From: jliddle@rs6000.cmp.ilstu.edu (Jean Liddle)
Subject: Local Bus support?
Date: Sat, 11 Apr 1992 16:15:26 GMT
Organization: Illinois State University

I am posting this for a friend:

Hello netters.  I was just curious as to whether or not LINUX supports
32-bit local bus cards, such as 32-bit video cards and/or disk controllers.
This is _not_ the same as EISA.  I understand that programs running over
the bios have no problem, but since LINUX manipulates the hardware directly
I wasn't sure.

Please reply to me or this newsgroup and I'll forward the responses
accordingly.

Jean.
-- 
Jean Liddle
Computer Science, Illinois State University 
e-mail:  jliddle@rs6000.cmp.ilstu.edu
         jliddle@katya.acs.ilstu.edu
From: mcbeeb@nyssa.CS.ORST.EDU (Brian Mcbee)
Newsgroups: comp.os.linux
Subject: Seagate SCSI *almost* working...
Date: 9 Apr 92 04:27:03 GMT
Organization: CS Dept. Oregon State University, Corvallis, Oregon.

I've been using linux now for a couple of months, and I decided to
try and get an old seagate st-277n I had laying around working
with it.  I got an ST-01 controller, and ftp'd the linux95a
scsi patches from headreset.colorado.edu.  Hacked them into
my Linux .95c system.  Had to make one small change to
seagate.c, as my signature "SEAGATE SCSI BIOS REVISION"
is at offset 17 rather than the 16 indicated in the file.
Upon bootup, the system does find the host adapter, and 1
scsi disk (yay!).  Where do I go from here?  I get several
messages here, but I don't know if they are normal or not.
and how do I partition the drive?  Here is what I see:

...
1 host adapters detected
Detected scsi disk at host 0, ID 0, lun 0
Detected 1 disks, 0 tapes total
Warning: SCSI device at host 0, id 0, lun 0 failed READ CAPACITY
status=5345c
Sense not available
Block size assumed to be 512 bytes, disk size 1 GB
Cannot read partition table for sd 0

Is any of the above normal for the seagate?  Or is it totally
hosed?  Or is it just a matter of getting the partition info
on there?  Any help appreciated.


-- 
Brian McBee   mcbeeb@jacobs.cs.orst.edu  or  brianop@opac.UUCP
"The strongest reason for the people to retain the right to keep and bear
arms is, as a last resort, to protect themselves against tyranny in
government."			Thomas Jefferson
From: dcuka@cbnewse.cb.att.com (david.a.cuka)
Newsgroups: comp.os.linux
Subject: Re: Questions from a beginner...
Keywords: 1.44 A: drive, compiling, shells
Date: 13 Apr 92 18:07:51 GMT
Organization: AT&T

In article <1992Apr13.150808.10585@cis.umassd.edu> slowhand@cis.umassd.edu (Chris P. Sullivan) writes:
>Hello everyone,
>
[installation glee deleted, but still present]
>
>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?

try "sh < install"
	or
  "chmod +x install"
  "./install"

[floppy problems deleted]

>
>Any responses will be appreciated.
>
>Chris Sullivan
>UMass Dartmouth
>
>slowhand@cis.umassd.edu


DAC
Xref: sparky comp.os.linux:518 alt.config:3006
From: ccs7@aber.ac.uk (Christopher Samuel)
Newsgroups: comp.os.linux,alt.config
Subject: Re: Too many duplicated messages
Date: 16 Apr 92 11:38:26 GMT
Organization: University of Wales - Aberystwyth - Prifysgol Cymru

In article <1992Apr15.175109.10117@athena.mit.edu>
   tytso@athena.mit.edu (Theodore Y. Ts'o) doodled:

> [..]  If those sites haven't created comp.os.linux by
> now, they probably have lame sysadmins and it is unlikely they will
> get around to creating those groups any time soon.  So, I don't think
> we really have an obligation to accomodate them much longer; having
> two newsgroups is somewhat confusing, and we should really transition
> everyone over to using comp.os.linux. 

A suggestion would be for those people who are at sites which have not
yet processed the newgroup for comp.os.linux to mail there news-admin
and ask _nicely_ for them to process it.

> So, let me repeat my call.  Shall we rmgroup alt.os.linux?  I think its
> time has come.

I've no objection to that, the only problem being that will the
sysadmins who havent't newgrouped comp.os.linux honour the rmgroup ?
Despite that, however, it is definately worth a try. 

- Chris
-- 
 Christopher Samuel, c/o Physics Dept, UCW Aberystwyth, Aberystwyth, WALES
 RFC: ccs7@aber.ac.uk  UUCP: *!mcsun!uknet!aber!ccs7  JNT: ccs7@uk.ac.aber
    "Live real fast, still not die, never get old." - New Model Army
Newsgroups: comp.os.linux
From: drew@ophelia.cs.colorado.edu (Drew Eckhardt)
Subject: Re: When will "Linux 1.0" come to the world ?
Organization: University of Colorado at Boulder
Date: Mon, 13 Apr 1992 22:45:27 GMT

In article <1992Apr13.215610.22632%dr794348@cs.nthu.edu.tw> dr794348@cs.nthu.edu.tw (mr79) writes:
>Linux 0.95c is still in the period of development.
>Everything is rather unstable.

The only things unstable in Linux right now is caused by the lack of 
limits and a reasonable scheme to insure that there is enough virtual
memory for every process running, and tar not handling EOF and consequently
multi-volume tars correctly.

I think that before Linux reaches 1.0, it definately needs to have the limit
system calls implemented, and a "real" filesystem on top of VFS, 
such as Berkely FFS, or LFS.

To be on a par with what BSD / HURD / etc will be once they are out 
of development, an X port should be finished,
and support for TCP / IP over "standard" ethernet boards, as well as
SLIP / CSLIP in the kernel should be added.  QIC-02 tape support 
would be nice too.
From: bolsen@mcs213h.cs.umr.edu (Brian Olsen)
Newsgroups: comp.os.linux
Subject: Re: Linux Printer
Keywords: linux, printer
Date: 15 Apr 92 19:31:26 GMT
Organization: University of Missouri - Rolla


Hello!
I'm running linux 0.95c+ and have been working on connecting up my printer
(Panasonic KXP-1123).
When I tried 
/bin/mknod /dev/lp1 c 6 0
I got a 'device not found' error (to that effect)
using 
/bin/mknod /dev/lp1 c 6 1
I was able to print to stuff, but I lost a lot of character in the printout
(about one in every three or four).

Suggestions anyone?
Brian
bolsen@cs.umr.edu
From: radel@ravel.udel.edu (Todd Radel)
Newsgroups: comp.os.linux
Subject: CBREAK mode, etc.: Questions
Summary: Is cbreak broken?
Date: 17 Apr 92 13:03:01 GMT
Organization: University of Delaware

Thanks to everyone who helped me get my printer set up as /dev/lp1.  Now
for some more questions:

1) Is CBREAK mode broken in the .95c+ release?  I'm trying to write some
   stuff using the curses library, and I explicitly say cbreak();, but
   I still have to press <Enter> after every key I hit.  I also tried
   compiling XBBS version 7.91, which exhibited the same symptoms.

2) How do I set up a swap *file*?  Not a separate partition, but a file.

3) Is Linux set up to be 8-bit clean?  If I set up a BBS, will 8N1 callers
   have a problem?

AdvTHANKSance to all who respond...

-- Todd
   (getting better at this Linux stuff, but still a little confused...)


-- 
* Todd Radel                      Sysop, Dickinson Domain BBS                *
| CIS/English                     FidoNet: 1:150/160; VirtualNET @3023       |
| University of Delaware          REGISTERED Alpha Colony VI!                |
*         "You don't need to be crazy to be a sysop, but it helps!"          *
From: stevem@stevem2.intel.com (Steve McCalla)
Newsgroups: comp.os.linux
Subject: PS/2 Systems and Linux. was: What is linux?
Keywords: linux
Date: 8 Apr 92 18:58:32 GMT
Reply-To: stevem@stevem2.intel.com (Steve McCalla)

The following is a recollection of news items posted when Minix was ported to
the PS/2 back in the dark ages, so take it with a grain of salt.

The main (only?) difference between microchannel machines and ISA bus machines
is the way interrupts happen. The microchannel has level-triggered interrupts
as opposed to edge-triggered interrupts on the ISA bus. This means that
multiple devices may share a single interrupt line. When an interrupt comes
in on a shared line, the devices sharing that line must be polled to find out
what caused the interrupt. That device must be serviced before sending the EOI
out, otherwise you end up getting another interrupt from the same device.
With edge-triggered interrupts, you can only have a single device per interrupt
line so this is never a problem; you can simply send the EOI and then
handle the
device that caused the interrupt. Naturally, different devices must be serviced
in different ways; I seem to recall a SENSE command being sent to the floppy
device in Minix as being sufficient for having it remove the intterupt request.
I don't know what the commands are for other devices. I believe they found a
way to set up Minix such that it would run on either bus, but I don't have
the details. (They = Bruce Evans, Steve Ackerman, and a host of others).
Hope these ramblings help.

- stevem
"#include <stddisclaimer.h> my opinions are my own, etc"
--
"It's pushbutton automation. First you push 'v', then  you push 'i'...:)
From: moyerg@jove.cs.pdx.edu (gary a moyer)
Newsgroups: comp.os.linux
Subject: shoelace -- errors at boot from partition
Keywords: shoelace
Date: 7 Apr 92 23:53:04 GMT

I recently  got linux to boot from the second partition via
shoelace.  It boots fine and everything, however, I get some
interesting warning messages.  Anyone else had this problem?

BTW -- kudos for the port to Linux, that floppy grinding away
at bootup was s l o w......

                   moyerg@cs.pdx.edu
From: david@csource.oz.au (david nugent)
Newsgroups: comp.os.linux
Subject: Re: When will "Linux 1.0" come to the world ?
Date: Thu, 16 Apr 92 01:53:32 +1000
Reply-To: david@csource.oz.au
Organization: Unique Computing Pty Ltd, Melbourne, Australia

jwinstea@jarthur.claremont.edu (Jim Winstead Jr.) writes:

 > In article <1992Apr13.215610.22632%dr794348@cs.nthu.edu.tw> dr794348@cs.nthu.
 > >Linux 0.95c is still in the period of development.
 >
 > I follow you here....
 >
 > >Everything is rather unstable.
 >
 > "Everything"?  "rather unstable"?  What are you basing these
 > judgements on?

If what was meant by "unstable" was "dynamic" and "moving", I agree.

I hope it remains that way. It's great working with an OS that mulitple
people are working on at all sorts of levels. It's an even greater
opportunity to learn.


 > My experience with Linux indicates it is more stable
 > than DOS+DESQview on my machine, and allows me to get even more done,
 > with the small exception of word processing.

But this is NOT FAIR! Anything remotely DOS-associated is definitely NOT
STABLE in that sense by definition. No memory protection == not relatively
stable.

I might mention that apart from during the boot process when I had the kernel
attempting to find it's root device in the wild blue yonder, I've _never_ had
a fatal kernel panic trap - not once in the last 5 weeks in which I've been
running it almost full time. I've been pushing it hard too. I've had gcc grind
the system (8 meg RAM + 8 meg swap) to a halt and cause some strange apparent
HD errors on the swap device (ie. out of vitual RAM), but after killing one of
the compiles and restarting when the other one stopped, it continued on...

Gee, if this is unstable, then what will "stable" be like? :-)

I previously ran Interactive UNIX for over 2 years. I remember seeing 3
panic traps in the first attempt to install it on exactly the same hardware!
I also installed it ans SCO's product on several machines as a part of my
work and I can honestly say that while the facilities offered by Linux don't
yet match the SCO/ISC product, that Linux certainly _feels_ and _acts_ more
stable in most ways.



 > (Which I hope to
 > overcome, once I figure out how the !@$*!@ to set up TeX.  I
 > appreciate the absolute lack of instructions included with the TeX
 > distributed for Linux.  Grr.)

I bet you'd love it in texinfo format, right? :-)

(Read: don't ask me - I use emacs, when I have to, under sufferance! :-))



..............................................................................
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.
Newsgroups: comp.os.linux
From: dr794348@cs.nthu.edu.tw (mr79)
Subject: When will "Linux 1.0" come to the world ?
Organization: National Tsing Hua University (HsinChu)
Date: Mon, 13 Apr 1992 21:56:10 GMT

Linux 0.95c is still in the period of development.
Everything is rather unstable.
when will Linux 1.0 come to the PC 386/486 world ?

			J.H.Lin
Newsgroups: comp.os.linux
From: n84261@pbhrzx.uni-paderborn.de (Nan-shan Chen)
Subject: help, incompatible video .. 
Summary: My video card is incompatible, a hardware scroll does not work
Keywords: Softscroll
Organization: Uni-GH Paderborn
Date: Wed, 15 Apr 1992 17:07:48 GMT


Hi everybody, 

I have just downloaded the Boot & Root image of LINUX.  There is, however,
a serious problem in the first place.  I could not even view the screens.
That's the same problem as in MINIX.  But I could set it to software
scroll under MINIX just by pressing a key or doing:

	setterm -softscroll

There is no "softscroll" option of setterm in LINUX.

What should I do? 



--

                         ////\
                        { 0-0 }
                         \ o /
From: dje@sspiff.UUCP (Doug Evans)
Newsgroups: comp.os.linux
Subject: Getting started
Date: 9 Apr 92 23:01:58 GMT
Followup-To: poster
Organization: Edmonton, Alberta

I'd like to get linux and have several questions. I have set Followup-To
poster because I don't receive this newsgroup (yet!).

1) Does it come as source, like 386bsd? If so, what are the archive sites?
   How big is the source?

2) Is there an archive site for alt.os.linux and/or comp.os.linux?

1e6 thanks in advance!
-- 
Doug Evans                   |
..!{canada,uunet}!sspiff!dje | Vancouver 11, Calgary 0
dje@sspiff.UUCP (prefered!)  | There is no joy in Cowtown.
dje@ersys.edmonton.ab.ca     | But how 'bout those Canucks, eh?
Xref: sparky comp.os.linux:549 alt.os.linux:2570
From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Newsgroups: comp.os.linux,alt.os.linux
Subject: Re: How to set the path ?
Date: 16 Apr 92 16:12:19 GMT
Followup-To: LeBlanc@mcc.ac.uk
Organization: Computing Centre, University of Manchester

In article <1992Apr15.104226.1795@csdvax.csd.unsw.edu.au> s9100786@csdvax.csd.unsw.edu.au (Matthew Jackson) writes:
>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. 

Did you also type 'export PATH' after setting it?  You can look at
PATH by typing 'echo $PATH'.  If you then type 'sh' and 'echo $PATH'
and get a different answer, then PATH is not exported.

     -- Owen
     LeBlanc@mcc.ac.uk
From: nicolai@lysator.liu.se (Nicolai Wadstr|m)
Newsgroups: comp.os.linux
Subject: Re: Has anyone thought about threads?
Date: 9 Apr 92 18:55:05 GMT
Organization: Lysator Computer Club, Linkoping University, Sweden

drew@caesar.cs.colorado.edu (Drew Eckhardt) writes:

>In article <1200@lysator.liu.se> nicolai@lysator.liu.se (Nicolai Wadstr|m) writes:
>>Has anyone given any thoughts on implementing threads in linux?
>>I know it's not a standard UNIX feature, but it's were nice to
>>write programs with threads, it's often possible to gain a lot
>>of performance in using threads.
>>(I've done a lot of OS/2 programming and just love the idea of 
>>threads!)

>fork()ing is the same thing as creating a heavy weight thread.
>lightweight threads can be implemented with minimal modifications. 

Ok, fork()ing isn't as straight forward to use, but accomplishes roughly
the same thing, altough that approach has more overhead than if you
would have an createthread() call (ex. createthread( stack, funcaddr ); ).
If I'm right (I don't know that much about UNIX) fork makes another copy
of the program, with a seperate data segment, I'm I right? 
With threads you still have access all the program data.

>Interprocess communication can be accomplished with pipes,
>or signals.

>Hopefully, sysV shared memory and semaphores will be 
>implemented too.

Yeah, that would also be nice! But how about queues? If you
are transfering bigger chunks between programs queues are much
better than pipes! 
(I know shared memory could be used for that, but queues are actually
only a way to handle shared memory).

>Yes.  Note that Linux uses shared, statically linked libraries.
>With some header field munging, and running ld(1) from user space, it would
>be possible to do dynamically linked shared libraries.

Ok, also a very nice feature!
That's also a very good way implement API's, in OS/2 the API's implemented
in that way.



/ nicolai



--
Nicolai Wadstr|m                   # Internet:      nicolai@lysator.liu.se
                                   #
                                   # BBS:           +46-40-124554 (down)
                                   # Voice:         +46-40-975535
From: hienl@Saigon.COM (Hien Luu)
Newsgroups: comp.os.linux
Subject: Linux and DOS
Keywords: Partitions
Date: 5 Apr 92 05:11:02 GMT
Organization: Station Zebra Corp, Sunnyvale CA Ph:408-739-1520


I would like to install Linux on my system, but the installation
instruction doesn't mention how to set the system up so one can have
DOS and Linux on the same system.  Also, how do I switch between DOS
and Linux and vice versa, so would some one please explain and give

some hints...
The installation instruction did mention that Linux must be installed
on a primary partition.  But in DOS, one can only have one primary
partition, so is there a trick to this?
 
Thanks in advance...