NIS during client build
Dominik Kasprzyk
dk at star.sr.bham.ac.uk
Tue Aug 2 12:31:03 CEST 2005
You could just do all the chowning operations as a post-install script (i.e. after FAI finishes and reboots, somewhere in run level 2) after NIS is up. It's a really simple way of getting around the problem that I've used, although not very elegant.
Dominik.
Implementation points:
Have a script in init.d (best if the file is created sing the default scripts) with the last line being rm -f /etc/init.d/scriptname (best added from the end of LAST) which creates a very simple run-once post-installer script.
On Mon, 1 Aug 2005 12:11:51 -0700
"ANDERSON RUSSELL D (ANDY)" <RXANDERS at srpnet.com> wrote:
> Does anyone use NIS during a build? Any recommendations on how to work aroung it?
>
> .............
> > How and when can I enable NIS on a client during the build? I have tried various hooks all the way up to the task faiend with no success. I also used a hook instsoft.DEFAULT that enables the loopback "ifconfig lo 127.0.0.1 netmask 255.0.0.0 up" with no change. What do I need to do to enable NIS services for chown, etc during the build?
> >
> > fai 2.8.4
> >
> > Thanks.
>
>
More information about the linux-fai
mailing list