HDTenEightyP/NetNews huggingface dataset:
From: toreh@bootes.sds.no (Tore Haraldsen)
Subject: Re: Almost Free Symbolic Links (source code)
Organization: Statens Datasentral A/S, SDS, Norway
Date: Mon, 28 Dec 1992 17:29:49 GMT

Thank you, Curt Mayer, for this nice, little hack!! It reduces my shadow
X11R5 tree from 12MB of symlinks to a mere 800kB, quite a difference!

I recognize the technique as the one applied to the Ultrix file system a
couple of years ago, it made a similar impact there...

Again, thank you for a very nice hack!

-- tore
-- 
------------------------------------------------------------------------
Tore Haraldsen, Statens Datasentral A/S - SDS, Norway
email: toreh@bootes.sds.no
Newsgroups: comp.unix.bsd
From: adrian@rachel.ibmpcug.co.uk (Adrian Hall)
Subject: Re: New kernel on rachel.ibmpcug.co.uk
Organization: The IBM PC User Group, UK.
Date: Tue, 22 Dec 1992 20:56:58 GMT

adrian@rachel.ibmpcug.co.uk (Adrian Hall) writes:
> For those with not enough memory/disk space to compile their own
> kernels, the latest (?) kernel on rachel.ibmpcug.co.uk has the
> following in it :-
> 
	
	Julians SCSI Drivers	(from ref.tfs.com)
	New NE-2000 Driver	(as Posted to the net recently)
	WD8003E Driver
	3COM 503 Driver
	2 COM Ports		(dist com drivers)
	NFS,ISOFS,XSERVER,INET
	WT Driver
	All patches except for 47
	Config for 32 Users and 32 Ptys

(Repeat Request --- Can I have the LPT patches of the favorite kind for
 inclusion please someone).

	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
From: adrian@rachel.ibmpcug.co.uk (Adrian Hall)
Subject: Re: [386bsd] SLIP is one way...
Organization: The IBM PC User Group, UK.
Date: Sat, 2 Jan 1993 19:50:21 GMT

pozar@kumr.lns.com (Tim Pozar) writes:
> 
>    With building any kernel the best I can get on slip sessions are
> packets going out a slip link and not making it back in.  The machine on
> the other end will echo pings back, but the 386BSD box is not getting them
> back.

I ran into this problem before correcting it....

You have to de-install the SLIP patch (patch 45????) - SLIP will then
work fine.

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.unix.bsd
From: rpaul@netcom.com (Raymond E. Paul)
Subject: [386bsd] Cannot boot TinyBsd - Help.
Followup-To: comp.unix.bsd
Keywords: 386bsd, TinyBsd
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Sat, 2 Jan 1993 07:44:23 GMT


I have the following system configuration and I have been unable to 
successfully boot from the TinyBsd floppy. I retreived this floppy from 
agate.berkeley.edu around 12/92 and have verified that it works fine on
various other systems.

	 386/486/387:  Utron 386/40MHz  AMI Bios
	 ISA/EISA/SCSI: ISA 
	 RAM size: 4 Meg
	 drive(s) type and size: Quantum LPS-120 256K cache
	 tape(s) type and size: Colorado 250 MB
	 ethernet type: none
	 graphics type: EGA / ATI EgaWonder (very old - 5yrs or more)
	 serial type: 2 serial ports on IDE disk controller
	 parallel type: 1 parallel port on IDE disk controller
	 other: USRobotics 14400/PC FAX Modem


After the system reads the drive for about 30 seconds I get the following error message:

trap type 19 code = 0 eip = fe00076c cs=8 eflags = 3002 cr2 0 cpl ffffffff
panic: trap
hit reset please

I have tried changing the AMI BIOS configuration so that shadow ram 
and caching are disabled. I have also removed the modem from the system. So
far everything I've tried has been to no avail.  

Any help would be greatly appreciated. In particular, does anyone out there
have experience with the same motherboard? Is there any useful information that
can be gleaned from the error message. (I know what the registers and flags 
mean, more or less, I just don't know what to do about it). Where do I go from
here?

-- 
Raymond E. Paul		rpaul@netcom.com
Newsgroups: comp.unix.bsd,comp.os.linux,comp.unix.pc-clone.32bit
From: roell@informatik.tu-muenchen.de (Thomas Roell)
Subject: Re: ET4000/W32 and VESA VL-Bus
	<1992Dec18.095906.3950@Informatik.TU-Muenchen.DE>
	<1hloneINNfnn@cbl.umd.edu>
	<1992Dec28.103211.12677@diomedes.robots.ox.ac.uk>
Organization: Inst. fuer Informatik, Technische Univ. Muenchen, Germany
Date: Mon, 28 Dec 1992 19:03:16 GMT

>The 801 is indeed DRAM based (60ns DRAM), For the 911 and 801 boards both
>for 71Hz refresh at 1024x768 on a 13MHz ISA bus I get:

Sorry, but this way of comparing things is quite rediculuts, if not
even dumb (sorry folks , but I lack a better word of stating that somebody is
not the brightest mind if he/she does things like that ;-)). 

The issue here is that you have to compare two things that appeared at the
market at about the same time. For example 86C911 vs. WD90C31
would make sence (ca 55k xstones vs. 45k xstones). Also 86C801/86C805
vs. mach32 (Ultra Pro) gives some sence: 100k vs. 64k. Or if you want
to stay in the domain S3, 801 vs 928. But what you do is comparing a
chip that's ONE year old, and which in fact was one of the very first
so called Windows accelerators. The 801/805/928 are simply the next
generation, and hence much faster than the last generation. Other uneaqual
comparisons wouldn't help you in comparing DRAM vs. VRAM at all.

You are right if you compare the price/performance ratio of the 911 and
a 801 based board today. But the 928 bases boards are just around the corner
and will not cost much more than 801 based boards. That's the scenario where
my comments apply. Then we have the same chips design as base and can compare
a VRAM and a DRAM implementation with the same graphics engine ...

- Thomas

--
-------------------------------------------------------------------------------
Das Reh springt hoch, 				e-mail: roell@sgcs.com
das Reh springt weit,				#include <sys/pizza.h>
was soll es tun, es hat ja Zeit ...
From: chk@mcshh.Hanse.DE (Christian Kuhtz)
Subject: [386BSD]  Installation via Ethernet
Organization: Point of Presence & MCS Hamburg
Date: Tue, 29 Dec 1992 06:39:42 GMT

Hi,

		I have some problems in installing 386BSD
		via Ethernet.
		The Board is recognized (NE2000 comp).

		The INSTALL.NOTES say something like this

			ifconfig ne0 <386bsd> <host>

		the IP address of the 386BSD machine is 139.9.42.112.
		               of the Gateway is 139.9.42.1

		So, my question is, what do I have to do to get
		ftp workin ? I tried various possible paramters
		but it doesn`t work.

		Please write me immediatly, cause this problem is
		very urgent. We have to get this machine runnin in
		the next few hours.

		Many thanks in  advance...

			Regards,
				Christian


		
Newsgroups: comp.unix.bsd
From: dfox@quack.sac.ca.us (David Fox)
Subject: [386BSD] happy new year, patch does work after all
Keywords: clock.c patch
Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'.
Date: 3 Jan 1993 22:22:43 UTC

I must have goofed when I tried to apply Andrew Chernov's patch to
fix the new year problem with clock.c.

I've re-applied the patch, rebuilt the kernel, and the date/time
is correct now.

BTW, I'm in GMT-8 (PST).
--
David Fox
dfox@quack.sac.ca.us
From: cgd@stinson.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: 386bsd BOF at USENIX?
Date: 2 Jan 93 05:20:55
Organization: Kernel Hackers 'r' Us
Distribution: world
NNTP-Posting-Host: stinson.cs.berkeley.edu

anybody interested in babbling at a 386bsd BOF at usenix?

if you're interested in talking about your favorite pet project,
or just think you're doing something important and wouldn't mind talking,
and will be at USENIX in San Diego in a few weeks, send me mail...


thanks,

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: dfox@quack.sac.ca.us (David Fox)
Subject: [386BSD] Floating point exceptions with Cyrix
Keywords: floating point Cyrix NDP
Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'.
Date: 24 Dec 1992 02:49:16 UTC


Hi everyone.

I just bought a Cyrix 387-SX math coprocessor and installed it a few
hours ago.  When I brought up 386BSD it recognizes the chip fine, and
some programs (whetstone benchmark, sc) seem to run fine with it.
 
However, ps -aux barfs with "floating exception" immediately after
printing the first report line.  ps -aux worked fine (but slow) without
the coprocessor.

Another program I've been trying to get working (almost useless to try
it without a math chip) is ephem and it also barfs with a floating
point exception.
 
Why does this happen?  Do I need to recompile anything?
Newsgroups: comp.unix.bsd
From: shipley@peyote.dis.org (Pete Shipley)
Subject: Re: recompiled ps exits with /dev/mem permission denied message
Organization: Processed People for a Processed America
	<CGD.92Dec31000133@stinson.CS.Berkeley.EDU>
Date: Sat, 2 Jan 1993 08:49:18 GMT




>From: cgd@stinson.CS.Berkeley.EDU (Chris G. Demetriou)
>Newsgroups: comp.unix.bsd
>Date: 31 Dec 92 00:01:33
>Organization: Kernel Hackers 'r' Us
>
>   umm, that should be
>
>   chmod g+s /bin/ps
>
>   8-)
>
>   i'm surprised that 'make install' did not do it properly...
>
>   perhaps the original poster didn't do 'make install'?


ps(1) should be setgid to group kmem and /dev/mem and /dev/kmem should be
owned root.kmem and mode 0640 (rw-r-----).





--
---------------
Pete Shipley:
email: shipley@berkeley.edu             Flames:  cimarron@postgres.berkeley.edu
Spelling corections: /dev/null          Quote: "Anger is an energy"
Newsgroups: comp.unix.bsd
From: draper@ais.org (Patrick Draper)
Subject: [386BSD] How do I know what's on the etc disks?
Organization: UMCC
Date: Thu, 24 Dec 1992 00:51:34 GMT

Is there an index to the etc distribution that is on wuarchive? There's over
90 of them now, and I can't really take to the time to sift through them all
to find the good stuff.

Also, is there any trouble with the GCC that is in the bindist? I've heard
rumors...


------------------////////////////////\\\\\\\\\\\\\\\\\\\\------------------
| Patrick Draper-ZBT       Disclaimer:  I can't control my fingers,        |
| draper@umcc.ais.org                   I can't control my toes! - Ramones |
| University of Michigan Computer Club                                     |
NO CARRIER                     We are a nation of laws, not people         |
------------------\\\\\\\\\\\\\\\\\\\\////////////////////------------------
From: blymn@awadi.com.au (Brett Lymn)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] gcc 2.3.2 compile problems
Date: 27 Dec 92 16:13:19
Organization: /usr/blymn/.organization
NNTP-Posting-Host: siren.awadi.com.au
In-reply-to: dhess@Xenon.Stanford.EDU's message of 20 Dec 92 00:43:03 GMT

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

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

Apart from that gcc 2.3.2 works fine, I have compiled X with it with
only one problem, in /usr/include stdlib.h there is the following
ifdef:

#if defined(alloca) && (alloca == __builtin_alloca)
void  *alloca __P((int));     /* built-in for gcc */
#else
void    *alloca __P((size_t));
#endif /* __GNUC__ */

You have to comment out the definition of alloca like this:

#if defined(alloca) && (alloca == __builtin_alloca)
/* void  *alloca __P((int));     /* built-in for gcc */
#else
void    *alloca __P((size_t));
#endif /* __GNUC__ */


Otherwise gcc gets confused and will not use the builtin alloca.
Apart from this X compiles without a hitch and it seems (to me at
least) a bit faster (not much) and a little bit smaller (again not
much).  I have not found any problems with commenting out the alloca
definition but I am not happy about doing it, anyone got a better
suggestion?

Newsgroups: comp.unix.bsd
From: thinman@netcom.com (Technically Sweet)
Subject: Re: Does 386BSD work on systems with 20 megabytes of memory! HELP!
Organization: International Foundation for Internal Freedom
Distribution: comp.unix.bsd
Date: Thu, 31 Dec 1992 20:13:47 GMT


It should be feasible to hack the standard I/O library to get 
always get disk buffers below the 16 meg mark.  Maybe the
mmap() call can help here?  Is there any paging control?
This would make 99% of the system utilities perform well.

-- 

Lance Norskog

Data is not information is not knowledge is not wisdom.
Newsgroups: comp.unix.bsd
From: bde@runx.oz.au (Bruce Evans)
Subject: [386BSD] Happy old year!
Organization: RUNX Un*x Timeshare.  Sydney, Australia.
Date: Fri, 1 Jan 93 12:07:02 GMT

The new year started fairly early in Australia.  But 386BSD-0.1 had two
Dec 31, 1992's.  I cut the second one short after 22.5 hours using this
fix.

*** clock.c~	Wed Dec 25 09:23:24 1991
--- clock.c	Thu Dec 31 22:34:16 1992
***************
*** 87,92 ****
  	unsigned long ret;
  
! 	ret = 0; y = y - 70;
! 	for(i=0;i<y;i++) {
  		if (i % 4) ret += 365*24*60*60;
  		else ret += 366*24*60*60;
--- 88,93 ----
  	unsigned long ret;
  
! 	ret = 0;
! 	for(i = 70; i < y; i++) {
  		if (i % 4) ret += 365*24*60*60;
  		else ret += 366*24*60*60;
***************
*** 146,150 ****
  	sec += bcd(rtcin(RTC_MIN)) * 60;			/* minutes */
  	sec += bcd(rtcin(RTC_SEC));				/* seconds */
- 	sec -= 24*60*60; /* XXX why ??? */
  
  #ifdef notdef
--- 147,150 ----
-- 
Bruce Evans  (bde@runx.oz.au)
Newsgroups: comp.unix.bsd
From: dfox@quack.sac.ca.us (David Fox)
Subject: [386bsd] happy new year
Keywords: clock.c patch
Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'.
Date: 3 Jan 1993 01:27:36 UTC

Hi.

I've tried both Andrew Chernov's and Bruce Evans' patches for the
'happy new year' problem where the date was repeated - i.e., on
Jan 1 93, 386bsd reports the date as 12/31/92.

I don't experience the problem as such.  On my 386bsd, I get two
Jan 1 dates - on Jan 2 (today), 386bsd reports the date as Jan 1.

Bruce says it might be because of timezone differences, nevertheless,
I've tried both patches, and neither works for me.  With the patch
installed (doesn't matter which one), the date returned is 'Mon Jan 6';
clearly incorrect.
 
 If it helps, I can post my clock.c.
Newsgroups: comp.unix.bsd
From: jkizi01@convex.zdv.uni-tuebingen.de (M. Class)
Subject: Two questions: COM, SLIP
Keywords: COM SLIP
Organization: Comp. Center (ZDV) U of Tuebingen, FRG
Date: Sun, 27 Dec 1992 09:40:17 GMT

Hi out there,

I am working now for two weeks again with 386bsd, and almost
everything is working fine. But there are still two unresolved
Problems.

1. COM-ports: I am using the COM-Multiport-Driver and 16550-USARTs.
	Im still getting SILO-Overflow's at 38400 Baud. Due to the 
	fact that I am using a 14400 Baud Modem with V42bis, I would
	want to use the fastest possible COM-Speed. 

	Question: Is there a driver (or driver-configuration) that will
		work at these speeds? What will happen if i'd change
		FIFO_TRIGGER_4 to 8 or 14 in the Multiport-driver.
		Are the lost chars due to getting too many interrupts,
		or is the response-time to a given interrupt to long?
		Will a COM-Driver that uses CTS/RTS do any better?

2. SLIP: (or even better routing between SLIP and WE0)
	My machine is setup to use an WD8003E-Card as an Ethernet-
	interface. One other PC is connected via SLIP. Each of the
	interfeaces works fine. But the requests dont get routed
	towards the different networks (Etherent, SLIP). The route-
	Manualpage states that this is done automaticly. I suspect
	that I am doing something wrong. Would someone be so kind
	and explain to me what I have to do to get the routing to work?
	Thanks!

For the first Question I think I should add that the Machine is NOT
heavily loaded, has 16 Megs of RAM and an 486/33Mhz.


Thanks a lot for not getting tired in answering dumb questions.


Michael Class   jkizi01@convex.zdv.uni-tuebingen.de
From: ppan@nobeltech.se (Per Andersson)
Newsgroups: comp.unix.bsd
Subject: Re: Dumb Americans (was INTERNATIONALIZATION: JAPAN, FAR EAST)
Keywords: Han Kanji Katakana Hirugana ISO10646 Unicode Codepages
Date: 30 Dec 92 01:02:16 GMT
Organization: NobelTech AB

In article <2564@titccy.cc.titech.ac.jp> mohta@necom830.cc.titech.ac.jp (Masataka Ohta) writes:
>
>Do you know that Japan vote AGAINST ISO10646/Unicode, because it's not
>good for Japanese?
>
>>So even if the Unicode standard ignores backward compatability
>>with Japanese standards (and specific American and European standards),
>>it better supports true internationalization.
>
>The reason of disapproval is not backward compatibility.
>
>The reason is that, with Unicode, we can't achieve internationalization.

But, what has Unicode got to do with ISO-10646 ? Has the promised (very much
needed IMHO) revision of Unicode arrived ? (1.1). Unicode is a 16bit character-
set which I know did ugly things with asiatic languages. I thought 10646,
which is a 32bit standard (by ISO !) did not, except for doing something
the turks didn't like, don't remember what it was. Enlighten me !

/Per
-- 
-----------------------------------------------------------------------------
Per Andersson - ppan@nobeltech.se (perand@stacken.kth.se on free time)
Managing networks at, but not speaking for Nobeltech AB, J{rf{lla, Sweden
-----------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: grefen@convex.com (Stefan Grefen)
Subject: Re: Does 386BSD work on systems with 20 megabytes of memory! HELP!
Reply-To: grefen@convex.com
Organization: CONVEX Computer Corporation
Distribution: comp.unix.bsd
Date: Wed, 30 Dec 1992 08:49:05 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

In article <1992Dec29.165705.28771@Informatik.TU-Muenchen.DE>, gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart) writes:
|> In article <1992Dec29.082629.3222@convex.com> grefen@convex.com writes:
|> >In article <287902vW30DE01@JUTS.ccc.amdahl.com>, tjw00@zombie.uucp (Tom Wye) writes:
|> >|> Does 386BSD work on machines with 20 megabytes of memory or more? HELP!!!!
|> >|> 
|> >You need an  Adaptec 174x (EISA) or change the code in the driver to use a 
|> >buffer and copy the data for requests outside the first 16M.
|> 
|> I had the same problem and heard about the problem with first 16M and the 1542.
|> So I put only 16M to my box. Now my question is, does Julian's SCSI-Kit
|> handle that correctly, e.g. does it use such buffers to avoid direct access
|> to memory above the 16M ?
No not yet, go and fix it it's not too hard ... but your system will behave
funny (at least if you do benchmarks).
|> 
|> Ralf
  Stefan
Newsgroups: comp.unix.bsd
From: duzan@sol.cis.udel.edu (Gary D. Duzan)
Subject: 386BSD and VESA?
Organization: Your Organization Could Be Here!
Date: Sat, 26 Dec 1992 18:13:34 GMT

   I'm starting to look into various systems for home use, and I was
wondering if 386BSD currently supports VESA bus cards, especially video
and SCSI. The unofficial FAQ talks about EISA and MCA, but not VESA.
If it is not supported, is anyone working on it? Thanks.

                                        Gary Duzan
                                        Time  Lord
                                    Third Regeneration
                         Humble Practitioner of the Computer Arts



-- 
                             duzan@cis.udel.edu
   _o_                       ------------------                         _o_
 [|o o|]       Virtual Reality? No thanks, I've already got one.      [|o o|]
  |_O_|       Disclaimer: I have no idea what I am talking about.      |_O_|
Newsgroups: comp.unix.bsd
From: adrian@rachel.ibmpcug.co.uk (Adrian Hall)
Subject: Re: New kernel on rachel.ibmpcug.co.uk
Organization: The IBM PC User Group, UK.
Date: Wed, 23 Dec 1992 18:24:25 GMT

rivers@ponds.uucp (Thomas David Rivers) writes:
> 
> Well, enough requests, etc... have been posted recently to warrant
> (at least in my opinion) a repost of this driver.
> 
> Finally, we need to provide a *fixed* major # for the printer - I'm
> getting tired of moving it around for every new driver that comes up...
> 
> Currently mine is set to 16.

This driver is now currently set up as major device 16 in the kernel
on rachel.ibmpcug.co.uk.

Anyone think there is a call for a central "person" who gives out
major device numbers to those developing device drivers?

	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
From: cwa@oasis.icl.co.uk (Chris Adams)
Newsgroups: comp.unix.bsd
Subject: Will 386BSD work with mine?
Date: 23 Dec 92 09:49:44 GMT
X-Newsreader: Tin 1.1 PL3

I have a reasonable PC:

20MHz 386sx
4Mb RAM
200Mb HD
VGA

Will this be enough to run 386BSD (and probably X) ok? or do I need more RAM/
disk space/power?

Also, how much disk space does the base installation take?

Thanks

     .-----------------------------.----------------------------------.
     |   .  .     ____    _   _    | WARNING: This Superman suit does |
     |  /| /| .-.    /   |_| |_>   | not enable the wearer to fly.    |
     | / |/ | |     /___ | | |     `----------------------------------|
     |      aka Chris Adams            cwa@getafix.oasis.icl.co.uk    |
     `----------------------------------------------------------------'
Newsgroups: comp.unix.bsd,alt.suit.att-bsdi
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: AT&T/USL CD-ROM Review Process
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Wed, 23 Dec 1992 14:10:20 GMT

In article <1992Dec22.140345.545@crd.ge.com>, davidsen@ariel.crd.GE.COM (william E Davidsen) writes:
| In article <wilko.724689346@spoetnix.idca.tds.philips.nl>, wilko@russia.idca.tds.philips.nl (Wilko Bulte) writes:
| | Yuck. All this makes me feel infected: I've seen AT&T and SCO source. Will
| | this make me forever a no-go for GNU-ish software?
| 
|   Didn't they tell you that after you see the source they have to kill you?

Of course, seeing GNU code will forever infect you so that you can never write
for-profit code.  

What we need is a sanatarium for infected programmers.  They also need to be
re-trained, say to become telephone disinfectors or IRS inspectors.  Perhaps 
this will be part of Billy's new health and economics plans?

-- 
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA
Newsgroups: comp.unix.bsd