HDTenEightyP/NetNews huggingface dataset:
From: merlin@neuro.usc.edu (merlin)
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Date: 14 Aug 1992 12:20:21 -0700
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: neuro.usc.edu

In article <l8n8qcINN2c5@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:

>Boo!  Hiss!  cgd !!!

That should have been:

    "Boo!  Hiss!  cgd !!!     :-) "

Chris has been doing a yeoman's job of taking care of bug reports, patches,
and updates.  He is really making an outstanding contribution.  I didn't
mean to castigate him personally -- I was trying to make the point that any
claims of individual property rights in material integrated into 386BSD-0.1
or 4.3BSD-NET2 may have an extremely adverse impact on the overall concept.

Chris, Bill, and Lynne are making a major contribution to academia.  I hope
they will see tangible reward for their efforts.  I certainly am going to
send them some small contribution which I can afford.  Perhaps others will
be able to help them continue this work with similar contributions, grants,
contracts, or other side benefits which might help them regain some of the
losses they have endured to carry this work to a quite usable product.

------------------------------------------------------------------------------
Alexander-James Annala
Principal Investigator
Neuroscience Image Analysis Network
HEDCO Neuroscience Building, Fifth Floor
University of Southern California
University Park
Los Angeles, CA 90089-2520
------------------------------------------------------------------------------
From: peter@micromuse.co.uk (Peter Galbavy)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD 0.1 keyboard problems on laptop...
Date: 12 Aug 92 14:32:14 GMT
Organization: MicroMuse Limited, London, England.

peter@micromuse.co.uk (Peter Galbavy) writes:

>The keyboard is supposed to work like any other, and they are running
>commercial *NIX on it OK. Anyone seen this ? I have looked around in
>pccons.c and the like, tries checking return codes from the kbd_cmd
>etc, but all seems OK.

Found the solution !!!

I took the kbdreset() function from i386/stand/kbd.c and replaced the
code that resets the keyboard in pccons.c (pcprobe() ?), and all
is now OK. The extra lines to "defeat gate a20" (will someone *please*
explain what A20 is ?) seem to make the differnce.

Have fun now,
-- 
Peter Galbavy
Tech Support, Micromuse Ltd
Phone: +44 71 352 7774		E-Mail: P.Galbavy@micromuse.co.uk
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: SUMMARY of answers to: "how to label partition to 386BSD?"
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Fri, 14 Aug 1992 15:02:20 GMT

WRT the standard single hard drive configuration:

I don't understand why people what to go to all that *unnecessary* effort:
just do what the instructions tell you to do!!!

If you want a DOS partation and a 386BSD partition:

  1) Fdisk a DOS partition for your dos stuff. 

  2) Boot TinyBSD and Install.

That's it!!!  DON'T CREATE OTHER PARTITIONS using fdisk, DON'T RUN
DISK EDITORS, or anything.  The install procedure will notice that
you have free space on your disk that is not assigned to any partition, 
and will do the right thing.

-- 
---
 Robert Withrow, R.W. Withrow Associates, Swampscott MA 01907 USA
 Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
From: brendan@cygnus.com (Brendan Kehoe)
Newsgroups: comp.unix.bsd
Subject: time for comp.unix.bsd.386
Date: 21 Aug 92 21:38:52 GMT
Reply-To: brendan@cygnus.com
Organization: Cygnus Support, Palo Alto, CA


Any reason not to start a discussion for creating comp.unix.bsd.386?
(For the many people who are interested in geeric BSD issues, but
could care less about device drivers in 386BSD, etc.)

--
Brendan Kehoe                                               brendan@cygnus.com
Cygnus Support, Palo Alto, CA                                  +1 415 322 3811
                       Oooh! A handsome stranger! And me, without my shoes on.
                                     --The Princess, The Emperor's New Clothes
From: bob@obiwan.uucp (Bob Willcox)
Newsgroups: comp.unix.bsd
Subject: Re: Using Swap partition on 2nd drive?
Date: 13 Aug 92 03:28:38 GMT
Organization: Bob's Place, Austin TX

In article <1992Aug9.070714.5380@news.tu-graz.ac.at> chmr@fstgds01.tu-graz.ac.at (Christoph Robitschko) writes:
>In article <1992Aug8.233253.3870@BitBlocks.COM> bvs@BitBlocks.COM (Bakul Shah) writes:
>>bob@obiwan.uucp (Bob Willcox) writes:
>>
>>>swapon: /dev/wd1b: Device not configured
>>
>>>Can someone please tell me what I have failed to do or done wrong?
>>>I am quite new to BSD systems and have run out of ideas.
>>
>Bob, I can verify that your configuration file and swap386bsd.c are right.

My system is now working fine with swap partitions on both disks.
My problem turned out to be related to my specification of the sf
flag in the disktab entry for my second disk.  Or, at least, when
I removed this flag, and re-disklabeled the disk it began working.
There is obviously alot that I don't know about bad block handling
with bad144.  I have both of my (ESDI) disks formated with sector
sparing so that they present an error-free view to the system.

<bunch of stuff about the patch deleted...didn't seem to be the problem>

>All I can say is that it works perfectly for me. (With swap on both disks).

For me as well now. Thanks.

>
>							Christoph
>-- 
>------------------------------------------------------------------------
>Christoph M. Robitschko  | "the only man who got his work done by Friday
>chmr@edvz.tu-graz.ac.at  |             was Robinson Crusoe."


-- 
Bob Willcox           ...!{rutgers|ames}!cs.utexas.edu!uudell!rancor!obiwan!bob
Phone: 512 258-4224 (home)
       512 838-3914 (work)
Newsgroups: comp.unix.bsd
From: colin@marsh.cs.curtin.edu.au (Colin Manning)
Subject: IDE HARD WRITE ERRORS PLEASE HELP ME
Keywords: IDE ERRORS
Organization: Curtin University of Technology
Date: Wed, 19 Aug 1992 04:17:07 GMT

Hi,
My setup:
386DX 33MHz
AMI BIOS (04/09/90)
fd0: 1.44MB
fd1: 1.2MB
RAM: 4M
wd0: MAXTOR 7040 AT (40MB IDE)
wd1: MAXTOR 7040 AT (40MB IDE)
	Two Questions:
1)  wd1 has three areas that get hard write errors.  What do I do?

2)  My disktab entries for the drives reserve 5 cylinders on each drive
for bad sector mapping.  I read that one shouldn't use bac144 with IDE
drives.  Does that mean that I don't need to reserve the 5 cylinders?

advthanksance
(thanks in advance)
Colin
------
colin@cs.curtin.edu.au
Newsgroups: comp.unix.bsd
From: rminnich@super.org (Ronald G Minnich)
Subject: Re: 386BSD won't boot off Compaq 386sx/16
Organization: Supercomputing Research Center (Bowie, MD)
Date: Wed, 19 Aug 1992 14:42:26 GMT

In article <1992Aug17.190759.8713@hotb.sub.org> thomas@hotb.sub.org (Thomas Brettinger) writes:
>I tried to install 386BSD on a Compaq 386sx/16, with Numeric
>Coprocessor, 5M Ram, 84M Conner IDE Harddisk.
>The screen stays black, and the machine reboots after reading some
>tracks from the floppy. And reboots, and reboots....

yup, 0.0 dist.fs boots fine, but you can not build a boot
track for floppy from 0.0, nor can you boot 0.1 dist.fs at all. 
You are not alone. something weird about compaqs, i have heard about
this from 486, 386, everybody with one of those !@#$#@$! compaqs. 
There is one guy i have heard from, who has many compaqs, and precisely
one of these machines will boot 0.1! it is in no known way different.

for what it is worth, bsdi stuff will boot on a compaq, according
to bsdi, and this has been tested by no less than COMPAQ itself. 
I don't have the time to fool with these machines so am 
going to drop a kbuck on bsdi and stop beating my head against the wall.
ron
-- 
--------------------------------------------------------------------------------
satisfaction: the feeling you get when you        | rminnich@super.org
run newfs on a DOS disk so you can install 386BSD.| (301)-805-7451
Now if only I could do this to AIX on the RS/6k ...|
From: lm@slovax.Eng.Sun.COM (Larry McVoy)
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Date: 18 Aug 1992 06:01:22 GMT
Organization: Sun Microsystems, Inc.  Mt. View, Ca.
NNTP-Posting-Host: slovax

allard@isi.edu (Dennis Allard) writes:
: So, you might argue, that prevents shrink wrapping since noone would
: buy it.  I wonder about that.  The advantages to shrink wrapping,
: viz., on the shelf availability, quality bound documentation, tech.
: support for registered owners, update mailing list membership, etc.
: are often worth the price of shrinkwrap, even if a free copy (or
: stolen copy, in the case of noncopyleft material) is avaiable at no
: charge.

This is, by the way, exactly how Borland made their money off of Turbo
Pascal on CPM machines (yeah, way back when).  There was a pascal
compiler out there that cost $500 or so and then Borland came along
with the $50 Turbo Pascal package.  They did one very smart thing - the
manual is a paperback book, not an easily copied looseleaf binder.
People were typically willing to let you copy the disks but people got
really pissed if you were to borrow their docs and return them trashed
from copying them.  The general attitude was "look, it's reasonably
priced, go get a copy and leave me alone".

I personally would find $50-100 for access to compiled and tested major
releases of X, gcc, 386BSD, etc., quite reasonable.  I like having
source, but I have real work to do - I don't want to sit around
babysitting gcc through yet another compile.

I think there is a market for freeware that costs money.
---
Larry McVoy			(415) 336-7627			 lm@sun.com
From: bvs@BitBlocks.com (Bakul Shah)
Newsgroups: comp.unix.bsd
Subject: Re: Motif on X386???
Date: 18 Aug 92 17:48:02 GMT
Organization: Bit Blocks, Inc.

terry@cs.weber.edu (A Wizard of Earth C) writes:

>I also saw problems with menus not coming active unless you let go of the
>button popping up the menu, then quickly pressed it again (not in the menu
>area) to get the menu selection bar to follow the mouse.

Make sure you are using the latest com.c driver (with select()
bug fixed).  But even then there is some problem with the mouse
code in X386 as the very first button press is not seen until
after you either release the button or move the mouse a bit.

If you wish to track this problem down, check out file
$X11R5/mit/server/ddx/x386/x386Io.c.  Routine x386MseEvents()
seems to be the culprit.

-- Bakul Shah <bvs@bitblocks.com>
Newsgroups: comp.unix.bsd
From: paigen@tfs.com (David Paigen)
Subject: 386bsd doesn't recognize my (non-scsi) tape
Organization: TRW Financial Systems
Date: Fri, 14 Aug 1992 13:59:16 GMT

386bsd doesn't recognize my tape drive on bootup, nor does it
find it when I access /dev/rwt0.  The table in the install notes
specify 0x300, irq 5, drq 1, while SCO Unix reports 0x338-0x33c,
irq 5, drq 1.

This is a standard wangtek, QIC-36 interface drive, and the standard
wangtek QIC-36 interface.  I don't have a manual for the board or
drive, and I haven't pulled it to look for jumpers yet.

Does anyone know if I can jumper the board to work off of 0x300?
Or can someone supply me with a kernel that expects the tape drive
at 0x338?

Second Problem:
I have searched hard yet, but I don't think my second disk has been
recognized.  I am using cgd's 'newbootables'.  Bootup reports a wd0,
but not a wd1.  Both drives are Maxtor MFM hanging off of the same
controller card.

----------------------->"Lay on, McDuff,    14th c. ideals in a 21st c. world
David Paigen            and damn'd be he        N: PLO Bush IRA CIA KKK
TRW Financial Systems   who first cries,        S: terrorism pipe bomb kill
paigen@tfs.com          'hold, enough!'"        A: assasination maim
From: dxper@dtek.chalmers.se (Per Anders Olausson)
Newsgroups: comp.unix.bsd
Subject: Re: Bug Report: Missing strtod in 386BSD, plus code
Date: 18 Aug 92 22:46:35 GMT
Organization: Chalmers University of Technology, Gothenburg Sweden

karl@NeoSoft.com (Karl Lehenbauer) writes:

>hlu@phys1.physics.wsu.edu (Hongjiu Lu) writes:
>Please don't use it. The code is a joke. Please send a note to
>David M. Gay at dmg@research.att.com. He has what you want.

>It's not like it calls scanf or something.  I can't read your mind.  What
>is wrong with it?  And why don't you just post the code?

  By the look of the email address I think you really don't have to ask why.

  It probably carries a nice AT&T copyright header + the usual "use this
and we'll have your head on a plate" message.

  Just a wild guess. I could be right or I could be AT&T.

pao


--
-------------------------------Andrew Olausson--------------------------------
--------------------------Unemployed Unix Specialist--------------------------
------------------------------pao@cd.chalmers.se------------------------------
-------------------------------pa-ola@proxxi.se-------------------------------
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd install program :-)
Date: 19 Aug 92 11:32:33 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <RAEBURN.92Aug19005834@cambridge.cygnus.com> raeburn@cambridge.cygnus.com (Ken Raeburn) writes:

>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

No problem. Just try to install 386BSD on a 386 system without any
hard disk. Perhaps we might consider making a kernel image with
a memory file system for diskless 386-PCs with 64MB main memory ;-)

Holger

-- 
|  |   / Holger Veit             | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
From: comrade@uniwa.uwa.edu.au (Peter Cooper)
Newsgroups: comp.unix.bsd
Subject: Re: time for comp.unix.bsd.386
Date: 23 Aug 92 05:26:05 GMT
Organization: University of Western Australia

jiu1@husc9.harvard.edu (Haibin Jiu) writes:

>In article <34254@hoptoad.uucp> brendan@cygnus.com writes:
>>
>>Any reason not to start a discussion for creating comp.unix.bsd.386?
>>(For the many people who are interested in geeric BSD issues, but
>>could care less about device drivers in 386BSD, etc.)

>Someone please do this!!!!!!  People like me who use true 4.xBSD
>UNIX need this group to talk about issues that concern 4.xBSD in
>general.  There has been just too much on 386BSD (which I abandoned

It looks to me like it's time.  Will c.u.bsd still have enough traffic
to make it a viable group?  I think so.  Discussions on the 68k port,
stuff on NET/2 (including the pending legal action) should keep it
ticking along - and I think quite a few people will be happy NOT to have
to skip the 386BSD/BSDI386-related discussions.  I can't understand why,
though ;-)

Peter
-- 
email:  comrade@uniwa.uwa.edu.au   snail:  Peter Cooper, box 22
fax:    +61 9 380 1041                     Guild of Undergraduates
phone:  +61 9 380 3929                     University of Western Australia
"It was the banana that did it!" - Julia Marley
From: alm@netcom.com (Andrew Moore)
Newsgroups: comp.unix.bsd
Subject: lpd and whatis fixes (trivial)
Date: 20 Aug 92 04:10:16 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest)

For the sake of completeness...

Printing man pages with lpr (e.g., man X | lpr -h) would cause a
reboot.  The problem was solved by recompiling lpd. This may only be
necessary if kvm.c was patched (e.g., after applying David Greenman's
kvm.c patch).  I am also using Haug's lpt patch from agate, and Chris
Flatters' patch to lptprobe() in lpt.c.


*** /usr/src/usr.bin/man/whatis/whatis.c.orig	Tue Aug 18 18:00:08 1992
--- /usr/src/usr.bin/man/whatis/whatis.c	Tue Aug 18 17:57:44 1992
*************** main(argc, argv)
*** 65,70 ****
--- 65,71 ----
  	char *p_augment, *p_path, **getdb();
  
  	progname = "whatis";
+ 	p_augment = p_path = NULL;
  	while ((ch = getopt(argc, argv, "M:m:P:")) != EOF)
  		switch((char)ch) {
  		case 'M':
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on free UNIX / 386BSD (R
From: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats
Date: Thu, 20 Aug 1992 04:02:22 GMT
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)

In article <1992Aug18.234401.2087@nrao.edu> cflatter@nrao.edu writes:
>In article 8526@fcom.cc.utah.edu, terry@cs.weber.edu (A Wizard of Earth C) writes:
>>Does [the GPL] mean that I can't sell my own program (we'll call it '/usr/bin/true')
>>for $500.00, and then give away GNU Hurd in order to run it, but don't tell
>>anyone what the program is (except you all know now ;-)), offer to send source,
>>like in GPL, but say they can't copy it because they can't distinguish my
>>part from GNU's part?
>
>You don't have to supply source for your own /usr/bin/true because you stuck
>it in the same packet with the GNU Hurd (unless of course it is a modified
>version of a GNU /usr/bin/true).  You still have to supply source for the
>Hurd and you can not restrict the rights of anyone who gets the source from
>you to make further copies of the Hurd source.
>
>>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. Even a lawyer would think that that was silly.


From what I understand, the Hurd, in and of itself, is not really an OS,
but a UNIX-like environment that will sit on top of Mach 3.0.  Part of the
duo will be controlled by CMU licensing specifications, and part by the
GPL.  Since the Hurd will assuredly use the GNU libc.a, it would seem that
all binaries would come under the separate GPL library license.  What is the
difference between the libc.a license and the "normal" GPL?

-- 

Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
From: ianr@muppet.bt.co.uk (Ian Robertson )
Newsgroups: comp.unix.bsd
Subject: 386BSD 3.5 floppy1 dosent fit
Date: 12 Aug 92 11:17:28 GMT
Reply-To: ianr@muppet.bt.co.uk
Organization: British Telecom

I got a copy of the first floppy of 386BSD via an ftpmailer
however after concatetanating the files , removing the mail
headers and uudecoding the size is 1514319 this dosent fit
using dd onto a high density 3.5 floppy.

What am I doing wrong ??

Please email
From: richard@aiai.ed.ac.uk (Richard Tobin)
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on 'free' UNIX / 386BSD (R
Date: 18 Aug 92 13:09:36 GMT
Organization: AIAI, University of Edinburgh, Scotland

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, no more than any application that runs under SunOS falls under Sun's
licence.

It would probably be better if you didn't suggest this to USL's lawyers :-)

-- Richard
-- 
Richard Tobin,
AI Applications Institute,                                R.Tobin@ed.ac.uk
Edinburgh University.
From: cs@Germany.EU.net (Chris Schmidt)
Newsgroups: comp.unix.bsd
Subject: Re: where to get 386bsd 0.1 in europe
Date: 14 Aug 1992 12:40:50 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

In article <5045@tuegate.tue.nl>, wswire3@rw9.urc.tue.nl (G. van Rooij) writes:
> I didnt see a FAQ mentioning all ftp-mirrors of agate (but I didnt read
> all of the newsgroup yet). Is there a list a european ftp-sites for
> 386bsd v0.1?

Try ftp.Germany.EU.net ~ftp/pub/comp/i386/386BSD-0.1

	Chris 
                             
            EUnet-Support-Infoserver  +   EUnet-Support-News 
     Universitaet Dortmund, IRB, Postfach 500 500, D-4600 Dortmund 50
                   cs@Germany.EU.net (Chris Schmidt)
                        Tel. : +49 231 755 2444

/* Unix is a registered trademark of AT&T in the USA and other countries. */
/*                    AT&T is a modem test command.                       */
From: pjangli@afterlife.ncsc.mil (Philip Anglin)
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Date: 18 Aug 92 21:41:21 GMT
Organization: The Great Beyond

In article <1992Aug18.155958.3671@murdoch.acc.Virginia.EDU> gsh7w@fermi.clas.Virginia.EDU (Greg Hennessy) writes:
>In article <GTFIR8A@taronga.com> peter@taronga.com (Peter da Silva) writes:
>#And while it's [MSDOS] a screaming horror from
>#the sewers of hell, it *does* run out of the box without any diddling, and
>#has a zillion applications for it.
>
>Then how come every time my brother wants to install a new program, I
>have to use EDLIN to edit the config.sys file on his pc?
>
And how come I have to wrestle with add-on memory managers to
use anything beyond 640K?  How come I have to severely limit
the number of network drivers, device drivers, tsr's, etc, that
I have loaded, lest I run out of memory?  I've done a heck of a
lot more "diddling" with my PC than I have with my SparcStation.
At least Unix uses all its available memory right out of the box.

-- 
/***************  pjangli@afterlife.ncsc.mil (Philip J. Anglin)  **************/
/* Disclaimer: My employer doesn't speak for me, and I don't speak for them.  */
/*             Views expressed are mine alone...  Boy, are they ever! ;-)     */
/* Cute Quote: "Intel: Putting the 'backward' in 'backward compatibility'."   */
Newsgroups: comp.unix.bsd
From: tgt@neon.ecn.purdue.edu (Conan the Librarian)
Subject: SCSI driver bug when accessing DOS partition
Organization: Purdue University Engineering Computer Network
Date: Wed, 19 Aug 1992 02:05:35 GMT

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"

I have verified that the zone I wish to begin reading is the beginning of
the DOS partition, via "dd if=/dev/ras0d ...".  The driver is bombing when
attempting to initially read the FAT, which is 160 sectors (2 sectors/MB).
When I limit disk_read() to attempt no more than 80 sectors per any given
read attempt (1/2 the FAT on the first attempt), things works (mdir is able
to get enough of the FAT and then the main directory entry to show me what is
on the disk).

I am running with this "hack" right now, which is ok until I start filling
up the DOS partition with files.  Any driver hackers out there care to take
a crack at a real fix for this one??

Thanks very much.

-tom

--
Tom Tobin				UUCP:     pur-ee!tgt	
Dept. of ChE				INTERNET: tgt@ecn.purdue.edu
Purdue University			Ma Bell:  home (317) 463-0189
W. Lafayette, IN 47907				  office "   494-4052