HDTenEightyP/NetNews huggingface dataset:
From: cummings@hammer.Prime.COM (Kevin Cummings)
Newsgroups: alt.os.linux
Subject: Re: Problems compiling df and system utils under gcc 2.1
Date: 15 Apr 92 18:44:31 GMT
Article-I.D.: hammer.1992Apr15.144431
Organization: Prime Computer R&D

In article <1992Apr14.224228.9691@ra.msstate.edu>, dam1@ra.msstate.edu (Daniel A. Martin) writes:
> I got a few errors while compiling df as well as chsh and mkswap from the
> system-0.95a.tar.Z file...BTW shouldn't df be in this file too?
> 
> df compiled ok before I installed gcc 2.1 so SUPER_MAGIC was probably
> defined in one of the old include files...what is it supposed to be?

I just recompiled df.c last night.  I even made a change to it to print out
the remaining disk space as a percentage as well as an absolute.  Trial and
error (and a well placed printf call) told me to put the following line
in df.c:

#define SUPER_MAGIC 0x137F

It's the same value that appears as MINIX_SUPER_MAGIC in the file minix_fs.h.

In a related note, adduser seems to work pretty well, except that it got
screwed up by the "extra" last line in my /etc/passwd file.  I don't think
the "extra" line is needed if you are running on a system compiled with
gcc-2.1.  I took it out with no (yet, knock on wood) ill effects.

The su program that I gott from tsx-11 is old and out of date.  First off,
it doesn't encrypt the password typed in.  So you have to type in the
encrypted password.  Second of all, I'm not sure what the requirement is
for a user being able to sucessfully su to root.  su complained that
I was not in the proper group, so my request was invalid.  Under SUNOS, anyone
who knows the root password can su to root.  Under Sys V, you need to be
in the file /etc/su_people, and su_people MUST have the right permissions
and owners on it (and it doesn't prompt for a password).  What should
the proper LINUX behaviour be?  Personally I vote for knowing the
root password AND being listed in the appropriate file.  This protects
administrators against inadverdantly leaving their terminal unattended
as well as restricting usage from people who may have "stolen" one password.
su whould in effect require two passwords to become root (user password
and root password) on those lines where root cannot log in directly.

=================================================================
Kevin J. Cummings                       Prime Computer Inc.
20 Briarwood Road                       500 Old Connecticut Path
Framingham, Mass.                       Framingham, Mass.

Work:  cummings@primerd.Prime.COM
Home:  cummings@kjc386.framingham.ma.us

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
		  I've come to the conclusion that your new
		  defense system SUCKS..."   --  War Games
=================================================================
Organization: Sophomore, Physics, Carnegie Mellon, Pittsburgh, PA
Newsgroups: alt.os.linux
Date: Fri, 17 Apr 1992 03:59:36 -0400 
From: "Demian A. Johnston" <dj1l+@andrew.cmu.edu>
Subject: Re: mount:unable to open lock-file

Login in as root and delete /etc/mtab~



                                                  Demian 
                                              --->  daj+@cmu.edu
                                              --->  dj1l@andrew.cmu.edu
                                              --->  demianjn@ids.jvnc.net

Newsgroups: alt.os.linux
From: alsaggaf@ERL.MIT.EDU (M. Saggaf)
Subject: How to FORMAT a floppy in Linux?
Organization: Massachvsetts Institvte of Technology
Date: Sat, 11 Apr 1992 06:01:11 GMT

This is just that. I'd like to know how to format a floppy under Linux.

-- M. Saggaf (alsaggaf@erl.mit.edu)

Newsgroups: alt.os.linux
From: Epstein@DOCKMASTER.NCSC.MIL
Subject: Linux will be beta until can handle compress
Reply-To: Epstein@DOCKMASTER.NCSC.MIL
Organization: The Internet
Date: Sun, 12 Apr 1992 23:13:16 GMT

I had a bad file which compress -d did its thing.  Only sometimes when
this happens will the CONTROL-Z (running bash) take affect.  Can never
get service on other virtual consoles.  Scroll lock always available.
IMHO Scroll lock (or other key) should kill all processes and do a sync
--- presently any uncompress of a bad file (single byte error) can cause
a file system crash.  MINIX used CTRL-F9 or SHIFT-F9 for this function.

Of course, nice if uncompress would quit or be killed if exceed memory
limit.

Running 0.95c (not quite sure of exactly what is in 0.95c+).  fsck -vs
and fsck -a work.
                    John
Newsgroups: alt.os.linux,comp.os.linux
From: abc@banjo.concert.net (Alan B Clegg)
Subject: ABC Release Soon! (Was: Re: gcc 2.1 beta is available)
Organization: Concert Network -- Internet Operations Group
Date: Mon, 6 Apr 1992 19:21:56 GMT

In article <1992Apr6.181958.22339@ods.com> david@ods.com (David Engel) writes:
>hlu@yoda.eecs.wsu.edu (Hongjiu Lu -- Graduate Student) writes:
>: THANKS TO ALL THE ALPHA TESTERS. You did a great job and help me a lot,
>: Without you guys, I cannot image how I could find all those bugs.
>
>It took longer that I think any of us expected, but we now have one heck 
>of a compiler and library.  Thanks H.J.

I second this emotion (8-) and would like to ask the following question:

  HAS ANYONE FOUND ANY PROBLEMS WITH THE CURRENT VERSION OF 2.1(beta)?

If not, I am going to use it as the base for the ABC Release of Linux .95a
which I hope to have available by this Friday.

    Thanks to those of you that submitted code to me for the release!

-abc
BTW:  Anyone at the University of Hawaii around reading this?  If so, send me
	some mail ASAP.
-- 
abc@concert.net				Alan Clegg - Network Programmer
KD4JML (just my luck!)			MCNC -- Center for Communications
Xref: sparky alt.os.linux:2449 comp.os.linux:370
From: hlu@yoda.eecs.wsu.edu (Hongjiu Lu -- Graduate Student)
Newsgroups: alt.os.linux,comp.os.linux
Subject: Re: gcc 2.1 problem: parse error before '('
Keywords: gcc 2.1 problem parse error
Date: 13 Apr 92 02:28:12 GMT
Article-I.D.: serval.1992Apr13.022812.21560
Organization: Washington State University

In article <whitney2.703128454@husc10> whitney2@husc10.harvard.edu (Wayne Whitney) writes:
>Hello Linux users,
>
>	As this is my first post to the .os.linux group(s), I just
>want to thank Linus and everybody else whose been working on this
>project for a great job and all the time and effort you've put into
>it.  Anyway, what brings me to post is a problem I've had trying to
>get gcc 2.1 to work.  Basically, whenever I try to compile something,
>the compiler dies on the first line with a '(', saying: parse error
>before '('.  I remember there was an earlier post about this problem,
>but a solution was never posted.  So I was hoping that someone could
>tell me how to fix it, as I don't really know where to begin.  I'm
>sure the archives that I've gotten weren't corrupted, and I've checked
>twice to be sure that all of gcc 1.4 was gone; I followed the
>instructions in the FAQ on gcc2.1 for installing it.
>	Thanks.
>
>Wayne Whitney
>whitney2@husc.harvard.edu

The solution has been posted several times. MAKE SURE YOUR TAR/COMPRESS
WORK CORRECTLY. It is in FAQ of 2.1 too.

NOT ALL TAR/COMPRESS'S ARE WORKING RIGHT. If you are not sure,
uncompress gcc 2.1 on the other machine and move gcc 2.1 binaries to
Linux one at a time.

H.J.
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Newsgroups: alt.os.linux
Subject: Re: kermit5A.tar.Z
Date: 12 Apr 92 19:53:45 GMT
Organization: University of Helsinki

In article <1992Apr11.234044.27436@athena.mit.edu> wet!dhl@netcom.com (Dahai Li) writes:
>
>I have seen your notice about re-uploading a working version of kermit5A to
>tsx-11.mit.edu, and downloaded it (it is dated 4/10/92, I think). However,
>it still fails to work with a "segment fault".
>
>I am running Linux 0.95c+ on a 8Meg 486 (with 16Meg swap space). Could you
>check it again please?

This might not have anything to do with this particular problem, but I'd
just like to say:

When using gcc-2.1 to compile binaries that you distribute on the net,
/PLEASE/ use the "-static" flag to get a statically linked binary. 
Otherwise, the binary won't work on a machine without the library, and
the result is a segfault.  The binary should really print out "unable to
find /lib/libXX.XX.XX", but due to a minor bug in the crt0.s code, it
doesn't: it just dies with the segmentation fault. 

There is a very easy way to check if a binary is linked with a shared
library: the first 1200 bytes (or so) will contain the ascii string
"unable to find /lib/libXX.YY.ZZ" (where XX.YY.ZZ probably is 92.04.06,
but it really depends on the shared-library version).  The signature can
easily be found using "strings xxx | head" or "od -c xxx | head" or
similar ("head -c1200 xxx", "less xxx" also work)

		Linus

PS.  The crt0.s bug is being fixed, and future versions will give a
clear error message telling you why it doesn't work...
Newsgroups: alt.os.linux
From: johnsonm@stolaf.edu (Michael K. Johnson)
Subject: stuff at tsx-11.mit.edu
Reply-To: johnsonm@stolaf.edu (Michael K. Johnson)
Organization: The Internet
Date: Thu, 16 Apr 1992 16:50:18 GMT

files added at tsx-11.mit.edu:

sources/usr.bin/acu.tar.Z
                su.tar.Z
                tarsplit.shar.Z
docs/man/make.tex.Z

michaelkjohnson
Newsgroups: alt.os.linux,comp.os.linux
From: jpo@informatik.tu-chemnitz.de (Joerg Pommnitz)
Subject: Re: Taylor-uucp 1.03 beta - porting status
Organization: tu-chemnitz
Date: Thu, 16 Apr 1992 06:48:34 GMT

Well, could be you might help me.
In your article about Taylor-uucp you wrote that you were able to fix
the "Memory fault problem".
It's possible I have the same problem when running compress (and some other
programs).
If you found a solution not specific to uucp, please make it available.

Newsgroups: alt.os.linux
From: cwilson@seq.uncwil.edu (c t wilson)
Subject: Re: Compilers
Summary: 4 megs (32 bit) is lot's cheaper than that!!
Keywords: n
Organization: Univ. of North Carolina @ Wilmington
Date: Mon, 6 Apr 1992 23:01:15 GMT

In article <1992Apr6.201319.9055@coe.montana.edu>, osynw@giac1.oscs.montana.edu (Nate Williams) writes:
> In article <ktvj19INNf1r@alhena.usc.edu> ajayshah@alhena.usc.edu (Ajay Shah) writes:
> >Come on... it's $130 for a 4 Meg SIMM.
> 
> Yeah, but you have to buy 4 x 4-Meg simms to work on a 32bit machine.
> 
> After shipping that's around $500.  But, you can buy 4 1-Meg Simms, if 
> you still have slots left.
> 


Where do YOU buy your memory?!?!?!?  My 4 meg, 32 bit simm (80 ns) cost about
half that AFTER shipping.  Not only that, I found an even better price ($210 
before shipping) after I ordered..


> 
> Nate
> -- 
> :-):-):-):-):-):-):-):_):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-)
> :-)Inet: osynw@giac1.oscs.montana.edu  :-) Sys. Mgr. - GIS lab : Earth Sci.:-)
> :-)Bnet: osynw@MTSUNIX (Painfully slow):-) The guy blamed for everything   :-)
> :-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-)

Tom Wilson                                 <cwilson@seq.uncwil.edu>
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Newsgroups: alt.os.linux
Subject: Re: what does linux rhyme with?
Date: 14 Apr 92 09:21:42 GMT
Organization: University of Helsinki

In article <1992Apr13.183516.19064@ra.msstate.edu> dam1@ra.msstate.edu (Daniel A. Martin) writes:
>In article <7823@cayman.COM> pgf@cayman.COM (Paul Fox) writes:
>>
>>	Big question:
>>	
>>	Does "linux" sound like "linus" (i.e.  like "line" followed by "ux"
>>	which rhymes with "us"), or does "linux" sound almost just like
>>	"minix", which I assume people say the way they start "minimal"?
>
>Yeah!  I have been wondering about this too...
>I've been pronouncing in line-ux since that is how I would pronounce
>Linus...although pronouncing it like minix seems to make a lot of
>sense too...hmmmmm...I guess we need Linus to settle this :)

Oh God. This comes up again :)

No, linux doesn't sound like Linus - it's a short [i] sound, like in
mInIx or mInImal or prInt or ...  The reason isn't that I wanted it to
sound like minix, it's just the natural way to pronounce it (imho) in
Swedish.  Pronouncing it like "line"+"ux" is totally foreign to Swedish:
in that case I'd have written it "lainux".  So there.  Maybe this should
be in the FAQ :)

		Linus
From: eonu24@castle.ed.ac.uk (I Reid)
Newsgroups: alt.os.linux
Subject: Re: Beginner's Guide: Installation
Date: 7 Apr 92 19:23:31 GMT
Distribution: alt
Organization: Edinburgh University

jdough@unf6.unf.edu (Joseph Dougherty) writes:

>In article <19765@castle.ed.ac.uk> eonu24@castle.ed.ac.uk (I Reid) writes:
>>--------------------------------------------------------------
>>This is an updated release of my guide to installing Linux. It mostly corrects

>	In reading through this informative post, I discovered only one real
>major error. In the table where you point out the minor numbers of the hard
>disk partitions, there is an error that should be corrected.:

>	In the second set of device numbers, the drive major number should be
>4 with the minor numbers as 1 through 8. This is for a second disk drive
>on a system, using single or multiple partitions. 

>	This should clear up any problems people might be having accessing
>second drives.

My apologies to anyone who had problems with drives following my posting and
thank you to Joseph Dougherty for his correction. What happened was....

When I wrote that bit I did an ls -l /dev on my Linux setup to get the device
numbers and put in what I found. I was writing under a newly installed version
of 0.95a and wasn't aware that I had made a mistake. What can I say.... sorry.

Iain
Newsgroups: alt.os.linux
From: jknapka@aisun1.ai.uga.edu (Joseph Knapka [MSAI])
Subject: Texinfo
Reply-To: jknapka@aisun1.ai.uga.edu (Joseph Knapka [MSAI])
Organization: The Internet
Date: Tue, 14 Apr 1992 19:43:28 GMT

Thanks for the tex-info^2. Two more questions:

1) Can texinfo documents (if that's the word) be created using LaTeX, of
is raw TeX necessary? 2) I assume Texinfo has been ported to Linux; where
is it?

Thanks,

Joseph
From: murthy@cs.cornell.edu (Chet Murthy)
Newsgroups: alt.os.linux
Subject: Meta-Question
Date: 10 Apr 92 17:34:27 GMT
Organization: Cornell Univ. CS Dept, Ithaca NY 14853

Please do not misunderstand this question.  I am very much 
in favor of what Linux is about.  What Ihave been wondering, though,
as I watch this group, and see the activity, and wish I had a laptop
to run Linux on, is this:

  What relation does Linux have to the GNU  Hurd Project?
  Essentially, what I'm trying to figure out, is why all
  this work on Linux is being done in what seems complete
  disconnection from GNU, when the aims of this group,
  and GNU in general, are almost identical.

(Of course, I mght be mistaken about that, but I think I saw
where Linus had written that he didn't want people to hoard
source code, or prevent its free dissemination, which, in a sense,
is the central spirit of GNU)

In any case, I think that what you guys are doing is great, and
first chance I get to get myself a 386/486 machine, I will be
ftp-ing Linux, and getting busy using it.

Thanks,
--chet--
From: lee@uhunix.uhcc.Hawaii.Edu (Greg Lee)
Newsgroups: alt.os.linux
Subject: Re: FINAL: (DOS) BEGINNER'S GUIDE...(also on tsx-11.mit.edu)
Date: 6 Apr 92 10:01:37 GMT
Article-I.D.: news.1992Apr6.100137.22347
Organization: University of Hawaii

Your Guide is very well done.  Following are some notes I made
reading through it.
-----------------------
}Neat, huh? And this is where 'cat' gets its' name; cancatenate,
						     ^-->o

}You can only use 'cat' to list the contents of text files. It won't
}work on 'binary' (executable) files.

Suggest you omit this sentence, since 'cat' is perfectly general,
and since 'binary' is not the same as 'executable'.

}'head' reads to stdout the first 5 lines of a text file. Perhaps
				  ^-->10

}             'ls -l(ENTER)' gives;.....
}             f.....rwxr--r--    01234    Mar2 10:00  file1
              ^^^^^^ ??

}             'ls -lFR(ENTER)' gives.....
	          ^^^^-->-FR

}printenv 
}        from within BASH command shell, print the
}        automatically searched directories, prompt style, aliases, 
}        etc. Print all environment variables. (This is a shell 
}        thing.)

I don't think printenv is bash internal.  (By the way, you might mention
some bash internal commands -- especially 'help'.)

--
Greg Lee <lee@uhunix.uhcc.hawaii.edu>
From: johnsonm@stolaf.edu (Michael K. Johnson)
Newsgroups: alt.os.linux
Subject: When will "Linux 1.0" come to the world ?
Date: 16 Apr 92 16:09:28 GMT
Article-I.D.: athena.1992Apr16.160928.25454
Reply-To: johnsonm@stolaf.edu (Michael K. Johnson)
Organization: The Internet

From: david@csource.oz.au (david nugent)

   [stuff deleted]
   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.

Agreed.  I am learning a lot as I attempt my first device driver.

    > 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.

Yes, but DESQview _does_ provide memory protection.  OS/2 2.0 provides
even better memory protection.  And someone real pedantic might point
to Linux's lack limit enforcement...

[stuff deleted]

   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.

It certainly does better than the obnoxious NeXTen here at stolaf, and
the vaxen.  It is not yet as hardy as the suns, but it is getting there.

michaelkjohnson
johnsonm@stolaf.edu
Newsgroups: alt.os.linux
From: thomas dunbar <GSTD@VTVM2.CC.VT.EDU>
Subject: boot 0.95c+ and lp
Reply-To: GSTD@VTVM2.CC.VT.EDU
Organization: The Internet
Date: Fri, 10 Apr 1992 13:55:33 GMT

now that there's patched bootimage posted, will someone please repost
how to use the lp dev. as i recall, i can just cat the file to the
device, i know lp have major of 6, what's the minor nr?
From: a0356514@let.rug.nl (H.H. Bergman)
Newsgroups: alt.os.linux
Subject: Re: make
Date: 6 Apr 92 13:55:59 GMT
Organization: Faculty of Arts & Letters, Groningen University, The Netherlands

In article <1992Apr4.164652.20151@athena.mit.edu> johnsonm@stolaf.edu (Michael K. Johnson) writes:
>Would whoever has gotten a version of GNU Make succesfully compiled
>that doesn't give the heinous error when non-root please put it up on
>tsx-11?  I have having broken software around for months when people
>have a fixed version just waiting to replace it...  I know I saw
>someone say that it was working flawlessly with the new version that
>they compiled.
>
>This problem shouldn't be a FAQ -- this problem shouldn't even be here.
>
>Thanks a lot!
>
>michaelkjohnson
>johnsonm@stolaf.edu

I have uploaded a version of GNU make (3.62) to nic.funet.fi:/pub/OS/Linux/bin.
It includes patches for gcc1.40 and gcc2. Isn't nic.funet mirrored to tsx-11?


-Hennus Bergman
Newsgroups: alt.os.linux,comp.os.linux
From: david@ods.com (David Engel)
Subject: Re: gcc 2.1 beta is available
Organization: Optical Data Systems, Inc.
Date: Mon, 6 Apr 1992 18:19:58 GMT

hlu@yoda.eecs.wsu.edu (Hongjiu Lu -- Graduate Student) writes:
: THANKS TO ALL THE ALPHA TESTERS. You did a great job and help me a lot,
: Without you guys, I cannot image how I could find all those bugs.

It took longer that I think any of us expected, but we now have one heck 
of a compiler and library.  Thanks H.J.

-David
-- 
David Engel                        Optical Data Systems, Inc.
david@ods.com                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081
From: dam1@ra.msstate.edu (Daniel A. Martin)
Newsgroups: alt.os.linux
Subject: Problems compiling df and system utils under gcc 2.1
Date: 14 Apr 92 22:42:28 GMT
Organization: Mississippi State University

I got a few errors while compiling df as well as chsh and mkswap from the
system-0.95a.tar.Z file...BTW shouldn't df be in this file too?

df compiled ok before I installed gcc 2.1 so SUPER_MAGIC was probably
defined in one of the old include files...what is it supposed to be?

gcc -O3 df.c -o df
df.c: In function `do_df':
df.c:92: `SUPER_MAGIC' undeclared (first use this function)
df.c:92: (Each undeclared identifier is reported only once
df.c:92: for each function it appears in.)

gcc -O3 chsh.c -o chsh
chsh.c: In function `main':
chsh.c:120: `LOCK_FILE' undeclared (first use this function)
chsh.c:120: (Each undeclared identifier is reported only once
chsh.c:120: for each function it appears in.)

I have a link in /usr/include to /usr/src/linux/include/linux to deal
with most of the programs that need kernel header files...I included
kernel.h (from 0.95c+) since it was so short...will someone better
versed in C than me tell me what's wrong...

gcc -O3 mkswap.c -o mkswap
In file included from /usr/include/linux/mm.h:7, from mkswap.c:26:
/usr/include/linux/kernel.h:11: parse error before `('

----------------beginning of kernel.h--------------
/*
 * 'kernel.h' contains some often-used function prototypes etc
 */
void verify_area(void * addr,int count);
volatile void panic(const char * str);
volatile void do_exit(long error_code);
int printf(const char * fmt, ...);
int printk(const char * fmt, ...);
void console_print(const char * str);
int tty_write(unsigned ch,char * buf,int count);
void * malloc(unsigned int size);
void free_s(void * obj, int size);

#define free(x) free_s((x), 0)

/*
 * This is defined as a macro, but at some point this might become a
 * real subroutine that sets a flag if it returns true (to do
 * BSD-style accounting where the process is flagged if it uses root
 * privs).  The implication of this is that you should do normal
 * permissions checks first, and check suser() last.
 */
#define suser() (current->euid == 0)
---------------------end of kernel.h---------------


thanks for any help...

-- 
Danny Martin : dam1@Ra.MsState.Edu
Newsgroups: alt.os.linux
From: thomas dunbar <GSTD@VTVM2.CC.VT.EDU>
Subject: dvilj2p
Reply-To: GSTD@VTVM2.CC.VT.EDU
Organization: The Internet
Date: Tue, 7 Apr 1992 18:35:42 GMT

uploaded dvilj2p.tar.Z to tsx-11.mit.edu
  this is a laserjet driver for TeX dvi files. the binary is for IIp,
IIIp, III, & IIIsi. includes info on diffs from the ftp.wu-wien.ac.at
(dir /pub/src/Typeset/dvi2xx) source and fonts needed for printing
the included man-page dvi.
   speaking of source/binaries, it is specifically the binaries (and
diffs) that should be posted at the Linux sites. If i want the source
for gcc, etc., it is easily available elsewhere. besides, not many binaries
break in kernel updates.
Newsgroups: alt.os.linux