Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!caesar.cs.montana.edu!milton!oregon!rickm
From: rickm@oregon.uoregon.edu (Rick Millhollin)
Newsgroups: comp.dcom.lans
Subject: Re: Default Netware ServerDIR/REG
Message-ID: <13553@oregon.uoregon.edu>
Date: 5 Jan 90 17:45:54 GMT
References: <6906@pdn.paradyne.com>
Distribution: na,usa
Organization: University of Oregon
Lines: 13

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.