Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!texsun!pollux!attctc!cbradley
From: cbradley@attctc.Dallas.TX.US (Chris Bradley)
Newsgroups: comp.dcom.lans
Subject: Re: Default Netware ServerDIR/REG
Summary: Waiting for a domain NameService
Message-ID: <10843@attctc.Dallas.TX.US>
Date: 6 Jan 90 00:50:51 GMT
References: <6906@pdn.paradyne.com> <13553@oregon.uoregon.edu>
Reply-To: cbradley@attctc.Dallas.TX.US (Chris Bradley)
Followup-To: comp.dcom.lans
Distribution: na,usa
Organization: The Unix(R) Connection BBS, Dallas, Tx
Lines: 17

In article <13553@oregon.uoregon.edu> rickm@oregon.uoregon.edu (Rick Millhollin) writes:
>I second that; and it is not just a matter of convenience.  In the case of
>diskless workstations on a multi-server network, the current approach is a real
>pain in the ***! You don't necessarily want to have to put a DOS boot image file
>on every server's LOGIN directory; in fact in an environment where servers are
>maintained by different people you may not be able to.  A SHELL.CFG parameter
>for this would really be nice.

Won't the attach-to-nearest-server feature of NET?.EXE go away with the
advent of the global naming service (due ?2Q90)?


-- 
Chris Bradley               |  "To integrate Advanced Technologies into new |
Sr. Eng'r, Advanced Systems |  and existing customer environments."         |
Businessland, Inc.          |- - - - - - - - - - - - - - - - - - - - - - - -|
Dallas, Texas USA           |  Known to management, but unclaimed thereby   |