HDTenEightyP/NetNews huggingface dataset:
From: fhg2@cunixb.cc.columbia.edu (Farhan H Garib)
Newsgroups: comp.os.linux
Subject: Re: HELP! Problems with rootimage.
Date: 9 Apr 92 19:49:22 GMT
Article-I.D.: cunixf.1992Apr9.194922.10252
Reply-To: fhg2@cunixb.cc.columbia.edu (Farhan H Garib)
Distribution: comp
Organization: Columbia University

In article <1992Apr8.210115.5364@vax.oxford.ac.uk> tony@vax.oxford.ac.uk writes:
>In article <TSILLANP.92Apr7144847@blob.hut.fi>, tsillanp@niksula.hut.fi (Timo Jaakko Sillanp{{) writes:
>> ...
>
>> Am I doing something totally wrong? 
>> I get rootimage.Z from nic.funet.fi (yes, binary mode is on),
>> uncompress it and write it to a floppy disk (1.44Mb) using
>> rawrite.exe. 
>
>the rootimage is (I think !) for a 1.2Mb floppy.  Try to find a rootimage for a 
>1.44 disk - this could be the problem ...
>
>Tony
>
>						    _
>Tony Kew,   Oxford University Computing Services,  (_)xford,  England,  U.K.
>====================================================|=========================
>Janet:- tony@uk.ac.oxford.vax                     --+--    Disclaimer :-
>Internet:- tony%vax.oxford.ac.uk@nsfnet-relay.ac.uk | Who is the more foolish?
>Earn/Bitnet:- tony%vax.oxford.ac.uk@ukacrl	    |    The fool, or the
>Phone:- +44 (0)865 273268   Fax:- +44 (0)865 273275 |  man who follows him?
>==================================================\=|=/=======================
>						   \|/




I use 1.44MB floppies without a problem.

-Greg
Newsgroups: comp.os.linux
From: britt@leland.Stanford.EDU (Britt Park)
Subject: libtermcap.a bugs?
Summary: Are there known bugs in libtermcap?
Keywords: termcap libtermcap 
Organization: DSG, Stanford University, CA 94305, USA
Date: Tue, 7 Apr 92 22:52:11 GMT


I was trying to compile my much beloved version of uEmacs 3.8, (I've made
several changes to it and am very fond of it.) and found that it compiles
but doesn't work under GCC 1.40.  Does the GCC 1.40 libtermcap have a known
bug in it?  I've traced the problem to that vicinity.  Thanks.

					Britt
					britt@cb-iris.stanford.edu
From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Newsgroups: comp.os.linux
Subject: Dr DOS and fdisk 0.91
Date: 14 Apr 92 12:27:58 GMT
Followup-To: LeBlanc@mcc.ac.uk
Organization: Computing Centre, University of Manchester

Someone reported recently that the Linux/Minix partitions
created by my fdisk 0.91 are recognised as DOS partitions
by Dr. DOS 6.0.  I suspect what is happening is that
Dr. DOS is ignoring the high bit of the type field.  If
this is so, it should certainly be reported to the Dr. DOS
suppliers, since it will cause problems for MINIX users
as well.  The 8-bit field contains 00000001 for a DOS partition
with a 12-bit FAT, and 10000001 for MINIX/Linux.  You can
always change to another number, e.g., 0x41, which I expect
even Dr. DOS will let alone.

A bug in the version of fdisk 0.91 makes it delete partition
5 incorrectly.  This bug is fixed in fdisk 0.92, which I shall
be distributing soon.

     -- Owen
     LeBlanc@mcc.ac.uk
From: books@fsunuc.physics.fsu.edu (Roger Books)
Newsgroups: comp.os.linux
Subject: Re: Help, can't compile 0.95a!
Date: 3 Apr 92 03:40:20 GMT
Article-I.D.: mailer.1992Apr2.224021.9407
Reply-To: books@fsunuc.physics.fsu.edu
Organization: F.S.U. Dept of Physics
News-Software: VAX/VMS VNEWS 1.3-4

In article <magister.702263905@garfield.catt.ncsu.edu>, magister@garfield.catt.ncsu.edu (Mike Dodds) writes...
>nicolai@lysator.liu.se (Nicolai Wadstr|m) writes:
> 
>>I'm unable to compile Linux 0.95a, I have installed the new sources
>>and bootup with the 0.95a binary kernel image, using the old gcc (1.40?),
>>and I get and error "cc1 got return code 16" when compiling fork.c!
>>Does this anything to to with the old gcc compiler? Or do I need new library
>>for 0.95a?
>Well,	

  Worked fine for me.  I'm using a 486 with 4MB of ram and 4MB of swap space.
I also saw mentioned somewhere that Linus was converting to gcc 2.0 (now 2.1).
I am using 2.1

			Roger

			books@fsunuc.physics.fsu.edu
Newsgroups: comp.os.linux
From: jeng@ipanema..bellcore.com (Fureching Jeng)
Subject: expr
Keywords: Softscroll
Reply-To: jeng@ipanema.UUCP (Fureching Jeng)
Organization: Bellcore MRE
Date: Wed, 15 Apr 92 17:53:01 GMT

I have installed gcc 2.1 on my machine. Unfortunately, I can't run g++ without

"expr". Does anyone know where I can get "expr"?


Thanks,

FC


Newsgroups: comp.os.linux
From: bjones@magnus.acs.ohio-state.edu (William A Jones)
Subject: Modems and com port access
Organization: The Ohio State University
Date: Fri, 10 Apr 1992 23:35:41 GMT

Now that I have a copy of UUCP for linux, I decided that it was time to
see if my modem worked properly.  So, I scanned all of the digest entries
that had anything to do with the modem and decided that, under version
0.95c+, COM2 was assigned to /dev/ttys2.

Following the FAQ, I put the following line in /etc/inittab

ttys2:console:/bin/getty -m 1200 ttys2

and rebooted.  So far, so good.

Now, kermit, uucico, pcomm, and everything else will not recognize that
a modem exists.  What have I done wrong?

If someone who has a working kermit, uucp, etc., would send detailed(!!)
instructions on how to get set up I would be very grateful.

Bill

===================================================================
bjones@cambria.UUCP		..!osu-mps!cambria!bjones
bjones@magnus.acs.ohio-state.edu
===================================================================
From: knapka@athena.cs.uga.edu (Joseph Knapka)
Newsgroups: comp.os.linux
Subject: Writing a device driver
Date: 9 Apr 92 23:34:11 GMT
Organization: University of Georgia, Athens

Hello, all...

I'd like to write a device driver for my Trident VGA card, so I could
implement something like Sun's pixrect library under Linux. Could
someone versed in such arcane endeavors perhaps email me a reference
or two to some good literature on device-driver writing? How do people
learn this stuff, anyhow? :-)

Thanks in advance for any pointers,

Joseph
Newsgroups: comp.os.linux
From: jwinstea@jarthur.claremont.edu (Jim Winstead Jr.)
Subject: Re: tar files on floppy.
Organization: Harvey Mudd College, Claremont, CA 91711
Date: Tue, 14 Apr 1992 23:04:18 GMT

In article <1992Apr14.200059.27535@nmrdc1.nmrdc.nnmc.navy.mil> rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson) writes:
>I am just about finished with linking everything in 2.1shared-A.tar.Z with
>shared libs and symlinking into /usr/bin.  A word of caution, DON'T use
>shared libs or symlinks on anything in /bin or /etc if / and /usr are on
>different partitions.  They won't work until /usr is mounted.  Keep a good
>bootimage floppy and root floppy handy just in case.

As long as /lib is on your root partition, and /lib/lib92.04.* is
actually present in that directory, and *not* a sym-link, you can use
shared binaries in /bin just fine.  /lib/lib92.04.* really shouldn't
be symlinked....

The idea of keeping a good boot disk and root disk is valid, though.
I've had to go back to mine on a few occasions.  (Usually the boot
disk, when I screw up a kernel compilation.)
-- 
Jim Winstead Jr. (CSci '95)    | "Catch a fish!"
Harvey Mudd College            |  -Geddy Lee,
jwinstea@jarthur.Claremont.EDU |   San Diego Sports Arena
Disclaimer: Mine, not theirs!  |   January 20, 1992
Newsgroups: comp.os.linux,alt.os.linux
From: joel@wam.umd.edu (Joel M. Hoffman)
Subject: Re: Keyboard dies when I hit Caps-Lock (+SCSI)
Organization: University of Maryland at College Park
Date: Tue, 14 Apr 1992 13:09:32 GMT

In article <1992Apr13.224913.15109@odin.diku.dk> dingbat@diku.dk (Niels Skov Olsen) writes:
>drew@caesar.cs.colorado.edu (Drew Eckhardt) writes:
>
>[My keyboard locks up when Caps-Lock is hit both in scsi-version
>at sc.tamu.edu (DK and US keyb.) and in the scsi0.95c+ version at
>headrest.woz.coloradu.edu.]
>
>[scsi devices now use major 8]
>
>>The keyboard : 
>
>>Does the keyboard lock up, period, do numlock, CAD still work,
>>or not?
>
>Ok I checked it more thoroughly.
>
>Following keys gives TOTAL lock up but with Linux stil running:
>	Pause
>	Scroll Lock (gives a task-info)
>	Caps Lock
>	Num Lock

Are you sure the keyboard is locked up?  On my system, many of those
keys provide a ``hidden feature.''  They convert everything into
control sequences until Linux is rebooted.  So, `a' becomes C-a (which
looks invisible), `c' becomes C-c, etc.  BTW, you can still logout, as
`d' become C-d, and if you have a ``sync'' in your history (bash), you
can use `p' (which becomes C-p) to retrieve it.

-Joel
(joel@wam.umd.edu)

Newsgroups: comp.os.linux
From: harlick@lindy.Stanford.EDU (Will Clark)
Subject: Where is expr?
Organization: Stanford University
Date: Sat, 11 Apr 1992 18:19:48 GMT


I saw someone (I forget who) say that expr is part of the gnu shell
utilities v1.6.  This is great, but I don't know where to find
it/them.  I'm getting an error message while making the 0.95c+ kernel
(although I still get a bootable image) so I would guess that expr has
already been ported to Linux.

(Thanks to everyone who told me where to find dd two weeks ago.)

Will Clark
will.an@site007.saic.com
------------------------
SAIC does not share my opinions.
harlick@lindy is a friend's account, but you can send me email here, too.
Newsgroups: comp.os.linux
From: david@ods.com (David Engel)
Subject: Re: <assert.h> in gcc2.1
Organization: Optical Data Systems, Inc.
Date: Thu, 9 Apr 1992 17:58:59 GMT

knapka@athena.cs.uga.edu (Joseph Knapka) writes:
: Has anyone had trouble using assert under gcc-2.1? The problem I'm
: having (and it only takes a trivial bit of code to demonstrate) is
: that while #define-ing NDEBUG turns off assertions as advertised, it
: seems that subsequently #undef-ig NDEBUG and re-#include-ing
: <assert.h> *fails* to turn them back on.  Am I hallucinating, or is
: there really a problem?

You're right!  You need to delete the #ifndef _ASSERT_H/#define _ASSERT_H
and associated #endif stuff from include/assert.h.

David
-- 
David Engel                        Optical Data Systems, Inc.
david@ods.com                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081
Newsgroups: comp.os.linux
From: drew@kinglear.cs.colorado.edu (Drew Eckhardt)
Subject: Re: mtools and messed characters on hard boot   help.
Organization: University of Colorado at Boulder
Date: Fri, 17 Apr 1992 05:42:56 GMT

In article <1992Apr17.035352.8699@ux1.cso.uiuc.edu> chojnows@osiris (Brian Chojnowski) writes:
>
>	I have finnaly gotten my hard drive configured to hold both the dos
>and Linux OS's invisible to each other. A friend of mine found a neat
>utility that let me select f1,f2, etc.. on bootup, which partition to boot
>from. I gave up on figuring out how to create a linux only boot partition,
>so I wound up making a 3m dos partition, and used bootlin. If anyone knows
>how to make Linux boot from the hard drive sans Dos, it would be neat. I


Shoelace is quite bletcherous, but it does work, and it works reasonably
well once installed.  

Get shoelace.  Install the following files : 
/shoelace (NOTE : THIS MUST BE IN /)
/etc/bootlace 
/etc/winiboot 

and 

/etc/config 
/etc/disktab

Edit the boot line in /etc/config to suit your personal tastes.
/vmunix is a NORMAL name for a kernel, so I boot that.  You can
ignore the other lines, as they concern the building 
of a Minix image, and other minix things.

/etc/disktab

laceup should be in /etc or /usr/etc.

Now, run laceup on your root partition with 

laceup /dev/hd[whatever] wini

This will put a boot block on THAT PARTITION.  If you choose this 
partition as your 'active' partition, this partition will boot up.

Now, you need a program to select your active partition at bootup,
so you don't have to use fdisk or some heinous DOS program to 
select your boot partition.   

winiboot does this.

laceup -w [default boot partition] /dev/hd[wholedevice]  

where wholedevice is the device for the ENTIRE hard disk.

Booting : 
1.  Winiboot will prompt for a partition number to boot, with the 
	default marked with an asterisk.  Hit a number,
	or if it times out, the *'d partition will be 
	booted.  

2.  /shoelace will load.  When this happens, it will either 
	boot the file specified in the boot line,
	or if you space bar it, you can select 
	any other file to boot from.  Use ls  to find what 
	you want, load to run it.  

>know have 2 problems: 1) I grabbed the binaries for mtools from
>tsx-11.mit.edu, and when they are run, I always get the message 'Device not
>found -- please specify device' or something like that. What have I not done

The old mtools utilities used /dev/DosA /dev/DosB and /dev/DosC or 
other equally heinous device names.  Recompile it with your 
preferences.
From: buckley@csa.bu.edu (David Buckley)
Newsgroups: comp.os.linux
Subject: Job Ctrl && $$->programmers (How?)
Keywords: jobs, money, bash, happy
Date: 7 Apr 92 08:24:28 GMT
Reply-To: buckley@csa.UUCP (David Buckley)
Organization: Computer Science Department, Boston University, Boston, MA, USA


	Is there some version of jsh, or some implementation of the
functions fg, bg, %[n] etc... I didn't find them on the version of
bash I am using. Are there several versions of bash?  How do we get 
access to job ctrl?  I know these exist from reading previous 
postings, are they hiding or should I chmod u+rwx mybrain.out?

	Also, is there some list of developers-port|ers so that
it might be easyer to direct financial contributions to this venture? 
I haven't seen any postings with regards to how and to who money
should be donated, and I think it would be interesting to be able 
to direct donations for specific implementations (our unix favourites),
beyond Linux itself.  Such a posting (I feel) would be greately 
appreciated. 
	
	I am very impressed with the work being done!
	(As a newbie-linuxite I would love to contribute...)


David Yates Buckley		    | Disclaimer: Recursive lunacy is
buckley@buphy.bu.edu, @csa.bu.edu   | employed in the most trivial tasks...
From: einari@rhi.hi.is (Einar Indridason)
Newsgroups: comp.os.linux
Subject: Re: User's Guide project
Date: 15 Apr 92 09:29:04 GMT

In <kuelccINN613@alhena.usc.edu> ajayshah@alhena.usc.edu (Ajay Shah) writes:

>knapka@athena.cs.uga.edu (Joseph Knapka) writes:

>>1) Do you think there is a need for such a document?

>Yes, I think such a document would be rather valuable.

>Linux is great.. what more could a hacker ask for?
>But we could make the results of the same work accessible to
>a much larger class of users if we add "a little" effort
>on documentation and easy-to-use installation/administration.


And perhaps some co-ordination regarding patches.  Perhaps a few persons
would take each patch, and compare it to some "standard" source tree.

I have used Minix a bit, but haven't installed Linux (yet), but I'd
hate to see the "patch-mess", that minix has gotten into, hit Linux as
well.


--
einari@rhi.hi.is
From: cccstevn@dino.ucdavis.edu (Steve Ansell)
Newsgroups: comp.os.linux
Subject: TEX for Linux at tsx
Date: 17 Apr 92 18:16:53 GMT
Organization: Computing Services, UC Davis


In the binaries/usr.bin directory on tsx-11 there is a directory containing
what I assume to be the TEX package.   It contains the following files:


dvips.tar.Z
dvilj2p.tar.Z
ptex.tar.Z
texfile1.tar.Z
texpk300.tar.Z
textfm.tar.Z

It has been a long time since I have done anything with TEX, but I thought
that this would be an ample time (besides, if I can create documents under
Linux my DOS stuff will be almost completely useless!).  The problem is 
that there is no explaination (or none that I saw) as to what these files
are.  Before I download almost 2MB of stuff, I would like to know just
what I do and don't need.  I know that dvips and dvilj2 convert the TEX
output files into the respective printer language and I think that the 
texpk300 and textfm archives contain fonts (yes? no?).  The main program seems 
to lay in ptex and I am not sure, but I think texfile1 contains style sheets.
Could someone more knowlegable about TEX than myself confirm or correct this
and possibly tell me just how much of this is absolutely needed (I have very
limited HD space right now).  Of course, an installation guide would be 
nice, but I can usually hack my way through getting things installed if it
is possible.  If this is covered elsewhere (i.e. in some README I missed)
please direct me to the correct location.


-- 
                                         	-Steven T. Ansell
                                          	Unix Consultant
                                          	Computing Services U.C.D.	
                            
Newsgroups: comp.os.linux
From: chojnows@osiris (Brian Chojnowski)
Subject: Re: Graphics and IPC questions...
Keywords: Graphic standard and how to IPC?
Organization: University of Illinois at Urbana
Date: Fri, 17 Apr 1992 15:08:59 GMT


	I plan to add a direct to screen library. Basically I envision
creating a terminal type that is a superset of vt100. Nothing as fancy or
system hog like X. Just a characterset based graphix system. So while we are
at it, if anyone has some info somewhere on how to write assembly stuff
under linux, I can start porting some of my dos-mode screen routines.
Newsgroups: comp.os.linux
From: peterw@archsci.arch.su.oz.au (Peter Williams 8169821)
Subject: man.1 files available for tex, mf and related programs
Organization: Design Computing Unit, The University of Sydney
Date: Wed, 15 Apr 1992 01:24:56 GMT

In pub/linux on archsci.arch.su.oz.au (129.78.66.1) there are now available
the man.1 files for tex, latex, mf, dvips, etc.

They are in the file texmfman.tar.Z and should be detarred in the "man" 
directory under which you wish them installed. They should automatically go into
the "man1" directory within the directory they are untarred in.

Don't forget to update your "whatis" file.

-- 
Peter Williams                |e-mail: peterw@archsci.arch.su.oz.au
Key Centre for Design Quality |phone: +61-2-692 2053 or +61-2-660 6156
University of Sydney          |+++++++++++++++++++++++++++++++++++++++
From: burley@albert.gnu.ai.mit.edu (Craig Burley)
Newsgroups: comp.os.linux
Subject: Re: Help Mr. Fortran
Date: 6 Apr 92 18:52:36 GMT
Article-I.D.: albert.BURLEY.92Apr6145236
	<Mar.31.22.07.27.1992.4385@dartagnan.rutgers.edu>
	<1992Apr1.165146.10869@ssd.kodak.com>
	<1992Apr1.182702.8464@colorado.edu>
	<1992Apr02.135130.26689@watson.ibm.com> <IMHW400.3@INDYVAX.IUPUI.EDU>
	<1992Apr03.132
Organization: Free Software Foundation 545 Tech Square Cambridge, MA 02139
In-reply-to: jlnance@eos.ncsu.edu's message of 3 Apr 92 14:20:14 GMT

In article <1992Apr3.142014.28253@ncsu.edu> jlnance@eos.ncsu.edu (James L Nance) writes:

   I remember reading a post here not too long ago from the person who was writing
   gnu FORTRAN.  I was wondering if this person, whose name I can not recall, has
   considered porting FORTRAN to Linux.  I would like to see if I can get Spice2g6
   ported to Linux, but parts of it (lots of it) are written in FORTRAN and
   I think
   it would be a Major job to translate them into C.

Hi, that was me.  If (99% likely) and when (within a month or so) I do get
a 486 box and start getting Linux up and running, I indeed would like to use
it as my main Fortran-compiler-development machine.  BUT, that might take a
while (especially if I have to do driver development to get my peripherals
working) and in the meantime I'll likely be modeming in to a Sun4 to do the
Fortran work.

Furthermore, GNU Fortran hasn't even reached alpha test yet, though from a
technical perspective it's pretty close (testing and some backend changes to
get COMPLEX support working still needed).

I suggest you ftp to research.att.com, login as netlib (I think; maybe it's
anonymous ftp, but I think they changed that), get f2c from ~dist/f2c or
some such place, and use that to compile your Fortran code for use on Linux.
f2c is pretty good; it's free (public domain); and when GNU Fortran comes
out (as alpha), it'll be inter-module compatible with f2c-compiled programs.
(f2c comes with it's own I/O and intrinsic libraries, so it ought to be quite
easy to get it running under Linux.)

If nobody seems to have gotten f2c ported to Linux by the time I get Linux
working on my machine, I'll do it myself and let people know what changes,
if any, need to be made.  I doubt it'll be much; I've gotten f2c running on
two 68k machines (HP and NeXT) and a Sun4 with a trivial amount of work.
(On the other hand, I haven't run a whole lot of Fortran code through it
anywhere, yet.)
--

James Craig Burley, Software Craftsperson    burley@gnu.ai.mit.edu
Member of the League for Programming Freedom (LPF)
From: Adrian.Wallaschek@arbi.informatik.uni-oldenburg.de (Adrian Wallaschek)
Newsgroups: comp.os.linux
Subject: Questions and suggestions
Keywords: linux
Date: 14 Apr 92 14:18:55 GMT
Organization: University of Oldenburg, Germany

Hi everybody!

I've got some questions:

	- is there anybody working on a serial driver for multiport cards as
	  ast-compatible cards, etc. (There is a freeware-driver for commercial
	  *nix-versions called FAS which does a quite good job!) ?

	- under DOS there is a package called FDREAD which makes it possible to
	  write 1.44 MB on 5.25"-floppies without problems. I think it should be
	  possible to modify the floppy driver that way, it could handle those
	  disks. (Perhaps you'd like some extra 240k on your distribution disk)
	  Is there a nearer description on the floppy-devices, esp. the minor
	  device-numbers ?

	- how soon can we expect a pre^n-release of the new filesystem? (We
	  are working with three users on a 386/33 and even though we have
	  fast SCSI (Adaptec) the system actually pauses every user if we
	  e.g. untar a file of 300k!)

prefect
Adrian.Wallaschek@ARBI.Informatik.Uni-Oldenburg.DE
(I didn't make the address, sorry!)
Newsgroups: comp.os.linux,alt.os.linux
From: spoo@speedy.acns.nwu.edu (Herbert M. Zinn)
Subject: lots o problems, many to choose from
Summary: GCC2.1 ld errs, kern2.1patch, serial ports, bad juju!
Organization: The Cabal of the Infinite bounded Spoo
Date: Wed, 8 Apr 1992 16:36:04 GMT

	Hi, this is my first post here so if this has already been dealt with
in a FAQ somewhere please let me know. I recently grabbed GCC2.1 beta, the
shared libs, and the kernel patches from tsx-11 and am having problems with
the libs. When I run the install.sh in /usr/lib/shared/obj, it invokes the
2.1 GCC with options -s -o on the make.a file. this (i assume) then invokes
the linker, which promptly bombs with "unknown option: ---" followed by a
usage message. Ive tried invoking it by hand and it always seems to generate
this error message. I'm using the ld that came in binutils.tar.Z, but I noticed
its only a couple hundred bytes different, could I perhaps have grabbed the
wrong one? 
	Another GCC2.1 problem: when I install the 2.1kern patches (aside from
the somewhat odd path [/mnt/linux/... for the kernel sources] that it puts in
every makefile) it generates parse errors on a lot of the linux kernel headers.
	This may have been covered elsewhere; are the /usr/src/linux/include
files duplicated in the old gcc1.4 /usr/include? are they in gcc2.1 includes?
	Finally, until I get around to digging through the famous ralph brown
interrupt list, has anyone else found the need to use more than 2 serial ports
at once? I don't know enough about the coding of comm routines myself, but,
since sharing IRQ's is basically nonfunctional for concurrent IO in DOS,
I have my third serial port (3e8) set to IRQ5. Anyone have patches || diffs
|| help in general with changing the serial drivers to use it? (Digging through
the includes didn't seem to help ;-) )
	Thanks in advance for any help, responses, email, flames, et cetera,
and a great big THANKS! to Linus and all the other code wizards for putting
together a great package!
						Herb
_____________________________________________________________________________
|Herb M. Zinn INET: spoo@speedy.acns.nwu.edu USPS: 6211 N. Artesian Ave.    |
|"Standing is harder than moving."                 Chgo., IL. 60659-2828    |
|_______________-Moshe Feldenkrais___________ISDN:_312-274-8149_____________|