site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com :) export MANPATH=$MANPATH:/opt/local/man /etc/httpd/http.conf this is the first and the last... Best Regards -----BEGIN PLUMBER CODE BLOCK----- Version: 1.0 ¬ | | > Regards Plumber || GNU Darwin. ¬ \\\ plumber.gnu-darwin.org ¬ ¬ | | > OOP --\///\ (0)=(0) Darwin/Power Mac G4. ¬ | | > ( __ò ó__ ) The best for Fede ¬ \\\ federicafontana.it ¬ ------END PLUMBER CODE BLOCK------ -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GMU/S d+@ s: a- K+++++ PGP++++ K---- dpu s--:-- C++++ C-- B L X U++++ P+++ C-- P! L--- E+++ W+++ P! L--- N+++ o-- K+++++ ------END GEEK CODE BLOCK------ Plain, Loving, Useful, Mischievous, Brutal, Explosive, Responsible _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Is there somewhere some description of a) changes in configuration files from one release to the next? b) differences in configuration file usage from what I'd find in antique unix documentation (or experience) and/or linux documentation? For instance, I'm familiar with ~/public_html but here it's ~/Sites :) Basically, I'd like to be pro-active rather than reactive in these things -- I hate tripping over something and then having to go looking for the cause, often without any real clue. "No manual entry" in my ManOpen window, for instance, is the first clue about manpath going away ... I"It's making my eyes better. And it's legal. I could walk up to the President and blow smoke in his stupid monkey face, and he'd just have to sit there groovin' on it!" Homer J Simpson, Springfield, Illinois, Massachusetts nobody knows :) This email sent to site_archiver@lists.apple.com