Hey Charles<br><br><div class="gmail_quote">2009/9/15 Charles Lepple <span dir="ltr"><<a href="mailto:clepple@gmail.com">clepple@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
All,<br>
<br>
With AsciiDoc, we can make use of some macros to cut down on some of the repetition in the driver man pages.<br>
<br>
I don't want to go overboard on this, though - I know that drivers aren't meant to be invoked directly by users anyway.<br>
<br>
I propose that we put all of the gory details into the nutupsdrv(8) man page (mostly there anyway), and just add a few basic options to the SYNOPSIS section of each driver page for completeness:<br>
<br>
-h (help)<br>
-V (version)<br>
-a ups-id (auto-start)<br>
-D (debug)<br>
<br>
For "-D" we can continue to include the admonition about not sending debug info unless requested, and even leave out the fact that you can pass multiple "-D" options (which could be mentioned on nutupsdrv(8)).<br>
<br>
Thoughts?<br>
</blockquote><div><br>we should use "BASIC OPTIONS" instead of the standard "OPTIONS" used in nutupsdrv<br>also making a direct link to nutupsdrv (with the standard boilerplate "for other avail. options, refer to...") is a good idea.<br>
<br>cheers<br>Arnaud<br></div></div>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>
Debian Developer - <a href="http://www.debian.org">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br><br>