HDTenEightyP/NetNews huggingface dataset:
From: scott@statsci.com (Scott Blachowicz)
Subject: PC-NFS access to UNIX filenames
Reply-To: scott@statsci.com
Organization: Statistical Sciences, Inc., Seattle, WA USA
Date: Mon, 6 Apr 1992 23:05:33 GMT

Hi-
   Some co-workers are really dealing with this stuff, but...

   I was wondering how the PC NFS implementations deal with the different
filenaming conventions and restrictions among the systems that can be running
NFS. The main problem is that MSDOS is more restrictive in what filenames are
legal than UNIX is (shorter names, different characters in the names). Are
there PC NFS implementations that allow you to put a file in each directory to
designate what the filename should appear as to an MSDOS user? This would
allow a directory containing the files
   bigfilename1.c bigfilename1.h bigfilename2.c bigfilename2.h
to get mapped to the names
   bigfn1.c bigfn1.h bigfn2.c bigfn2.h

   The idea here is to share the use of files between UNIX and MSDOS. Does
anything take care of the differences in text-file line termination characters
(NL vs CR-NL)? Or is this just a hopeless cause?

Just wondering what other people do...

Thanx,
--
Scott Blachowicz    USPS:  Statistical Sciences,  Inc    Ph: 206/283-8802 x240
                             1700 Westlake Ave N #500   FAX: 206/283-8691
E-Mail: scott@statsci.com      Seattle, WA USA  98109
..or..  uunet!statsci!scott
..or..  scott%statsci.uucp@coco.ms.washington.edu
From: cro@socrates.ed.asu.edu (C. R. Oldham)
Newsgroups: comp.protocols.nfs
Subject: Re: PC-NFS access to UNIX filenames
Date: 7 Apr 92 15:43:37 GMT
Organization: North Central Association, Commission on Schools

scott@statsci.com (Scott Blachowicz) writes:

>Hi-
>   Some co-workers are really dealing with this stuff, but...

>   I was wondering how the PC NFS implementations deal with the different
>filenaming conventions and restrictions among the systems that can be running
>NFS.

Well, for PC-NFS, long filenames and mixed case filenames get mapped
to totally unintuitive 8.3 names on the PC side consisting of the
first four characters of the original filename, a tilde (~), and two
random characters.  This is a real pain--there are better ways
that it could be done.  For instance, in my home directory I have a
file called "dead.letter"--common occurrence on Unix.  When I mount
that directory on the PC, I get a file called
	DEAD~~HI
What's more, next time I login, the file may be mapped as
	DEAD~~HO
For Unix filenames starting with a dot, the mapped filename starts with
a ~.  So .nn maps to
	~NN~~~BY
Fortunately, Sun's PC-NFS's ls program for the PC allows you to see
what the Unix filenames are.

If you're using OS/2 and the IBM TCP/IP package, this limitation
is not present.  (Disclaimer--this is hearsay--I don't have the
packages yet.)

>   The idea here is to share the use of files between UNIX and MSDOS. Does
>anything take care of the differences in text-file line termination characters
>(NL vs CR-NL)? Or is this just a hopeless cause?

PC-NFS provides PC programs dos2unix and unix2dos that translate
the line terminators.  But printing from a PC to a printer attached
to a Sun exhibits many problems if the printer needs CR/LF to end
a line instead of a LF.  I had to write a quick Perl script to
add the CR and all my print jobs (that I start from my Unix terminal)
have to pipe the text through that script before it will print out
right.  Print jobs sent from a PC are fine--they already contain the
correct line terminators.

>Thanx,

You're welcome.

Charles R. (C. R.) Oldham | North Central Association, Commission on Schools
cro@socrates.ed.asu.edu or| Arizona State University, Tempe, AZ 85287-3011
aocro@acvax.inre.asu.edu  | 602/965-8700:800/525-9517 | #include <disclaimer.h>
"For the Lord is a great God, and a great King above all gods..." Psalm 95:3
Xref: sparky comp.protocols.nfs:1254 comp.os.msdos.pcgeos:290
From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs,comp.os.msdos.pcgeos
Subject: Re: PC-NFS 3.5 and GeoWorks Ensemble
Date: 9 Apr 92 18:42:47 GMT
Reply-To: geoff@east.sun.com (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Organization: Sun Microsystems PC-NFS Engineering
NNTP-Posting-Host: hinode.east.sun.com

Quoth angelini@irisa.fr (Pierre Antoine Angelini) (in <1992Apr9.143317.22480@irisa.fr>):
#Hello.
#I'm trying to have GeoWorks Ensemble working with PC-NFS 3.5.
#
#I mean:
#-full installing GeoWorks on a networked drive (r:)
#-launching it from r:
#
#All I got is
#
#System error: Fatal error in z.
#
#Everything works perfectly well when installed on a local hard disk,
#even with PC-NFS running. I can browse with Geomanager through
#networked drive, etc...
#
#BUT:
#
#The documentation says that : ...... Geoworks supports various lans
#Lantastic, Novell, PC-NFS 3.5 and Lan Manager. I don't really believe
#the local representative who told me that the documentation was wrong.
#
#Can you help me ?
#
#Thank you
#
#--------------------------------------------------------------------------------
#Pierre-Antoine ANGELINI (PAA)          #  E-mail :    angelini@irisa.fr     

I'm cross-posting this to comp.os.msdos.pcgeos to see if any other
GeoWorks users have any idea. I haven't tried this myself: I always
run GeoWorks from my local hard disk. It's reasonably stable, though
I still get an occasional "bad handle". Running with FILES=64 and
putting /f64 on the PCNFS.SYS line helps.

Geoff

------------------------------------------------------------------------------
--         Geoff Arnold, PC-NFS architect (geoff.arnold@East.Sun.COM)       --
--                SunConnect, A Sun Microsystems Business                   --
------------------------------------------------------------------------------
From: sob@TMC.EDU (Stan Barber)
Newsgroups: comp.protocols.nfs
Subject: Re: PCNFSDV2/Ultrix/PC-NFSV4.0
Date: 13 Apr 1992 03:26:30 GMT
Organization: Baylor College of Medicine, Houston, Tx

In article <1992Apr8.115602.7304@waikato.ac.nz> slang@waikato.ac.nz writes:
>Does PC-NFS V4.0 require PCNFSDV2, or will it run with PCNFSDV1 as well.

Yes, it will work with PCNFSDV1, but some functionality is lost mostly having
to do with printer management.

-- 
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
From: hello@cs.utwente.nl (Ronald Hello)
Newsgroups: comp.protocols.nfs
Subject: Re: YPBIND Question
Date: 6 Apr 92 12:45:49 GMT
Reply-To: hello@cs.utwente.nl
Organization: University of Twente, Dept. of Computer Science

In article 278@gordon.UUCP, jpd@gordon.UUCP (Jim Drummey) writes:
cp>I've just set up an HP9000/700 on my network and configured the lan0
cp>interface. I can telnet and ftp til the cows come home, but can't get
cp>ypbind to find a server. I've done some packet watching during the time
cp>that ypbind is trying and don't see any packets coming out. I've checked
cp>all the obvious things, portmapper, domainname etc., ...everything looks
cp>right. There are several other machines configured the same way on the same
cp>net which are OK ( non-HPUX) . Is there a known problem with yp on this
cp>machine? I'm running HP-UX 8.05.
cp>========================================================================
cp>Jim Drummey Unix Admin
cp>Computer Associates Intl    harvard!necntc!gordon!jpd
cp>=======================================================================


You probably suffer from a mismatch in broadcast addresses. HP uses all 1's
(e.g. 192.15.98.255) and SUN's use default all 0's (e.g. 192.15.98.0).
The machines only recognize what they use themselves, so your NIS servers
(who probably use all 0's) don't recognize the broadcast generated by
ypbind.
It's easy to change broadcast addresses on SUN's, it's harder on a HP.

Hope this helps,
Ronald.
From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs
Subject: PC-NFS and Intel Etherexpress-16
Date: 15 Apr 92 22:16:25 GMT
Reply-To: geoff@east.sun.com (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Organization: Sun Microsystems PC-NFS Engineering
NNTP-Posting-Host: hinode.east.sun.com

Quoth  Fred Yang (in <10405@inews.intel.com>):
#Anyone out there know if PCNFS4.0 runs on Intel EtherExpress 16
#Ethernet controller card?
#
#I tried to install PCNFS3.01 on EtherExpress-16, it does not work,
#I think I did not install the driver correctly.  

I've been working with Intel to fix some compatibility problems between
PC-NFS and the EXP16.DOS NDIS MAC. It's almost there, but there are a
couple of outstanding issues. I'm running an Exp16 with his latest
driver and it looks pretty good - fast, too. If there's interest I'll
put a copy up on bcm.tmc.edu for FTP (but not until it's really
ready).

Geoff

------------------------------------------------------------------------------
--         Geoff Arnold, PC-NFS architect (geoff.arnold@East.Sun.COM)       --
--                 SunSelect, a Sun Microsystems Business                   --
------------------------------------------------------------------------------
From: geoff@East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs
Subject: Re: Does PC-NFS V. 3.5 work with class B IP
Date: 7 Apr 92 12:26:04 GMT
Reply-To: geoff.arnold@East.Sun.COM
Organization: Sun Microsystems PC-NFS Engineering
NNTP-Posting-Host: bodleian.east.sun.com

The answer is, it works, mostly, except for a few situations. This was
fixed in the PC-NFS 3.5a/b/c jumbo patches, ftp'able from various sites.
Or you can upgrade to 4.0....

------------------------------------------------------------------------------
--         Geoff Arnold, PC-NFS architect (geoff.arnold@East.Sun.COM)       --
--                SunConnect, A Sun Microsystems Business                   --
------------------------------------------------------------------------------
From: leoh@hardy.hdw.csd.harris.com (Leo Hinds)
Newsgroups: comp.protocols.nfs
Subject: Re: PC-NFS 4.0 and MS Windows--telnet windows only painting halfway
Keywords: PC-NFS windows telnet
Date: 16 Apr 92 19:09:58 GMT
Organization: Harris Computer Systems, Ft. Lauderdale, FL

In article <hz01930.703255404@cygnus> hz01930@hx.deere.com (Jay D. Anderson) writes:
>This problem occurs on both 3.0 and 3.1 versions of Windows.  About 50% of the
>time, telnet windows will not repaint completely after a return is typed in.

This problem IS mentioned in the readme file ... I only assume that it implies 
a fix is imminent.

leoh@hdw.csd.harris.com         	Leo Hinds       	(305)973-5229
Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n
creireg ?!!!!!!? ... znlor arkg gvzr
Xref: sparky comp.protocols.nfs:1228 comp.sys.sgi:6526
From: ianh@resmel.bhp.com.au (Ian Hoyle)
Newsgroups: comp.protocols.nfs,comp.sys.sgi
Subject: How do I clear a stale NFS file handle (Irix 4.0.1) ?
Date: 7 Apr 92 04:25:11 GMT
Organization: BHP Research - Melbourne Laboratories, AUSTRALIA

We have a machine (morrigan) which exports one of it's file systems
which another machine (morgana) mounts using a soft mount point. From
the /etc/fstab on morgana (remembering that these are SGI machines running
Irix 4.0.1):

morrigan:/utils1      /utils1       nfs rw,retry=1,soft,intr,bg  0 0

We have just had morrigan's disk replaced and in that time morgana has
decided that it doesn't like the NFS mounted /utils1 any more:

# df -k
Filesystem                 Type  kbytes     use   avail %use  Mounted on
/dev/root                   efs   31164    9057   22107  29%  /
/dev/dsk/xyl0d1s7           efs  981925  518531  463394  53%  /data1
/dev/dsk/xyl0d2s7           efs  982506  719450  263056  73%  /visual
/dev/dsk/xyl0d0s2           efs  560616  464659   95957  83%  /ipada
/dev/usr                    efs  292320  227695   64625  78%  /usr
morrigan:/utils2            nfs  305152  197376  107776  65%  /utils2
df: cannot get status from /utils1: Stale NFS file handle

I have tried to umount /utils1 but get 

# umount /utils1
/utils1: Device or resource busy

The -k flag to umount doesn't work either. I even tried re-exporting /utils1 
from morrigan but I'm starting to clutch at straws now.

How do I clear away the stale NFS file handle without rebooting ????

        ian
--
               :   Ian Hoyle,  Senior Research Scientist
               :   Image Analysis Group
     /\/\      :   BHP Research - Melbourne Laboratories
    / / /\     :   245 Wellington Rd, Mulgrave, 3170, AUSTRALIA
   / / /  \    :   Phone    +61-3-560-7066
  / / / /\ \   :   E-mail   ianh@resmel.bhp.com.au
  \ \/ / / /   :   
   \  / / /    :  "Now I've got the bead on you with MY disintegrating gun.
    \/\/\/     :   And when it disintegrates, it disintegrates. (pulls trigger)
               :   Well, what you do know, it disintegrated."
               :        -- Duck Dodgers in the 24th and a half century
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.protocols.nfs
Subject: Re: Sun automount bug w/ direct maps
Date: 8 Apr 1992 06:18:49 GMT
Organization: Thinking Machines Corporation, Cambridge MA, USA
NNTP-Posting-Host: godot-1.think.com

In article <4508@d75.UUCP> curt@aixwiz.austin.ibm.com (Curt Finch) writes:
>Automount should ignore direct map entries of the form
>
>/directoryname -options myhostname:/directoryname
>
>whenever the local hostname is myhostname.

The usual workaround is to put all your exported directories in a different
location than what people normally use.  For instance:

/directoryname -options server:/export/directoryname

This will work on clients and on servers.  In this case, automount *is*
smart about recognizing that it's running on the server; instead of
doing an NFS mount, it just creates a symbolic link from /directoryname to
/export/directoryname.  It's kind of silly that it doesn't go further and
recognize when the server is the current system and the pathnames are the
same.

>Has anyone else ever encountered this, and has Sun fixed it and if
>so in which release?

Many people have complained about it.  As far as I know, Sun hasn't fixed
it as of 4.1.2.
-- 
Barry Margolin
System Manager, Thinking Machines Corp.

barmar@think.com          {uunet,harvard}!think!barmar
Newsgroups: comp.protocols.nfs
From: sherwood@fenris.space.ualberta.ca (Sherwood Botsford)
Subject: Re: number of nfsd to run
Organization: University Of Alberta, Edmonton Canada
Date: Thu, 16 Apr 1992 18:56:43 GMT

Guy Harris writes
> >Since nfsds run in a round-robin fashion (and rapidly) if there are more of
> >them then there are contexts in the MMU there can be a significant amount
> >of overhead involved (I know this to be true on Suns and assume it may be  
true
> >on DEC systems).
> 
> Oh, no, not this again, please.
> 
> 1) SunOS 4.x does *NOT* assign MMU contexts to processes, such as
>    "nfsd"s (and "biod"s), that have relinquished the user-mode portion
>    of their address space.  They all run in context 0, which is
>    permanently assigned to the kernel, so you can run more "nfsd"s than
>    there are contexts in the MMU without thrashing contexts.
> 
> 2) The DEC system is probably a MIPS-based system - its MMU is basically
>    just a TLB that causes a fault if you get a TLB miss, and it gets
>    reloaded by software.  The page tables themselves are probably kept
>    in main memory; the only place where context numbers might be
>    involved are in virtual address caches and in TLB searching (the
>    R-series chips do have a 6-bit "PID", which is basically a context
>    number, used in TLB entries).

So, does this mean that running an arbitrarily large number of nfsd's will  
exact only a small performance hit on the machine?  (Assume that most of the  
time, most of them are snoozing.)
Newsgroups: comp.protocols.nfs
From: sherwood@space.ualberta.ca  (Sherwood Botsford)
Subject: timing between ethernet packets....
Organization: University Of Alberta, Edmonton Canada
Date: Fri, 10 Apr 1992 03:50:07 GMT


I'm going to muff it on terminology here...

When tinkering with spray, I found out something interesting about a machine on
the adjacent net:

Send packets of 1K,2K,3K... No problem 6K .1% dropped 7K 3% dropped 8K 90%  
dropped.  This was with a delay of 4000 microseconds.

It would appear that one of the routers in between couldn't handle an 8k  
packet. (which would be 6 ethernet packets)

On another experiment, I found that with no delay, there was a 17% loss with 1  
K packets, and at 2K, the router gave up the ghost.

This brings up a couple questions:
With NFS, or on the configuration of the ethernet driver, is there a built in  
delay between transmission of successive packets?  If so, what is it?

The router is a PC.  I don't recall the software package used, but I do recall  
that one such PD package was mentioned once upon a time here.  What is the name  
of that package, and is it more robust about not crashing when hit by closely  
spaced packets.
From: moty@techunix.technion.ac.il (Moty Gerner)
Newsgroups: comp.protocols.nfs
Subject: How to connect a MAC to SGI fileserver.
Keywords: IRIX MAC SGI
Date: 12 Apr 92 09:48:16 GMT
Article-I.D.: techunix.moty.703072096
Organization: Mail to News Gateway

Hi net-people !

We have here three MAC IIsi connected to an appletalk net. We also intend to
buy some IRIX indigo SGI stations using one of them as a fileserver.
Now, we want to use NFS and mount the fileserver disks on the MACs.
My question is - how do we do this ? What hardware/software do we need ?
The word is such connection is very slow, is this true ?

Thanks

Moty Gerner.
Newsgroups: comp.protocols.nfs
From: john@iastate.edu (John Hascall)
Subject: Re: Problems with NFSWATCH
Organization: Iowa State University, Ames, IA
Date: Mon, 13 Apr 1992 13:21:15 GMT

G.Eustace@massey.ac.nz (Glen Eustace) writes:
}Has anyone got a copy of NFSWATCH that works correctly with Ultrix
}4.1/2  The version we have doesn't seem to see any RPC packets at
}all.  The only things counted are broadcasts and non-IP packets.

Yes, normally it doesn't see any packets directed to itself.  You
can do (at least under V4.2):

	# ifconfig ln0 copyall
	# nfswatch [options]...
	# ifconfig ln0 -copyall

to change this (you don't want to leave copyall on though).  I have
heard rumors of a new & improved NFSWATCH on gatekeeper.dec.com
but haven't checked it out yet.

John
From: banner@spock ( banner@semi.mitel.com )
Newsgroups: comp.protocols.nfs
Subject: NFS products for OS/2
Keywords: OS/2,NFS,software
Date: 15 Apr 92 17:34:10 GMT
Followup-To: banner@semi.mitel.com
Organization: Mitel. Kanata (Ontario). Canada.

I am looking for information about any commercially available NFS
packages that run under OS/2. If you know of any, or have any experience
please drop me a line at the Email address below... I'll post a summary
at a later date.

If this is a FAQ, point me the direction where I can nab the information
file...

Thanks,

-- 
========================================================================
Ross Bannerman           | Usenet: banner@semi.mitel.com
MITEL Corp. Kanata, Ont. | "It was like that when I got here..."
========================================================================
From: curt@aixwiz.austin.ibm.com (Curt Finch)
Newsgroups: comp.protocols.nfs
Subject: Sun automount bug w/ direct maps
Date: 6 Apr 92 14:55:17 GMT
Reply-To: curt@aixwiz.austin.ibm.com (Curt Finch)
Organization: IBM AWD, Austin, TX


If you have a direct map with Sun's 4.1.1 automounter which maps
/dirmap on host fred.com to /dirmap, so that any reference on any
machine to /dirmap will cause fred.com:/dirmap to be mounted,
this will cause a hang on that mount point if you are on fred.com.

i.e. while running automount on fred.com, if you try to access /dirmap,
the automount program prohibits local access to that directory.
Automount should ignore direct map entries of the form

/directoryname -options myhostname:/directoryname

whenever the local hostname is myhostname.

Has anyone else ever encountered this, and has Sun fixed it and if
so in which release?

curt@aixwiz.austin.ibm.com (Curt L. Finch) | AIX NFS/NIS Field Quality 
My views are unrelated to those of IBM     |       Austin, TX
 "A little rebellion is a good thing now and then" - Thomas Jefferson
From: hanke@nessie.cs.id.ethz.ch (Norbert Hanke)
Newsgroups: comp.protocols.nfs
Subject: Re: Using DOS BACKUP with PC-NFS mounted drives
Date: 8 Apr 92 06:34:48 GMT
Article-I.D.: bernina.1992Apr8.063448.2607
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH

In article <7462@uqcspe.cs.uq.oz.au> dirk@cs.uq.oz.au writes:
>I am having problems using the standard DOS program, "BACKUP", to
>backup local drives on to a drive mounted under PC-NFS.  The message
>displayed is "Target can not be used for backup".  The mount seems
>to be set up correctly, ie. I have write permissions, etc.
>
>Any assistance would be greatly appreciated.  I am using DOS 3.3 and
>PC-NFS v3.5c on a 386-25.
>

Using DOS 5.0 BACKUP to a drive mounted under PC-NFS works: BACKUP creates
a subdirectory BACKUP on the mounted disk and stores two files in it:
A small index file and a large file with the backed-up files in it.

Norbert Hanke
ETH Zurich, Switzerland
Newsgroups: comp.protocols.nfs
From: phil@saxon.syd.dwt.CSIRO.AU (Phil Irvine)
Subject: Re: PC-NFS 4.0, Xvision 4.0, and Win 3.1 - Problems ?
Keywords: NFS, XVISION, WIN 3.1
Organization: CSIRO Division Of Wool Technology,Sydney
Date: Fri, 10 Apr 1992 04:48:01 GMT

In article <russur.702758131@convex.convex.com> russur@convex.com (Russ Urquhart) writes:

>My groups is about to upgrade to PC-NFS 4.0 & Win 3.1, using Xvision 4.0. ARe
>there any problems with using these together? Has anyone already used them?
>
>Speaking to Unipress Tech Support for Xvision, they stated that I would have
>to re-install Xvision after Win 3.1 was installed! I hope that there is an
>easier solution! They said that Visionware was aware of the problem!
>
>They are faxing my some info on problems that they are aware of, if anyone is
>interested, I can post that info up here!
>
>They were, however, unable to inform me as to whether Xvision 4.o would work
>with the new version of PC-NFS. They weren't sure if their TSR (NCINFS) would
>be necessary for this version or not!
>
>Can anyone shed some light on this?
>

I am intending to run the same configuration. 

At present we are using PC-NFS3.5c, Windows3.0 and Xvision 4.0.

The Australian technical suooprt person for Visionware told me that
the version of VWCOMMS that we  have does not support PC-NFS 4.0. It is
expected to be available by June!!! I hope it is sooner than that
I think that NCINFS may not be needed, as for some other NFS on PC software.

What it will allow, even if the NCI is needed is for it to be loaded
by Windows so that it does not occupy low memory space. This can be done
using WINSTART.BAT. With pc-nfs 3.5 this causes system crashes but v4.0
has DLL support and allows proper use by windows.

-- 
Phil Irvine  (phil@syd.dwt.CSIRO.AU)
CSIRO Division of Wool Technology
RYDE, NSW, AUSTRALIA
From: sumargoh@serss0.fiu.edu (H. Sumargo)
Newsgroups: comp.protocols.nfs
Subject: A Driver to Redirect any LPT# to a Network Port
Keywords: Network
Date: 15 Apr 92 00:57:18 GMT
Organization: Florida International Univ.


I am looking for a device driver that allows me to map any LPT# port to the network port such that if I print to that port, it will be redirected to any of the designated network printer.  Please send you response to sumargoh@serss0.fiu.edu

Thank you.
Xref: sparky comp.protocols.nfs:1253 comp.os.msdos.desqview:1623