On Sat, Nov 28, 2009 at 04:47:53PM -1000, Ryo Furue wrote: > Before installing NIS, I had known that I needed to > edit /etc/yp.conf for NIS to work; I intended to
What makes you say that you need to edit /etc/yp.conf? > To solve this problem, I'd like to suggest that debconf > ask either > 1) whether it should start ypbind now; or > 2) whether NIS servers can be found by broadcasting > (or something like that). > If the answer to the question is "no", debconf won't > start ypbind but advise the user to start NIS after > editing relevant configuration files. This sort of transitiory configuration is really not the sort of thing that should go into debconf so I don't really think that this is an appropriate solution. Given that the issue occurs only when installing on a network where no existing server is available (which is a fairly rare occurrence) and results in less than a minute of latency in the installation I don't think the drawbacks of trying to force it through debconf are worth it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
