I remember in my intro operating systems class we learned that you could open a file for read or write and they had a file offset pointer etc. Then I learned that NFS (v1 and v2) were stateless. The joke I heard was that Sun servers were so unstable in the 1980's that the system was stateless so that it could crash and reboot and didn't need to worry about the client's file state.
My college used AFS (Andrew File System) and the DCE Distributed Computing Environment. It was great as a normal user being able to create my own ACL Access Control Lists of other groups of students and give them read access to some files and make directories for class projects and give another student write access to a single directory in my home dir. NFS with groups is so limiting in comparison.
https://en.wikipedia.org/wiki/Distributed_Computing_Environm...
I haven't used LaTeX in a long time but I was always impressed how it could make integral symbols over fractions with summations and everything else look perfect.
I had a summer internship in 1995 and the Win 3.1 machine was so unstable for running an X server to the Suns, 3270 mainframe emulator, and browser using the Win32s (environment for running 32-bit application on 16-bit Win 3.1)
We found the supply closet with over 200 old 486 machines. The other intern and I installed Linux on some and it worked far better than the Win3.1 setup. The older guys saw it and wanted one too. We set up an assembly line with a Linux NFS server with the Slackware disk images to avoid swapping floppies. At least over a 10 Mbit network we found the NFS performance to be fine.
A couple of years later at my job after graduation I convinced our manager to buy PCs to use as X terminals with larger monitors and move the Suns to the closet for the chip design jobs.
I remember having some NFS issues and Trond Myklebust (Linux NFS guy) had me trying some NFS version 3 patches that improved performance between a Linux client and Solaris server.