HDTenEightyP/NetNews huggingface dataset:
From: steve@Nyongwa.CAM.ORG (Steve M. Robbins)
Newsgroups: comp.os.linux
Subject: Re: Kermit lock files
Date: 11 Sep 92 16:31:28 GMT
Organization: Chiral Symmetry Breaking, Inc.

In article <1992Sep10.160855.23000@news.nd.edu> jonathan@nova.next.nd.edu (Jonathan Bradshaw) writes:
>I have linux running using the MCC-Interim release (and by the way, a great
>job done in that package.)  The kermit that comes with it (which I'm using now)
>works fine but it puts its lock file in /tmp/LCK..ttys0 and I'd like it in
>/usr/spool/uucp/LCK* instead. I assume somewhere there is a way of changing it
>but I have yet to find it. The reason I need this is that UUGETTY checks
>/usr/spool/uucp/LCK* for lock files and since kermit doesn't place one there
>I get a serial port confliction between kermit and UUGETTY.

In point of fact, the lock dir for uugetty (from getty_ps, I'm assuming) is a
#define, so you can set it to whatever you like.  (/tmp seems like a goofy
choice to me, however)

> Jonathan Bradshaw | jonathan@nova.decio.nd.edu | HAM: N9OXE | Prodigy XMSN02B
-- 
Steve Robbins  --  steve@nyongwa.cam.org
Do not think that I have come to bring peace on earth;
I have not come to bring peace, but a sword.
			- Jesus (Matthew 10:34)
Newsgroups: comp.os.linux
From: hurtta@cs.Helsinki.FI (Kari E. Hurtta)
Newsgroups: comp.os.linux
Subject: Re: Background processes not dying on parent exit
Date: 6 Sep 92 15:02:32 GMT
	<1992Aug31.071515.24296@klaava.Helsinki.FI> <20189@plains.NoDak.edu>
Organization: Department of Computer Science, University of Helsinki, Finland

<This is said here one time earlier at least, but seems that someones don't
 understand without repeating.>

In article <20189@plains.NoDak.edu> person@plains.NoDak.edu (Brett G Person ) wrote:
> Why is it done this way?  This is kinda sloppy.  I know that
> somethimes unix will forget to kill one of my processes, but it
> doesn't seem to happen very often.  Why would linux be designed this
> way?   
> 
> I think that all processes that aren't specifically nohup'ed should
> have to die when their parents die. 

Linux does what programs ask to it do.

It is shell, what is designed this way. From csh's manual page:
"All processes detached with  & are effectively nohup'd." This
apply also to tcsh. 

So ask from writer of csh.

- K E H
( Kari.Hurtta@Helsinki.FI,
  hurtta@cc.Helsinki.FI,
  hurtta@cs.Helsinki.FI,
  HURTTA@FINUH.BITNET
)
From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Newsgroups: comp.os.linux
Subject: Re: MCC 0.97pl2 and lilo
Date: 14 Sep 92 10:11:56 GMT
Reply-To: LeBlanc@mcc.ac.uk (A. V. Le Blanc)
Organization: Computing Centre, University of Manchester

In article <1432@yetti.UUCP> frank@cs.yorku.ca (Frank Pikelner) writes:
>I was installing MCC-interim version 0.97pl2
...
>I maybe ignorant, but
>the docs (installation) said nothing about lilo writing into my master boot block.

In the file README.lilo.first I wrote a section titled 'How do I set up LILO?'.
This section contains an example lilo installation with a bit-by-bit explanation
saying

     Now this command means:
          execute /etc/lilo/lilo to install LILO,
          ...
          installing the LILO boot code in the master boot record of /dev/hda,
          ...

At the bottom of this little file (99 lines long) there is a section of
WARNINGS explaining how to install LILO somewhere other than the master
boot record, among other things.  The file README.lilo contains a complete
set of instructions for backing up the master boot sector and restoring
it.  There are many WARNINGS (almost invariably in upper case letters)
in all the README files to the effect that you can wipe out everything
on your hard disk in a number of intriguing ways.

>Now I'm stuck. I have downloaded the lilo documentation - I doubt that I can 
>uninstall it....
>Maybe this info can be included in the documentation for installing mcc0.97pl2
>with a warning.

The information is there, and was there before you suggested it.  Please
do not install Linux -- or any other operating system -- without reading
the documentation.

     -- Owen
     LeBlanc@mcc.ac.uk
Newsgroups: comp.os.linux
From: jwinstea@fenris.claremont.edu (Jim Winstead Jr.)
Subject: Re: patch to Pax v1.2
Organization: Harvey Mudd College, WIBSTR
Date: Tue, 15 Sep 1992 18:09:26 GMT

In article <1992Sep15.135231.29487@novell.com> bboerner@novdpd.uucp (Brendan B. Boerner) writes:
>Has anyone used pax to write multiple floppy archives?  I'm using 0.97
>Pl 5 kernel with a system built using Jim Winstead's boot/root disk set
>and am trying this:
>
>$ pax -w -v -f /dev/fd0 <some stuff>
>
>(also tried /dev/fd0h1200 and /dev/fd0d360 on a 360K disk).  The floppy
>runs for a while and then stops and nothing happens.  Data is getting
>written because I can do a pax -v -f /dev/fd0 and read the archive - it
>gets to the end and asks for the next volume.

Yes, this problem had been reported before, but I never really had the
time to experiment with Pax enough to find the bug.  I hope you fixed
it.  :)  (I haven't recompiled pax to check it yet....)

>The problem is that the last write to the floppy returns 0 so this just
>loops forever.  I checked out write(2) and it did say that write/read
>will return 0 on EOF sooooo.... what's different?  Did the defined
>return value for write() change since pax was written?

It's possible that someone changed the rules on pax.  A good example
of this is the utimbuf stuff - that is apparently a POSIX thing now,
and you would expect pax to use it (being a POSIX-defined utility),
but apparently pax predates that.

Pax 1.2 overall is not really up to POSIX specs.  It's apparently a
draft or two behind the current one, which mainly effects the
interface (some of the options have changed, etc.)  I've been working
on cleaning it up at least enough so it acts like it should, and I'll
release the source that I've modified 'soon'.

I've also been looking at adding the much-requested -z switch, but
time is limited and motivation is even more limited.

It's interesting to note that most of the chages in your patch were to
bring pax up to POSIX conformance rather than making it compilable on
a Linux system.  :)
-- 
                                    +      Jim Winstead Jr. (CSci '95)
                                    |      Harvey Mudd College, WIBSTR
                                    |   jwinstea@jarthur.Claremont.EDU
                                    + or jwinstea@fenris.Claremont.EDU
Newsgroups: comp.os.linux
From: donadio@wilbur.psu.edu (Beaker)
Subject: A few question about the future plans
Keywords: question tc/pip security NFS
Organization: Penn State University, Center for Academic Computing
Date: Tue, 15 Sep 92 03:24:05 GMT

I have a few questions about the future plans of linux.  How are the
TC/PIP tests going.  I just purchased a 10baseT card for a ridiculous
price and was wondering when I could use it.  I know about ka9q, but
I haven't had time to really check it out (or find my autoexec.net
file from DOS).

Second, how secure is linux?  Are there any known holes in getty or
any ways to gain superuser access?  Cound something like kerberos
be implemented or used?

Third, are there any plans to implement something like NFS? I guess
this is related to the second question because a few of my friends 
and I would like to use NFS and be able to use our machines remotely.


-- 
Beaker aka Matt Donadio| When you've seen beyond yourself--then you may find
-----------------------| peace of mind, is waiting there--And the time will
mxd120@psuvm.psu.edu   | come when you see we're all one, and life flows on
donadio@wilbur.psu.edu | within you and without you.  --George Harrison
From: wirzeniu@klaava.Helsinki.FI (Lars Wirzenius)
Newsgroups: comp.os.linux
Subject: Re: gcc 2.2.2d installation woes
Date: 8 Sep 92 07:01:29 GMT
Organization: University of Helsinki

kk@cs.tu-berlin.de (Kolja Kaehler) writes:
>I'm currently trying to install gcc 2.2.2d and ran into a few major problems;
>this is what I did so far:
>
>- got 2.2.2d{db,lib,misc}.tar.Z

The file release-2.2.2d contains a list of _all_ needed files (the above
ain't it).  Be absolutely certain that you get the README and release*
files.

After you get the files, put them all into a dedicated directory
(/usr/tmp/gcc-install is fine), make certain you have the kernel sources
online (prefereably in /usr/src/linux), then run the shell script
install.2.x with the command 

	sh 2.2.2d /usr/src/linux

and follow instructions given by the shell script.

This should be all you need to do to install gcc.  Persons with some
experience and not suffering from reading difficulties should also be
able to follow the directions given in the README and release-2.2.2d
files, which say just about the same thing as the above (I think; the
above is from memory, and I'm tired, so if the docs say something else,
I'm wrong).

--
Lars.Wirzenius@helsinki.fi
From: Rob.Levin@f217.n3802.z1.fidonet.org (Rob Levin)
Newsgroups: comp.os.linux
Subject: GP faults and other trivia. . .
Date: Thu, 10 Sep 1992 21:14:56 -0800

 LBT> The above (mostly deleted) description does sound like a memory
problem:
 LBT> I should probably enable the NMI just to get a warning about it,
but I
 LBT> think current versions of linux disable it at bootup (I think I
disable
 LBT> it as soon as possible as the system cannot handle it during
setup, and
 LBT> after the system is up and running and a NMI could be handled, I
never
 LBT> re-enable them.  I haven't looked into in a long time, so I could
be
 LBT> wrong.)

Linus,

This sounds like a great idea!  Whenever you get around to it, would it
be possible for you to make it user-configurable in the main kernel
Makefile?


Rob L.


 * Origin: Via the Annex in Victoria, TX (1:3802/217)
From: frank@cs.yorku.ca (Frank Pikelner)
Newsgroups: comp.os.linux
Subject: Re: MCC 0.97pl2 and lilo
Date: 15 Sep 92 17:48:07 GMT
Article-I.D.: yetti.1434
Distribution: world
Organization: York University, Dept. of Computer Science

In article <5799@mccuts.uts.mcc.ac.uk>, zlsiial@uts.mcc.ac.uk (A. V. Le Blanc) writes:
|> In article <1432@yetti.UUCP> frank@cs.yorku.ca (Frank Pikelner) writes:
|> >I was installing MCC-interim version 0.97pl2
|> ...
|> >I maybe ignorant, but
|> >the docs (installation) said nothing about lilo writing into my master boot block.
|> 
|> In the file README.lilo.first I wrote a section titled 'How do I set up LILO?'.
|> This section contains an example lilo installation with a bit-by-bit explanation
|> saying
|> 
|>      Now this command means:
|>           execute /etc/lilo/lilo to install LILO,
|>           ...
|>           installing the LILO boot code in the master boot record of /dev/hda,
|>           ...
|> 
|> At the bottom of this little file (99 lines long) there is a section of
|> WARNINGS explaining how to install LILO somewhere other than the master
|> boot record, among other things.  The file README.lilo contains a complete
|> set of instructions for backing up the master boot sector and restoring
|> it.  There are many WARNINGS (almost invariably in upper case letters)
|> in all the README files to the effect that you can wipe out everything
|> on your hard disk in a number of intriguing ways.
|> 
|> >Now I'm stuck. I have downloaded the lilo documentation - I doubt that I can 
|> >uninstall it....
|> >Maybe this info can be included in the documentation for installing mcc0.97pl2
|> >with a warning.
|> 
|> The information is there, and was there before you suggested it.  Please
|> do not install Linux -- or any other operating system -- without reading
|> the documentation.
|> 
|>      -- Owen
|>      LeBlanc@mcc.ac.uk

THe file you mentioned README.lilo.first is it included in the lilo directory
in the MCC-INTERIM version 0.97pl2? I did not see it. If it is there my appologies. The documentation I followed was for installing the mcc version, which
tells you to run the lilo installation script.
-- 

--------------------------------------------------------------------------
 ---  ---    Frank Pikelner                                          /~\
 \    \  \   Technical Assistant, Department of Computer Science    <v.v>
  \-   \--   York University (Toronto, Canada)                      ,\^/;
   \    \    Internet: frank@cs.yorku.ca                            _{!}_
--------------------------------------------------------------------------
From: johnhm@vaxc.cc.monash.edu.au
Newsgroups: comp.os.linux
Subject: Re: GP faults and other trivia. . / Internal compiler errors
Date: 9 Sep 92 14:00:46 +1000
Organization: Computer Centre, Monash University, Australia

In article <1992Sep8.104048.1@ualr.edu>, nmspillers@ualr.edu writes:
> Hello and welcome to my first posting on this news group. . .
> 
> First of all, let me add my compliments and general awe to all who work
> on this project--fantastic job guys, you have probably created the
> Volkswagon of Unixes, no real snob value, but a loveable, durable solution that
> gets the job done--the people's OS!
> 
> Anyhoo, the crux of my question is this--I'm working with Linux 0.96c
> (no patches yet, I want to solve this problem first) and trying to compile
> the kernel.  I usually get a general protection fault somewhere in the kernel
> compile, this leads to a 4-11 meg (no lie!) core and the compile degenerates
> into signal 11 and 6 compiler errors.  Ok, these usually mean you are running
> out of space, and with cores that big I can understand that one, but the
> few times I don't get a GP, I still get the signal 11's and 6's.  I *know*
> that I still have about 10-15 megs free on the partition where my sources are,
> could it be complaining about the swap space?
> 
Stuff deleted
> 
> Could it merely be a memory problem?  If it's unix or a derivative, most
> problems can be solved by an additional 4 megs (which, by the way, is on the
> way!) and a larger swap space, or is it something with my bloody motherboard?
> The infamous AMD timing problem?  Has that been affecting folks running
> Linux?
>
> nate
> ACS resource manager 
> nmspillers@ualr.edu
> nms@curie.ualr.edu
  I had problems like this for some time which I managed to live with until
one of the .97 patches changed the way memory was used, then internal compiler
errors and machine hangs became endemic. I eventualy traced the problem to
a faulty 1Meg SIMM which occasionaly lost bits and now it has been replaced
the machine has run without a hitch.
  This isn't to say that your problem is bad memory though because I think
a lot of things can bring about a memory fault. It could be for instance
that a swapped page gets corrupted somewhere between the hard disk and main
memory which could be caused by anything on the AT bus or (heaven forbid)
the motherboard. It could also be caused by the kernel or some illbehaved
program (in this case it is unlikely unless the compiler is corrupted).
  Try checking the compiler first since that is easier than swaping hardware.

-- 

John H. Morris                          E-mail: johnHM@vaxc.cc.monash.edu.au
Monash University Computer Centre       Phone:  +61 3  5654763
Wellington Road,                        FAX:    +61 3  5654746
Clayton 3168,
Australia.
From: lebailli@cicb.fr (Olivier Le Baillif)
Newsgroups: comp.os.linux
Subject: Help need for mount, tar and rebuilding kernel 0.96c
Date: 14 Sep 92 15:27:11 GMT
Organization: CICB, Universite' de Rennes I, FR


	Hi !

I installed the whole SLS package linux 0.96c + X11R5 and I've 3 problems:

	- I'm just a froggy so I want my french keyboard working, I've edited the main
Makefile in the kernel subdir in order to specify a french keyboard. But I run Make
everything get out of control. Many many errors like Incompatible pointer type in ... or
Structure xxxx has no member yyyy and so on. I've tried to compile with cc or gcc 2.0 the
result is the same except that the error messages differ. And it seems to me that I that I've
no all the include files or they are at a wrong place....


	- Secondly, when I use mount I get the message you must be a superuser even if i'm
root !!! the most strange thing is that I can mount a floppy using the program menu which is
a built in interface for system administrating and other....

	- And finally, on some archive packed in a tar.Z file form any sources, I use the
command:  zcat xxxxx.tar.Z | tar xvf -  the things begin in a good way and after a number of
files untared I got the message broken pipe xxxx blocks proceeded etc ... And some files are
missing....


	If someone could help I will apreciate that. I'd like very much linux and don't wnat to go
back to DOS.


	many thanks.

You may reply by posting or via e-mail at lebailli@cicb.fr

Lebaillif Olivier
Laboratoire de Radiocommunications
Universite de Rennes I
France.
Newsgroups: comp.os.linux
From: ashtray@yoyo.cc.monash.edu.au (John Newnham)
Subject: Hardware compatibility - list?
Summary: We should discuss a hardware registry.  And can you answer my Q's?
Organization: you have got to be kidding!
Date: Tue, 8 Sep 1992 11:55:17 GMT

Is there a list anywhere of "known compatible" hardware?  The last 800 articles
I read (I do not get to read news very often) treated each piece one by one.
This costs a lot of bandwidth and reader-time.  Perhaps a registry, much like we
have with software/features, would be a good idea...

Failing that, is anyone familiar with the "Grassroots" SCSI controller?  Will
0.98 support it gracefully?  And what displays are now supported?  It seems that
most, but not all, ET4000's will, plus a few others.  I also hear something
about Trident - I assume this means Trident SVGA, not VGA.

Myself and some friends intend to set up a BBS in Melbourne, Australia, and to
use Linux as the OS.  We would like to run SCSI HD and FODD (Floptical drive),
and not have any other drives.  Will Linux be bootable?  We will not have messy-
dog on the system at all.

Also:  what multi-port serial cards are supported by Linux?  What is required
to support one?  How much knowledge would be required to hack the AST-4Port 
driver to suit another card, assuming I had specs for the other card?  We will
start with only a few lines, but we see no reason not to expand to 16 lines once
we have the $$$, so multi-port cards seem to be the way to go.

Assuming all goes well, complete Linux source, root and boot disks will be
available to people from a dialup source in Victoria.  The dominion of Linux
over the world grows.... :-)  Didn't JC say something about the meek inheriting
the earth?

TIA,
Ashtray
this
-- 
When I say a word, it means exactly what I want it to mean, no more and no less
 [Humpty Dumpty to Alice (Lewis Carroll)]
Vogt's commentary on the theory of Morphic Resonance:
  There is no god!  The universe just got into bad habits. (Marcus Voght)
From: nmiller@starbase.trincoll.edu (norman miller)
Newsgroups: comp.os.linux
Subject: OK, how does a fella start?
Date: 11 Sep 92 00:20:00 GMT
Organization: Trinity College, Hartford, CT.

OK, I'll bite.  Would some kind soul tell me:

1. Where to get Linux and how to start it up.

2. The smallest hardware configuration that Linux
can live with.  Specifically:
    
Does it make sense to partition a large hard disk that already has
OS2 and Dos on it, and if so how much space to devote to Linux?

Thanks in advance,

Norman Miller
Newsgroups: comp.os.linux
From: butler@cs.tulane.edu (Larry Butler)
Subject: Backups
Organization: Computer Science Dept., Tulane Univ., New Orleans, LA
Date: Fri, 11 Sep 1992 20:23:37 GMT
Nntp-Posting-Host-[nntpd-10349]: jupiter

How do I make a backup of a file system on to floppies?

Thanks,
Larry
Newsgroups: comp.os.linux
From: rafal@utstat.uucp (Rafal Kustra (summer student))
Subject: internal compiler error - what happened ????????
Organization: University of Toronto, Dept. of Statistics
Date: Fri, 11 Sep 1992 04:48:02 GMT


My system:
Linux 0.97 pl1 plus 1 line putch in buffer.c plus
cole@(.. sorry forgot) patch for microsoft bus mouse.
386-dx25 plus 2 kalok 105.Mb Hdisks.
gcc 2.2.2d installed over 2.2.2


I got gdb -4.6 from prep.ai.mit.edu.
run configure linux; make.
It went up to second file in which point I had to
undefine sys-errlist (or symilar) from errno.h 
(the one for __STDC__). Done it before, seems include
file is wrong.
Make run up to breakpoint.c in gdb dir when I got:
cc: internal compiler error: cpp got fatal signal 11.
And compilation by hand gave same result. I was running X
with couple of xterms. Exit X, reboot, tried again.
Same thing. Tried small program I wrote and compiled
before. Same thing. Restored gcc from backup.
No help. Copied cpp from 2.2.2 to 2.2.2d. Yeah. it worked
until values.c. Then I got :
cc: Internal compiler error. Program cc1 got fatal signal 11
Whaw! Restored all cc,cc1,cpp cc1plus and crt0.a (since
it also begins with c hence c* ;). Tried again. At
signal.c I got:
Internal compiler error. Program cpp got fatal signal 11.
Kicked the bloody mini-tower. Tried again. It worked! ;)
No, of course not.
Seems my gcc got corrupted. But it was OK. I compiled so
many things (including kernel) with no problem (except
xv, but that uses -V 2.2.2 flag.).
Can someone tell me what happened?
Even hello.c gets a boot (signal 11) now.

			Rafal

-- 
/|| 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: stewart@wimsey.bc.ca (Jim Stewart)
Subject: Re: free on ps097pl4 doesn't know about my swap
Organization: Wimsey 
Date: Thu, 10 Sep 1992 10:46:43 GMT

In article <1992Sep9.092025.4018@monu6.cc.monash.edu.au> int177c@aurora.cc.monash.edu.au (Jae Won) writes:
>Hi.
>
>	I have been using 0.97 pl4...wonderful stuff. Anyway, I have installed...or
>copied the binaries of ps for the new patch and it seems to be working pretty
>well. The ps recognizes the swap partition but free doesn't seem to.
>	How can I fix this?

Here is a midnight patch to free that works with at lease one swapfile :-)
.. sorry, it is normal diff, I don't know how to get RCS to do anything
   fancier...

js who_is_NOT_proud_of_this_code_but_needs_to_watch_his_swapspace

------------Cut---------------------------------------------------

9a10,11
> #define MAX_SWAPFILES 8     /* js 1 */
> #define SWP_USED 1
27c29
< unsigned long swap_bm;
---
> unsigned long nr_swapfiles; /* js 1 */
71c73
<     swap_bm = /* get_kword(k_addr("_swap_bitmap"));  */ 0;
---
>     nr_swapfiles = get_kword(k_addr("_nr_swapfiles"));
75c77
< 	swap = (swap_bm != 0);
---
> 	swap = (nr_swapfiles != 0);
81c83
<     if (swap && swap_bm)
---
>     if (swap && nr_swapfiles)
157a160,172
> 
> struct swap_info_struct {	   /* this is stolen ftom the kernel source */
>         unsigned long flags;
>         struct inode * swap_file;
>         unsigned int swap_device;
>         unsigned char * swap_map;
>         char * swap_lockmap;
>         int lowest_bit;
>         int highest_bit;
> }swap_info[MAX_SWAPFILES];
> 
> 
> 
161c176
<     int i;
---
>     int i,f;
164c179
<     printf("swap:   ");
---
>     kmemread(swap_info,k_addr("_swap_info"),sizeof(swap_info));
166,174c181,191
<     if (swap_bm == 0)
< 	printf("No swap device.\n");
<     else {
< 	freepg = 0;
< 	kmemread(bitmap, swap_bm, 4096);
< 	for (i = 0; i < SWAP_BITS; ++i)
< 	    freepg += bit(bitmap, i);
< 
< 	if (swap_total != 0) {
---
>     for (f = 0 ; f < MAX_SWAPFILES ; f++)
>       if (swap_info[f].flags & SWP_USED)
> 	{
> 	  printf("swap:%1d  ",f);
> 
> 	  freepg = 0;
> 	  kmemread(bitmap, (swap_info[f].swap_map), 4096);
> 	  for (i = swap_info[f].lowest_bit; i < swap_info[f].highest_bit ; ++i)
> 	    freepg += (bitmap[i] == 0);
> 	  
> 	  if (swap_total != 0) {
176,178c193,195
< 		swap_total << pg_shift,
< 		swap_total - freepg << pg_shift);
< 	} else
---
> 		   swap_total << pg_shift,
> 		   swap_total - freepg << pg_shift);
> 	  } else
181,183c198,201
< 	printf("%10d\n", freepg << pg_shift);
<     }
< }
---
> 	  printf("%10d\n", freepg << pg_shift);
> 	}
>   }
>