HDTenEightyP/NetNews huggingface dataset:
From: johnsonm@stolaf.edu (Michael K. Johnson)
Subject: Custom setups: RFD
Reply-To: johnsonm@stolaf.edu (Michael K. Johnson)
Organization: The Internet
Date: Sat, 11 Apr 1992 04:48:09 GMT

   May I suggest that instead of describing in long and careful detail how
   to fix the failed patch hunks in swap.c, you simply provide a new patch
   file which doesn't fail?  I suspect it would take up less room than your
   description, and would be simpler for most people to do.

I think that providing a description _is_ worthwhile, not because it
fixes this problem, but because it demonstrates the process of
patching, and especially the process of patching by hand, to people
who are not used to patching.  I know that the first time I ever
patched something, I was flying by night.  I was lucky enough to do
things right, but not everyone is.  So anyone who follows these
instructions can provide diffs, and those who want to understand
patching can follow the instructions to learn the process.

Note that the manual project influences my thinking this way :-)

   As to your point about a configuration process, I agree with you.  Linux

Ross Biro has made available a configuration system.  Unfortunately, I
have not had time to look at it, as all my hacking time (non-existent
these past two weeks :-( ) is being spent on scsi for the DTC.

   is rapidly approaching the point where it could really use a
   /usr/etc/config program ala BSD to build its Makefile.  Although I
   haven't had the time in a while to do any kernel hacking in a while
   (unfortunately, sigh....) I will note that the config program is freely
   available in /packages/bsd-sources/usr.sbin/config on ftp.uu.net.
   Perhaps someone would be willing to take a whack at adapting it for
   Linux?  If not, when I manage to find some time I'll look into it.

							   - Ted

michaelkjohnson
johnsonm@stolaf.edu
Newsgroups: alt.os.linux
From: wet!dhl@netcom.com (Dahai Li)
Subject: Re: kermit5A.tar.Z
Reply-To: wet!dhl@netcom.com (Dahai Li)
Organization: The Internet
Date: Sat, 11 Apr 1992 23:40:44 GMT

Hi Michael,

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?

Dahai
From: moyerg@jove.cs.pdx.edu (gary a moyer)
Newsgroups: alt.os.linux
Subject: problem compiling kernel...
Date: 6 Apr 92 20:11:12 GMT

Has anyone gotten the following error when compiling
the kernel:
(compiling fork.c..)
caught fatal signal 6 (??!!?)

Has anyone else had this happen on the way to a kernel build ?

               Thx.  moyerg@cs.pdx.edu
From: johnsonm@stolaf.edu (Michael K. Johnson)
Newsgroups: alt.os.linux
Subject: bash 1.12
Date: 16 Apr 92 01:27:24 GMT
Article-I.D.: athena.1992Apr16.012724.28540
Reply-To: johnsonm@stolaf.edu (Michael K. Johnson)
Organization: The Internet

bash 1.12 (from Owen's site) is available as
tsx-11.mit.edu:/pub/linux/binaries/usr.bin/bash-1.12.tar.Z

michaelkjohnson
Newsgroups: alt.os.linux
From: thomas dunbar <GSTD@VTVM2.CC.VT.EDU>
Subject: Texinfo
Reply-To: GSTD@VTVM2.CC.VT.EDU
Organization: The Internet
Date: Tue, 14 Apr 1992 19:17:57 GMT


  >>What is Texinfo
========================================================================
Texinfo is a special macro package for TeX. Designed by Richard Stallman
and others, it is specially designed for computer documentation. One
writes a texinfo source file and then 1) run it thru TeX to get the dvi
file to generate a printed manual or 2) generate Info files with
i)makeinfo or ii)inside Emacs with texinfmt.el. The resulting documentation
can then be browsed using Emacs or the Info standalone-both of which give
a hypertext sort of system.
   the emacs-18.58 dir at tsx-11.mit.edu contains lots of info files
(6+ Megs uncompressed) but not the TeXinfo sources.
   the texinfo system is GNU's default. i'd certainly like to see
Linux's documentation in this form also. it does require some TeXpertise,
tho.
From: nalston@cix.compulink.co.uk (Nik Alston)
Newsgroups: alt.os.linux
Subject: Re: problem compiling kernel...
Date: 9 Apr 92 13:31:50 GMT
Reply-To: Nik Alston <nalston@cix.compulink.co.uk>
Organization: Gated to News by demon.co.uk


if u are using gcc1.40, you need to uncomment the line
#GCC_OPT = -fcombine-regs
in the Makefile ...

nik
Newsgroups: alt.os.linux
From: johnsonm@stolaf.edu (Michael K. Johnson)
Subject: mtools (mcopy) problems
Reply-To: johnsonm@stolaf.edu (Michael K. Johnson)
Organization: The Internet
Date: Tue, 7 Apr 1992 20:36:13 GMT

Are you using the mtools.n.tar.Z version?  If not, get it, as it works
and is configurable to whatever environment.

michaelkjohnson
johnsonm@stolaf.edu
Newsgroups: alt.os.linux
From: thomas dunbar <GSTD@VTVM2.CC.VT.EDU>
Subject: Info source files
Reply-To: GSTD@VTVM2.CC.VT.EDU
Organization: The Internet
Date: Mon, 13 Apr 1992 17:05:06 GMT

 at txx-11.mit.edu,
the dir pub/linux/binaries/emacs-18.58 contains over six megs of Info
files for Emacs. topics include BASH, calc(Emacs), emacs lisp, gawk, gcc
and many other topics.
  It is very nice to have this documentation. It would also be nice to
have the TeXinfo source files. would the person who posted the info files
please post the tex sources.
Newsgroups: alt.os.linux
From: jgifford@attmail.com
Subject: more on my problem(I still haven't got any help) :)
Reply-To: jgifford@attmail.com
Organization: The Internet
Date: Wed, 15 Apr 1992 23:20:24 GMT

Ok, here goes:
I had xcomm, it was running fine.  suddenly, it started outputting to the
screen 2 cr/lf for every one I hit on the keyboard.  I went into kermit
to see if it was xcomm, or the place I  am calling.  kermit was doing
this:
C-Kermit>set line /dev/ttys4

C-kermit> set speed 2400

/dev/ttys4, 2400 baud
C-Kermit> set parity none

C-Kermit>connect

(note all the double line-feeds above)
once connected though, kermit does allright.
on the other hand, xcomm does allright offline, but double line on-line
(kermit fine on-line, messed up off-line)
I am writing this using xcomm(difficult to do with double spacing)
note also that the output that the attmail service sees is good.
I think I may have screwed up the termcap or something(?)
If anyone at all can help, please do, this is getting unbearable.
I have rebooted a dozen times, gone to various versions, and nothing changes.
Please Help Me someone!!  
thanks in advance,
jim gifford
jgifford@attmail.com
Newsgroups: alt.os.linux
From: jgifford@attmail.com
Subject: uudecode problems (anyone else?)
Reply-To: jgifford@attmail.com
Organization: The Internet
Date: Sun, 12 Apr 1992 00:42:31 GMT

I am trying to ftp from tsx-11 using ftpmail.  the following is a sample mail:

    reply jgifford@attmail.com
    connect tsx-11.mit.edu
    chdir /pub/linux/images
    binary
    uuencode
    get bootimage-0.95c+.Z
    quit

I have done the above three times.  I cat the files, uudecode them, and uncompress
does it's famous OOM and segmentation fault trick.
on a dos box, i used decomp and the computer churned for 30 minutes(xt)
and finally belched out a 9MB!!! file.  I have tried for bc.tar.Z,
pmake, lpd, shoelace, and others, and they all uncompress, but tar can only
read half of the tar(or less), making about 10 hours work worthless. :(

Has anyone else had this prob?

Does anyone know of a solution?

(if someone can send me uuencoded bootimage-0.95c+ uncompressed already,
I would be very grateful. : jgifford@attmail.com)

What I really need is a way to make the ftpmail procedure work properly.

FYI: 386/33 4MB/100MB
     I used my xt to connect at 19200 to 386, and then kermit to connect thru modem
to attmail.  from attmail i dump the uuencoded file to screen and do a screen cature
on the xt.  I then use pcedit(procomm plus editor) to remove all the headers.
then I u/l the uuencoded file @19200 to the 386, uudecode, uncompress, and then
tar doesn't like most of it.  :(
any suggestions?

Thanks,
Jim Gifford
jgifford@attmail.com
Newsgroups: alt.os.linux
From: Epstein@DOCKMASTER.NCSC.MIL
Subject: Linux makefile
Reply-To: Epstein@DOCKMASTER.NCSC.MIL
Organization: The Internet
Date: Tue, 14 Apr 1992 03:20:52 GMT

With mv math_emulate.c to emulate.c got linux-0.95c+ to compile.

Recommend adding sync line at end of disk:  ala Image:  which already
ends with a sync.

BTW:  CTRL-ALT-DEL using AMI BIOS on 386 no longer works, am I suppose
to use the re-boot program?

I find the speeded-up auto-repeat too fast.  This "feature" should be in
the top level Makefile (I actually haven't looked where its at).
                              John
Xref: sparky alt.os.linux:2488 comp.os.linux:419
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: Wed, 8 Apr 1992 23:01:57 GMT

I made patched source for patchlevel .95c (not including the
patchlevel fix -- If you are really worried about that, you darn well
better be able to fix it yourself ;-) available:

tsx-11.mit.edu:/pub/linux/sources/system/0.95c.source.tar.Z
(gee, I hope I remembered that right)

Also, I have fixed the .95c patches in the patches directory, for
those of you who may have noticed that I unwittingly broke them.
There is also a diffs.Z it you don't want to uudecode them yourself.

I hope that we get a compiled version soon -- I have been unable to,
and will be for another day or more, so if anyone running virgen .95c
would like to upload a copy, I'd be very grateful.  But if you do,
please make sure that it is just .95c (patchlevel fix optional) and
please mail ftp-linux@tsx-11.mit.edu when you do.

michaelkjohnson
johnsonm@stolaf.edu
etc.  no .sig, as usual...
Xref: sparky alt.os.linux:2355 comp.os.linux:254
From: eonu24@castle.ed.ac.uk (I Reid)
Newsgroups: alt.os.linux,comp.os.linux
Subject: Re: Beginner's Guide: Installation (Possible errors?)
Keywords: linux, installation, partitions, correction
Date: 8 Apr 92 14:39:28 GMT
Distribution: alt
Organization: Edinburgh University

I'm not doing well this week with my beginner's guide to installation :-)

caadams@leo.unm.edu (Clifford A Adams) writes:

>pfdisk> 2 6 0 292
>pfdisk> 1 128 293 521
>[**********1: should these lines read:
>           pfdisk> 1 6 0 292
>	   pfdisk> 2 128 293 521
>		    (swap the partition #s)]

Quite correct! I changed things around on my drive because of a still
unresolved problem with bad blocks and I forgot to change some bits of the
guide. For the record, my partition 1 should be a Dos partition (type 6) and
partition 2 should be a Linux partition (type 128).

>pfdisk> a 2
>[**********2: should this read: "pfdisk> a 1" ?]

Yep.

># mkfs -c /dev/hda1 48090
>[**********3 should this line be: "# mkfs -c /dev/hda2 48090" ?]

># mount /dev/hda1 /mnt
>[**********4 should this line be: "# mount /dev/hda2 /mnt" ?]

Again both your changes are correct.

>	Again, thanks for the effort in making installation much easier...
>I'm going to try Linux from floppy today, and will probably HD install
>it as soon as I get positive replies to this message...

I hope all goes well for you and I'm very sorry about the errata I posted. What
can I say, it was late, I was tired, I made a mistake. Sorry. I will repost a
(hopefully) correct guide tonight (and try to upload it to tsx or somewhere).

Iain
Newsgroups: alt.os.linux,gnu.misc.discuss
From: juh@qt.IPA.FhG.de (Juergen Henke)
Subject: Re: HELP!  Trying to build gcc-2.1 on a VIRGIN system...
Organization: /users/juh/.organization
Date: Thu, 9 Apr 1992 15:22:39 GMT

In article <64374@apple.Apple.COM> erc@Apple.COM (Ed Carp) writes:


   OK, this is what I'd like to do. I'd like to build gcc on a SPARC,
   but run it on a 386 running linux 0.95a.


Ok, i think you get a start with the patches available at tesla.ee.cornell.edu,
in pub/386bsd. They managed to cross-compile 386bsd on a sparc, however they had to link
on a (good old) vax, because of bugs in the gnu-ld...

Juergen

PS.: I suppose you're only using news at APPLE ??

--
_________________________________________________________________________
Juergen Henke, e-mail juh@IPA.FhG.de, PSI-mail PSI%4505016002::JUH_IPA
Fraunhofer-Institut f. Produktionstechnik u. Automatisierung
Nobelstrasse 12, D-7000 Stuttgart 80
From: jdough@unf6.unf.edu (Joseph Dougherty)
Newsgroups: alt.os.linux
Subject: Re: Beginner's Guide: Installation
Date: 6 Apr 92 12:31:35 GMT
Distribution: alt
Organization: University of North Florida, Jacksonville

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
>one or two errata but there are one or two new bits. It is being reposted
>because the original is disappearing from many news feeds and I think there is
>still a demand for it.

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

>>>
        For a hard disk the major number (offset 509) is always 3, and the
    minor number (offset 508) is a combination of primary or secondary HD
        drive and partition details (see FAQ for details). Here are the details

    Device      Major    Minor       Device      Major    Minor
    ------      -----    -----       ------      -----    -----
    /dev/hda1     3        1         /dev/hdb1     3        65
    /dev/hda2     3        2         /dev/hdb2     3        66
    /dev/hda3     3        3         /dev/hdb3     3        67
    /dev/hda4     3        4         /dev/hdb4     3        68
    /dev/hda5     3        5         /dev/hdb5     3        69
    /dev/hda6     3        6         /dev/hdb6     3        70
    /dev/hda7     3        7         /dev/hdb7     3        71
    /dev/hda8     3        8         /dev/hdb8     3        72

>>>>

	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.

	See you all around.

Joe Dougherty
jdough@unf6.cis.unf.edu
From: gt0449a@prism.gatech.edu (Rob Coleman)
Newsgroups: alt.os.linux
Subject: Problem with tar (?)
Date: 7 Apr 92 02:16:47 GMT
Reply-To: gt0449a@prism.gatech.edu (Rob Coleman)
Organization: The Internet


I am apparently one of the small number of people who are having trouble
with using tar (any version that I can find) to extract certain files
from their archives uncorrupted.  The latest incarnation of this problem
was with the beta version of GCC v2.1, where after extracting all the
files and trying to compile a "hello world" program, I get the "parse
error before '('" in stdio.h.  When I try to untar the same set of files
with different versions of tar under different versions of the kernel
(.12, stock .95a), I still cannot get working versions of the programs.
Oddly enough, a friend of mine has a similar Linux system set up and
is able to take the same tar files that I tried to extract, and yet can
get working copies of the programs using the distribution version of tar.
I was able to "get around" the problem before by booting .12, untarring
the files, and then booting off the hard drive again, but there does not
seem to be any way that I can get GCC v2.1 untarred correctly.  Any
help would be appreciated!

Oh, my system consists of a 486/33, Linux v.95c (.95a with Linus' patches
and the lp patches), two IDE drives (125meg and 105meg), and I boot
off of floppy disk.

Thanks!
From: dam1@ra.msstate.edu (Daniel A. Martin)
Subject: Re: got root95c+, now need device driver for lp0...
Keywords: lp, lpd, lpr, lp0
Organization: Mississippi State University
Date: Sun, 12 Apr 1992 05:46:13 GMT


To make the lp devices use the following commands:

mknod /dev/lp0 c 6 0
mknod /dev/lp1 c 6 1
mknod /dev/lp2 c 6 2

to send a file to the printer do cat filename > /dev/lp0 (or 1 or 2
depending on what device exists in your system...)
-- 
Danny Martin : dam1@Ra.MsState.Edu
Newsgroups: alt.os.linux
From: jgifford@attmail.com
Subject: extra line update
Reply-To: jgifford@attmail.com
Organization: The Internet
Date: Wed, 15 Apr 1992 18:23:04 GMT

I have tried pcplus, kermit-MS,kermit-C, windows term(3.0&3.1),and even (blech)
pcomm, and none have the extra line feed problem, only xcomm, and it didn't
start until after a download early this morning(around 2:00am) I don't know 
why, and I can't find a reference in the init file or the docs.  I tried
set cr on;set cr off;set nl on;set nl off;anything else that looked even
remotely possible.  

on to another note, about these cross-posts, the long ones are really annoying
(try 5 pages twice)anyway, an idea:
   You have software translating from the groups to the list, why not a script
   to take messages from one group and send it to the other group(this is for
   those that can get one or the other, but not both) and then tell people
   not to crosspost, that everyone will see it anyway.
      whatta ya think, Ted?, can it be done, and is it worth it?

Jim Gifford
jgifford@attmai.com
 ...!uunet!attmail.com!jgifford
From: wolff@neuron.et.tudelft.nl (Rogier Wolff)
Newsgroups: alt.os.linux
Subject: Re: Partitioning Warning!
Date: 12 Apr 92 15:17:34 GMT
Organization: Delft University of Technology, Dept. of Electrical Engineering

visnucc@ubvmsd.cc.buffalo.edu (Niagara U. Courtesy Account) writes:

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


YEP happened to me too! DR DOS 6.0 recognizes MINIX and Linux partitions
as if they are DOS 2.0 partitions, and will friendly as ever write format
recover files to them, thereby destroying them.

This is clearly DR DOS's fault. I won't use it anymore. (too bad for the
extra 30M i'd get on my 30M partition, haven't bought/found Stacker yet...)


						Roger
-- 
If the opposite of "pro" is "con", what is the opposite of "progress"? 
	(stolen from  kadokev@iitvax ==? technews@iitmax.iit.edu)
EMail:  wolff@duteca.et.tudelft.nl   ** Tel  +31-15-783644 or +31-15-142371
Xref: sparky alt.os.linux:2295 comp.os.linux:196
From: hlu@luke.eecs.wsu.edu (Hongjiu Lu -- Graduate Student)
Newsgroups: alt.os.linux,comp.os.linux
Subject: diff of FAQ for gcc 2.1 (beta)
Date: 6 Apr 92 20:16:31 GMT
Article-I.D.: serval.1992Apr6.201631.4875
Organization: Washington State University
Originator: hlu@luke.eecs.wsu.edu

Hi,

Here is the diff of FAQ for gcc 2.1 (beta). Please use this one.

H.J.
----------------
*** FAQ.old	Sun Apr  5 21:48:02 1992
--- FAQ		Mon Apr  6 11:59:59 1992
***************
*** 169,179 ****
  utilities get an error from kernel saying something about binary file
  format?
  
! ANSWER: Linux has changed a.out.h. The new a.out.h is compatible with
! the applications compiled with the old a.out.h. But if an application is
! compiled with the new a.out.h, you have to use the new a.out.h. If you
! get this error message, you should get the new a.out.h and old ld from
! where you get this and use them to recompile the kernel.
  
  QUESTION: Why does g++ complain?
  
--- 169,180 ----
  utilities get an error from kernel saying something about binary file
  format?
  
! ANSWER: Linux has changed a.out.h. The new a.out.h in Linus' second
! patch is compatible with the applications compiled with the old
! a.out.h. But if an application is compiled with the new ld which uses
! the new a.out.h, you have to use the kernel compiled with the new
! a.out.h. You have to recompile the kernel with Linus' second patch
! applied and old ld. And then use new ld to compile the programs.
  
  QUESTION: Why does g++ complain?
From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Newsgroups: alt.os.linux
Subject: Re: Patching Bootimage disks
Date: 14 Apr 92 13:41:20 GMT
Followup-To: LeBlanc@mcc.ac.uk
Organization: Computing Centre, University of Manchester

In article <kirsch.3@eaeps1.tuwien.ac.at> kirsch@eaeps1.tuwien.ac.at (Rainer Kirsch) writes:
>I got pmk32.zip from wuarchive.wustl.edu in order to patch my boot-disk to 
>tell about an alternative root device. (Wanting to change bytes no. 508 and 
>509).
>But: It did not work. I checked the behaviour of pmk with the new formatted 
>disk - all ok. It seems, that the data of the boot information is too 
>different from that of an ordinary MS/DOS disk. So a "General disk error" is 
>reported.
>Can anyone tell me an alternative mechanism for patching boot-disks?

The best tool I have seen is the rdev program, from Werner Almesberger
of ETH.  With no arguments it prints out the first line for /etc/mtab,
with one argument (a boot image) it prints the device configured as
the root device, and with two arguments (boot image, device), it sets
the device as the default root in the specified image.

Source is available by anonymous ftp from several sites, and I think
the program is on the latest root disks instead of rootdev.
It is on the utilities disk of my 'interim' version.

     -- Owen
     LeBlanc@mcc.ac.uk
Newsgroups: alt.os.linux
From: johnsonm@stolaf.edu (Michael K. Johnson)
Subject: IMPORTANT: gcc 2.1, libc.a 2.1a and Linux
Reply-To: johnsonm@stolaf.edu (Michael K. Johnson)
Organization: The Internet
Date: Tue, 7 Apr 1992 20:46:18 GMT

From: hlu@luke.eecs.wsu.edu (Hongjiu Lu -- Graduate Student)

   >From Linus's second patch, we are moving to VFS. As a result, there
   will be some changes in libc.a. That means next release of gcc 2.x and
   libs will not run under the kernel below Linus's second patch to 0.95a.
   I strongly recommend you move to 0.95a with Linus's second patch if you
   haven't done so.

If this is so, then we should make available a new bootimage and
patched source at the major ftp sites, I think.  Requiring a new
kernel for the compiler should mean easy access to a runnable
system...

michaelkjohnson
johnsonm@stolaf.edu


Xref: sparky alt.os.linux:2347 comp.os.linux:247
From: rob@wzv.win.tue.nl (Rob J. Nauta)
Newsgroups: alt.os.linux,comp.os.linux
Subject: alt.os.linux ?
Summary: rmgroup it ?
Keywords: obsolete rmgroup kill-it
Date: 6 Apr 92 09:22:39 GMT
Followup-To: alt.os.linux
Organization: Sex, UNIX & Rock 'n Roll

Hi

I notice that most messages are now posted to both alt.os.linux, and
comp.os.linux. Generally comp groups get better distribution, so maybe
it's time to rmgroup it ? Any comments ?

Rob
-- 
+-----------------------+
| Rob J. Nauta          |       "In the end, all time spent is wasted time."
| rob@wzv.win.tue.nl    |
| Phone: +31-40-833777  |
Xref: sparky alt.os.linux:2430 comp.os.linux:352