On Fri, Jun 06, 2008 at 01:03:58PM +0200, Edward Welbourne wrote: > 1. HOW TO SETUP A LOCAL NIS CLIENT
> 1.1 Install the netbase, portmap and nis packages > 1.2 The installation procedure will ask for your NIS domainname. This > is just a name which describes the group of systems that use NIS, it > is not a hostname. ... > </quote> Saying "just a name" isn't very helpful. It's necessary to > tell me how I can find out the right name to give ! It seems the name > I have to give is in fact the response nisdomainname gives me on the > machine I'll be using as server (1.3). 1.2 should say that. The point here is just that a valid NIS domainname needn't be a valid hostname - the expectation is that your network administrator will tell you what it is and normally it is simply referred to as the NIS domain name with no further commentary. If anything the clarification that it needn't be a hostname should be removed rather than going into any more detail. > I conclude that nis needs bind (or something else pulled in by > bind9-host); 1.1 should mention this (and ideally the nis package > should actually Depend on it). No, DNS shouldn't be required at all for NIS unless something in your configuration requires it (for example, using a hostname that isn't in /etc/hosts) and you should certainly never require a local name server. Without knowing what other packages were installed it's a bit difficult to see what might have gone wrong - do you have that information? -- "You grabbed my hand and we fell into it, like a daydream - or a fever." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
