HDTenEightyP/NetNews huggingface dataset:
From: card@masi.ibp.fr (Remy CARD)
Newsgroups: comp.os.linux
Subject: efsprogs alpha 6
Date: 17 Aug 92 10:24:20 GMT
Organization: Laboratoire MASI - Universite Pierre et Marie Curie - Paris - France


	Hi,

	For people that downloaded the efsprogs version alpha 5,
DON'T USE THEM !!!  In version alpha 5, efsck contains a bug which
can cause some great damages on an ext fs.  The bug is fixed in
the new version (alpha 6) which is available on ftp-masi.ibp.fr
in the directory pub/linux/ALPHA/extfs (files efsprogs6.tar.Z,
efsprogs6.bin.tar.Z, efsprogs6.src.tar.Z) and I expect them to
be available on tsx-11 in directory pub/linux/ALPHA/extfs soon.

Changes from alpha 5 to alpha 6 are :
- in efsck, a bad test on directory structures is fixed,
- efsck and mkefs now use getopt() to decode arguments,
- mkefs now accepts a -i option to specify the ratio of inodes.

	I strongly apologize for the bug in efsck :-{

		Remy
--

	Remy Card
	card@masi.ibp.fr
Newsgroups: comp.os.linux
From: rafal@utstat.uucp (Rafal Kustra (summer student))
Subject: Re: Modem dial-in procedures needed
Organization: University of Toronto, Dept. of Statistics
Date: Thu, 13 Aug 1992 13:20:47 GMT

In article <1992Aug13.052324.8490@athena.mit.edu> chchen@stat.fsu.edu writes:
>[stuff deleted]
>   I've tried   (1) edit the /etc/inittab to add a line
>                         ttys1:vt100:/etc/getty -m 2400 ttys1 
>                    reboot, and type the command
>                          echo atq1e0s0=2v1x4 >/dev/ttys1
>                    Now the system says the device is busy and my 
>                    friend can not dial in.
>                (2) Without changing the /etc/initab, give the command
>                          echo atq1e0s0=2v1x4 >/dev/ttys1
>                          (no device busy this time)
>                    and then
>                         getty 2400 /dev/ttys1 &
>
>                    This seemed to work but after my friend logout,
>                    his screen went messy (he is also running Linux)
>
>                    Also, how to choose terminal type with this
>                    apporach?
>
>I will be greatly appreciated if someone can post his whole procedures
>to allow modem dial-in.
>                         
>Steve Chen             chchen@stat.fsu.edu
I thing best way is to give modem the neccesary
instruction _before_ you spawn getty on it (ie with
inittab unchanged). Otherwise I remember getting my
system locked. Than change inittab and
(soft!)reboot. But, I'm using getty_ps and is SO much
better I strongly recommend it (!).
To change terminal permanently you change relevant part
of inittab entry. But you can also do it (as root) with
setterm redirecting it to /dev/ttysX.

-- 
/|| Numbers exist only in our minds. There is no physical entity that
 ||_is_ number 1. If there were, 1 would be in a place of honor in 
 || some great museum of science, and past it would file a steady
==== stream of mathematicians gazing at 1 in wonder and awe.
Newsgroups: comp.os.linux
From: kenc@sol.acs.unt.edu (Ken Corey - Operator)
Subject: Re: Don't upgrade to cyrix 486 from 386 yet...
Organization: University of North Texas
Date: Wed, 12 Aug 1992 13:30:54 GMT

davidsen@ariel.crd.GE.COM (william E Davidsen) writes:
>  You realize that you're telling this to people who use an "OEM only"
>/operating system/, with no refund if it doesn't work. At least Cyrix
>won't release patches ;-)

*grin* That's right.  There's no patch program we can run that'll upgrade
microcode...on a cyrix 486DLC, so, in order to save time and trouble, I
figured that I'd let the net know what Cyrix said...

I mean, with software, you can continue to tweak it until it works.  With
hardware, you're sorta stuck unless you've got good diagnostic devices. 

Of course the gentleman of asian extraction I spoke with on the phone
assured me that it would work "very well".  Hrm...I wonder if he's talked to
Cyrix lately?

>  "What's Linux?"
>  "A new hardware diagnostic tool, Pete."

Funny, according to my last girlfriend, Linux is a method of punishing
wayward girlfriends...;)

-- 
Ken == kenc@sol.acs.unt.edu == kenc@vaxb.acs.unt.edu
 One difference between a man and a machine is that a machine is quiet
 when well oiled.
From: duperval@ERE.UMontreal.CA (Duperval Laurent)
Newsgroups: comp.os.linux
Subject: Misc. problems & questions
Date: 22 Aug 92 14:03:53 GMT
Organization: Universite de Montreal

(*Sigh*)

Hi everyone,

First, I'd like to thank all those who have answered my post about removing an
invalid directory.  I haven't applied the changes to my kernel yet but I will,
sometime today.  Read on to find out why I'm waiting a bit.

I was really enjoying Linux and having a lot of fun until this week.  I've
encountered a few problems which I need a bit of help with:

1) When I untar a file that contains a file with more than 14 characters, for
some odd reason, the system reboots.  What is the problem?

2)  I've had major problems with system reboots all week.  I try zipping files
and the whole thing blows in my face after a while.  Is there a known limit to
using zip on Linux?

3) I'm currently using 0.96cpl1.  Now, after all the trouble I've been
through, I'm going to update to 0.97, hoping all the problems will go away
(wishful thinking? :-) ).  I need to know what the current release is.  I know
we're up to patch #1 (it's on tsx).   What is the one line patch?  Is it
already included in the patch on tsx?  And I seem to recall that patch #2 is
also available.  Am I wrong?  If not, where can I find it?

Thanks for your help.  Hopefully, within 24 hours I will once again have a
stable system.

-- 
Laurent Duperval
duperval@ere.umontreal.ca
duperval@jsp.umontreal.ca
"If you gotta go, you might as well go happy... or suprised"   -Me
Newsgroups: comp.os.linux
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.os.linux
Subject: Re: AMD386 vs. Intel386 & external cache problems
Keywords: AMD 386 Intel cache
Date: 13 Aug 92 13:05:54 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <1992Aug12.153149.29972@news.th-darmstadt.de>, herr@hp11.iti.informatik.th-darmstadt.de (Gabor Herr) writes:

Let me start by saying that this was a good example of how to describe a
problem, how to test for it, and what you did to isolate the problem
component. I'm going to keep the test programs around to test any new
machine I want to use, even though I've had no problems.

| As a last try I went back to my dealer and after he made me a good
| price, I changed the board for an Intel 486DX, 33Mhz, 256KB cache, 
| C&T Peak chipset. And now Linux works fine on this even much faster
| machine. I stopped the gcc/groff test after 4 hours of running without
| any errors.:-)

  My thought was a heat problem. I could rule out your case since it
failed in your friend's machine (nice to have a friend who will swap a
motherboard with you), but the second possibility is that you had the
chip in a different place which got less cooling in both cases. I would
have suggested cooling the CPU with a hair drier set on cold air
setting, just to test the hypothesis. I would recommend heating the chip
because of possible damage (although I might do it on my own system).

| I also want to know what was the reason for this kind of errors.
| Therefore some questions:
| 
| - Is there anybody out in the net using Linux on a configuration
|   similar to my old one? Please try to run the above tests and tell me
|   if it worked...
| 
| - Are there differences between AMD 386 and Intel 386? Has the AMD
|   probably some bugs?

  No bugs I've seen (other than POPAD which is in Intel chips, too), and
they generally run a bit cooler. If you can remember the placement of
the CPU on the board, you might confirm that it was or wasn't different
from the board which works for your friend.
-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    I admit that when I was in school I wrote COBOL. But I didn't compile.
Newsgroups: comp.os.linux
From: david@ods.com (David Engel)
Subject: Re: /lib/libc.2.2.2 problems
Organization: Optical Data Systems, Inc.
X-Newsreader: Tin 1.1 PL4
Date: Wed, 12 Aug 1992 14:17:59 GMT

kevins@cae.wisc.edu (Kevin Schroedel) writes:
: 
: 	I have caught this thread a couple of times in comp.os.linux but
: can't seem to find the messages that say how to resolve the problem.  When
: I run xgames programs like xpuzzle or othello, I get the messages
: 			/lib/libc.2.2.2
: 			/lib/libm.2.2.2
: and then the program dies.
: At one point, I saw a posting that said the ldd was responsible for the 
: message but didn't explain why the programs just die afterward.  Is this
: a GCC problem?  Is it an X problem?  I have tried compiling my own test
: programs with and without shared libraries and /lib/libc.2.2.2 seems
: to work just fine.

OK, one more time, with feeling ...

The problem is NOT caused by ldd.  In fact, it is beause of ldd that
this problem is relatively easy to diagnose.

Every Linux program has a special function called by the startup code
before main.  Normally, this function informs the kernel about the
required shared libraries and returns.  However, when the program is
run in a special way, typically by ldd, the function prints the names
of the required libraries on stdout and exits.

This is the output you are seeing.  The only way you should see this
output when running a program normally (i.e. not from ldd), is if the
startup code gets re-executed.  There are several things which could
cause this to happen but the most common is the use of mismatched
shared libraries.

Any program linked with the shared X libraries MUST be linked with the
EXACT SAME shared C and math libraries which were used to create the
shared X library image.

David
-- 
David Engel                        Optical Data Systems, Inc.
david@ods.com                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081
From: smp@myamig2.myamiga.mixcom.com (Steve Palm)
Newsgroups: comp.os.linux
Subject: Re: Can I use dd on my UNIX system instead of Rawrite?
Date: 18 Aug 92 15:28:22 GMT
Article-I.D.: myamig2.92081825
Organization: Proud Linux Site, Milwaukee WI
X-Newsreader: Tin 1.1 PL4

smace@nyx.cs.du.edu (Scott Mace) writes:
: >>Or use dd(1)? I'm pretty sure this would accomplish the same thing as 
: >>rawrite under DOS. Has someone tried this?
: >
: >dd will work too, but cp is easier...
: >
: don't forget you need to do dd bs=8192 if=Image of=/dev/PS0
: 
: bs = bootsector and you need this for the kernel boot disk in order for
: it to work.  I don't no what will happen if you don't use the 'bs'
: option.

 I believe bs is buffer size.  It's set to 8K to increase throughput with
 the floppy device.

--
Steven M. Palm
smp@myamiga.mixcom.com   or   smp@myamig2.myamiga.mixcom.com (LINUX SITE)
Milwaukee, WI
Newsgroups: comp.os.linux
From: jjb0391@tm0006.lerc.nasa.gov (James J. Bahm)
Subject: TCP/IP and Utilities
News-Software: VAX/VMS VNEWS 1.41    
Organization: NASA Lewis Research Center / Cleveland, Ohio
Date: 18 Aug 1992 14:45 EST  

Hello,

   I am new to Linux, I have it up and running and I am just wondering
if anyone is working on network support or if it is available.  If it
is available please let me know if someone is working on it also let me
know.  I would also like to know what NICs will be supported and any
general information....

Jim Bahm
jjb0391@tm0006.lerc.nasa.gov
From: bsp10@cd.amdahl.com (Byong Pak)
Newsgroups: comp.os.linux
Subject: New version of X
Keywords: where is it?
Date: 17 Aug 92 20:58:25 GMT
Reply-To: bsp10@duts.ccc.amdahl.com
Organization: Amdahl Corporation, Sunnyvale CA

Is the new version of X386 available (in binary form) for linux yet?  
I think I want the one based on 1.2   Anyone know where it is or when 
it will be available?

Thanks.

-- 
* Byong "the pakman" Pak             * These opinions are my own and do *
*        aka                         *   not reflect the opinions or    *
*  email:  bsp10@duts.ccc.amdahl.com *    policies of Amdahl Corp.      *
*  phone:  408-746-7871              *                                  *
Newsgroups: comp.os.linux
From: jbm@cyclone.sbi.com (Jeffrey B. Moore)
Subject: Re: Logo in hand-hacked PostScript
Reply-To: jbm@cyclone.sbi.com (Jeffrey B. Moore)
Organization: The Internet
Date: Wed, 19 Aug 1992 18:01:49 GMT

[...]
| The "hand-hacked" version from jbm is a lot smaller, but it's missing
| the nice gradient on the blue background.

Take a look at the code.  See the line which reads:
    /llDoGradient false def 	% Do funky shading of triangle?

Try changing `false' to `true'.  I have the gradient behavior turned
off by default b/c I don't trust the previewer I tested against, and
this may look odd; but I'd love to hear how it actually looks on a
real color PostScript device.  The `from' and `to' blues of the
gradient (and the red of the cross-bar) can be tuned by tweaking the
lines:
    /llTriangleTopRGB { 0.96 0.95 1.0 } def	% These are guesses because...
    /llTriangleBottomRGB { 0.4 0.3 0.75 } def	% ...I'm not sure about my test...
    /llBarRGB { 0.8 0.0 0.5 } def		% ...output device.
    
-Jeff (jbm@sbi.com)
Newsgroups: comp.os.linux
From: jaatine@tutka.uku.fi (Kai Jaatinen)
Subject: X and S3 ?
Date: 21 Aug 92 13:27:10 GMT
Organization: University of Kuopio, Finland


Does X run with S3-card, for example with Stealth ?

Does S3-card work with interlaced monitor in 1024x768i-mode ?

My monitor has frequencies:

  horisontal: 31.5 kHz  vertical: 43.5 Hz interlace
              35.2                56
              35.5                60
                                  70      interlace
Will it work with S3-card ?

--
Kai Jaatinen             
email: jaatine@tutka.uku.fi
Newsgroups: comp.os.linux
Subject: mkfs -c /dev/hda3 results in Kernel panic during install to HD
From: brand@addvax.llnl.gov (Hal R. Brand, LLnL, 510-422-6312)
Date: 18 Aug 92 21:43:00 GMT
Organization: Lawrence Livermore National Laboratory
News-Software: VAX/VMS VNEWS 1.40    

Booting the Linux 0.97 bootimage gives:
	Serial port at 0x03f8 (irq 4) is a 16450
	Serial port at 0x02f8 (irq 3) is a 16450
	8 virtual consoles
	4 ptys
	lp_init: lp1 exists (0)
	lp_init: lp1 exists (0)
	Bus mouse detected and installed.
	Linux version 0.97-11 Aug 1 1992 13:33:18
	Floppy drive(s): fd0 is 1.2M, fd1 is 1.44M
	floppy: FDC version 0x90
	sock_init: initializing family 1 (AF_UNIX)
	scsi : 0 hosts
	scsi : detected 0 scsi disks 0 tapes total.
	hd0:
	 part 1 start 32 size 450528 end 450559
	 part 2 start 450560 size 204800 end 655359
	 part 3 start 655360 size 122880 end 778239
	 part 4 start 778240 size 122880 end 901119
Note: This a agrees with the what the NORTON utilities say. An YES, I know
 these 4 partitions don't fill the disk: 1 & 2 are for DOS, 3 and 4 are
 for Linux, but the (current) 64 Mbyte limit prevents using bigger partitions
 until later (soon?).
	Partition table ok
After feeding the floppy the 0.97.1 root disk:
	325 buffers = 332800 bytes buffer space
	Free mem: 15568896 bytes
	Welcome to the Linux V0.97.1 root disk
Now, logging in as root:
	# mkfs -c /dev/hda3 61440
	20480 inodes
	61440 blocks
	Firstdtazone = 653 (653)
	Zonesize = 1024
	Maxsize = 268966912
	HD: read_intr: status = 0x51
	HD: read_intr: error = 0x10
	HD: read_intr: status = 0x51
	HD: read_intr: error = 0x10
	HD: read_intr: status = 0x51
	HD: read_intr: error = 0x10
	HD-controller reset
	Kernel panic: Trying to write bad sector
	In swapper task - not syncing
At this point, there is not "#" prompt, but the keyboard is still active
in the sense that keystrokes are echoed and the "delete" key does the
right thing.

Anybody got any ideas, suggestions?

					Hal R. Brand
					LLNL
					brand@addvax.llnl.gov
Newsgroups: comp.os.linux
From: maniattb@cs.rpi.edu (Bill Maniatty)
Subject: Re: shared libs - can everyone be happy with this?
Date: Mon, 17 Aug 1992 18:09:37 GMT

Newsgroups: comp.os.linux
From: maniattb@cs.rpi.edu (Bill Maniatty)
Subject: Re: shared libs - can everyone be happy with this?
Date: Mon, 17 Aug 1992 18:02:50 GMT

In article <1992Aug17.152210.23427@riacs.edu>, laredo@cc.gatech.edu (Nathan I. Laredo) writes:
|> In article <d-dyhz_@rpi.edu> maniattb@cs.rpi.edu (Bill Maniatty) writes:
|> >In article <1992Aug17.065450.28834@colorado.edu>, drew@ophelia.cs.colorado.edu (Drew Eckhardt) writes:
|> >|> In article <NOP.92Aug16220027@theory.Mankato.MSUS.EDU> nop@theory.Mankato.MSUS.EDU (Jay A. Carlson) writes:
|> >|> >In article <1992Aug15.042420.18914@serval.net.wsu.edu> hlu@phys1.physics.wsu.edu (Hongjiu Lu) writes:
|> >	[Stuff Deleted] 
|> >|> Also, if we ever unbreak Linux, writing to code space should trigger
|> >|> a segmentation fault - it's like it is now because the estdio library 
|> >|> was broken, and wrote to the code. 
|> >	Does linux permit self modifying code (by design or bug)?
|> >	This seems like a pretty bad ``feature''.
|> 
|> Hopefully we won't start another nasty chain here.. but someone correct
|> me if I'm wrong, but I've always been from the school that said that
|> all static variables went into the code space, otherwise how would
|> they be loaded in.
	[Stuff Deleted]

I don't have a machine to run Linux on (yet :-) so I have to ask a stupid
question here.  My original post may have an incorrect assumption about
how memory management is performed.

	I thought that traditional C compilers/linkers used the following segment
structure for memory management (for more details see Comer's Designing
Systems - the Xinu Approach)

	text - instruction space
	data - initialized data space
	bss - uninitialized data space
	stack - stack segment
	(typically the heap and stack are at opposing ends of the same segment,
		and grow towards each other)

I think data and bss could be combined into a single segment on 80x86.

How does linux do memory management at compile/run time?
Also what flavors of memory protection does linux support?

Bill

|> Nathan I. Laredo (this spot: $9) Internet: gt7080a@prism.gatech.edu 
|> uucp:  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt7080a
|> "Having had the correct view is nothing meritorious: statistically,
|>  it is almost inevitable..."  -- Mr. Palomar,  On biting the tongue

-- 
|
|	maniattb@cs.rpi.edu - in real life Bill Maniatty
|
From: hlu@phys1.physics.wsu.edu (Hongjiu Lu)
Newsgroups: comp.os.linux
Subject: Re: GCC questions
Date: 19 Aug 92 22:07:24 GMT
Article-I.D.: serval.1992Aug19.220724.9928
Organization: Washington State University

In article <1992Aug19.194738.16080@mits.mdata.fi>, kennu@mits.mdata.fi (Kenneth Falck) writes:
|> In article <1992Aug18.185326.23062@serval.net.wsu.edu> hlu@phys1.physics.wsu.edu (Hongjiu Lu) writes:
|> >|>        /lib/*.*
|> >|>        /usr/lib/...../i386-linux/2.2.2d/*.*
|> >|>        /usr/lib/...../i386-linux/2.2.2d/shared/*.*
|> >|> 
|> >|> 
|> >
|> >You need them. 
|> 
|> By the way, may I ask where that unbeliavably long and cryptic
|> path to the library files has come from? :-) No offence to whoever
|> is "responsible", but somehow I think it might be a little bit
|> less complex...

.......

|> 
|> I suppose it has something to do with having a lot of GCC
|> libraries for different compilers on different machines on 
|> the same filesystem.
|> 

You are right here.

|> I must admit though, that I haven't even checked whether
|> you can change the default path very easily, probably so...
|> 

gcc -b i386-linux -V 2.2.2

Read gcc.1/gcc.ps/gcc.man.

-- 
H.J.
Gcc/libc maintainer for Linux.
Newsgroups: comp.os.linux
Subject: Re: Problems compiling Elm and mail
From: tomlin@elec.canterbury.ac.nz (Mark Tomlinson)
Date: 17 Aug 92 09:57:02 +1200
Distribution: world
Organization: Electrical Engineering, University of Canterbury, New Zealand
X-Newsreader: Tin 1.1 PL5

Jim Segrave (jes@grendel.demon.co.uk) wrote:
: - more at the original authors for
: such sloppy coding practices. I'd had a long day dealing with just these
: problems in another large chunk of code.

You too huh? I just spent quite a while searching through the source for the
reason that mail was not resolving @ addresses. I found that the search of
the 'paths' file just didn't work. Has anyone else made alterations to the
mail in mailpak1.2? What I've got now does work, but the code is messy. It
looks like there have been changes made by various people at various times,
all contributing to a very messy piece of code.

 - Mark Tomlinso
Newsgroups: comp.os.linux
From: Ching-Hsiang Chen <chchen@stat.fsu.edu>
Subject: Modem dial-in procedures needed
Reply-To: chchen@stat.fsu.edu
Organization: The Internet
Date: Thu, 13 Aug 1992 05:23:24 GMT

I've seen several discussions about modem dial-in for Linux system. I
got two unsolved questions here:
1. Is it necessary to get getty_ps program to allow modem dial-in?
2. If I just want to use the getty from MCC-INTERIM or root image (.96 or
   .97), what steps should I follow?
   I've tried   (1) edit the /etc/inittab to add a line
                         ttys1:vt100:/etc/getty -m 2400 ttys1 
                    reboot, and type the command
                          echo atq1e0s0=2v1x4 >/dev/ttys1
                    Now the system says the device is busy and my 
                    friend can not dial in.
                (2) Without changing the /etc/initab, give the command
                          echo atq1e0s0=2v1x4 >/dev/ttys1
                          (no device busy this time)
                    and then
                         getty 2400 /dev/ttys1 &

                    This seemed to work but after my friend logout,
                    his screen went messy (he is also running Linux)

                    Also, how to choose terminal type with this
                    apporach?

I will be greatly appreciated if someone can post his whole procedures
to allow modem dial-in.
                         
Steve Chen             chchen@stat.fsu.edu
Newsgroups: comp.os.linux
From: cc_s525@kingston.ac.uk (Francis Bell)
Subject: EISA bus machines
Followup-To: comp.os.linux
Keywords: EISA
Organization: Kingston University
Date: Sat, 22 Aug 1992 14:10:56 GMT
Expires: Tue, 8 Sep 1992 23:00:00 GMT

Hi Linuxers,
       The FAQ says that Linux won't run on EISA machines. Can anyone
explain why, and suggest how difficult it would be to remedy ?

Thanks,


-- 
   _____                 "There's so many different worlds,
    /  '                     so many different Suns" - Mark Knopfler
 ,-/-, __  __.  ____         
(_/   / (_(_/|_/ / <_    fgtbell@kingston.ac.uk
From: mj@dfv.rwth-aachen.de (Martin Junius)
Subject: BUG: crashing program kills file system
Organization: Communication Networks
Date: Wed, 19 Aug 1992 19:58:39 GMT

The following bug I ran across while trying to uncompress/tar a 
.tar.Z file directly from floppy disk:

uncompress died with a core dump, obviously it didn't like the 
garbage right after the last byte of the .tar.Z file (can be 
reproduced with 2.2.2dmisc.tar.Z from the GCC distribution and 
RAWRITE). This can be solved by dd'ing the files to floppy disk 
with `conv=sync', but that's not the problem.

The problem is that uncompress while writing to disk and core 
dumping corrupts the file system!!! Looks like the kernel 
does some strange things to the buffers while dumping core, so 
that the currently written files are not written to disk, but 
blocks for them are marked used, or something like that. After 
some more disk activity your file system will be ready for a new 
install.

Maybe someone should take a deep look in the core dump code ...

One way to prevent the file system from getting corrupted is 
_immediately_ after the crash deleting this extracted files and 
then calling "fsck -r", which will be able to restore the file 
system.

Martin
-- 
 _____ _____
|     |___  |   Martin Junius           FIDO:      2:242/6.1
| | | |   | |   Communication Networks  Internet:  mj@dfv.rwth-aachen.de
|_|_|_|@work|   Aachen U of Technology  Phone:     ++49-241-8790220 (voice)