Chris G <c...@isbd.net> writes: > I just want 'man owfsxxx' to work, and it doesn't, even after adding > the /opt/owfs/share/man directory to the MANPATH database. The > trouble is all those wierd xxxx.1so manual pages seem to throw a > spanner in the works. Can you point me at anywhere that describes how > it's supposed to work - then maybe I can mend it and actually read the > owfs documentation. > > Why doesn't it just use ordinary symbolic links?
the .so directive is commonly used on Linux, too: linux$ zcat /usr/share/man/man1/help.1.gz .so man1/builtins.1 >> .... and why are there manual pages called things like help.1so, >> that's inevitably going to cause problems. for the most part, it should work just fine. after all, you're not supposed to read these pages directly. it might work more reliably if, e.g., man/owfs.1 contained ".so man1/help.1so" rather than ".so help.1so". also, it would probably be a good idea to use a prefix for pages only intended for inclusion (like "ow-help.1so"), so that "man -s 1 help" is certain to bring up the bash builtin, and not the owfs snippet. -- Kjetil T. Homme Redpill Linpro AS - Changing the game ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
