[comp.dcom.lans] Default Netware ServerDIR/REG

rickm@oregon.uoregon.edu (Rick Millhollin) (01/06/90)

In article <6906@pdn.paradyne.com>, dixon@gumby.paradyne.com (Tom Dixon(813-530-8358)) writes:
> If anyone from exelan/novell is listening, can we have a default command
> or environment variable in future releases?  It could be as simple as
> if a variable defaultserv=xxx then net4 would wait some small extra amount
> of time for an answer from that server.  If no answer then it would pick the
> lucky first answerer.  How hard would that be?

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.

cbradley@attctc.Dallas.TX.US (Chris Bradley) (01/06/90)

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   |