I've emerged djbdns and can not install per the instructions on cr.yp.to Reproducible: Always Steps to Reproduce: 1. emerge djbdns 2. tinydns-conf tinydns dnslog /etc/tinynds 66.58.97.27 3. ln -s /etc/tinydns /service 4. svstat /service/tinydns Actual Results: Originally: /service: Unable to open supervise/ok: file does not exist Later: /service: unable to chdir: file does not exist Expected Results: This is the final step in installing tinydns. /service is s a symlink. How can there be a /service/tinydns? (referrenced in step 4, above)
Please disregard this bug-report: Though I have one very small complaint about the djbdns-1.05-r8 ebuild, it installs correctly and runs. My errors were the result of a botched emerge resulting from mounting the / and /usr filesystems as read-only. Though I unmerge'd & remerge'd djbdns, I didn't think to unmerge & remerge djbdns' dependencies. Once I did this, djbdns & it's dependencies emerge'd quickly and began working *after* I updated the rc files. The one minor flaw: No warning was given after emerge'ing to execute the /usr/portage/net-dns/djbdns/files/tinydns-setup script* or to add svscan to the default runlevel. * The default tinydns-setup script seems to do the same thing though so my point is kind of mute.
