HDTenEightyP/NetNews huggingface dataset:
From: david@maxwell.ucsc.edu (David Darknell)
Newsgroups: comp.unix.bsd
Subject: [386BSD] XFree86 Questions: Help!
Keywords: [386BSD] XFree86 Help
Date: 10 Jan 93 22:23:57 GMT
Organization: University of California, Santa Cruz
NNTP-Posting-Host: maxwell.ucsc.edu

Congratulations to all of you wonderful programmers for this treat!
Wow!  I have been trying to install 386BSD on my 486/33 8M/535M HD
and have some problems, primarily they are:

1.  I can't find anywhere the procedure for installing XFree86 with
	a Logitech bus mouse (irq5).  I did manage to get XFree86 to
	recognize a serial mouse.  
2.  Whenever I invoke xinit with the Logitech settings (in Xconfig)
	Logitech	"/dev/com1:
	etc..
	My screen is shifted to graphics mode, and is never restored when
	X dies.  I have to sync;shutdown to restore my screen.  when I
	comment out the Logitech device driver, the screen is not corrupted.
	Why?
3. I now have the message, when I invoke xinit:
	...
	VGA256: SpeedUp mode selected (Flags=0x3f)

	Fatal Server error:
	could not open default font 'fixed'
	XIO:  fatal IO error 32 (...

	I have two font directories, 75dpi, and misc which were in the 
	orig distribution.  Neither has any font named, 'default'.  What
	am I missing here?

thanks!

David
Newsgroups: comp.unix.bsd
From: asu@server2.panther.mot.com (Russell Trotter)
Subject: [386bsd] bind() errors on various stuff
Organization: Motorola Panther Project, Chandler, AZ
Date: Mon, 4 Jan 1993 15:15:47 GMT

Just a quickie,

  I get bind() errors on about any  software (syslogd, startx/xinit, 
etc ...) that cause these programs to just exit.  I don't have an
ethernet card so the kernel doesn't configure anything at bootup time,
is this my problem?  I remember reading in the BUGLIST that to fix
this problem with talkd, one just has to make sure their /etc/host
contains an entry like '127.1  myhostname'.  This didn't appear to
fix the problem, any other ideas?


Thanks!

Russ
From: gregb@murphy.com (Greg Banschbach (Unigroup of New York))
Subject: Re: [386BSD] Soundblaster Pro CD-ROM Driver
Organization: Murphy & Durieu, NYC NY, USA
Date: Thu, 7 Jan 1993 15:06:33 GMT

In article <1993Jan5.121701.22607@marlin.jcu.edu.au> cejjb@marlin.jcu.edu.au (Jeffrey Bird) writes:
>Has anybody managed to produce a driver that will allow me to use my
>Soundblaster Pro's CD-ROM drive under 386BSD?
>
>Or failing that, does anybody have any programming information on the
>CD-ROM interface?
>
>			Jeff Bird
>
>-- 
>    Jeff Bird - Novell Supervisor and Postgraduate Student
>            Department of Electrical and Computer Engineering
>	        James Cook University of North Queensland
>AARNET/Internet:	cejjb@marlin.jcu.edu.au

	Try to get a the last three issues of Dr. Dobbs Journal - it 
	has addressed this topic and will provide even more on it.
From: rick@mav.com (Hendrik Groeneveld)
Newsgroups: comp.unix.bsd
Subject: [386bsd] gcc 2.3.2/2.3.3 compile solution
Date: 8 Jan 93 18:40:51 GMT
Organization: Maverick International Inc.

In article <RICH.92Dec27171213@superego.Rice.edu> Rich@rice.edu writes:
>>>>>> In article <BLYMN.92Dec27161320@siren.awadi.com.au>, blymn@awadi.com.au (Brett Lymn) writes:
>>>>>> On 20 Dec 92 00:43:03 GMT, dhess@Xenon.Stanford.EDU (Drew William Hess) said:
>D> I'm having problems getting gcc 2.3.2 to compile under 386bsd.  It's choking
>D> on enquire.c, line 2303, and complaining about a floating point constant
>D> being out of range.  Can someone please post or email me a fix?  Thanks.

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

There is also a circular dependancy for protoize.o/unprotoize.o in the
Makefile. Add the lines

	touch protoize.o
	touch unprotoize.o

after the line

	touch stamp-proto

After this "make bootstrap" will run to completion.


>Brett> I would not worry about it too much, if you have a look at the
>Brett> comments in the .h file enquire generates you will see that the errors
>Brett> that it has detected are rather infesteminal (ie the order of 1e-308)
>Brett> so I suspect the rounding is wrong rather than anything else more
>Brett> serious.

enquire won't generate a .h file if you can't compile it

--
Hendrik Groeneveld					rick@mav.com
Software Engineer					(206) 743-6659
Maverick International
Mukilteo Washington.
From: f54762@sakura.kudpc.kyoto-u.ac.jp (koichiro yamaguchi)
Newsgroups: comp.unix.bsd
Subject: CAPS HUNG UP
Keywords: CAPS
Date: 13 Jan 93 04:30:13 GMT
Organization: Data Processing Center, Kyoto University, Kyoto, JAPAN


Hi 386BSDers

   I have installed 386BSD0.1 and used it to numerical calculation.
That works almost satisfactorily except a problem that the system
always hungs up whenever CAPS key is pressed.
   So I got around the FAQ but never found any likely problem.
   I inspected pccons.c to solve the problem and found that
scantokey[] and extscantokey[] seemed to be wrong in CAPS key position.
The keynumber for keyscancode 58H i.e. CAPS is defined as 0
instead of 30. I think this is not a bug but coded intentionally,
since this table is very fundamental for the system to run successfully.
So I have not yet rebuild the kernel. I'm a greenhorn in UNIX.
   Please let me know how to solve this problem if you know anything
about that.
   Thanks for any helps.

--
Yamaguchi Koichiro  : a graduate student @ Division of Molecular
Engineering, Kyoto University, 606 Kyoto, JAPAN
E-mail : f54762@sakura.kudpc.kyoto-u.ac.jp
From: cgd@stinson.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: DDB: no symbols
Date: 8 Jan 93 21:33:38 GMT
Organization: Kernel Hackers 'r' Us
NNTP-Posting-Host: stinson.cs.berkeley.edu
In-reply-to: pogyk@unixg.ubc.ca's message of 8 Jan 93 20:06:08 GMT

In article <pogyk.726523568@unixg.ubc.ca> pogyk@unixg.ubc.ca (Pogy Kurniawan) writes:
>Hello folks, Well I applied all patches x19,45,47 recompiled the kernel.
>Rebooted, and lo and behold it worked(for me this was a surprise)
>BIG BUG it reports DDB: no symbols. What is this and how can I clear it up.

you've gotta run "dbsym 386bsd" on the kernel...

this creates the ddb symbols that it needs...

this isn't really documented, and should probably be done automatically
somehow, but alas, i know not how... 8-)

chris


--
Chris G. Demetriou                                    cgd@cs.berkeley.edu

"Sometimes it is better to have twenty million instructions by
        Friday than twenty million instructions per second." -- Wes Clark
Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: patch for 386bsd pty code
Organization: Trw Financial Systems
Date: Tue, 12 Jan 1993 06:31:14 GMT

I have tracked down the problem that causes over 50% of the
crashes on ref.tfs.com
These are the crashes where ref still appears to be alive.
(i.e. you can still ping it)
[!! UNFORTUNATLY I AM UNABLE TO TEST IT AT THIS TIME!!!]

Two processes each write to the same pty
in a special case, each sleeps waiting on the output queue.  
Unfortunatly, the pty code sleeps and wakes up on this same address
because the sub-field it sleeps on is the first in the output
queue structure, and thus has the same address as the queue
as a whole.
The solution is to make the pty code sleep and wakeup
on another sub-field of the structure.

The result of the confusion is that the two processes
writing to the pty simply keep waking each other up
(at high priority, and then going to sleep themselves at 
high priority) As a result, all other work on the processor
comes to a stop.

the following patch  should fix the problem

*** tty_pty.c.pl3	Mon Jan 11 22:11:25 1993
--- tty_pty.c	Mon Jan 11 22:15:24 1993
***************
*** 234,240 ****
  			pti->pt_selr = 0;
  			pti->pt_flags &= ~PF_RCOLL;
  		}
! 		wakeup((caddr_t)&tp->t_out.rb_hd);
  	}
  	if (flag & FWRITE) {
  		if (pti->pt_selw) {
--- 234,240 ----
  			pti->pt_selr = 0;
  			pti->pt_flags &= ~PF_RCOLL;
  		}
! 		wakeup((caddr_t)&tp->t_out.rb_tl);
  	}
  	if (flag & FWRITE) {
  		if (pti->pt_selw) {
***************
*** 334,340 ****
  			return (0);	/* EOF */
  		if (flag & IO_NDELAY)
  			return (EWOULDBLOCK);
! 		if (error = tsleep((caddr_t)&tp->t_out.rb_hd, TTIPRI | PCATCH,
  		    ttyin, 0))
  			return (error);
  	}
--- 334,340 ----
  			return (0);	/* EOF */
  		if (flag & IO_NDELAY)
  			return (EWOULDBLOCK);
! 		if (error = tsleep((caddr_t)&tp->t_out.rb_tl, TTIPRI | PCATCH,
  		    ttyin, 0))
  			return (error);
  	}

----
From: deeken@iti.informatik.th-darmstadt.de (Hans-Christoph Deeken)
Subject: Re: codrv problems..
Date: Thu, 7 Jan 1993 16:49:04 GMT
Organization: TU Darmstadt
Keywords: 386BSD, codrv

In article <1993Jan6.184438.5175@lgc.com>, danson@lgc.com (Doug Anson) writes:
> HI:
> 
[ description of codrv problems ]
> 
> I have the 386BSD 0.1 kernel with 1-58 patches applied + pcfs.

Exactly the same problem here. Also "panic: syscall", also 386BSD 0.1.pl58.

The kernel prints out the devices as they are probed/attached(?), but dies
after that with a "panic: syscall", before /etc/rc output starts.
The only occurance of panic("syscall") that I've found is in
/sys/i386/i386/trap.c, at the start of syscall(). Since I don't know anything
about the stuff done in trap.c, I'm stuck.


> Any help would be appreciated.
> Doug

Me too. Holger?

Hannes
-- 
Hans-Christoph Deeken | hannes@flinx.{RoBIN.de,hotb.sub.org} (home)
Gerauer Str. 20       | deeken@iti.informatik.th-darmstadt.de (university)
6000 Frankfurt/M 71   | IRC: Glenlivet
      "Das Beispiel hinkt nicht, das sitzt im Rollstuhl" -- Marsi
From: news@hrd769.brooks.af.mil (InterNet News)
Newsgroups: comp.unix.bsd
Subject: PC File System Code
Date: 3 Jan 1993 14:20:06 -0600
Organization: Armstrong Lab MIS, Brooks AFB TX
NNTP-Posting-Host: hrd769.brooks.af.mil

  I just finished loading the PC File System patches that were transmitted
to the net last week.  I found a bug.

  The symptom is that the mount works great, but the umount locks up the
machine.  I got looking into umount.c, and found that it was trying to
unmount a MOUNT_MSDOS partition.  There isn't any such beast.  It is a
MOUNT_PCFS partition.  Below are the changes to make umount work:

  In the file /usr/src/sbin/umount/umount.c  , change the two 'MSDOS'
references to pcfs, like the example below:

Starting at about line 372:

	for (i = 0; fslist; fslist = nextcp) {
		if (nextcp = index(fslist, ','))
			*nextcp++ = '\0';
		if (strcmp(fslist, "ufs") == 0)
			av[i++] = MOUNT_UFS;
		else if (strcmp(fslist, "nfs") == 0)
			av[i++] = MOUNT_NFS;
		else if (strcmp(fslist, "mfs") == 0)
			av[i++] = MOUNT_MFS;
!		else if (strcmp(fslist, "pcfs") == 0)
!			av[i++] = MOUNT_PCFS;
		else if (strcmp(fslist, "isofs") == 0)
			av[i++] = MOUNT_ISOFS;
	}
	av[i++] = 0;
	return(av);
}

Re Make umount and install it.  A good rule for me is to make sure that install
puts the executable where I run it from (using 'where' or whatever).  If it   
doesn't, make sure it gets updated correctly in your path.

TSgt Dave Burgess
NCOIC AL/MIS
Brooks AFB, TX

BTW:  This particular option is NEAT.  Good Work!!!!!!!

Dave
Newsgroups: comp.unix.bsd
From: peter@ferranti.com (peter da silva)
Subject: Re: 386BSD install problem -- can't mount /
Organization: Xenix Support, FICC
Date: Tue, 12 Jan 1993 15:18:48 GMT

In article <1993Jan11.022758.10164@cs.wright.edu> corcoran@valhalla.cs.wright.edu (Michael P. Corcoran) writes:
> 	Data Technology DTC6282-24 ESDI controller set for 63 sector
> 		per track mapping mode which is recommended for Novell,
> 		OS/2 and UNIX.

Here's your problem. Either turn off the sector mapping, or find a sector
where the mapping and the real cylinders match. At least part of the 386BSD
boot sequence uses real track offsets. Like 0 (which is why it works when
you do a "whole disk" install).

I would suggest turning off the sector mapping. The ONLY reason for this is
to allow DOS access to cylinders past 1024 without patching the BIOS, and
if you're using a small DOS partition and a large BSD partition you'll never
need that.

You'll also get a performance improvement on BSD (cylinder groups end up on
real cylinder boundaries!), and probably a little more disk space (I got an
extra 30 MB on a Maxtor 4380E when I switched from the Compaq controller to
my Ultrastor 12F24... and I could have gotten another 30 MB if I'd wanted
to use BAD144 for all my bad-track mapping). It's a win all round.

Insert obligatory flaming about idiot manuals that encourage bad procedures
here, and go on to the next message...
-- 
Peter da Silva                                            `-_-'
Ferranti International Controls Corporation                'U` 
Sugar Land, TX  77487-5012 USA
+1 713 274 5180                            "Zure otsoa besarkatu al duzu gaur?"
Newsgroups: comp.unix.bsd
From: peter@ferranti.com (peter da silva)
Subject: Re: [386bsd] Kernel build dies, unref symbol _version
Organization: Xenix Support, FICC
Date: Mon, 4 Jan 1993 15:21:27 GMT

In article <1993Jan2.004817.26258@aio.jsc.nasa.gov> poirot@mickey.jsc.nasa.gov (Daniel Poirot) writes:
> In article <id.E4CW.XE@ferranti.com> peter@ferranti.com (peter da silva) writes:
> >I did. It isn't. You have to "make newvers" to get a vers.c file to resolve
> >this symbol. This should be documented. :->

> Actually, shouldn't the Makefile target '386bsd' depend on 'vers.o'?

Well, that would help. You'd also have to have a "vers.c" target.
-- 
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: heiser@acs.bu.edu (Bill Heiser)
Newsgroups: comp.unix.bsd
Subject: Installing from SCSI tape
Date: 8 Jan 93 04:16:00 GMT
Organization: Boston University, Boston, MA, USA
Originator: heiser@acs.bu.edu

I'm trying to install the distbin (for starters) from a 1/4" SCSI
tape on a 486/33 with AMI bios, Opti chipset, 16mb ram, Maxtor 8760S
disk, and CDC Wren IV 307mb disk.  I got the base installation done
from a floppy into a 300mb partition.  When I try to access the
Archive 2150S tape unit to extract the files, I get an "error 9"
from cpio.  The tape is loaded, and the drive worked just a few
hours ago (on the same system) when it was running Esix (system V r3).

The scsi drive is id 4, the boot disk is 0, and the cdc disk is 1.
During the boot, there is an error trying to read the disk label
from the cdc drive (it is formatted for dos).

Is this reminiscent of any known problems?  BTW, this is 0.1 I'm 
using.

Thanks,
Bill

-- 
Bill Heiser
heiser@bu.acs.edu, heiser@world.std.com
From: mycroft@hal.gnu.ai.mit.edu (Charles Hannum)
Newsgroups: comp.unix.bsd
Subject: Re: Still more XFree86 problems
Date: 8 Jan 93 20:09:53 GMT
Organization: /etc/organization
NNTP-Posting-Host: hal.gnu.ai.mit.edu


In article <51103@shamash.cdc.com> pbd@runyon.cim.cdc.com (Paul Dokas)
writes:
>
> notice how the date changed right in the middle of booting.

This happens to me, too; but that's because I run `ntpdate' on booting.

-- 
 \  /   Charles Hannum, mycroft@ai.mit.edu
 /\ \   PGP public key available on request.  MIME, AMS, NextMail accepted.
Scheme  White heterosexual atheist male (WHAM) pride!
From: mmead@meadmc.async.vt.edu
Newsgroups: comp.unix.bsd
Subject: Installation of 386BSD 0.1
Date: 11 Jan 1993 06:56:51 -0600
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu

  Howdy.  I am currently faced with the problem of getting a unix for my PC
for cheap that will support slip and networking and be able to run some
binaries that I need to have and I'm seriously considering 386BSD because of 
its apparent stable slip code.  What I would like to know before I purchase a
brand new Hard Drive (200MB) is whether or not I'm going to be able get
source for Tinyfugue (latest version), and TinyMUCK to compile.  These two
binaries are the ones I am most concerned about, and would really like to know
before I spend the money.  If you have these running under 0.1 386BSD would
you please let me know either on here, or by email to mmead@vtssi.vt.edu?  I
would greatly appreciate it.  Also, am I correct in what I read about the
installation program being able to download the system using slip and install
it while downloading?  If so, Kudos go to someone since that is one of the
niftiest ideas I have seen in a while, eliminating a lot of the fuss with
floppy transfer of files...then just moving it all back to the hard drive...



*----------------------------------------------------------------------------*
* Matthew C. Mead -- mmead@vtssi.vt.edu |  "To know everything would be      *
*  A \ Ogion       | mmead@nyx.cs.du.edu \_____ impractical; access time     *
*    k \  the      | mmead@meadmc.async.vt.edu \__  would be exceedingly     *
*      A \ Silent  | akcs.matt1@hpcvbbs.cv.hp.com \                 high"    *
*----------------------------------------------------------------------------*
Newsgroups: comp.unix.bsd
From: bri@athena.mit.edu (Brian D. Carlstrom)
Subject: GCC 2 something for Apollo
Organization: mit
Distribution: comp
Date: Thu, 7 Jan 1993 20:41:00 GMT

Hi i have a working gcc 1.40, but it seems like i need to get
a gcc 2.* going now. is there a a version of this for the apollo.
i seem to remember seeing patches, but i dont remember where.
thanks a lot

-bri

Newsgroups: comp.unix.bsd
From: gtoal@pizzabox.demon.co.uk (Graham Toal)
Subject: 'op' command ported to 386bsd; on rachel.ibmpcug.co.uk:/usr/local/src/op
Organization: Cuddlehogs Anonymous
Date: Wed, 6 Jan 1993 09:03:47 GMT


Op is a utility to allow restricted su access to particular commands.
Well worth having if you share the admin load with your users.

Graham
From: pozar@kumr.lns.com (Tim Pozar)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] corrupt files
Date: 6 Jan 93 04:30:12 GMT
Organization: Late Night Software (San Francisco)

chapman@acf3.NYU.EDU (Gary W. Chapman, , ,) writes:
>After downloading 386BSD from agate.berkeley.edu (and from another place
>as well), I get 
>
>bin01.02 is corrupt
>bin01.03 is corrupt
>
>when doing 'extract'.  What can I do?
>- Gary Chapman, chapman@nyu.edu

   Try re-getting the file before it too (ie bin01.01).  I have notice
extract will identify the file following a corrupt "bad" when the one 
before it was bad (truncated, etc.).

                    Tim

-- 
    Internet: pozar@kumr.lns.com     FidoNet: Tim Pozar @ 1:125/555
Snail: Tim Pozar / KKSF / 77 Maiden Lane / San Francisco CA 94108 / USA
                        Voice: +1 415 788 2022
Newsgroups: comp.unix.bsd
From: hannes@flinx.RoBIN.de (Hannes Deeken)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] Queries for the new scsi driver.
Date: 9 Jan 1993 11:17:59 +0100
Organization: Me, organized? You're kidding!
NNTP-Posting-Host: flinx.robin.de

mhiroshi@tansei.cc.u-tokyo.ac.jp (H. Murakami) writes:

>My current problem with this julian new scsi driver system is,

>the kernel built does not add the partition sd0e for the swap area. 
>The "swapon /dev/sd0e" makes error message saying that 
>	
>	adding swap: failed! (unchanged)
>	swapon: /dev/sd0e Device not configured

>Note, I have the line in the file /etc/fstab like:

>	/dev/sd0e - swap sw - -

>This kind of trouble never happened when I used the old scsi driver.
>What is the reason that I cannot assign /dev/sd0e  for swap ?


What is the type of sd0e in the disklabel of sd0?

After changing to Julian's drivers, my system reportet "no swap space present",
because my swap partition was labeled "unused" (which was fine with the as-
driver). Changing this to "swap" made it work.

Another point: Did you try to remove all object files and reconfigure and 
remake the kernel from scratch? Maybe something went wrong before...


Hannes
-- 
Hans-Christoph Deeken | hannes@flinx.RoBIN.de (home)
Gerauer Str. 20       | deeken@iti.informatik.th-darmstadt.de (university)
6000 Frankfurt/M 71   | IRC: Glenlivet
Newsgroups: comp.unix.bsd
From: adrian@rachel.ibmpcug.co.uk (Adrian Hall)
Subject: Re: [386bsd] happy new year
Organization: The IBM PC User Group, UK.
Date: Mon, 4 Jan 1993 15:28:01 GMT

dawes@physics.su.OZ.AU (David Dawes) writes:
> In article <fXrM6yq@quack.sac.ca.us> dfox@quack.sac.ca.us (David Fox) writes:
> The patch works for me, but both Andrew, Bruce (and I) are east of GMT/UTC
> while you are west (so the TZ sign will be different).  Anyone else
> tried these patches?  The results from someone at GMT might be
> interesting.

Im on GB-Eire - worked for me.

Adrian
-- 
------------------------------------------------------------------------------
Adrian Hall				Telephone: +44 (0)81 863 1191
Connect Systems Manager			Fax:	   +44 (0)81 863 6095
The IBM PC User Group			Internet:  adrian@ibmpcug.co.uk
Newsgroups: comp.unix.bsd,comp.std.internat
From: peter@ferranti.com (peter da silva)
Subject: Re: Dumb Americans (was INTERNATIONALIZATION: JAPAN, FAR EAST)
Followup-To: comp.std.internat
Keywords: Han Kanji Katakana Hirugana ISO10646 Unicode Codepages
Organization: Xenix Support, FICC
Date: Mon, 4 Jan 1993 15:35:27 GMT

In article <1i2k09INN4hl@rodan.UU.NET> avg@rodan.UU.NET (Vadim Antonov) writes:
> You omitted one small "detail" -- you need to know the language of the word
> the letter belongs to to make a conversion.

Yes.

> Since Unicode does not
> provide for specifying the language it is obvious that is should be
> obtained from user or kept somewhere off the text. In both cases
> as our program ALREADY knows the language from the environment it knows
> the particular (small) alphabet -- no need to use multibyte encodings!

Unless you want your document to contain multilingual data. *your* solution
is only useful for documents containing a single language, in which case
why bother with ISO8859.*... a separate character code table for every
language is quite acceptable. For that matter, you can take the next step
and say "why standardise character sets when every application has specific
needs? Financial packages need dozens of currency symbols, for example, and
mathematics needs a whole host of its own symbols... each application knows
the set it needs to use... and for most text documents a 6-bit code is quite
adequate"...

You have identified two problems with Unicode and ISO 10646: case conversion
and lexical ordering.

> See how Unicode renders itself useless?

Unless you want to work on multilingual documents, yes. It could be better,
certainly, but to say it's *useless* is hyperbole.
-- 
Peter da Silva                                            `-_-'
Ferranti International Controls Corporation                'U` 
Sugar Land, TX  77487-5012 USA
+1 713 274 5180                            "Zure otsoa besarkatu al duzu gaur?"
Newsgroups: comp.unix.bsd