Searched hist:35459 (Results 1 - 2 of 2) sorted by relevance
| /freebsd-10.1-release/etc/rc.d/ | ||
| H A D | defaultroute | diff 35459 Sun Apr 26 04:32:13 MDT 1998 phk Jean-Simon Pendry's paper on amd refers to the use of "ypcat -k" against the "master map" to get the list of mount point/amd map correspondences, and using that list as command-line arguments to start amd. When I tried to do this with the existing /etc/rc* scripts, I found that I couldn't do this by modifying only /etc/rc.conf: that file gets sourced very early by /etc/rc, well before any networking functionality is present, let alone NIS. Further, I wasn't able to figure out a way to use various levels & types of quoting to defer evaluation of the string to a point subsequent to NIS initialization. As a result, I resorted to hacking /etc/rc.network -- but I did it in a way that ought to be reasonably general, and avoid breakage for anyone else. PR: 6387 Reviewed by: phk Submitted by: David Wolfskill <dhw@whistle.com> |
| H A D | netoptions | diff 35459 Sun Apr 26 04:32:13 MDT 1998 phk Jean-Simon Pendry's paper on amd refers to the use of "ypcat -k" against the "master map" to get the list of mount point/amd map correspondences, and using that list as command-line arguments to start amd. When I tried to do this with the existing /etc/rc* scripts, I found that I couldn't do this by modifying only /etc/rc.conf: that file gets sourced very early by /etc/rc, well before any networking functionality is present, let alone NIS. Further, I wasn't able to figure out a way to use various levels & types of quoting to defer evaluation of the string to a point subsequent to NIS initialization. As a result, I resorted to hacking /etc/rc.network -- but I did it in a way that ought to be reasonably general, and avoid breakage for anyone else. PR: 6387 Reviewed by: phk Submitted by: David Wolfskill <dhw@whistle.com> |
Completed in 78 milliseconds