HDTenEightyP/NetNews huggingface dataset:
From: vikki@e40-008-10.MIT.EDU (Vikki King)
Newsgroups: comp.unix.bsd
Subject: AIR or Dell motherboards & 386BSD?
Date: 12 Jan 93 02:29:31 GMT
Organization: Massachvsetts Institvte of Technology
X-Newsreader: Tin 1.1 PL4

Has anyone been running 386BSD on AIR or Dell motherboards?  We are buying
~30 PC's and I want to make sure that we get something that will work with
386BSD.  While I'm at it, does anyone want to recommend an ethernet board
(10BT) that they'd buy for the same thing at this point?  Right now I've been
using a few 3C503's that I was lucky enough to have around, but mostly we have
a whole lot of Racal Interlan NI6510-10BT cards installed now, but I haven't
heard a peep out of anyone about a driver for 386BSD for them being worked on.
written.  That's not a complaint, BTW.  IMHO, 386BSD and the software that's
available for it right now are nothing short of incredible :-)) :-))!

-John
jackson@a1.mec.mass.edu or vikki@athena.mit.edu
Newsgroups: comp.unix.bsd
From: rstevens@noao.edu (W. Richard Stevens)
Subject: bad sector appeared on IDE drive
Organization: National Optical Astronomy Observatories, Tucson, AZ, USA
Date: Tue, 5 Jan 1993 12:48:45 GMT

I'm running BSD/386 and a bad sector has appeared on my IDE drive.
I thought IDE drives were supposed to look "perfect" to the software.  
How does one handle this?

	Rich Stevens  (rstevens@noao.edu)
Newsgroups: comp.unix.bsd
From: bad@flatlin.ka.sub.org (Christoph Badura)
Subject: Re: 386BSD - Network services w/ 2 ethernet boards
Organization: Guru Systems/Funware Department
Date: Mon, 4 Jan 1993 11:10:52 GMT

In <C08r81.3qJ@moxie.hou.tx.us> hackney@moxie.hou.tx.us (Greg Hackney) writes:
>Is there a way to activate some inetd network services for one board,
>but not for the other?

Not with the standard inetd. Sockets aren't bound to network
interfaces and you can't tell over which interface a particular packet
arrived.

You could try hacking inetd and other listeners to check the source IP
addresses of incoming data and respond only to certain "known good"
addresses.
-- 
				Christoph Badura  ---  bad@flatlin.ka.sub.org

AIX is a better... is a better...  is a better... OpenSystem.
					IBM Rep at GUUG Symposium '92
From: peter@ferranti.com (peter da silva)
Subject: Re: codrv problems..
Keywords: 386BSD, codrv
Organization: Xenix Support, FICC
Date: Mon, 11 Jan 1993 20:24:11 GMT

Is there a reliable console driver? I've twice crashed or hung 386BSD by
leaning on the keyboard, and I've got all 58 patches installed, except the
WD networking card one.

I'm running PCcons, though I'd rather use one that presented an 8859.1
character set.

Another problem I'm having is that if I don't have anything plugged
into my serial port when I come up, it sees it in the probe but later
attempts to open it get ENXIO. If there was a device there on boot it
works.

Finally, an update to the BSD FAQ:

	"compat" library:

	The fix to allow building programs without -lcompat suggests
	putting #defines for sgtty in termios.h. Actually, the right
	place is sgtty.h. :->
-- 
Peter da Silva                                            `-_-'
Ferranti International Controls Corporation                'U` 
Sugar Land, TX  77487-5012 USA
+1 713 274 5180                            "Zure otsoa besarkatu al duzu gaur?"
From: au141@cleveland.Freenet.Edu (Amber M. Spillers)
Newsgroups: comp.unix.bsd
Subject: [386BSD] patched binary device drivers avalible anywhere?
Date: 8 Jan 1993 22:31:38 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Reply-To: au141@cleveland.Freenet.Edu (Amber M. Spillers)
NNTP-Posting-Host: hela.ins.cwru.edu


  the title says it all, I don't have source nor do I have space for it
(tho I wish I did) and I really woudl like to get a copy of the patched
com drivers and/or the lp driver.  

  feel free to respond via post or e-mail.


-- 
"Stay Sane Inside Insanity" -- The Rocky Horror Picture Show
sysop of the Rocky Horror Picture Show BBS 1-618-529-5999 24Hrs
USR Dual Standard ** programming support ** NON-Etherealized

Newsgroups: comp.unix.bsd
From: bde@runx.oz.au (Bruce Evans)
Subject: Re: [386bsd] gcc 2.3.2/2.3.3 compile solution
Organization: RUNX Un*x Timeshare.  Sydney, Australia.
Date: Mon, 11 Jan 93 09:18:33 GMT

In article <1993Jan10.223405.23735@zia.aoc.nrao.edu> cflatter@nrao.edu writes:
>In article 5674@mav.com, rick@mav.com (Hendrik Groeneveld) writes:
>>
>>The problem is not a floating constant out of range. The problem
>>is a floating point stack overflow. To get passed this, manually
>>compile fold-const.c using -S in place of -c. Edit fold-const.s
>>and replace "fsts" with "fstps" in _real_value_truncate. Then
>>assemble (as -o fold-const.o fold-const.s). 
>
>I didn't get this problem but I have had problems with the macro DBL_MAX.

I think the "fstps" bug was the main 386-related bug fixed in gcc-1.40.

>It turns out that the values of DBL_MAX and DBL_MIN are one digit too
>short in /usr/include/float.h: this is a problem since DBL_MAX is
>rounded to the next highest digit and is therefore larger than the
>maximum representable double...

The problem is inaccurate rounding (in atof()) more than the lack of
digits.

>#define DBL_MAX         1.7976931348623157E+308

The correct rounding of the last three digits is 159, not 157.  I'm
not sure what should happen when either of these is rounded to 160
and the last 0 is dropped.  The dropped digit is really beyond the
precision available, so maybe atof/scanf should round the number
down to DBL_MAX.

In any case, float.h should have a value that works, not necessarily
a value that is correctly rounded.  The above doesn't work either.
Look at how it gets munged further by gcc's output routine (printf) and
by gas:

foo.c:
	double x = 1.7976931348623157E+308;
				   ^^
foo.s:
	...
	.double 1.7976931348623168000eE+308;
				^^
foo.o:
	02 00 00 00 00 00 00 F0 7F

This is a NaN (as printf will tell you).  DBL_MAX is

	FF FF FF FF FF FF FF EF 7F

while +Infinity is

	00 00 00 00 00 00 00 F0 7F

gas apparently has bugs too.  It should produce +Infinity.  I think it is
OK internally but it may be trusting the library too much.  gcc can easily
be changed to avoid printf for output, but input is harder.

One value that works is

#define DBL_MAX         1.7976931348623147E+308
					^ was 5

gcc prints 58 for the last two digits and gas converts the number correctly.
Printing the number then puts 68 in the last 2 digits...

All this is for the stock 386BSD-0.1 gcc and gas binaries.  Partial fixes
could easily make the problem worse.  (I made one to improve the accuracy
of atof() in 0.1 :-().
-- 
Bruce Evans  (bde@runx.oz.au)
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Newsgroups: comp.unix.bsd
Subject: door open with disk inserted problem (fd.c patch)
Date: 4 Jan 1993 17:05:57 GMT
Organization: I.Physikalisches Institut RWTH-Aachen
Distribution: world
Reply-To: kuku@acds.physik.rwth-aachen.de
NNTP-Posting-Host: acds.physik.rwth-aachen.de
Keywords: patch fix kludge hack fd.c door open


For about half a year I have been living with a behaviour of the
386BSD floppy driver which showed up in not recognizing the presence
of the fd controller when a disk was inserted and the door was left open.
Booting the fd has never been a problem. I always was blaming
some strange BIOS or hardware property for being responsible until
some genious mind kicked me to perhaps try it with door open and disk removed.

I did and the problem could be worked around. I did not like this workaround,though,  because all too often I forget a floppy in the slot and system uptime is a  precious resource - you know. Anyway, here is something
what I would not call a patch because it lacks the proper format, but for applying the fix manually, I leave it here for everyone's convenience:

------------------------- file /sys/i386/isa/fd.c --------------------
/*
!* probe for existence of controller
 */
fdprobe(dev)
struct isa_device *dev;
{
	fdc = dev->id_iobase;

	/* see if it can handle a command */
+	outb(fdc+fdout,0);
+	DELAY(100);
+	outb(fdc+fdout,4);
	if (out_fdc(NE7CMD_SPECIFY) < 0) {
		fdc = 0;
		return(0);
	}
	out_fdc(0xDF);
	out_fdc(2);
	return 1;
}

----------------------------------- end of fix -------------------------- 

--
--Chris
Christoph P. U. Kukulies
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.
Newsgroups: comp.unix.bsd
From: randy@chinet.chi.il.us (Randy Suess)
Subject: Re: out of mem
Organization: Chinet - Public Access UNIX
Date: Wed, 6 Jan 1993 14:19:54 GMT

In article <1icvjgINNl1g@ftp.UU.NET> sef@Kithrup.COM (Sean Eric Fagan) writes:
>In article <C0E4ME.12L@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes:
>>>What about the ksh `ulimit' builtin?
>>	'ulimit' is for disk file size and is a sysv thing, not bsd.
>
>ksh (the real ksh, not a ksh clone) exists for BSD, and the ulimit builtin
>can do everything that the limit command in csh can do.  Amazing that someone
>actually thought about it, huh?
>
	This is the real ksh (11/16/88d) and ulimit is unlimited.  Again,
	it does not seem to be a shell problem, but a kernel one.  However
	seeing as no one else has a problem, I will go back to sysvr4.


-- 
	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: admerlev@cip.informatik.uni-erlangen.de (Arnd Merlevede)
Newsgroups: comp.unix.bsd
Subject: german keymap patches around ?
Date: Tue, 12 Jan 1993 22:08:52 GMT
Organization: CSD., University of Erlangen
NNTP-Posting-Host: faui00j.informatik.uni-erlangen.de

Hi, does anybody know, where I could find patches to use 
a german keymap layout ?
Thanx for the help
Arnd
From: peppe@ipgaix.unipg.it (G. Vitillaro)
Newsgroups: comp.unix.bsd
Subject: [386bsd] Disk partitioning
Date: 10 Jan 93 19:13:53 GMT
Organization: Universita' di Perugia

I'm going to install 386 bsd on my home machine in the next
weeks.

My hardware:

   clone 486DX 33Mhz AMI Bios, 256Kb cache,
   16Mb RAM, OPTI chipset (I believe)

   LongShine LCS-6631(F) SCSI controller emulating
   a WD 1003/1006

   Fujitsu M26225-512 320Mb SCSI disk  ID=7
   IBM     00663L12   1Gb   SCSI disk  ID=1
   (both disk are attached to the LongShine controller,
   that handle both HD and FD as it was a WD controller)

   Adaptec 1542B (with standard setup) with no SCSI
   devices attached for now (I plan to attach to it
   a TANDBERG TDC 3660 150Mb/250Mb tape next week on
   SCSI ID 2)

   Trident 2.1 SuperVGA passthru attached to an 
   ATI 8514 Ultra graphics card (both with 1Mb of
   display memory)

   NEC 4FG Display

   Logitech Mouseman 3 buttons serial attached mouse
   (emulating a Microsoft).

   I have some questions:

   1) It is the current release of 386bsd going
      to work on my hardware?
  
   2) Does exist an X server working at 1024x768x256colors
      available for one of my cards? (8514 in particular)

   3) The second of my disk has 1944 tracks. DOS is obviously
      able to see only the first 1024 tracks (504Mb) of
      my disk. It is 386bsd able to see tracks greates than 1024?
      My idea is to install 386bsd on the first disk and mount
      500Mb from the second. Any hint about a better partition
      scheme? My controller may remap part of the second disk
      on the first, but I'll loose perfomance I believe.

Please e-mail any answer to me, as I'm not (for now) a regular
follower of the group.

Regards,  Peppe

-- 
Giuseppe Vitillaro - IBM SEMEA      |  E-Mail : peppe@ipgaix.unipg.it 
University of Perugia Italy         |  06100 Perugia  Phone:+39.75.585-2200
---------------------------------------------------------------------------
All comments/opinions are mine and don't represent those of IBM
Newsgroups: comp.unix.bsd
From: wnkretz@ikesg1.energietechnik.uni-stuttgart.de (Oliver Kretzschmar)
Subject: Problem to transfer large data via socket communication - Need Help
Organization: IKE
Date: Fri, 8 Jan 1993 07:16:12 GMT


  Hey,

  we develope a program with socket communication. We have large
  datas to transfer. So we use the following routines
  to send data from socket to socket (stream):

        write(socket,(char*)data,buffer)
        read(socket,(char*)data,buffer)

  But now we've problems sending/receiving large data for
  example 50*50*50 matrix of floats or larger. Is there any
  transfer-bufferlimitation by using streamsockets, that we can
  manipulate ? Exists there no more comfortable possibility to
  transfer the data ? Please mail me your informations

  Thanks for your great efforts

     Oliver

-- 
 NAME : O.Kretzschmar                      Inst.IKE / University Stuttgart
 PHONE: +49 711 685 2130                           Pfaffenwaldring 31
 FAX  : +49 711 685 2010                            7000 Stuttgart 80
 EMAIL: wnkretz@ikesg1.energietechnik.uni-stuttgart.de
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.unix.bsd
Subject: Re: SCSI card supported with new drivers (Julians)
Date: 4 Jan 93 14:16:23 GMT
Organization: St. Peter's College, US

In article <1i84d4INN1lo@uwm.edu>, knier@miller.cs.uwm.edu (Robert Knier ) writes:
>  Would anyone know anything about this card?

  It sounds like a clone of the TMC-885. Does the SCSI driver support those?

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
Newsgroups: comp.unix.bsd
From: bde@runx.oz.au (Bruce Evans)
Subject: Re: [386 BSD] Permissions set wrong - HELP
Organization: RUNX Un*x Timeshare.  Sydney, Australia.
Date: Wed, 6 Jan 93 12:47:11 GMT

In article <1id1uiINN6n7@manuel.anu.edu.au> titus@coombs.anu.edu.au (titus chiu) writes:
>bde@runx.oz.au (Bruce Evans) writes:
>
>>zip).  One advantage of cpio over tar is that it restores directory
>>permissions so the default /tmp permissions would get fixed up by a
>>/tmp with the correct permissions in another archive.
>
>that is incorrect i am afraid ;) .. tar will restore permission for
>root if the -p flag is used (i am pretty sure gnu tar has this flag) ..

Nope.  gnu tar-1.10 only restores the permission if the directory doesn't
already exist.  This seems to be a bug in gnu tar.  tar calls mkdir(),
which fails when the directory already exists.  It then calls make_dirs()
which returns early when errno != ENOENT.  Apparently too early.  The
errno from mkdir is EEXISTS.

For directories not explicitly mentioned in the tar file, the -p flag
causes the umask to be ignored, so the directories get permissions 777.
I think ~umask is a better guess for the right permissions in this case.
-- 
Bruce Evans  (bde@runx.oz.au)
Newsgroups: comp.unix.bsd
From: msw@world.std.com (Mark S Warren)
Subject: [386BSD] Where is BOOTEASY?
Organization: The World @ Software Tool & Die
Date: Tue, 12 Jan 1993 15:33:48 GMT

I know I remember seeing it posted a few months ago, but I can't
find it now.  Can someone please remind me?  Thanks.
-- 

 == Mark S. Warren    msw@world.std.com     (508) 772-6045 ==
Newsgroups: comp.unix.bsd
From: corcoran@valhalla.cs.wright.edu (Michael P. Corcoran)
Subject: 386BSD install problem -- can't mount /
Organization: Wright State University
Date: Mon, 11 Jan 1993 02:27:58 GMT

Help!  I'm having problems with the installation of 386bsd.
I've noticed at least 3 other postings in this group with
the same problem but no solutions.  Here's a little more info:

Both the dist.fs and fixit.fs boot disks boot fine.  I then run
install which also runs without complaints; but, when I try to 
reboot after it installs files on the hard disk, the system goes
into an infinite reboot with a panic:"can't mount root."

After investigating with disklabel on the fixit.fs disk, I found 
that the hard disk label was corrupted.  ok, so I ran disklabel -e wd0
and corrected it.  I then read it back with disklabel -r and all 
was fine, further I was able to mount /dev/wd0a on /mnt and the
filesystem was in good shape.  fsck also passed on it without errors.

Now the weird part.  When I reboot, the disk label gets corrupted
again.  Even if I reboot on the fixit.fs disk, the hard disk label
is restored to some default incorrect values, wrong #cylinders, sectors, 
etc.  When this happens, I am unable to mount /dev/wd0a /mnt so it's
not surprising that the system can't.

I went so far as to create a new /etc/disktab entry in case that
was involved somehow -- No luck.

Now an even more weird part.  If I tell the install program to 
use the entire disk (after deleting all partitions on the disk)
everything works great and the system boots off the hard disk.
I don't really want to do this as I still need to boot dos for
some programs and would like to keep it in a separate partition.

The steps I've taken:
	-- delete all hd partitions
	-- boot dos 5.0 off floppy
	-- create 80MB primary dos parition, format c:, install dos 5.0
	-- boot tinybsd, install
	-- create 263MB 386bsd partition, allow installation to proceed.
 	-- try to reboot off hd, fail.

Another attempt:
	-- delete all hd partitions
	-- boot tinybsd, install
	-- bug?  The system only gives me the choice of installing
		on the entire disk (which works) but does not allow me
		to create a 386bsd partition of the size of my choice.
		Only if a dos parition exists does it ask me what size
		bsd partition I want.

Help! Help!

Configuration:
	Maxtor 8380E 360MB ESDI disk with 512 byte sectors.
	Data Technology DTC6282-24 ESDI controller set for 63 sector
		per track mapping mode which is recommended for Novell,
		OS/2 and UNIX.

Please email replies to corcoran@valhalla.cs.wright.edu.

Any ideas will be appreciated; thanks in advance.:

-- 
_____________________________________________________________________________
 Michael P. Corcoran, Computer Systems Engineer (corcoran@cs.wright.edu)
 College of Engineering and Computer Science	FAX  :(513) 873-5009
 Wright State University, Dayton, Ohio.  	VOICE:(513) 873-5157
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: 386bsd HELP laptop back to DOS 5.0 H/Disk prob
Organization: Weber State University  (Ogden, UT)
Date: Wed, 13 Jan 93 04:29:29 GMT

In article <1992Dec11.163609.9644@ryn.mro4.dec.com> ashley@gidday.enet.dec.com (STEPHEN ASHLEY) writes:
>	HELP HELP,
>	  Fellow 386bsd people, I am in a bit of a bind and need help on
>this one. I tryed (for a lark) installing 386bsd on to my laptop tonight,
>it is a 386sx/16 olivetti V16. Anyway the install got creamed 3/4's of the
>way through the extract, I had to go to work. I took the laptop to work
>with me and decided to reinstall DOS 5.0 back on to the hard drive. But
                                  ^^^^^^^
>I can't get the thing to boot of the hard drive even after several 'fdisk'
>sesions and diffrent combniations of primary and extended DOS drives. I 
>keep getting this message :-
>
> File not found - didn't load 386bsd, will try 386bsd.alt
> File not found - didn't load 386bsd.alt, will try 386bsd.old
> File not found - didn't load 386bsd.old, will try boot
>
>	The hard drive on the laptop is a conner 40meg 2 1/2" IDE drive,
>I have also tryed some disk diags to read and write all sectors but no
>luck yet. I do want to get DOS 5.0 loaded again, any idears out there ?

DOS 5.0 command to overwrite master boot record:

	fdisk /mbr

For non DOS-5.0 DOS-heads:

	Instructions in README and INSTALL documents.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
From: david@maxwell.ucsc.edu (David Darknell)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Anybody try to use OS/2 Boot Manager to load BSD?
Date: 12 Jan 1993 15:44:16 GMT
Organization: University of California, Santa Cruz
NNTP-Posting-Host: maxwell.ucsc.edu
Keywords: OS/2 Boot Manager 386BSD

I have been trying to get the OS/2 boot manager to select 386BSD,
but BSD reboots the computer, re-invoking boot manager.  Any way 
around this, or is boot manager not compatible with 386BSD?

David

Newsgroups: comp.unix.bsd
From: rich@Rice.edu (& Murphey)
Subject: Re: WordPerfect on 386BSD?
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Sat, 9 Jan 1993 05:38:44 GMT

>>>>> In article <1993Jan9.214255.26478@fcom.cc.utah.edu>, terry@cs.weber.edu (A Wizard of Earth C) writes:

Terry> In article <93010913477@erato.iowa-city.ia.us> jdb@erato.iowa-city.ia.us (John D. Boggs) writes:
>I want to be able to run WordPerfect on a unix box at home, and the good
>folks at WordPerfect Corporation have apparently never heard of 386BSD.
>So, is 386BSD binary compatible with the commercial flavor of Unix (what
>is that, system 5?)  Has anyone got WordPerfect running on 386BSD?

[useful answers about binary compatibility...]

Terry> If you have X going, there has been a lot of recent work on the WYSIWYG
Terry> editor that comes with InterViews(sp?), and that may be your best bet
Terry> (unless you didn't want an editor to edit, but just to have WP).

Yes, 'doc' is intended for many of the same purposes as WP.  The binary
distribution and patches are on agate.berkeley.edu (128.32.136.1) in
pub/386BSD/0.1-ports/x-apps/InterViews and README-iv3.1-386bsd has
more info.  Here's a description of doc.  Rich


Doc is a WYSIWYG document editor.  In addition to text, doc contains a
simple table editor, and it can import graphics generated by the
drawing editor Idraw and several types of rasterized images.  The
editor's functionality and terminology is modeled loosely after the
LaTeX document preparation system.  In particular, doc stores its
documents in a format that is reminiscent of LaTeX; you can translate
many LaTeX documents into doc format with relatively little effort.

Doc is styled as a technical paper preparation tool.  It supports
floating figures, cross-referencing, section and figure numbering,
page numbering, user-defined macros and user-defined styles.
Currently, however, it does not include an equation formatting
facility or indexing.

Doc uses high-quality TeX formatting algorithms and precise PostScript
font metrics (where available).  The TeX algorithms are able to find
pleasing line and page breaks for most documents; where necessary, you
can guide the formatter by inserting discretionary breaks.  With care,
you can expect a high-quality final document.

Newsgroups: comp.unix.bsd
From: chmr@fstgds01 (Christoph Robitschko)
Subject: Re: [386bsd] happy new year
Organization: Technical University of Graz, Austria
X-Newsreader: TIN [version 1.1 PL7]
Date: Mon, 4 Jan 93 10:43:39 GMT

In article <C0AFoE.2GB@moxie.hou.tx.us> Greg Hackney (hackney@moxie.hou.tx.us) wrote:
:> However, when setting the date under 386BSD, the onboard computer clock does
:> not seem to get updated. A reboot reverts back to it's idea of time.
:> Could this be the problem?
:> 
I have rewritten the clock routines, adding one to write the time back to
the CMOS. I wrote this a few months ago, but did not release it, because
it also contains some (probably) non-portable code to automatically
write Time-zone information along with the time to the CMOS. This makes
it possible for DOS and 386bsd to (nearly) always have the correct time,
even if you have DST. Because this code uses the ALARM registers of
the CMOS clock, it might collide with some DOS applications (which one ?),
and so is only enabled with a config option.

I will clean it up and post it in a few days.


							Christoph
Newsgroups: comp.unix.bsd