From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: How to Setup Multiple System Distro Manpages
Date: Sun, 15 Jul 2018 12:19:00 -0000 [thread overview]
Message-ID: <2d7c66c8-7bc4-f813-9942-ba33337dacc4@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAHSx_StCgHyvwLy9O3hczBUQ=kJY=rvNJZtGkUhUiDa7WcYc_w@mail.gmail.com>
On 2018-07-14 22:25, Wayne Davison wrote:
> On Sat, Jul 14, 2018 at 1:51 PM Brian Inglis wrote:
>> $ l /proc/cygdrive/c/usr/local/share/man/
>
> Shouldn't those be under /usr/local instead of
> /proc/cygdrive/c/usr/local? Typically /usr is something like
> C:/cygwin64/usr, which is not the C:/usr dir you've used.
Shouldn't be any problem as long as the search path is in man-db.conf or MANPATH.
Under Filesystem Hierarchy Standard:
- /usr/share/man/ is for system supplied package manpages;
- /usr/local/share/man/ is for locally built package manpages for that system:
/opt/man/ on some systems; comes *before* system paths in MANPATH;
- /proc/cygdrive/c/usr/local/ is not FHS but follows those rules, where I store
my system top level distros, including AST, DJGPP, Cygwin, etc., links to
WSL distros' rootfs; and native, common, or shared stuff goes under
subdirectories:
. bin/ native user .exe .cmd .reg;
. etc/ configs .ini etc.;
. lib/ support or addins .dll .exe;
. sbin/ native system admin .exe .cmd .reg;
. share/ data, docs, etc. including:
~ man/ misc and old stuff, like alt.sysadmin.recovery (**) and
funny manpages (**NSFW); *after* system paths in MANPATH;
~ cat1/ cmd.exe internal and external command and
native Windows utilities help;
. src/ native utility and package sources e.g. from net or github;
where these are not part of a distro, and if I wipe out a distro, they remain;
similar to, and could become, a network mount instead of local storage.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-07-15 7:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 4:26 Brian Inglis
2018-07-15 4:32 ` Jack
2018-07-15 6:39 ` Brian Inglis
2018-07-15 7:19 ` Thomas Wolff
2018-07-15 6:49 ` Wayne Davison
2018-07-15 12:19 ` Brian Inglis [this message]
2018-07-15 7:21 ` john doe
2018-07-15 13:23 ` Brian Inglis
2018-07-15 15:40 ` john doe
2018-07-15 17:23 ` Thomas Wolff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d7c66c8-7bc4-f813-9942-ba33337dacc4@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).