🚀 go-pugleaf

In article <1992Oct3.115657.15290@csus.edu> eps@futon.SFSU.EDU (Eric P. 
Scot) writes:

> + Logging out did not unmount AppleShare servers.  Logging in
>   again would wedge the automounter resulting in NFS getattr
>   failures on terminals or a hopelessly hung Workspace when
>   attempting to browse AppleShare, making it impossible to log
>   out.  (Reboot seems to be the best course of action here.)
> + The automounter didn't always dismount properly at shutdown,
>   with the message "CAUTION: some processes wouldn't die"
>   appearing.
> 
> "Really looking forward to NeXTSTEP 3.1"

I have had problems with printing. I've printed OK from root every time I've
tried it, but when logging in as a user the print job seems to hang. After
a few minutes, trying to access the /Net/AppleShare folder locks up my
WorkSpace, forcing me to reboot without first being able to sync the
filesystem.

The automounter sequence(s) used under AppleShare are causing me great pain.
In fact, AppleShare has been disabled on my machine and will remain that
way until NS 3.1. If NeXT is going to advertise AppleShare connectivity as an 
advantage, then it better work or it severely damages the reputation of
NeXT. I've found one of the major advantages of NeXT has been stability of
major OS releases. 3.0 is on the hairy edge so far. If the new IB, PB, DL,
etc. cause me more grief, then I'll start wishing I had waited to install
3.1.

As far as AppleShare, doesn't it strike you a bit funny that several pages
of the 3.0 Release Notes were dedicated to NetWare problems/fixes, while
NO problems in using AppleTalk were noted? Sounds like untested SW to me...

Michael McCulloch
Huntsville, AL