HDTenEightyP/NetNews huggingface dataset:
From: pyrros@braindamaged.cis.udel.edu (Christos T. Pyrros)
Subject: How would you spec a Computer Room?
Organization: University of Delaware, Newark
Date: Tue, 29 Sep 1992 09:31:37 GMT

Well, I've finally convinced management that we need a machine room, so
I'm writing up a spec.

The room will contain 2 486-based Novell servers, a backup computer, and
an alarm computer (in addition to all documentation, disks, etc).

I only get one shot at this, so I'm looking for your comments on this list:

                        Proposed Machine Room Specifications

                      Listed in Approximate Order of Importance

1.	Located adjacent to air shaft on 3rd Floor for direct access to current network wiring.

2.	Main area of 8' X 12'.

3.	Adjacent to main room, doorless closet space of 5' X 6' with shelving, with space for a fireproof safe for tape backups.

4.	Climate controlled environment at 65 deg F and 35% relative humidity.

5.	Quad Isolated Ground outlets around the perimeter of the main room every 4' tied to a separate breaker panel located within the main room for future direct hookup to UPS.

6.	Quad RJ-45 Voice/Data Jacks around the perimeter of the main room every 4' using Plenum Shielded Twisted Pair tied to an independent AT&T 110 Cross Connect panel in the 3rd Floor Wiring Closet.

6.	Single entrance security doorway of solid steel or other secure type with lock and deadbolt.

7.	All surrounding walls  to be  insulated, fireproof, and extend from the floor all the way to the above deck.

8.	Smoke detector tied to building fire alarm, automated Halon fire extinguishing system, rather than sprinklers, and a Halon fire extinguisher for event of fire.

9.	Linoleum Flooring.

10.	Brightly lit with cool-white fluorescent lighting.

11.	Drop ceiling with several "breathing" panels for air circulation.



Thank you,

Chris
Newsgroups: comp.sys.next.sysadmin
From: obrooks@worf.hssc.ksc.nasa.gov (Oscar Brooks)
Subject: NeXT to MAC printer
Keywords: Apple Share, MAC, printer
Organization: NASA
Date: Wed, 30 Sep 1992 19:21:12 GMT

How can I print to the MAC printers on ethertalk?
Can someone point me in the right direction for
documentation on the matter?

Oscar

--

------------------------------------------------
Oscar Brooks		
NASA, Real Time Systems Branch
Kennedy Space Center, Fla.
Internet <obrooks@dale.ksc.nasa.gov> (NeXT Mail Preferred)
--

------------------------------------------------
Oscar Brooks		
NASA, Real Time Systems Branch
K-----------------------------------


-- NewsGrazer, a NeXTstep(tm) news reader, posting --
M>UQR=&8P7&%N<VE[7&9O;G1T8FQ<9C!<9G-W:7-S($AE;'9E=&EC83M]"EQM
M87)G;#$R,`I<;6%R9W(Q,C`*7'!A<F1<='@V,C)<='@Q,C0U7'1X,3@V.%QT
M>#(T.3!<='@S,3$S7'1X,S<S-EQT>#0S-3E<='@T.3@Q7'1X-38P-%QT>#8R
M,C=<9C!<8C!<:3!<=6QN;VYE7&9S,CA<9F,P7&-F,"!(;W<@8V%N($D@<')I
M;G0@=&\@=&AE($U!0R!P<FEN=&5R<R!O;B!E=&AE<G1A;&L_7`I#86X@<V]M
M96]N92!P;VEN="!M92!I;B!T:&4@<FEG:'0@9&ER96-T:6]N(&9O<EP*9&]C
M=6UE;G1A=&EO;B!O;B!T:&4@;6%T=&5R/UP*7`I/<V-A<EP*7`HM+5P*7`HM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2U<"D]S8V%R($)R;V]K<PD)7`I.05-!+"!296%L(%1I;64@4WES=&5M<R!"
M<F%N8VA<"DME;FYE9'D@4W!A8V4@0V5N=&5R+"!&;&$N7`I);G1E<FYE="`\
M;V)R;V]K<T!D86QE+FMS8RYN87-A+F=O=CX@*$YE6%0@36%I;"!0<F5F97)R
(960I7`H*?0ID
`
Newsgroups: comp.sys.next.sysadmin
Subject: Help!  Pub. Domain X for Turbo NeXT 
From: slxmw@smithfield.enet.dec.com (869883 Medlyn)
Date: 1 Oct 92 15:49:47 MDT
Reply-To: slxmw@smithfield.enet.dec.com (869883 Medlyn)
Distribution: world
Organization: Digital Equipment Corporation


	Does anyone know how to get a public domain X version to run
     properly on a Turbo Station.  I loaded XNext from cs.orst.edu and 
     sonata.cc.purdue.edu and neither would work.  When I ran X the screen
     changed but I couldn't really see a window.  As I moved the mouse 
     around, I could see static moving like something was not displaying
     properly.  

        I would really appreciate any help.  I have assignments that I am 
     have to write in X-windows.  It would be nice to do it on my own 
     machine.  Thanks.

		Dayne Medlyn
                slxmw@cc.usu.edu
Newsgroups: comp.sys.next.sysadmin
From: dleon@seas.smu.edu (David Leon)
Subject: A Tale of Two Questions...
Organization: School of Engineering and Applied Science
Date: Fri, 2 Oct 1992 04:52:12 GMT

I have two important questions:

1.  Exactly how does the "nbuf=xx" work?  I broke into the NMI, hit the MON,
typed "bsd nbuf=99" and the thing booted with 16 buffers and then failed.
I tried several different syntaxes, but to no avail.  What gives?


2. What is needed to make the CDROM boot in single-user mode?  Since my hard
drive went south, I need to boot from CDROM so that I can use the backups
which are on several ODs.  Do I need to somehow prepare a floppy kickstarter?
If so, how exactly do I do this?

Reply via email and I'll post a response.

dleon@seas.smu.edu

Newsgroups: comp.sys.next.sysadmin
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Subject: Re: 900 dpi DPS limit
Organization: University of Maryland, College Park
Date: Mon, 28 Sep 1992 19:50:17 GMT

In article <19vj1nINNjus@darkstar.UCSC.EDU> isbell@cats.ucsc.edu (Art Isbell) writes:
>Bzzzt!!!  Bloodsuckers win again :-)  The addendum included with the license
>agreement supersedes section 6. and prohibits the creation of bitmaps at
>greater than 900 dpi.  But you may transmit PS files to any other device with
>its own PS interpreter.

I've looked at two different "NeXTSTEP 3.0" boxes (one for the machine
at work, and the one I bought for my machine at home).  Neither
contain any license addendum that I can find.

louie
From: borchers@poogh.llnl.gov (Robert R. Borchers)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: AppleTalk and 3.0. It does not work.
Date: 30 Sep 92 16:18:58 GMT

In article <1992Sep29.170327.20939@news2.cis.umn.edu>  
jalegre@htlv.med.umn.edu (John Alegre) writes:
> Has anyone got AppleTalk connections to work under 3.0?
--
I got it working first time, but I have not had time to run down all the  
properties. I do, for example, see the hundreds of zones on our network  
and can mount the file structure on my mac, and another one I have access  
to. One interesting thing is that i get the entire file structure on my  
mac hard disk, hot just the folder that is published under system 7.0.1 I  
also had no problem installing my printer, after I found the correct  
driver, since there are three. Bob

Robert R. Borchers
L-414
Livermore, Ca 94551
borchers@llnl.gov
NeXTmail Welcome
Newsgroups: comp.sys.next.sysadmin
From: steves@truevision.com (Steve Spicklemire)
Subject: slip on netinfo network?
Organization: Truevision Inc., Indianapolis, IN
Date: Tue, 29 Sep 1992 03:35:07 GMT


Hi, 
	I've been reading the comments about SLIP on the NeXT. I want to
allow users to dial into a NeXT on our netinfo network (most likely using a
PC or a Mac) start up SLIP on the NeXT/PC and then use POPMail, or Telnet etc.
from a remote site. Is this possible? I thought at first it would be, but 
then I read the bit about not being on a netinfo network...

(p.s. where is a good ref/intro to slip issues in general?)

thanks!
-steve


-- 
Steve Spicklemire
steves@truevision.com (daily)	spicklemire@gandlf.uindy.edu (sometimes)
Dept. of Mathematics and Physics, Univ of Indianapolis 
(317) 788-3313
Newsgroups: comp.sys.next.sysadmin
From: Hal.Varian@umich.edu
Subject: Re: chown under 3.0
Reply-To: Hal.Varian@umich.edu
Organization: University of Michigan Math Dept
Date: Tue, 29 Sep 1992 13:42:07 GMT

In article <RPRUESS.92Sep29074533@yoyo.weeg.uiowa.edu>  
rpruess@yoyo.weeg.uiowa.edu (Rex Pruess) writes:
> In article <1992Sep29.005224.25329@lsa.umich.edu>  
Hal.Varian@umich.edu writes:
> 
>   >   Well my fstab entry says
>   >   /dev/sd0a / 4.3 rw,noquota,noauto 0 1
>   >   /dev/sd1a /Users 4.3 rw,noquota,noauto 0 2
>   >
>   >  As far as I can tell from the documentation, this is what  
I'm  
>   >  supposed to say. 
> 
> Get rid of the "noauto" for "/dev/sd1a".  Try this:
> 
>       /dev/sd1a /Users 4.3 rw,noquota 0 2
> 
> Type "man mount" for details about "noauto".  Hope this helps.
> --

That solved the problem.  Thanks also to Garance Drosehn, Bill  
Chin, and Izumi Ohzawa who pointed out my error.
--
Hal.Varian@umich.edu    Hal Varian
voice: 313-764-2364     Dept of Economics
fax:   313-764-2364     Univ of Michigan
                        Ann Arbor, MI 48109-1220
Newsgroups: comp.sys.next.sysadmin
From: sherwood@fenris.space.ualberta.ca (Sherwood Botsford)
Subject: Re: 900 dpi DPS limit
Organization: University Of Alberta, Edmonton Canada
Date: Tue, 29 Sep 1992 16:23:42 GMT

900 dpi is underutilizing most film recorders resolution.

From my Film Recorder file:
	Captivator: (Crosfield Design Systems)
	Programable resolution 2K/4K/8K/16K lines

	FR1 (Montage)
	4096 x 2731 pixels.  
	(Comment that optical resolution is less than this)

	Solitaire Image Recorder
	4096 x 2731 pixels.  
	Draft mode of half the above.
	Solitaire 8
	8192 x 5464 pixels 32bits/pixel
	Solitarie 16
	16,384 x 10928 
	(Variety of film sizes can be used)

Anyway, how would the next know how many bpi the image was  
being rasterized for?  When you go to film, it is usually  
for blowup later either for illustration or projection.  So  
you would want the rasterizer to think that the size of the  
media was larger than it really is, so that the adobe  
hinting rules would work properly for spacing text.

Assuming that you have a film recorder, how the heck does  
the Next know how 'big' it is.
From: bryce_jasmer@next.com (Bryce Jasmer)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: How do you expand buffers?(solving 3.0 speed problems)
Date: 28 Sep 92 23:25:28 GMT

Bill Smith writes
>In article <1992Sep24.145410.3194@hamblin.math.byu.edu>  
>bill@mathnx.math.byu.edu (Bill Smith) writes:
>> You can set this in the ROM monitor by just typing  "p"  and then
>> in the boot preference  "sd- nbuf=64"  or whatever number you want.
>> If you are booting from network use  en  instead of sd  I suppose.
>> -Bill
>Hmm.  Well you can't set any number you want this way. The highest you
>can go this way is  99 .  If you want a larger number of buffers
>you must apparently do it by hand, say  as  bsd sdmach nbuf=1000  or
>some such at the ROM prompt.  Would someone at NeXT comment on what 
>the optimal setting might be for a given amount of RAM available?

You can say "sd- nbu=128"

I personally haven't done any testing for the optimal setting. We usually use  
128 on our 16MB file servers.

Bryce Jasmer
bryce_jasmer@next.com

#import <std/disclaimers.h>
From: tim@rri.UUCP (Tim Buck)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: Desjet and 3,0
Date: 1 Oct 92 16:29:17 GMT
Organization: Recognition Research Inc., Blacksburg, VA

Has anyone gotten the DeskJet driver (from the net) working with an HP
DeskJet 500 under NeXTSTEP 3.0?  If so, what version did you use and how
did you make it work????

Timothy Buck   --   rri!tim@vtserf.cc.vt.edu OR timbuck@borg.lib.vt.edu
 Recognition Research, Inc. (703) 231-6500	++ NeXTmail accepted ++
------------------------------------------------------------------------
 Hate Blacksburg's weather? Wait an hour.  Hate the season? Wait a day.  
Newsgroups: comp.sys.next.sysadmin
From: d1h1883@sc.tamu.edu (Dave Hess)
Subject: Re: I can't get photorealistic rendering working
Reply-To: David-Hess@tamu.edu
Organization: Texas A&M University, College Station
Date: Fri, 2 Oct 1992 13:11:57 GMT

In article <1992Oct1.222648.25295@athena.mit.edu> shanega@athena.mit.edu  
(Shane G. Artis) writes:
> Finally, I _can_ run prman by hand giving it a .rib file a input.  It
> will generate (after some time) a file, ri.pic.  Is this image file
> format documented somewhere?  I have The RenderMan Companion, but it
> only makes passing reference to this file and doesn't give its format.
> 
> Many thanks from myself and the others to anyone who can help us out!
> 
> Shane

Well I am having trouble with prman also. What happens for me though is
this shows up in /usr/adm/messages.

Sep 29 21:00:01 posaune rpc.renderd[633]: Inconsistent set of values to  
create NXBitmapImageRep

Not too sure why that is happening. If you want to run prman from the command
line you do need to be sure the rib file has the following line in it. (Most
of the examples shipped with 3.0 don't.)

Display "myFile.tiff" "tiff" "rgba"

This is documented at the bottom of the Intro3DKit.rtf document in Digital
Librarian.

--
David K. Hess
Graduate Assistant                     David-Hess@tamu.edu
Supercomputer Center                  Texas A&M University
From: sahayman@moose.cs.indiana.edu (Steve Hayman)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: 3.0: what gives with cron
Date: 28 Sep 92 05:17:38 GMT
Organization: NeXT Canada

>I'll bet you're piping your backup data to rsh, eh?  Sorry, bunkie; rsh in 3.0
>does not work under cron.  I spent several hours on this problem and fairly
>conclusively proved that rsh just dies silently when it is run under cron.


One possibility is that it could be a problem with $PATH.  If you add
something like this to /etc/crontab

	* * * * * root echo path is $PATH >/dev/console

and then look at the message in the console window, you'll see that
cron is using "/etc:/usr/etc:/bin:/usr/bin" as a default PATH.  Note the 
conspicuous abscence of "/usr/ucb", home of rsh, finger and many other programs.
So cron won't find those programs uness you go out of your way to
give it a better PATH.  I.e. crontab lines like this

	* * * * * root rsh somewhere blah blah

will fail silently.

You could fix this in 2 ways - the obvious way is to hard code the
pathname you want ...

	* * * * * root /usr/ucb/rsh somewhere blah blah

or, alternatively, if you're trying to execute a shell script,
you can add "PATH=/usr/local/bin:/usr/ucb:/bin:/usr/bin export PATH"
to the script you're executing.  (Setting the PATH explicitly is a good
idea for scripts in general.)

Also alternatively you could get the Paul Vixie public domain
cron replacement program, which has many useful features not found
in the standard cron.

Hope this helps someone.
Steve

-- 
Steve Hayman          Systems Engineer, NeXT Canada      Steve_Hayman@NeXT.com
Newsgroups: comp.sys.next.sysadmin
From: gsk@world.std.com (Geoffrey S Knauth)
Subject: lpr works but print panel does not
Organization: The World Public Access UNIX, Brookline, MA
Date: Tue, 6 Oct 1992 08:39:12 GMT

A friend asks:

"I simply cannot get buckaroo (in Wendy's office) to print via the
NeXTstep print panels.  It is driving me to distraction.  Printing the
Unix way (lpr) works fine, so I know the daemons and the NetInfo stuff
for printer routing (printcap) is all set up correctly, but whenever
you try to print from buckaroo from a NeXT print panel, it spins for
30 seconds before saying `Unable to connect to printer daemon.'  That's
hogwash, since I can clearly connect to the printer daemon via lpr."

"Any idea what the print panel is doing that lpr is not?
Any idea how to fix this (it works from other computers)."
-- 
Geoffrey S. Knauth, Marble Associates, Inc.                Member BCS-NeXT, LPF
gsk@marble.com, (617) 891-5555 work, (617) 547-5247 home   Standard Disclaimers
From: hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy))
Newsgroups: comp.sys.next.sysadmin
Subject: Re: 3.0: what gives with cron
Date: 28 Sep 92 18:53:07 GMT
	<1992Sep28.001755.801@news.cs.indiana.edu>
Organization: Department of Physics, UC Irvine, CA 92717-4575, USA
In-reply-to: sahayman@moose.cs.indiana.edu's message of 28 Sep 92 05:17:38 GMT

In my limited experience with cron I ALWAYS specify full pathnames to
the scripts/programs to be run; I also usually make the scripts log 
errors to some file in /tmp or /usr/adm, so I can check whether cron
has worked at all. 
--
Hardy 
-----
Meinhard E. Mayer,  Department of Physics, UC Irvine 
e-mail: hardy@golem.ps.uci.edu (preferred) or MMAYER@UCI.BITNET
Newsgroups: comp.sys.next.sysadmin
From: andrew@cubetech.com
Subject: Re: 900 dpi DPS limit
Organization: Cube Technologies, Inc.
Date: Fri, 2 Oct 1992 23:56:44 GMT

In article <pmarcos-280992105113@clive.mv.us.adobe.com> pmarcos@adobe.com (Paul Marcos) writes:
>In article <TTN.92Sep27174422@mustarastas.cs.tut.fi>, ttn@cs.tut.fi (Tero
>Nieminen) wrote:
>>> Unfortunately, this seems to put and end to the possibility of having a
>> decently priced PS-film recorder attached to a NeXT. Well, it could be
>> about the same resolution (in dots) as the screen, but if they just let
>> us use the laser printer effective bitmap size.
>> 
>Maybe I didn't make sense.  You could do bitmaps up to 900dpi and send the
>bitmaps down to a film recorder.  That's pretty good resolution if you ask
>me.  I know nothing about PS-film recorders, but if it has a RIP (a
>PostScript interpreter) built into it, then you should be able to send
>PostScript *code* to it and get any resolution that the recorder can
>physically do.  Does that make sense?  So if you've got a PS-film recorder
>with a RIP built into it, then you're stylin', otherwise, you could to up
>to 900 dpi.

Talus had a run in about their Rio film recorder (which is made by
Polaroid).  The film-recorder has a resolution of about 4k, but
Polaroid's legal department insists that most color film has less than
900 grains per inch.  Having used a grain-focuser, I tend to agree
with them.  Adobe is apparently satisfied (or they just don't want to
deal with Polaroid's legal department).

While I'm not a lawyer, I kind of think that the particular portion of
the NeXT licensing agreement in question is not easily enforceable.


andrew
-- 
andrew@cubetech.com     | "We shall not cease from exploration
Andrew Loewenstern      |  And the end of our exploring
Cube Technologies, Inc. |  Will be to arrive where we started
                        |  And know the place for the first time." -T.S. Eliot
Xref: sparky comp.sys.next.sysadmin:5484 comp.sys.next.software:1885
From: gbol@rglnext.geol.vt.edu (Gregory B. Lampshire)
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.software
Subject: SUN CD-ROM drive and installing 3.0 (the 2048 block size problem)
Date: 29 Sep 92 15:44:36 GMT
Reply-To: gbol@rglnext.geol.vt.edu
Followup-To: comp.sys.next.sysadmin


					


I seem to recall that someone had used the SUN cd-rom drive (connected to  
the NeXT0 to upgrade to NS3.0.  I am now trying the same but I get the  
2048 block size problem.  I was wondering if there was a fix for this so  
that the 3.0 cd can mount correctly...I don't remember one being posted  
and it conflicts with my thoughts that this blocks size conflict is  
unresolvable.


Any comments welcome.



--
Gregory Lampshire 
Virginia Tech 
Bradley Department of Electrical Engineering
gbol@rglnext.geol.vt.edu (NeXTmail welcome)
------------------------
My opinions are my very own and do not reflect the opinions of any  
employer
From: dillon@overload.Berkeley.CA.US (Matthew Dillon)
Newsgroups: comp.sys.next.sysadmin
Subject: Re:  Desjet and 3,0
Distribution: world
Date: 1 Oct 92 12:00:17 PST
Organization: Not an Organization

In article <BvEp6t.MxM@gate.demon.co.uk> paul@seer.demon.co.uk (Paul Lynch) writes:
>In article <dillon.0ojg@overload.Berkeley.CA.US>
>dillon@overload.Berkeley.CA.US (Matthew Dillon) writes:
>>     Note that your serial cable to the HP500[C] must be wired properly
>for
>>     hardware flow control, and note that the HP500[C] does not use RTS
>for
>>     flow control, but DTR.  It's a mess.  I don't know how you would do
>it
>>     on a non-turbo machine (which doesn't have hardware flow control).
>>
>>					    -Matt
>>
>I do believe that you might be in error.  It's the 030 machine that don't
>do flow control, not the nonTurbo 040s.

    Oh, yup!  your right!  It also occurs to me that I believe you can
    setup the HP-500[C] for XON-XOFF flow control, which ought to work fine
    with binary data since it's the HP sending XON/XOFF to you, not the
    otherway around.

				-Matt

>Paul
>--
>Paul Lynch
>P & L Systems			      (NeXTmail) paul@seer.demon.co.uk
>Tel: (0494)671501			     paull@cix.compulink.co.uk
>Fax: (0494)680228			      76711.451@compuserve.com

--

    Matthew Dillon		dillon@Overload.Berkeley.CA.US
    1005 Apollo Way		uunet.uu.net!overload!dillon
    Incline Village, NV. 89451	ham: KC6LVW (no mail drop)
    USA 			Sandel-Avery Engineering (702)831-8000

Newsgroups: comp.sys.next.sysadmin
From: ede978e@monu6.cc.monash.edu.au (Robert D. Nicholson)
Subject: sendmail 565c+IDA 
Summary: sendmail 565c+IDA
Organization: Monash University, Caulfield Campus
Date: Thu, 1 Oct 1992 18:29:27 GMT


I had sendmail 565c+IDA running fine under 2.1 and when I upgraded to 3.0
I simply replaced the /usr/lib/sendmail with my 2.1 sendmail and also
copied over the cf's in particular created a symbolic link: /etc/sendmail.cf
to /usr/local/lib/mail/cf/steffi.cf 

when I send mail to an outside user nothing gets put in /usr/spool/uucp/D.hostname.

any ideas?



Newsgroups: comp.sys.next.sysadmin
From: silbar@mpx2.lampf.lanl.gov (Dick Silbar)
Subject: oddity with man pages in 3.0
News-Software: VAX/VMS VNEWS 1.41    
Organization: LAMPF Data Analysis Center, Los Alamos, New Mexico
Date: Wed, 30 Sep 1992 02:39:00 GMT

I am responsible for two NeXTs in our group, my cube and the secretary's
TurboStation.  Yesterday I upgraded both to 3.0 and the following peculiar
situation has arisen with respect to man pages, e.g., "man ls".

Actually, it arose before yesterday, when I discovered that I no longer
could find man pages entries already last week.  That is because, to
save disk space on our two machines, we NFS-mount the NextLibrary/-
Documentation directory on both machines from another NeXTstation down the
hall in T-8, another group.  I soon learned that T-8 had already upgraded
to 3.0 last week.  Since the man pages were moved around some between 2.x
and 3.0, it was no surprise the entries could not be found.  But I expected
this problem to go away when I did _our_ upgrades.

Not quite the case.  In fact, if I remember correctly, neither my machine
nor Rachel's could find the man pages entries as of yesterday afternoon,
after the upgrades were complete.

The mystery compounds: later that evening, when signed on to my machine
remotely (from home), I tried (without much hope) once again a "man ls".
To my surprise, it worked (and it still does)!

Oh ho!, I said, Paul (the T-8 system administrator) must have fixed 
something earlier this evening.  Good!, but maybe I'll just check that 
"man" also works on Rachel's machine?  That's where the real mystery
comes in -- it DOESN'T!

Anybody have any clues as to what's going here?  (For the record, I've
rebooted everything a couple times; the mounts look good; the man pages
can be read in their nroff and catman forms directly from the NFS-
mounted directory.)

   Dick Silbar
Newsgroups: comp.sys.next.sysadmin