HDTenEightyP/NetNews huggingface dataset:
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Newsgroups: comp.unix.bsd
Subject: Re: want to dial in
Date: 17 Aug 92 10:19:19 GMT
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen


>>I want to use my 386BSD now for dialing in. 
>>I tried the D2400 getty type and when I switched off-on my modem I saw the
>>send/receive leds on the modem flash in conjunction with a console
>>message saying that there was some overflow problem at com1 (silo or
>>something like that). It looked like there was a feedback storm at the
>>input port.

>If you used your modem for DOS, you'll have to change the default settings.
>(This isn't a 386BSD problem, but a generic UNIX issue).  You need to turn
>off anything that echoes result codes or status back from the modem to 
>the computer, or you'll have a getty war.
>-- 
>bill@unixland.natick.ma.us                      ESIX Mailing List Moderator
>Public Access UNIX/USENET/E-MAIL!  UUCP Accounts Available!  (508) 655-3848
>5 lines  -  Located in Natick, MA   USA    Supporting V.32/PEP/V.42bis, etc.
 
I was looking for a standard way to do it (switching my modem to no command echo
etc.). Do you think editing /etc/gettytab and inserting something like

D2400|d2400
   :im=ATE0\r:

would be appropriate? Or is this done elsewhere? I remember that in an earlier
release of SCO (ODT 1.0) I had uugetty for this purpose. 

What is the correct (standard / nohack ) method to set up the modem to avoid
this "getty war" problem?

--Chris
-----------------------------------------------------------------
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.
Newsgroups: comp.unix.bsd
From: randy@chinet.chi.il.us (Randy Suess)
Subject: Problems with append using NFS
Organization: Chinet - Public Access UNIX
Date: Wed, 19 Aug 1992 21:58:01 GMT


	Seem to have a problem with NFS on my 386BSD system.  I am
	mounting a BSD partition on my Dell UNIX system using:
	mount -F nfs -orsize=1024,wsize=1024,hard chibsd:/local /mnt
	If I append to a file on the mounted partition, it overwrites
	the file instead of appending to the bottom.  Easiest way to
	do this is to 
	date >> foo
	date >> foo
	Only one line shows up.  This has completely screwed my rkive
	program as it does a lot of appending to the index files.
	It does not happen if I mount the Dell system to BSD or
	if I mount a Dell partition via NFS from the Dell box.

	Any ideas?
-- 
	I am created Shiva the Destroyer; Death, the shatterer of worlds!
	Who is this dog meat who stands before me now?
	That's the biz, sweetheart.
Randy Suess					 randy@chinet.chi.il.us
From: phr@soda.berkeley.edu (Paul Rubin)
Newsgroups: comp.unix.bsd
Subject: Re: selling 386BSD (was Re: 386BSD on CD-ROM?)
Date: 15 Aug 92 10:42:45
Organization: CSUA/UCB
	<1992Aug12.100430.3467@Urmel.Informatik.RWTH-Aachen.DE>
	<1557@hcshh.hcs.de> <1848@adagio.UUCP>
NNTP-Posting-Host: soda.berkeley.edu
In-reply-to: grog@adagio.UUCP's message of 15 Aug 92 07:20:44 GMT

    Don't misunderstand me. If you want 386bsd from me, you can call us up
    and get it via uucp for nothing. But it costs more money than you
    think to maintain archives and supply ``free'' software (yes, we
    really do put that in parentheses in our literature). The FSF charges
    $200 for their tapes, by the way.

The $200 goes the FSF charges for a tape mostly goes to pay the FSF's
programmers, documentation writers, and administrative staff; it
covers much more than the costs of making and sending out the tape.
Buying tapes is one way companies, etc. are able to help out the GNU
project.  Making and shipping a tape is not much more expensive than
making and shipping an Emacs manual (well, maybe two manuals) and the
FSF charges around $20 for those.  Manuals too do much more than cover
the manufacturing and shipping costs---the FSF's distribution arm
exists solely to generate funds for further GNU development and
maintenance.

  Paul Rubin
  former FSF staff programmer
   and still sometime GNU hacker
Newsgroups: comp.unix.bsd
From: wrn@opal.cs.tu-berlin.de (Chris Werner)
Subject: 386bsd /dev/lp ?
Keywords: 386bsd
Organization: Techn. University of Berlin, Germany
Distribution: fb20
Date: Sat, 15 Aug 1992 13:53:45 GMT

Hi,

who can help me to configure 386BSD ? I can't find GENERIC files.
/usr/sbin/config search in crazy directories for the file with name <SYSTEM-NAME>

Thanks for help

			Chris (Werner).
From: dmp3592@galileo.rtn.ca.boeing.com (Dean M. Phillips)
Newsgroups: comp.unix.bsd
Subject: Re: Endless boot cycle- suggestions?
Summary: Watch out for geometry translation
Date: 19 Aug 92 16:28:05 GMT
Organization: Boeing Commercial Airplane Group, Seattle

A disk drive which does geometry translation will hopelessly confuse
386BSD.

Background:

MessDOS has a hard limit of 10 bits for a cylinder number.  This
prevents MessDOS from accessing cylinders beyond 1023.  Most large hard
disks have more than 1024 cylinders.

So, to make these disks useable with MessDOS, the disk drive
manufacturers invented geometry translation.  The way this works is the
drive says that it has more heads than it really does, and less
cylinders than it really does, so that the total number of sectors
comes out the same but with less than 1024 cylinders.  When MessDOS
asks for a particular track, sector, and cylinder, the drive silently
translates this to the real location.  "Brain damage begets brain
damage."

386BSD gets the geometry and its partition info from the partition
table and then TURNS OFF GEOMETRY TRANSLATION.  If geometry translation
was on in the first place, 386BSD will get hopelessly lost, fail to
find its disk label and panic.

Solution:

Make sure that geometry translation is turned off.  I was able to do
this by running setup, specifying drive type 47 and keying in the real
number of heads, etc.

If you don't know what your disk's real geometry is, you can find out
with a little hacking.  I will post a patch when I get mwrite to work.

Disclaimer:

Not all reboot cycles are caused by geometry translation.

On my system, it would still work with geometry translation if I let
386BSD have the whole disk.  This is because the disk label is located
on cylinder 0, head 0, sector 2 for both the real and the translated
geometry.
-- 
----------------------------------------------------------------------
#include <standard_disclaimer.h>
Dean M. Phillips                                        (206) 393-9333
Boeing Commercial Airplane Group            dmp3592@galileo.boeing.com
From: guy@Auspex.COM (Guy Harris)
Newsgroups: comp.unix.bsd
Subject: Re: WD Ethernet Card not found on warmboot
Date: 22 Aug 92 06:15:27 GMT
Organization: Auspex Systems, Santa Clara

>Every solution I've gotten so far is to "recompile the kernel."  I
>really wonder why Unix *still* doesn't have installable device drivers.

Some versions of UNIX *do* have them.  Others don't; BSD is one that, at
present, doesn't.  (Some OSes that are, in part, derived from BSD do.)

>Is there a fundamental reason why Unix hasn't/will not support this?

Given that some versions of UNIX *do* support it, the answer is
obviously, "no, there's no such fundamental reason".
From: tj2n+@andrew.cmu.edu (Tao Jiang)
Newsgroups: comp.unix.bsd
Subject: Re: How could I add 2nd Hardisk in 386BSD 0.1 ?
Date: 14 Aug 92 19:52:32 GMT
Article-I.D.: andrew.4eX7y0i00WB853NEU=
Organization: Doctoral student, Statistics, Carnegie Mellon, Pittsburgh, PA

Please send me too!

Thanks!

TJ
Newsgroups: comp.unix.bsd
From: yergeau@leland.Stanford.EDU (Dan Yergeau)
Subject: Re: 386bsd/srcdist corrupt?
Organization: DSG, Stanford University, CA 94305, USA
Date: Wed, 12 Aug 92 19:42:41 GMT


In article <veit.713610524@du9ds3>, veit@du9ds3.uni-duisburg.de (Holger Veit) writes:
|> In <1992Aug12.023903.1433@msuinfo.cl.msu.edu> ignasiak@convex.cl.msu.edu (Todd Ignasiak) writes:
|> 
|> >I think the problem is the first line of the tar file, it seems to be
|> >garbled.  After that it looks normal.

[stuff deleted]

|> RTFM. These are cpio archives, to be extracted with "extract" or with
|> cat src* | uncompress | cpio -ivd
|> The information about this can be found in INSTALL.NOTES. But, of course,
|> real programmers don't read doc-files.

Real programmers can recognize the differences between cpio
archive headers and tar headers.  Real programmers can figure
out either header structure and write a perl script to do
the extraction without using tar or cpio. :^)

-- 
Dan Yergeau                         He's dead Jim.  Take his phaser
yergeau@gloworm.Stanford.EDU        and I'll get his wallet.
From: tmh@doppel.first.gmd.de (Thomas Hoberg)
Newsgroups: comp.unix.bsd
Subject: Re: SCSI driver bug when accessing DOS partition
Date: 19 Aug 92 23:32:32 GMT
Organization: GMD-FIRST, Berlin
In-reply-to: tgt@neon.ecn.purdue.edu's message of 19 Aug 92 02:05:35 GMT

In article <1992Aug19.020535.2080@noose.ecn.purdue.edu> tgt@neon.ecn.purdue.edu (Conan the Librarian) writes:

   I ran across the following Adaptec driver bug when attempting to configure
   mtools to read an 80 Mb DOS partition d:, which is on a SCSI disk.  The
   problem: the SCSI driver routine asstart (in the file /sys/i386/isa/as.c)
   fails with the message "out of range, cannot happen?" (due to
   nscatter==NSCATTER, which means nothing to me!!).  This subsequently
   causes the disk_read() routine of mtools (in the file buf_read()) to fail,
   printing the message "disk_read: read: Device not configured"

This is not a bug but simply a limitation of the current SCSI driver.
The Adaptec allows you to bundle a couple of reads together in a
scatter list. The hardware maximum size for this list is 16/17 entries
per mailbox. Since the Intel CPUs have a 4k page size at most 16 pages
of 4k can be read with a single command (64k). At a 2k cluster size
DOS allocates twice as many sectors for the FAT as there are megabytes
in the partition. With partition sizes greater 64MB the fat_read()
routines requests a read of more than 64k which then failes with that
warning. There are several workarounds:
1) use the block device (slow, but the easiest)
2) hack mtools to do it's own buffering (some work)
3) use a bigger cluster size for your DOS partition (more wasted disk
space)

Of course the best thing would be to enhance the Adaptec driver to
support command chaining (even more work). There is a new Adaptec
driver by Julian Fletcher (sp?) under evaluation, maybe that will fix
the problem.

---
Thomas M. Hoberg   | Internet: tmh@first.gmd.de
1000 Berlin 41     |           tmh@cs.tu-berlin.de
Wielandstr. 4      |
Germany            | BITNET:   tmh@tub.bitnet 
+49-30-851-50-21   |

Newsgroups: comp.unix.bsd
From: volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt )
Subject: 680x0 version of 386BSD?? [Was: Re: Mac version of 386BSD??]
Organization: Applied Math, University of Bonn, Germany
Date: Tue, 18 Aug 1992 10:57:23 GMT

In article <1992Aug17.215858.14408@news.iastate.edu> niko@iastate.edu (Nikolaus E Schuessler) writes:
>In article <1992Aug17.213706.10326@elroy.jpl.nasa.gov> minh@inst-sun1.jpl.nasa.gov (Minh Lang) writes:
>>Is there any Mac version of 386bsd
>I was seriously thinking of porting it... I however have a 40M hard drive

I would like to generalize the question:  Is anyone out there seriously
thinking about porting 386BSD to a Motorola platform?

I have followed the Maach for Mac development but it seems that you still need
a BSD source license which our CC will never get.  It seems that the GNU Hurd
is still years away, so 386BSD looks like the only unencumbered choice for a
really free Unix-like OS.

-- Volker


-- 
----------------------------------------------------------------------------
Bitnet:   UNM409@DBNRHRZ1                              Volker A. Brandt
UUCP:     ...!unido!DBNRHRZ1.bitnet!unm409             Angewandte Mathematik
Internet: volker@sfb256.iam.uni-bonn.de                (Bonn, Germany)
Newsgroups: comp.unix.bsd
From: peter@taronga.com (Peter da Silva)
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Organization: Taronga Park BBS
Date: Sun, 16 Aug 1992 02:04:55 GMT

In article <PHR.92Aug15151100@soda.berkeley.edu> phr@soda.berkeley.edu (Paul Rubin) writes:
>Try to think a little more clearly.  It is the ABSENCE of copyleft
>that leads to the possibility of non-freely-redistributable versions.
>The copyleft was designed to prevent that from happening.  If 386bsd
>was copylefted, these flames wouldn't be happening.

If 386BSD was copylefted, it would be Linux. It's the absence of copyleft
that leads to the possibility of more than a bunch of random hackers
benefiting from it.


-- 
                                                                `-_-'
                         Have you hugged your wolf today?        'U`

Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032
Newsgroups: comp.unix.bsd
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Subject: Re: X386 for 386BSD
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Wed, 19 Aug 1992 15:17:16 GMT

ac999a15@umbc5.umbc.edu (ac999a15) writes:

>  I have a Diamond stealth graphics card which I don't believe is supported
>for X386 yet.  Could someone tell me if it would be possible to configure
>X386 to run in standard VGA mode, and if it is how?
Me too. I will get an EISA-S3 VGA board next week. I hope there is no
no difference in the Video RAM access for EISA and ISA, except the speed :-)

Thanks in advance,

Norbert.
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.hardware
From: rommel@Informatik.TU-Muenchen.DE (Kai-Uwe Rommel)
Subject: Re: Another Adaptec Question
Organization: Technische Universitaet Muenchen, Germany
Date: Mon, 17 Aug 1992 17:38:07 GMT
Distribution: world,fj,spec

In article <15776@star.cs.vu.nl> kjb@cs.vu.nl (Kees J. Bot) writes:
>rommel@Informatik.TU-Muenchen.DE (Kai-Uwe Rommel) writes:
>>
>>In article <7@tama.spec.co.jp> amurai@tama.spec.co.jp (Atsushi Murai) writes:
>>>ariticle is not ..but) and Fujitsu M2266SA 1.2 GB Disks. Functionality
>>>is good but it looks like loosing a space about 200MB (above 1Gbyte).
>>>And some guy let me know about this is a known problem of 1542B and
>>>Adaptec will be fixed by new board - 1542C. (Oh well.....)
>>>Now a day, A lot of guys try to run 386BSD with this card without know
>>>this problem!!!
>It has nothing to do with heads, sectors or cylinders.  The group 0 SCSI
>read/write commands allow only for a 21 bit block address limiting one
>to 2 megablocks, which is 1GB at the usual 512 bytes per block.

We don't talk about smart OSes like 386BSD :-) but the original poster
asked why he doesn't see all the space under DOS/Novell. There it has to
do quite a lot with heads/tracks/sectors ...

>The group 1 SCSI read/write commands offer a 32 bit block address
>however, but not all O.S.'s are smart enough to use those commands.
>
>>Adaptec has now a new mapping scheme with 256 heads and 64 sectors per
>>track, [etc...]
>
>At least the 64 sectors per track number is wrong, you can't have more
>than 63 sectors on a track.  I don't like the 256 heads per track
>either, I know of one (1.5GB) disk with an AT interface that uses the
>top 2 head bits for two more cylinder bits.  This limits the number of
>heads per track to 64, but allows for 4096 cylinders.  I don't know if
>this is a normal way of addressing bigger disks under DOS.  Anyone?

Sorry, for those off-by-one errors, here is the original text from the
Adaptec README file:

--quote--
To eliminate the 1 Gigabyte limit, Adaptec's new extended
translation feature uses 255 heads and 63 sectors,
extending the disk drive capacity limit under
DOS to 8 Gigabytes.
--end-quote--

>I do not use the Adaptec BIOS by the way, there is a nice SCSI command
>to ask the drive how big it is and that is all the info you need with
>SCSI.  You can't even see more than two disks with the BIOS.

We may guess how DOS and Novell determine the disk geometry/size ..

Kai Uwe Rommel

/* Kai Uwe Rommel --- rommel@informatik.tu-muenchen.de */

DOS ... is still a real mode only non-reentrant interrupt
handler, and always will be.                -Russell Williams

Newsgroups: comp.unix.bsd
From: raeburn@cambridge.cygnus.com (Ken Raeburn)
Subject: 386bsd install program :-)
Organization: Cygnus Support, Cambridge MA
Date: Wed, 19 Aug 1992 04:58:41 GMT

I was having some problems with the "install" script, when trying to
re-install my disk, and decided to go through it by hand.  I looked
through the install binary so I could copy some of the commands (it
runs at least some as subprocesses), and found these:

    No disk drive to install 386BSD on.
    Would you care to have it installed on your TV instead? (y/n)
    Sorry, installation on TV sets not allowed per CCIR, "Green Book"
    15th Plenary Assembly, Geneva 1982 Vol. 9, Part I,
    International Telecommunications Union.

Um... has anyone ever actually gotten these messages? :-)

Ken
Newsgroups: comp.unix.bsd
From: hsu@pix.com (Dagwood Splits the Atom)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: Pix -- The company with no adult supervision.
Date: Tue, 18 Aug 1992 16:11:24 GMT

In article <16r3icINNhi3@wendy-fate.UU.NET> kyle@wendy-fate.UU.NET (Kyle Jones) writes:
>jfw@ksr.com (John F. Woods) writes:
> > The problem is that the law basically *requires* that the copyright get in your
> > face.
>
>Yeah, but does all the verbiage have to be up front?

No, it doesn't.  For the purpose of copyright notice, placement at the end
of the file is sufficient.  Quoting from an old circular (R61, Copyright
Registration for Computer Programs) I dug out of my files...

   LOCATION OF COPYRIGHT NOTICE
   Section 201,20(g), 37 C.F.R.

   (g) WORKS REPRODUCED IN MACHINE-READABLE COPIES

     For works reproduced in machine-readable copies (such as magnetic
   tapes or disks, punched cards, or the like), from which the work cannot
   ordinarily be visually perceived except with the aid of a machine or
   device,(footnote 1) each of the following constitute examples of
   acceptable methods of affixation and position of notice:

     (1) A notice embodied in the copies in machine-readable form in such
   a manner that on visually perceptible printouts it appears either with
   or near the title, or at the end of the work;
                      ^^^^^^^^^^^^^^^^^^^^^^^^^
   ...

Footnote 1 is an explanation that works requiring only optical enlargement
(such as microfiche) and works published in visually perceptible form but
used in connection with optical scanning devices are not included in this
category.

Disclaimer: I'm not a lawyer.  Reading this stuff is just a hobby.  Don't
ask me any detailed questions about intellectual property law.

-dave

-- 
Dave Hsu                           <hsu@pix.com> -or- <hsu@eng.umd.edu>
Caffeine and Salsa Czar	          "Yeah?  Well there are a lot of people out
Pix Technologies Corporation       there who are full of shit and making money.
Have nerds, will telnet.           And *I'm* not going to be the exception."
From: cflatter@nrao.edu (Chris Flatters)
Newsgroups: comp.unix.bsd
Subject: Re: Naive "imake" questions
Date: 16 Aug 92 21:33:04 GMT
Reply-To: cflatter@nrao.edu
Organization: NRAO

In article 11490@NeoSoft.com, karl@NeoSoft.com (Karl Lehenbauer) writes:
>OK, lots of X programs come with Imakefiles and need imake to generate
>a customized Makefile for the local machine.
>
>Firing up imake as distributed in X386 for 386BSD, it complains about
>not being about to find "Imake.tmpl".  I found that setting the env
>var IMAKEINCLUDE to "-I/usr/lib/X11/config" would get it to create
>makefiles OK, but not with quite the correct information to build
>the target, like library paths are wrong.
>
>Is there another place this is supposed to point to, to get to the right
>stuff?  If not, is there a copy or link that needs to be done?  Otherwise,
>what is the accepted way to set this up?

You need to run imake as follows

imake -DUseInstalled -I/usr/lib/X11/config

Most X11 installations have a script called xmkmf that invokes imake with
the correct flags.  I don't know if this is present in X386 for 386BSD.

There is also the possibility that you need to edit /usr/lib/X11/config/site.def
to reflect your particular installation but this is very unlikely if you followed
a standard installation procedure.

	Chris Flatters
	cflatter@nrao.edu
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: [386BSD] Help, X386 is a Zombie!
Date: Mon, 17 Aug 92 05:40:21 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

In article <david.714015192@mlb.geomechanics.csiro.au> david@mlb.geomechanics.csiro.au (David Le Blanc) writes:
>
>When I type xinit, I get a starting banner, then nothing. 
>
>So I rlogin as root from another machine, do a PS, and
>what do I see but
>
>	816 p0  Z  X386
>		^ Zombie!
>
>Why is this happening? Any Ideas.
>
>--
>David Le Blanc                         :
>Email: david@mlb.geomechanics.csiro.au : `Sort of a cross between a Jaguar
>CSIRO Division of Geomechanics,	       :  and a freight train.' the Alien
>P.O. Box 54 Mt Waverley 3149	       : in Alien^3.

There is a new version of X386 coming up soon with many bug fixes.
If you are very annoyed about the problem I can send you a copy of
my server.

Cheers,
amancio
From: gsh7w@fermi.clas.Virginia.EDU (Greg Hennessy)
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on 'free' UNIX / 386BSD (R
Date: 18 Aug 92 02:45:24 GMT
Organization: University of Virginia

In article <1992Aug18.015903.8526@fcom.cc.utah.edu> terry@cs.weber.edu
(A Wizard of Earth C) writes: 
#Because Hurd is an OS, does this mean that *any* application that runs on it
#is a derivitive work and falls under GNU Public License?

No.

--
-Greg Hennessy, University of Virginia
 USPS Mail:     Astronomy Department, Charlottesville, VA 22903-2475 USA
 Internet:      gsh7w@virginia.edu  
 UUCP:		...!uunet!virginia!gsh7w
Newsgroups: comp.unix.bsd
From: corey@cbnewsm.cb.att.com (william.c.brown)
Subject: Re: Major Problems with 386bsd0.1  please read
Organization: AT&T
Distribution: usa
Date: Thu, 13 Aug 1992 02:14:39 GMT
Summary: test, test

In article <9208100044.AA09303@cs.utexas.edu>, STDN%MARIST@VM.MARIST.EDU (Dan Newcombe) writes:
> Well, here are the problems that I am having:
> 
> 4) cc:  I compiled the following C program using cc -o test test.c
> 
> /* */
> #include <stdio.h>
> 
> main()
> { printf("\nHello Universe!\n"); };
> 
> and I get nothing.  The only thing I can think of here is that it
> is finding another test, so I shall try absolute path names but if
> anyone else has had this problem, would love to here it.
> 

HMMMM!!!!! test. Boy that sure sounds like a SHELL BUILT-IN to me.....




-- 


/* -----							*/
/* Corey Brown  (WB0RXQ): 20m, 15m, 2m(146.82) 70cm(443.63)     */
From: wiljo@kiel.uucp (Wiljo Heinen)
Newsgroups: comp.unix.bsd
Subject: Re: UUCP woes with 386BSD
Date: 17 Aug 92 21:58:10 GMT
Organization: OPeN - The Digital Advantage

bill@unixland.natick.ma.us (Bill Heiser) writes:

>Anyone have outbound mail working on 386BSD in a UUCP environment?

well yes, but then --- I'm using smail3.1 as MTA.

that doesn't count, does it ???

cheers
	Wiljo
-- 
wiljo@kiel.uucp            voice:+49 431 95311              fax: +49 431 978126
               "Alle woll'n was von mir haben / keiner will was von mir wissen"
                                       Die Lassie Singers --- "P.A.R.A.N.O.I.D"