HDTenEightyP/NetNews huggingface dataset:
From: krishnan@pms240.pms.ford.com (Hare Krishnan)
Newsgroups: comp.protocols.nfs
Subject: NFS locking issues
Date: 23 Nov 1992 16:03:50 GMT
Organization: Ford Motor Company
Distribution: world
NNTP-Posting-Host: pms240.pms.ford.com

Hello,

When a NFS client locks a record on the NFS server, and if the client 
goes down who is responsible for releasing the locks? Some of the vendors 
say that the locks will be released only when the client system comes up
again. When I read the NFS specs, it kind of indicates that the server
statd should identify the shutdown clients and release the locks.

Some of the vendors do not agree with this?

Could any of the NFS gurus out there help me with this?

This is a serious problem considering the number of PC NFS clients.
Please send me an email as I don't read News regularly. I will summarize
the responses and post it.

Thanks in advance 

Krishnan Subramaniam
From: geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs
Subject: Re: Ultrix & PC-NFS & CD-ROMs
Date: 19 Nov 1992 20:44:10 GMT
Organization: SunSelect
Distribution: net
NNTP-Posting-Host: tyger.east.sun.com

#From: toreh@bootes.sds.no (Tore Haraldsen)
#Subject: Ultrix & PC-NFS & CD-ROMs
#
#A while ago I complained that I could not see any files when I mounted
#an exported CD-ROM on my PC w/PC-NFS.
#
#The problem was with Ultrix 4.2, and it vanished with the installation
#of Ultrix 4.3. So horray ..... except:
#
#Although I now can mount the CD-ROM on the Ultrix machine, export it and
#see the contents WITHOUT the ;version stuff (courtesy the mount option
#'noversion'), PC-NFS's habit of making strange file names out of upper
#case names somahow destroys the feeling of bliss.
#
#WHEN will we get an option to PC-NFS so that we ON A PER FILE SYSTEM
#bases can avoid this messy "feature"?????

In the next release! (:-(

However... I'd be grateful for examples (using the PC-NFS "ls -b"
command) of CD-ROM direectory listings which give trouble. It would be
nice to be sure that I've covered all the cases.

Geoff
--
Geoff Arnold, PC-NFS architect, Sun Select. (geoff.arnold@East.Sun.COM)
ADMINISTRIVIA==========ADMINISTRIVIA=====ADMINISTRIVIA==========ADMINISTRIVIA
Our systems will be down from Thuursday 5PM EDT until some time on Monday, while we
move from Billerica to our new Chelmsford, MA campus. Apologies for etc. etc. etc.
Newsgroups: comp.protocols.nfs
From: stevea@puccini.crl.umn.edu (Steven R. Anderson)
Subject: Is there a PD NFS client for DOS
Keywords: PD NFS DOS
Organization: PESTMN
Date: Tue, 17 Nov 1992 22:25:41 GMT


Has a public domain NFS client package for DOS ever been written.  If so, 
would you please let me know where I could get it.
Newsgroups: comp.protocols.nfs
From: karl@ddsw1.mcs.com (Karl Denninger)
Subject: Re: PC-NFS and Bootp
Date: Wed, 18 Nov 1992 15:24:14 GMT
Distribution: na
Organization: MCSNet, Chicago, IL

In article <1e7cuuINNe30@gazette.bcm.tmc.edu> sob@TMC.EDU (Stan Barber) writes:
>In article <1db96aINN4b4@seven-up.East.Sun.COM> geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
>>Our current thinking (*not* committed product plans, please note!) is
>>that we'll skip BOOTP and adopt DHCP, which is a much more complete
>>solution.
>
>Geoff, I think this is a mistake. BOOTP is now quite widely used and you
>can leverage off of this installed base instead of forcing people to have
>to implement another protocol to support PC-NFS. Consider all the people who
>have bunches of X terminals (Yes, I know... it may be sacriledge to believe
>in X terminals...).

Actually, I hope they DON'T implement BOOTP.  It's another reason to buy
Beame's product instead of Suns -- standards complience.

(On top of the others, which include smaller size, better Windows
integration, fuller featured, no stupid "broadcast copy protection" 
hassles, better support, etc).  

Oh, did I forget that last time I checked B&W was less expensive too?

--
Karl Denninger (karl@ddsw1.MCS.COM, <well-connected>!ddsw1!karl)
Data Line: [+1 312 248-0900] Anon. arch. (nuucp) 00:00-06:00 C[SD]T
Request file: /u/public/sources/DIRECTORY/README for instructions
From: tyen@cs.utexas.edu (Anthony Yen)
Newsgroups: comp.protocols.nfs
Subject: Re: HELP:  Can't mount printers
Date: 19 Nov 1992 17:02:23 -0600
Organization: Coffee R Us
Distribution: world
NNTP-Posting-Host: ai.cs.utexas.edu

In article <lgl37rINNm4q@ai.cs.utexas.edu> tyen@cs.utexas.edu (Anthony Yen) writes:
>
>PC-NFS 4.0 refuses to mount a printer, with the diagnostic message:
>
>	NFS040F : The specified file system is not local to server mundo.
>
>This is after I give the command:
>
>	net use lpt2: mundo:lw_3.138 /cmd=h /fmt=p /wsize=1024
>
>Attempting to mount the printer from nfsconf fails with the diagnostic
>message:
>
>	NFS157F : The mount request failed.
>
>A "net printers" gives the diagnostic message:
>
>	NFS228F : Can't get printers from server
>
>However, a "net printers mundo" gives a complete and correct list of
>printers.  Also, there are no problems with mounting file systems,
>either from the command line or under nfsconf.


Thanks to everyone for their responses!  Ironically, the day after I
submitted the posting, I received the most recent issue of SunExpert,
which said the same thing everyone else mentioned: be sure to mount
/var/spool/pcnfs (or /var/spool) via /etc/exports.  I did that, but it
still didn't work.

I puzzled over this for awhile, and then from out of the blue I came
up with an idea to check my /etc/netgroups file.  I added the DOS
machine's name to the machine list, and everything went hunky-dory
after that.  Don't even ask me why I thought of /etc/netgroups, even I
don't know how I arrived at that.  The manual does not mention this,
too.  I am sort of puzzled why the authentication for file services
still let me pass through, even though the DOS box's IP name was not
on the validation list.

Oh, and to the PC-NFS team: what a SLICK piece of work, it's great!

Thanks again!
-- 
 ____     tyen@cs.utexas.edu.....Kowabunga!...
  /ony -- Claimer: Views expressed here == mine && only mine.  Sail tough.
From: curt@ekhadafi.austin.ibm.com (Curt Finch 903 2F021 curt@aixwiz.austin.ibm.com 512-838-2806)
Newsgroups: comp.protocols.nfs
Subject: Re: pcnfslpd v4 locking up w/AIX server
Date: 19 Nov 92 13:54:37 GMT
Organization: IBM AWD, Austin

In article <Nov1992.082953.17774@ccai.clv.oh.us> grover@ccai.clv.oh.us (grover davidson) writes:
>SUN, I have been sent a new version of pcnfslpd. The people at Sun have
>told me that rembak, the program that is responsable for actually sending
>the spool request to the remote machine, appears to be using a NEW socket
>for every job. So, after x number of jobs have been sent, the pc print

Does this mean that rembak has a bug?

should it be closing these sockets out or something in some way that
it's not?

certainly it is supposed to be ok (isn't it?) to use a different
socket for every request

or does the lpr/lpd protocol (such as it is) preclude such behaviour?


-- 
curt@aixwiz.austin.ibm.com (Curt L. Finch) | AIX NFS/NIS Field Quality 
My views are unrelated to those of IBM     |        Austin, TX
     Lead_or_Leave's objective is to get all Congressmen to sign a pledge 
  that if the Deficit has not halved by their term's end, they'll step down.
From: tyen@cs.utexas.edu (Anthony Yen)
Newsgroups: comp.protocols.nfs
Subject: HELP:  Can't mount printers
Date: 18 Nov 1992 12:35:39 -0600
Organization: Coffee R Us
Distribution: world
NNTP-Posting-Host: ai.cs.utexas.edu


PC-NFS 4.0 refuses to mount a printer, with the diagnostic message:

	NFS040F : The specified file system is not local to server mundo.

This is after I give the command:

	net use lpt2: mundo:lw_3.138 /cmd=h /fmt=p /wsize=1024

Attempting to mount the printer from nfsconf fails with the diagnostic
message:

	NFS157F : The mount request failed.

A "net printers" gives the diagnostic message:

	NFS228F : Can't get printers from server

However, a "net printers mundo" gives a complete and correct list of
printers.  Also, there are no problems with mounting file systems,
either from the command line or under nfsconf.

The DOS side: Compaq LTE/Lite 25, DR-DOS 6.0, MemoryMax memory
management, SuperStor disk compression, 4 Mb RAM, 60 Mb HD.

The Unix side: Sun SPARCserver 670MP, SunOS 4.1.2, no patches, pcnfsd
version 2.0, all printers are remote, /usr/spool/pcnfs is a local
drive (this is our file server).

I'm at my wits end, could someone please post some hints for what I
should try or look for?  I don't understand why I am receiving a
filesystem diagnostic for print sharing operations.  This is fairly
important to me, since if I can't get this to work, our department
will just look elsewhere for NFS/print-sharing solutions, and I don't
want to go with any other product.

-- 
 ____     tyen@cs.utexas.edu.....Kowabunga!...
  /ony -- Claimer: Views expressed here == mine && only mine.  Sail tough.
Newsgroups: comp.protocols.nfs
From: dte@cs.rit.edu (Dave Emlen)
Subject: Problem: PC-NFS, Windows & com1:
Followup-To: comp.protocols.nfs
Organization: Rochester Institute of Technology
Date: Tue, 17 Nov 1992 17:26:40 GMT

I have a 386 clone (AT&T) running PC-NFS 4.0a and Windows 3.1.  I
also have a serial printer hooked up to the COM1: port.  The
printer works find from the DOS prompt, but when I go into windows
and try to print I get an error message ("Cannot print.  Be sure
that your printer is connected properly...").

If I comment out the PC-NFS/ethernet stuff from config.sys and
autoexec.bat, I can print fine from windows.

If it's any help, my ethernet board is set to IRQ 7, i/o 0x280 &
ram 0xd0000.  I've also tried IRQ = 5.

Anybody know what's going on?

Thanks in advance for any help!

--
Dave Emlen
Computer Science & Information Technology
Rochester Institute of Technology
dte@cs.rit.edu
Newsgroups: comp.protocols.nfs
From: tstark@access.digex.com (Timothy M. Stark)
Subject: Help! Seeking PCNFSD Version 2 for SCO Unix.
Keywords: PCNFSD v2 SCO SYSV3 3.2.4
Organization: Express Access Online Communications, Greenbelt, MD USA
Date: Fri, 20 Nov 1992 12:30:14 GMT

Hello Everyone:

     I am looking for PCNFSD version 2 for SCO Unix system because I need to 
install print services on SCO for a shared PC printer. Only I have SCO PCNFSD
that is version 1 which will not work with print services. If so, I will
appericate that! Thanks you!

-- Tim Stark
  


-- 
Timothy Stark               Internet1: tstark@access.digex.com (Preferred)
837 North Van Dorn St       Internet2: tstark@netcom.com
Alexandria, Va. 22304-2723  TDD: (703) 212-9731 Pager: (703) 702-4078
"Washington, DC is the most deaf population!! -- Gallaudet University"
From: beepy@ennoyab.Eng.Sun.COM (Brian Pawlowski)
Newsgroups: comp.protocols.nfs
Subject: Re: Different implementations of NFS? Sun RPC NFS vs. U. of Guelph ?
Date: 18 Nov 1992 08:37:53 GMT
Organization: Sun Microsystems Inc., Mountain View, CA
NNTP-Posting-Host: ennoyab
Summary: nfs implementations
Keywords: NFS


You got it all wrong, or nearly so.

Sun defined NFS and has an implementation in SunOS (aka Solaris).
From this implementation has been extracted a UNIX reference release
which is ported to a BSD base (in the past) and generally licensed
(through Sun or a master distributor) on generally very good terms.
This release is variously called NFSSRC or ONCSRC.

I have this faint recollection that Lachman Associates (now Interactive),
Unisoft and Mt. Xinu had System V versions of above for licensing?
[It's been awhile since I thought about this].

End of Sun story.

An enterprising fellow at the University of Guelph took it upon
himself to implement an unencumbered (by Sun licenses) version
of NFS client and server in the 4.3BSD Reno release (I think it was that
release where it first appeared). I hear it's so cold in Canada
in the winter that this sort of thing is done all the time to relieve
the boredom. He had help from various people in at least two
countries regardless of the lack of a NAFTA. It is this unencumbered
version which appears in BSD 4.4 (and Net2, and 386/BSD and BSD386,
etc). It also is the basis for NFS in OSF/1 (OSF chose to go with
an unencumbered variant rather than pursue licensing from Sun:-).

There have been *many* non-UNIX implementations from the
public domain specification (as the Guelph work was) which include
(probably with lots of mistakes):

	Sun, Beame and Whiteside, FTP Software, NetManage:
		PC (MS-DOS)
	Sun/EDS/IBM: MVS/NFS
	IBM: VM
	NSC (?), DEC, TGV, Wollongong: VMS
	Wollongong, and others: MAC
	Symbolics: Lisp
	Telesoft: An Ada implementation
	Amiga: AmigaDOS
	Apollo: Domain (what a blast from the past)
	Transarc: NFS->AFS translator

And more (some of above may be slightly incorrect, doing
from memory).

In addition, you kinda threw "NFS" and "RPC" together, and
I thought I should mention that a freely licensed implementation
of RPC source is on-line (cs.rice.edu? others--use archie).
I believe this was used in Guelph implementation?

There's probably more to tell, but my mom just told me
it's time to go to bed.

Brian Pawlowski
In-house NFS historian

P.S. Out of total curiosity: why do you bring this up?
Newsgroups: comp.protocols.nfs
From: tomiii@mtu.edu (Thomas Dwyer III)
Subject: Re: HELP:  Can't mount printers
Organization: Michigan Technological University
Date: Fri, 20 Nov 1992 14:56:04 GMT

geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
>#A "net printers" gives the diagnostic message:
>#
>#	NFS228F : Can't get printers from server
>
>The message should be more informative :-)  If you don't supply a system
>name, NET PRINTERS  will use the current PCNFSD server (see
>NET ALL to list this and other stuff). If there is none, you get
>this message.
>

I hate to get picky here, but I'm not quite sure this is the whole
story.  :-)

What you describe is a great idea.  I would like to see it happen.
Unfortunately, the way I see things working is that using NET PRINTERS
without giving a hostname uses the name of the machine which LPT1 was
mounted from, regardless of the current PCNFSD server.  If there is no
LPT1: mounted, the command fails.

If this is not the case, please let me know what I'm doing wrong.

Thanks!

Tom.III
tomiii@mtu.edu
From: beepy@ennoyab.Eng.Sun.COM (Brian Pawlowski)
Newsgroups: comp.protocols.nfs
Subject: Re: Different implementations of NFS? Sun RPC NFS vs. U. of Guelph ?
Date: 19 Nov 1992 07:19:06 GMT
Organization: Sun Microsystems Inc., Mountain View, CA
NNTP-Posting-Host: ennoyab
Summary: rpc guelph
Keywords: NFS

In article <15546@auspex-gw.auspex.com>, guy@Auspex.COM (Guy Harris) writes:
> >In addition, you kinda threw "NFS" and "RPC" together, and
> >I thought I should mention that a freely licensed implementation
> >of RPC source is on-line (cs.rice.edu? others--use archie).
> >I believe this was used in Guelph implementation?
> 
> Actually, from what I've seen of the 4.3-reno version of Macklem's
> implementation, the kernel part doesn't use a Sun implementation of RPC;
> it has a hand-rolled version.
> 
> User-mode NFS-server services such as the "mount" protocol are
> implemented atop the Sun RPC implementation.

Yeah, I understand this is the case. I kinda slopped around and
assumed Rick didn't hand-roll RPC calls in mount, and do
XDR overlays, etc.

It's interesting code to view to see how one can eliminate
data copies and such...

Also, another correction (I think): Transarc's NFS->AFS translator
is not an NFS implementation, but a state of mind. Perhaps a Transarc
person will describe this functionality and the client proxy for
Kerberos creds and remote operation of acl commands and others.
I found it fascinating.

Brian
AFS apologist

P.S. I would've suggested going to comp.protocols.afs
     but I can't seem to find it... :-) Perhaps they'll slum
     long enough to expound on the translator features.
Newsgroups: comp.protocols.nfs
From: oldera@twg.com (Ed Alcoff -  Prod Mtg)
Subject: PCNFSD for OS/2????
Organization: The Wollongong Group, Palo Alto, CA
Date: Wed, 18 Nov 1992 00:10:19 GMT

Title sez it all.  Anybody done it?  Geoff- you
know of any ports to OS/2?

Thx in adv.

Ed Alcoff
e-mail: oldera@twg.com

Newsgroups: comp.protocols.nfs,comp.unix.ultrix
From: andrew@daneel.rdt.monash.edu.au (Andrew Moore)
Subject: NFS version in Ultrix 4.2 (repost - try again)
Summary: Whats the version of NFS in ultrix 4.2?
Keywords: NFS ultrix 4.2 Version
Reply-To: andrew.moore@rdt.monash.edu.au
Organization: Monash University, Melb., Australia.
Follow-Up: poster
Date: Sun, 22 Nov 1992 01:14:22 GMT

(Sorry if this is a repeat, my local news machine seemed a bit sick
last time.)

So shoot me for not saving articles that I'll need later....

There was a thread about NFS versions (versions of the NFS protocol) in
particular the differences in the number of transmitted packets (lookup
etc) between the version of NFS on Ultrix and SunOS....

Any body got the gory details saved away ? (and want to forward them to
me ?)

In particular what is the version of nfs in the Ultrix4.2
implementation and the version of NFS  on (say) SunOS 4.x ?

A Quick and dirty summary of the differences if they were posted would
be greatly appreciated.

(email me on this one as I figure this probably has little interest to
the groups. Given enough demand I will post a summary.)

look forward to a reply,
Thanks,
Andrew.
-- 
    Andrew Moore      |    Department of Robotics and Digital Technology
Ph:  +61 3 573 2063   |  Caulfield Campus, Monash Uni, VIC 3145, Australia
Fax: +61 3 573 2345   |       E-Mail:  andrew.moore@rdt.monash.edu.au 
 Be interested in the future, you will be spending the rest of your life there.
From: beepy@ennoyab.Eng.Sun.COM (Brian Pawlowski)
Newsgroups: comp.protocols.nfs
Subject: Re: Different implementations of NFS? Sun RPC NFS vs. U. of Guelph ?
Date: 18 Nov 1992 08:49:03 GMT
Organization: Sun Microsystems Inc., Mountain View, CA
NNTP-Posting-Host: ennoyab
Summary: whoops nfs
Keywords: NFS

I re-read my note, and the following sentence was a little
misworded:

> There have been *many* non-UNIX implementations from the
> public domain specification (as the Guelph work was) which include
> (probably with lots of mistakes):

Of course I meant there were probably lots of mistakes (and
omissions) in my list--*not* in the various implementations
from the specification:-)

BTW: You can read Rick Macklem's write-up on the Guelph work,
which is generally interesting (except for some conclusions
on fundamental server bottlenecks--an effect of his unfortunate
choice of platform to implement on:-) in the Winter '91
Usenix proceedings.

Brian
From: larry@elvis.NoSubdomain.NoDomain (Larry Pollack)
Newsgroups: comp.protocols.nfs
Subject: HELP: Can't access B:
Date: 20 Nov 92 20:10:24 GMT
Reply-To: larry@xlnt.com
Organization: XLNT Designs, Inc.

I recently upgraded to Windows 3.1 and PC-NFS 4.0 (in that order).
Now, when I run MS-DOS from Windows, I can no longer access drive B:.
I am using a Positive 386 25 MHz with a 3Com 3C503 network card. Here
are the CONFIG.SYS and AUTOEXEC.BAT files:

DEVICE=C:\QEMM\QEMM386.SYS R:2 rom RAM VHI:N ST:M x=a000-c7ff xst=c000
break=on
STACKS=0,0
buffers=30,8/x
shell=c:\dos\command.com /p /e:512
DEVICE=C:\dos\ANSI.SYS
install=c:\dos\share!.exe
DEVICE=C:\QEMM\LOADHI.SYS /R:1 C:\NFS\PCNFS.SYS /c^
DEVICE=C:\NFS\SOCKDRV.SYS
DEVICE=C:\QEMM\LOADHI.SYS /R:2 C:\NFS\VECIE6.SYS /i5
DEVICE=C:\NFS\NFSVEC.SYS


@ECHO OFF
path c:\qemm;C:\WINDOWS;c:\dos;c:\bin;c:\nfs;c:\brief;c:\borlandc\bin;c:\norton;c:\poly
PATH=%PATH%;p:\nfs4.0\utils
set bpath=;c:\brief\macros
set bhelp=c:\brief\help
set bpackages=h,c-c,asm:r
set bflags=-i120l256z -mLJP -Dega -D101key
set btmp=c:\temp
set MAILDIR=M:\
SET TZ=PST8PDT
SET COMSPEC=C:\DOS\COMMAND.COM
SET NFSDRIVE=C
SET NFSPATH=C:\NFS
set TEMP=C:\WINDOWS\TEMP
c:\qemm\loadhi /r:2 files 40
c:\qemm\loadhi /r:2 lastdriv v
c:\qemm\loadhi /r:2 nde
C:\QEMM\LOADHI /R:1 C:\WINDOWS\SMARTDRV.EXE /L
PRT -T30 *
C:\NFS\NET INIT
PROMPT $P$_$G
VER
rdate elvis
c:\qemm\loadhi /r:1 C:\XVIEW\rtm.exe
C:\XVIEW\rnmfile.exe
C:\XVIEW\ifpcnfs.exe
rem pause
win

If I insert the "pause" statement at the end of AUTOEXEC.BAT and stop
the batch file before running Windows, I can access the B: drive. If I
type WIN and run the file manager, I can access the B: drive. As soon
as I run a DOS prompt from Windows, I can no longer get to the B:
drive; not from the file manager, nor from DOS after exiting Windows.

Is there some option in the .PIF I should be setting when I run DOS
from Windows? Any help would be appreciated. Please e-mail to address
below.

/======================================================================\
| Lawrence J. Pollack                   | Your source for FDDI SMT.    |
| XLNT Designs, Inc.                    | Voice   : 619-487-9320       |
| Internet: larry@xlnt.com              | Fax     : 619-487-9768       |
\======================================================================/
Newsgroups: comp.protocols.nfs
From: toreh@bootes.sds.no (Tore Haraldsen)
Subject: YP sources available anywhere?
Organization: Statens Datasentral A/S, SDS, Norway
Date: Wed, 18 Nov 1992 23:16:24 GMT

The subject says it all: Is there sources available for YP anywhere on
the net? I would like to run YP on my 386BSD system...

-- tore
-- 
------------------------------------------------------------------------
Tore Haraldsen, Statens Datasentral A/S - SDS, Norway
email: toreh@bootes.sds.no
From: sob@TMC.EDU (Stan Barber)
Newsgroups: comp.protocols.nfs
Subject: Re: PC-NFS and Bootp
Date: 16 Nov 1992 05:52:30 GMT
Organization: Baylor College of Medicine, Houston, Tx
Distribution: na
NNTP-Posting-Host: tmc.edu

In article <1db96aINN4b4@seven-up.East.Sun.COM> geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
>Our current thinking (*not* committed product plans, please note!) is
>that we'll skip BOOTP and adopt DHCP, which is a much more complete
>solution.

Geoff, I think this is a mistake. BOOTP is now quite widely used and you
can leverage off of this installed base instead of forcing people to have
to implement another protocol to support PC-NFS. Consider all the people who
have bunches of X terminals (Yes, I know... it may be sacriledge to believe
in X terminals...).
-- 
Stan           internet: sob@bcm.tmc.edu         Director, Networking 
Olan           uucp: rutgers!bcm!sob             and Systems Support
Barber         Opinions expressed are only mine. Baylor College of Medicine