NIS configuration

[pll at lanminds.com]

In a message dated: Thu, 19 Sep 2002 11:02:29 EDT
mod+linux-fai at std.com said:

>I could lose the global definition, but then I'd
>be obliged to define nis-domain on a per-client
>basis, right?  I'd rather that FAI didn't helpfully
>make incorrect assumptions, and that when I say
>NONIS, I really do actually mean it...

Why not do something like seting 'nis-domain=NONE' for the one client 
you don't want to have an NIS config?

Of course, you can also define things on a subnet basis rather than 
using a global:

	subnet 192.168.1.0 netmask 255.255.255.0 {
	
		option nis-domain "foobar";
		.
		.
		.
	}

	subnet 192.168.2.0 netmask 255.255.255.0 {
	
		# No NIS on this subnet
		#option nis-domain "";
		.
		.
		.
	}


And, as you mentioned, you *could* use a per-client definition for 
NIS, but that would be a real pain, not to mention overly redundant.

Have you tried defining the NIS option as an empty string for the 
clients you want to boot without an NIS config?  Something like this
*should* work:


	host client { 
	  hardware ethernet 00:d0:a8:00:d8:46; 
	  fixed-address client; 
	  option fai-action "install";          # FAI_ACTION install/sysinfo 
	  option fai-flags "verbose createvt sshd reboot"; 
	  option nis-domain "";
	} 

That *should* over-ride the global and set it to an empty string 
which I would expect to evaluate to nothing when the FAI scripts do 
their test, which means you'd get the NONIS class defined.

None of this is tested or guaranteed, but I think it *should* work 
just fine.

-- 

Seeya,
Paul
--
	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.

	 If you're not having fun, you're not doing it right!