HDTenEightyP/NetNews huggingface dataset:
From: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
Newsgroups: alt.os.linux
Subject: Re: (none)
Date: 7 Apr 92 21:11:52 GMT
Article-I.D.: athena.1992Apr7.211152.4790
Reply-To: tytso@athena.mit.edu
Organization: The Internet

Well, look.  If you want to recompile everything from scratch each time
a new release comes out, more power to you!  Most of the stuff in the
FTP archive servers is available in source form, or if not, can be found
at your nearest GNU FTP server.  If someone puts something up for
anonymous FTP for which you can't find source, feel free to flame the
person who put it up.  (*NOT* the administrators of the FTP site,
please!  :-).

However, I don't think it's fair that you ask everybody to recompile all
of the binaries each time a new release comes out.  For this reason, I
do not plan on deleting the binaries subdirectory on TSX-11.  If you
don't trust the binaries there; fine, don't use them.  There will be
some people who will want to use the binaries which are provided there
instead of compiling their own from source.  That's fine too.  If
someone has a problem with one of the binaries, and recompiles it from
scratch, and uploads to the various FTP sites, I'm sure we'd be happy to
replace the broken version with the fixed one.

						- Ted
Newsgroups: alt.os.linux
From: thomas dunbar <GSTD@VTVM2.CC.VT.EDU>
Subject: Bash 1.12
Reply-To: GSTD@VTVM2.CC.VT.EDU
Organization: The Internet
Date: Thu, 9 Apr 1992 16:17:13 GMT


Bash 1.12 in at hpb.mcc.ac.uk in dir pub/linux/mcc-bin
From: dingbat@diku.dk (Niels Skov Olsen)
Newsgroups: alt.os.linux
Subject: Re: bootimage-0.95c+.scsi corrupt at nic.funet.fi ??
Date: 15 Apr 92 22:52:46 GMT
Distribution: alt
Organization: Department of Computer Science, U of Copenhagen

Johan,

SCSI devices now use major 8. See the scsi.faq at
headrest.woz.colorado.edu (probably other places 
too, I guess).

Niels
Newsgroups: alt.os.linux
From: harlick@lindy.Stanford.EDU (Will Clark)
Subject: Linux dies without SVGA mode.
Organization: Stanford University
Date: Mon, 6 Apr 1992 17:19:57 GMT


Every once in a while when I boot Linux, I miss the return key, (hit
the wrong key) and it starts to boot in 80x25 mode.  I get all the way
to the login prompt, and then the system locks.  I can't enter a
login, or switch VC's.

Is this a known problem?  I am using an unpatched 0.95a kernel from
tsx-11, booting from floppy with the root system on my hard disk.

386-40
8 Meg RAM


Will Clark (Yea!  The baseball season starts today!)
will.an@site007.saic.com
------------------------
SAIC doesn't share my opinions.
harlick@lindy is a friend's account, but you can send me email here, too.

Xref: sparky alt.os.linux:2566 comp.os.linux:535
From: cornell@inoc.dl.nec.com (Cornell Kinderknecht)
Newsgroups: alt.os.linux,comp.os.linux
Subject: linux support MFM hard disks?
Keywords: mfm linux disk drive hard junk
Date: 16 Apr 92 20:49:03 GMT
Article-I.D.: vivaldi.cornell.703457343
Reply-To: cornell@csl.dl.nec.com
Organization: NEC USA, Corporate Network Administration Division

I wonder if linux supports MFM hard drives?

--- Cornell

--
| Cornell Kinderknecht          | Email: cornell@csl.dl.nec.com |
| CNAD/CCSL                     |  UUCP: uunet!necbsd!cornell   |
| NEC USA/NEC America, Inc.     | Phone: 214-518-3509           |
| Irving, TX                    |   Fax: 214-518-3552           |
From: GSTD@VTVM2.CC.VT.EDU (thomas dunbar)
Newsgroups: alt.os.linux
Subject: Re: Digests
Date: 8 Apr 92 11:11:33 GMT
Reply-To: GSTD@VTVM2.CC.VT.EDU
Organization: The Internet


 :: time to remove alt.os.linux

yes, i agree alt.os.linux should disappear
Organization: Sophomore, Physics, Carnegie Mellon, Pittsburgh, PA
Newsgroups: alt.os.linux,comp.os.linux
Date: Wed, 15 Apr 1992 13:45:15 -0400 
From: "Demian A. Johnston" <dj1l+@andrew.cmu.edu>
Subject: Token Ring?

Hi, 
    I have had a wonderful time getting Linux 0.95c+ up and running. I
first had 0.95a and then compiled my own kernel.  (Gcc 1.40)  And
currently and loving gnu-emacs, gcc, bash, nethack, and kermit..  Great
Job Linus et al...

    My problem.  I have a network connection from my PC to my campus
network and the INTERNET via Token Ring..  (This sux if I want to use
unix anywhere)
I have software drivers for MSDOS. But I would love to be able to use my
token ring from under linux..  I am pretty sure the was an IBMTOKEN 
packet driver that worked with the MSDOS ka9q port.  Is there one I can
use with Linux's  KA9Q???

    Thanks again, and congratualtions to everyone on a great OS...



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

Newsgroups: alt.os.linux
From: osynw@giac1.oscs.montana.edu (Nate Williams)
Subject: Re: Compilers
Keywords: n
Organization: Montana State University, Bozeman  MT
Date: Mon, 6 Apr 1992 20:13:19 GMT

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.


Nate
-- 
:-):-):-):-):-):-):-):_):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-)
:-)Inet: osynw@giac1.oscs.montana.edu  :-) Sys. Mgr. - GIS lab : Earth Sci.:-)
:-)Bnet: osynw@MTSUNIX (Painfully slow):-) The guy blamed for everything   :-)
:-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-):-)
From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Newsgroups: alt.os.linux
Subject: Re: problem with chmod/ls -l
Date: 13 Apr 92 14:43:18 GMT
Followup-To: LeBlanc@mcc.ac.uk
Organization: Computing Centre, University of Manchester

>I'm not sure if the second problem is in chmod or ls.  When I change a files
>mode to 6777 ls -l tells me the file is rwsrwsrwx.  Same thing with
>chmod +os file.

This is correct.  There is no o+s.  If you chmod 7777, you should see
rwsrwsrwt.

     -- Owen
     LeBlanc@mcc.ac.uk
Newsgroups: alt.os.linux
From: mdj@mullian.ee.mu.OZ.AU (matthew douglas james)
Subject: where to get FAQ
Organization: Computer Science, University of Melbourne, Australia
Date: Fri, 17 Apr 1992 12:33:52 GMT

Hi guys - Linux looks interesting ! Where is the best place to look for a 

FAQ and other files ?


Matthew James
Newsgroups: alt.os.linux
From: jgifford@attmail.com
Newsgroups: alt.os.linux
Subject: CTL-ALT-DEL wipes CMOS?
Date: 13 Apr 92 17:33:11 GMT
Article-I.D.: athena.1992Apr13.173311.22668
Reply-To: jgifford@attmail.com
Organization: The Internet

I started with .95, moved up to .95a, and now I have .95c+, and in all of
these, I have had problems with ctl-alt-del wiping CMOS.  sometimes it just
hangs, sometimes it blitzes(screen goes blank and hangs), and sometimes
it hangs and wipes cmos.  I always end up having to press reset button
on front(actually two buttons in series to prevent accidents)
is this a known bug?  is it just me?

Jim Gifford
jgifford@attmail.com
 ...!uunet!attmail.com!jgifford
Xref: sparky alt.os.linux:2408 comp.os.linux:321
From: hedrick@dumas.rutgers.edu (Charles Hedrick)
Newsgroups: alt.os.linux,comp.os.linux
Subject: Re: Problems with serial port drivers??
Date: 10 Apr 92 22:54:54 GMT
Followup-To: alt.os.linux
Organization: Rutgers Univ., New Brunswick, N.J.

erc@Apple.COM (Ed Carp) writes:

>Has anyone seen any problems with the serial port drivers under
>linux?  I'm running 0.95a and am having a hard time making uucp fly
>at 9600 baud and above, either straight through or with a modem.

I have had a number of problems with KA9Q.  As of 0.95b or c, I
know of three possible problems:

 1) There's a tendency for the controller not to bother giving a
transmit done interrupt.  Linus added various timeout code that was
supposed to fix this, but I'm not convinced it does. I'm using my own
code. If remembers the time when the last transmit was started.  If a
new transmit is done more than 1/2 sec or so after that, it assumes
the done was missed and does the transmit immediately.

 2) Someone I know who is an expert in these things claims that
the read routine must loop until there's nothing more to read. He
claims that there is a small buffer even in the dumb controllers,
and if you don't empty the buffer each time, you'll lose.

 3) There's a problem in select.  If you are in emacs (which
waits for tty input at a select), and other program that uses
select will fail to activate.

I believe Linus is working on problem 3, but has declined my patches
related to the first two.  So far I haven't done careful enough tests
to be sure that all three of these problems actually exist.  I'm
waiting for him to fix select.  Once he does, if problems remain, I'll
try to verify exactly what they are.
From: scottd@cs.hw.ac.uk (Scott Dunn)
Newsgroups: alt.os.linux
Subject: Re. LINUX INSTALLATION PROBLEMS
Date: 7 Apr 92 08:20:03 GMT
Organization: Dept of Computer Science, Heriot-Watt University, Scotland


Sorry to be a real pain in the but, but here's the next installment in
the ongoing saga of 'Scott Tries To Install Linux'.

Early this morning playing around trying to get things to work.  Decided
to boot up with 0.95 as suggested in I Reid's Beginners Guide.  Made an fs,
rebooted, and it worked, no probs.  Tried 0.95a and :

8 virtual consoles
4 pty's
HD timeoutHD timeout .......
dev 0300, block 0
Unable to read partition table of device 0300
HD timeoutHD timeout .......
dev 0340, block 0
Unable to read partition table of device 0340
Partition tables ok.			/* Wonderful !!!! */
harddisk I/O error
dev 0341, block 1
Kernel panic : Unable to mount root

Back into 0.95, decided to install a few choice pieces of s/w just so
I could at least have a decent look around.  Everything worked, except
mtools (mcopy wouldn't work).  However on the whole it worked.

Before switching off, decided to reboot with 0.95a, just in case.
Amazing, it worked.  Closed eyes, took a deep breath, tried again, it
worked.  Installed some more s/w, mtools working properly.  Couldn't
install gcc at all.  One tar seems to be corrupted, one other returns
with 'out of swap space' and yet another does nothing.

Switched off, went to bed.

6.30 am, getting ready to leave, decided to try out linux,
0.95a - see above error message,
	switch to picture of me stomping around room (quietly) tearing
	at imaginary 'things' culminating in an almighty roar.
	Yes Linus, when you woke up at 6.30 and said 'What the ****
	was that?', now you know.

Tried again,
0.95 - works
0.95a -
HD timeoutHD timeoutHD timeoutHD timeout Partition tables ok.
39488/43545 blocks
14327/14515 inodes
226 buffers - 241424 bytes buffer space
Free mem : 1310720 bytes
All systems functioning

(none) Login :

0.95a seems to work in the above manner 1 in 10 attempts.  I am doing
nothing strange between reboots.

I would really appreciate it if somebody who could help would mail me
or post the group.  My configuration is as detailed in my previous 2 posts
and everything mentioned in them still holds

Remeber I can get 0.95a to works from hda1.  But for the moment at least
I need to keep DOS as it is installed.

Any help much appreciated,

Scott.
From: moyerg@jove.cs.pdx.edu (gary a moyer)
Newsgroups: alt.os.linux
Subject: problem caught
Summary: got the fix
Keywords: kernel
Date: 8 Apr 92 15:02:15 GMT

Thanks to everyone for the pointers on the kernel rebuilds -- I got
it figured now.  Thanks.  moyerg@cs.pdx.edu

Newsgroups: alt.os.linux
From: harvard!ames!amdcad!yarc!scott@EDDIE.MIT.EDU (Scott Beckstead)
Subject: Re:  Linux-Activists Digest #56
Reply-To: harvard!ames!amdcad!yarc!scott@EDDIE.MIT.EDU (Scott Beckstead)
Organization: The Internet
Date: Mon, 13 Apr 1992 07:42:44 GMT

   I discovered that the version of compress on the 95a root disk is completely 
screwed up.  I took the compress from the .12 release and it now works fine.  
Just thought I would enlighten people as I have seen a few complaints and problems concerned with decompress.
Scott
Newsgroups: alt.os.linux
From: cummings@hammer.Prime.COM (Kevin Cummings)
Newsgroups: alt.os.linux
Subject: Re: GCC2.1 (Wonderful !)
Date: 15 Apr 92 18:41:01 GMT
Article-I.D.: hammer.1992Apr15.144101
Organization: Prime Computer R&D

The bottom line here must be quality of the generated code.  And
in particular the CORRECTNESS of the generated code.  Whenever
a code generator bug is founf in gcc-1.4, that is the time to
retire it in favor of gcc-2.x (assuming of course that the same
bug does not (no longer?) exists in gcc-2.x.

=================================================================
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
=================================================================
From: visnucc@ubvmsd.cc.buffalo.edu (Niagara U. Courtesy Account)
Newsgroups: alt.os.linux
Subject: Partitioning Warning!
Date: 12 Apr 92 06:04:00 GMT
Organization: University at Buffalo
News-Software: VAX/VMS VNEWS 1.41

Hi,

   Just thought that I would throw my story into the "be careful partitioning"
arena in the hopes of helping someone.  Recently I got the new fdisk (0.9?) 
from tsx-11, and I used it to check my partitions out.  Everything seemed to
go fine, except that the signature for the partitions was that of an AIX
filesystem (according to fdisk).  So seeing that there was a Linux/MINIX
value (80) and a Linux Swap value (81) I proceeded to rename the signatures.
It went fine, and the system booted etc., but the next day when I booted
DOS (DR DOS 6.0) it recognized the Linux filesystems and called them disks
D: and E: pushing the DOS 2nd disk to F:, and creating a TMP directory
on D: in the process.  To say the least, I was confused.  I thought I lost
my 130+ disk that was D:, but luckily I didn't, but when I went to boot
Linux it was gone, so I did lose something.  I've since installed it over
again, but after 2-3 repartitions and about as meny installations I cannot
got Linux to boot from the HD.  It starts fine, then hangs.  I don't know
why DR DOS using the Linux partitions (Linux had no problem with the sig.
change), but for anyone doing this *BE CAREFUL*.  I'm out of the game for
awhile as a result... no problems from 0.11 to 0.95c until this.

-Rich

--------------------------------------------------------------------------
Richard P. Kernin                  Internet: visnucc@ubvmsc.cc.buffalo.edu
Niagara University                   BITNET: visnucc@ubvmsc.BITNET
--------------------------------------------------------------------------
Newsgroups: alt.os.linux
From: hlu@phys1.physics.wsu.edu (Hongjiu Lu)
Subject: Re: .95c+ and GCC2.1 kernel compiles, MAN?
Keywords: gcc files man kernel
Organization: Washington State University
Date: Mon, 13 Apr 92 21:06:32 GMT

In article <45185@mentor.cc.purdue.edu>, cheetah@sage.cc.purdue.edu (Bowen Goletz) writes:
|> I don't seem to be able to compile the .95c+ kernel using GCC 2.1.  Make
|> complained about not finding gpp, so I read through the GCC docs and
				^^^

Never heard of it. Cpp?

May I suggest use GCC -E instead of cpp?

H.J.
hlu@eecs.wsu.edu
Newsgroups: alt.os.linux
From: johnsonm@stolaf.edu (Michael K. Johnson)
Subject: changing keyboard repeat rate.
Reply-To: johnsonm@stolaf.edu (Michael K. Johnson)
Organization: The Internet
Date: Wed, 15 Apr 1992 18:51:51 GMT

OK, I have gotten several requests for info on how to change the
keyboard repeat rate, so here goes.  Note:  I can't just give diffs,
because there are lots of options, and for heaven's sake it's only
three lines of code.

In boot/setup.S, there are the lines:

! set the keyboard repeat rate to the max

	mov	ax,#0x0305
	mov	bx,0x0000
	int	0x16

If you don't want to change the repeat rate at all, just comment out
these lines.  If you want something in the middle, change the
	mov	bx,0x0000
to	mov	bx,0x????
where ???? is determined by (from Ralf Brown's interrupt list)
bh = delay value (0x00 = 250 ms to 0x03 = 1000 ms (one second))
	this is the delay before the repeat starts happening
bl = repeat rate (0x00 = 30/sec to 0x0c = 10/sec [default] to 0x1f = 2/sec)

I use	mov	bx,0x0006
to delay 1/4 sec, then repeat at what I think is a comfortable rate.
I am too lazy to calculate the exact speed -- maybe 20/sec? ;-)

Hope this helps people.

michaelkjohnson
johnsonm@stolaf.edu
Newsgroups: alt.os.linux
From: johnsonm@stolaf.edu (Michael K. Johnson)
Subject: User's Guide project
Reply-To: johnsonm@stolaf.edu (Michael K. Johnson)
Organization: The Internet
Date: Wed, 15 Apr 1992 17:21:56 GMT

From: einari@rhi.hi.is (Einar Indridason)
   In <kuelccINN613@alhena.usc.edu> ajayshah@alhena.usc.edu (Ajay Shah) writes:
   >knapka@athena.cs.uga.edu (Joseph Knapka) writes:

   >>1) Do you think there is a need for such a document?
   >Yes, I think such a document would be rather valuable.
   >Linux is great.. what more could a hacker ask for?
   >But we could make the results of the same work accessible to
   >a much larger class of users if we add "a little" effort
   >on documentation and easy-to-use installation/administration.

   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.

Well, as co-ordinator of both the manual project, and also the patch
directory at tsx-11, I suppose I should speak up ;-)

First, obligatory weekly plug, since new people seem to join this list
all the time:  If anyone is interested in helping in any way to create
manuals for linux (Not just man pages, but users' guides, programmers'
guides, etc.) mail linux-man-request@stolaf.edu and ask to be put on
the mailing list.  We have several projects going already, and the
more, the merrier.

The patches seem to be better co-ordinated than what I have seen in
minix, because it is so easy to get the latest official version -- you
don't have to patch patches of patches of patches of patches, some of
which were altered somewhere along the way, etc. etc.  The official
version keeps up fairly well with the patches, without bloating too
much, thanks to Linus's tireless editing and work.  (Well, I suppose
he gets tired of it sometimes, but it doesn't show...)  So generally
the patches are are ways to add extra features that are not in the
official version, and just are not so overwhelming as in minix.

So I am not terribly worried that linux will fall into the patch-mire
in the near (or far) future.  Even if Linus someday gives up making
_the_ official kernel, there are other people who will keep an
official version going (although he seems to be having fun -- again,
I'm not too worried).  This is no longer a one-person thing.

michaelkjohnson
johnsonm@stolaf.edu
linux-man-request@stolaf.edu
From: eonu24@castle.ed.ac.uk (I Reid)
Newsgroups: alt.os.linux
Subject: Re: GCC2.1 (Wonderful !)
Date: 15 Apr 92 15:31:08 GMT
Organization: Edinburgh University

kxb@matt.ksu.ksu.edu (Karl R. Buck) writes:

>johnsonm@stolaf.edu (Michael K. Johnson) writes:

>>Please, don't consider 1.40 retired -- It is smaller -- Not all the
>>features, and I am _very_ glad that 2.x is out, and I am sure that I
>>will switch some day.  But right now I want something small, and I
>>simply don't yet need 2.x's features.  I don't think that I am
>>alone...

>I'm not sure about this, but once you have completely recompiled
>everything to use shared libs, you should have a savings in disk
>space.

Add to that the far superior compiler error messages that 2.1 gives etc etc. I
don't want to see 1.40 retired since itr is a first class compiler in its own
right but I would suggest using 2.1 as the default kernel compiler with options
(easily configured) to allow a kernel rebuild with 1.40.

Iain
Newsgroups: alt.os.linux
From: ddd42961@uxa.cso.uiuc.edu (Daniel D Deavours)
Subject: Re: Binaries considered harmful
Organization: University of Illinois at Urbana
Date: Tue, 7 Apr 1992 14:29:24 GMT

Paul Allen <paula@atc.boeing.com> writes:

>- Software that is not needed for bootstrapping should be placed in the
>  archives in source or diff form only.

>- Part of the process of installing a new Linux release is to recompile
>  everything.

	There's a lot of good reasonds for distributing binaries.  Emacs
18.58 is a good reason!  The source code is 4 megabytes compressed, and
the time it would take to compile it on a 16mH SX with 2 megs of ram and
a slow hard drive would be measured in days.  Don't even think about X.

>I may be missing something really obvious here, but I just don't see
>the need for all these binaries.  I'd rather just have sources.  With
>the exception of a few things that simply couldn't be compiled, Minix
>has always been a source-only system.  (You got the binaries when you
>bought Minix, and sources/diffs from the net kept you current from then
>on.) I see no reason that Linux needs to work differently.  

	Minix is mostly a 16 bit OS, and has silly silly size limits to
everything.  Linux is different because it can compile and run HUGE programs.
(I easily ported gnuchess, try that on Minix.)  Also, keeping the source
code around for all the utilities you need can be pretty hard on a limited
sized hard drive.  Further, what compiles on gcc1.37 may not compile on
1.40 or 2.0 or 2.1 (it should, but....)  It's just so much more convenient.
	I like the idea, however, of keeping around sources and diffs.
Shared libraries are one of them.  I think that keeping binaries, even though
some day they may break, are a good idea also.

>Paul Allen
>pallen@atc.boeing.com

Dan Deavours
zeos@uiuc.edu
Newsgroups: alt.os.linux
From: drew@ophelia.cs.colorado.edu (Drew Eckhardt)
Subject: Re: interupts in Linux
Organization: University of Colorado at Boulder
Date: Thu, 16 Apr 1992 11:14:12 GMT

In article <1992Apr15.194056.2561@otago.ac.nz> psyxsgp@otago.ac.nz writes:
>
>	We have some large binary sound files which we read into RAM from
>disk and then send to a ADC/DAC board to drive a speaker.
>	Under DOS we disable most of the system interupts during this
>process to prevent artifact on the replayed signal.
>	What would be the effect of transiently disabling interupts in 
>this way under Linux? (would it crash the system/do terribler irrepairable
>harm ?)
>p.s. we retain one or two of the interupts even under DOS but they do not
>seem to do any harm to the replayed signal.
> 

1.  You can't disable interrupts from a user program.
	A cli should cause a general protection fault, and 
	consequently a SIGSEGV.

2.  There is no gurantee that the memory you've read the 
	file into is present.  If you've disabled any interrupts
	the disk driver depends on... you'll be unhappy.

3.  Unix is NOT real time.  If you have the timer interrupt
	enabled so that the disk driver works, other 
	user programs will be scheduled, and there 
	will be "holes" in what you're getting.

You should write a character device driver that will read/write to/from 
the fs segment directly to/from your board, and not allow any other 
tasks to be scheduled while in the read/write.

Newsgroups: alt.os.linux