04-09-2012
xemacs.1 and the other .1 files should be in directory man1
9 More Discussions You Might Find Interesting
1. News, Links, Events and Announcements
Usefull HP-UX Man Page Online Link
LINK: HP-UX Man Page
http://www.doc.ic.ac.uk/~mac/manuals/hpux-manual-pages/hpux.man1.html (0 Replies)
Discussion started by: killerserv
0 Replies
2. UNIX for Dummies Questions & Answers
i've never done this before. i created a script that I placed in /usr/bin, but want to create a man page for it. i'm clueless
thanks (3 Replies)
Discussion started by: theDirtiest
3 Replies
3. UNIX for Dummies Questions & Answers
I was wonderiong if ther is a way for a user to add a man page specific to thier account. similar to copying the .1 or .1.gz to /usr/share/man/man1 "cp *.1.gz /usr/share/man/man1". Except for using another folder as I don't have access to /usr/share/man/man1. I would think that this might involve... (1 Reply)
Discussion started by: jacob358
1 Replies
4. Solaris
Hi, I put an expiration on a few id's that I want to remove now. From the man page
-e expire Specify the future date on which a login can no
longer be used; after this date, no user will be
able to access this login. This option is useful
... (0 Replies)
Discussion started by: amheck
0 Replies
5. Red Hat
Hi Guys,
I'm looking for the man page for scp version 1.2.27
I have an old redhat server that has a few large scripts that use this version and I want to know what the -A flag does and the man page is not on there. (4 Replies)
Discussion started by: Tornado
4 Replies
6. UNIX for Advanced & Expert Users
Man page is not working my system. It is giving the following the following error
> man ls
gdbm fatal: read error
with debug option
> man -d ls
...
....
...
...
using less as pager
checking for locale en_US
add_nls_manpath(): processing /usr/local/man:/usr/share/man:/usr/X11R6/man... (4 Replies)
Discussion started by: praveenkumar_l
4 Replies
7. Solaris
Help,
it seem that i am unable to get man help form solaris 10.
I am running SunOS unknown 5.10 Generic_120012-14 i86pc i386 i86pc
when ever i try to man a command what i get is "No manual entry" like the one below.
# man grep
No manual entry for grep.
# man ls
No manual entry for ls.... (8 Replies)
Discussion started by: ezsurf
8 Replies
8. Solaris
What does the last change means in man page .. does that this man page has not been updated since 2003 or something else ?
newfs-options
The options are documented in the newfs man page.
SunOS 5.10 Last change: 9 Dec 2003 1
System... (2 Replies)
Discussion started by: fugitive
2 Replies
9. UNIX for Advanced & Expert Users
I realise that with GNU 'info' a lot of developers become, dare I say it, quite lazy when it comes to providing a well written man page - and some argue they're not needed at all. But I find, in the products that I develop, that man pages are used more often for quick reference, and therefore the... (1 Reply)
Discussion started by: cambridge
1 Replies
DH_LINK(1) Debhelper DH_LINK(1)
NAME
dh_link - create symlinks in package build directories
SYNOPSIS
dh_link [debhelperoptions] [-A] [-Xitem] [sourcedestination...]
DESCRIPTION
dh_link is a debhelper program that creates symlinks in package build directories.
dh_link accepts a list of pairs of source and destination files. The source files are the already existing files that will be symlinked
from (called target by ln(1)). The destination files are the symlinks that will be created (called link name by ln(1)). There must be an
equal number of source and destination files specified.
Be sure you do specify the absolute path to both the source and destination files (unlike you would do if you were using something like
ln(1)). Please note that the leading slash is optional.
dh_link will generate symlinks that comply with Debian policy - absolute when policy says they should be absolute, and relative links with
as short a path as possible. It will also create any subdirectories it needs to put the symlinks in.
Any pre-existing destination files will be replaced with symlinks.
dh_link also scans the package build tree for existing symlinks which do not conform to Debian policy, and corrects them (v4 or later).
FILES
debian/package.links
Lists pairs of source and destination files to be symlinked. Each pair should be put on its own line, with the source and destination
separated by whitespace.
In each pair the source file (called target by ln(1)) comes first and is followed by the destination file (called link name by ln(1)).
Thus the pairs of source and destination files in each line are give in the same order as they would be given to ln(1).
In contrast to ln(1), source and destination paths must be absolute (the leading slash is optional).
OPTIONS
-A, --all
Create any links specified by command line parameters in ALL packages acted on, not just the first.
-Xitem, --exclude=item
Exclude symlinks that contain item anywhere in their filename from being corrected to comply with Debian policy.
source destination ...
Create a file named destination as a link to a file named source. Do this in the package build directory of the first package acted on.
(Or in all packages if -A is specified.)
EXAMPLES
dh_link usr/share/man/man1/foo.1 usr/share/man/man1/bar.1
Make bar.1 be a symlink to foo.1
dh_link var/lib/foo usr/lib/foo
usr/share/man/man1/foo.1 usr/share/man/man1/bar.1
Make /usr/lib/foo/ be a link to /var/lib/foo/, and bar.1 be a symlink to the foo.1
var/lib/foo usr/lib/foo
usr/share/man/man1/foo.1 usr/share/man/man1/bar.1
Same as above but as content for a debian/package.links file.
SEE ALSO
debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
11.1.6ubuntu2 2018-05-10 DH_LINK(1)