10 More Discussions You Might Find Interesting
1. AIX
Hi,
when I boot I get an E1DC error code. I've looked it up and it says that this error occurs during the firmware check. But the error is called "Dynamic Console Selection" .
1- Machine stopped at LCD led display = E1DC = CA00E1DC
E1DC Dynamic console selection. (maybe cable or keyboard)... (3 Replies)
Discussion started by: filosophizer
3 Replies
2. AIX
Hi guys,
My company just bought pseries server from ibm,
would like to ask , if first i need to install HMC for creating lpars ?
or first i need to install aix , and then install hmc?
Thx, (3 Replies)
Discussion started by: prpkrk
3 Replies
3. AIX
Hello,
I'm trying to install AIX 7.1 on a machine. Unfortunately I forgot to load volume 2 DVD, but the server works fine. Was wondering, what all the contents will be in volume 2?
And I tried loading it after the complete reboot but the blade is not recognizing the volume2 DVD.
Please let... (6 Replies)
Discussion started by: pjeedu2247
6 Replies
4. AIX
Hello,
I'm very rookie to AIX and attempting to install AIX. I have vio ready on the machine and don't know how to install OS? Inserted Volume 1 DVD into the ROM, don't know what to do next. Searched many forum but cant find the this basic thing. Please let me know how to install AIX on this... (4 Replies)
Discussion started by: pjeedu2247
4 Replies
5. Red Hat
Hello,
What is the simplest way to install CentOS 6.1 with console base-system only using official LiveDVD image on VirtualBox machine? I'd like to get simplest console with network support like FreeBSD base installation. Then, install services which I need.
The installer jest extracts the... (2 Replies)
Discussion started by: newbie_develope
2 Replies
6. Solaris
hi people,
I receive this message in the nwadmin:
Registration info event: Server is disabled Install base enabler
License enabler: #none (Networker/10 Eval) has expired.
What happened?
Please help me...
Thank you (0 Replies)
Discussion started by: denisgomes
0 Replies
7. Shell Programming and Scripting
Hi,
I am trying to create a menu on AIX systen for operators in our office.
Please suggest how can I loop back to menu by pressing any key from a online running file. For example I can view the Database alert log file by tail -f command but how should I loop back to menu again. If I press <ctrl... (1 Reply)
Discussion started by: dwiravi
1 Replies
8. AIX
Hi,
I am trying to create a menu on AIX systen for operators in our office.
Please suggest how can I loop back to menu by pressing any key from a online running file. For example I can view the Database alert log file by tail -f command but how should I loop back to menu again. If I press <ctrl... (1 Reply)
Discussion started by: dwiravi
1 Replies
9. AIX
Hi All --
I have an old 7028-6C1 which I'm using to learn AIX. The system didn't include a graphics card, so I connected via the serial port and performed a fresh install of AIX 5L V5.3.
Later, I purchased a GXT135P (2849) graphics card, and added it to the system. When I ran diag, I was able... (2 Replies)
Discussion started by: i386tech
2 Replies
10. UNIX for Dummies Questions & Answers
I'm new with UNIX, i have a pseries server from IBM and i need to install AIX 4.3, i never used wyse terminal or AIX, i need help to know how to install it, i have the server and the wyse i get in into the aixterm, over com1 but i don't know wich command use or what to do to install it..... ... (0 Replies)
Discussion started by: Juan-ito
0 Replies
DH_INSTALLDOCS(1) Debhelper DH_INSTALLDOCS(1)
NAME
dh_installdocs - install documentation into package build directories
SYNOPSIS
dh_installdocs [debhelperoptions] [-A] [-Xitem] [file...]
DESCRIPTION
dh_installdocs is a debhelper program that is responsible for installing documentation into usr/share/doc/package in package build
directories.
In compat 10 and earlier, dh_install(1) may be a better tool for handling the upstream documentation, when upstream's own build system
installs all the desired documentation correctly. In this case, dh_installdocs is still useful for installing packaging related
documentation (e.g. the debian/copyright file).
From debhelper compatibility level 11 on, dh_install will fall back to looking in debian/tmp for files, if it does not find them in the
current directory (or wherever you've told it to look using --sourcedir).
In compat 11 and later, dh_installdocs offers many of the features that dh_install(1) also have. Furthermore, dh_installdocs also supports
the nodoc build profile to exclude documentation (regardless of compat level).
FILES
debian/package.docs
List documentation files to be installed into package.
debian/copyright
The copyright file is installed into all packages, unless a more specific copyright file is available.
debian/package.copyright
debian/package.README.Debian
debian/package.TODO
Each of these files is automatically installed if present for a package.
debian/README.Debian
debian/TODO
These files are installed into the first binary package listed in debian/control.
Note that README.debian files are also installed as README.Debian, and TODO files will be installed as TODO.Debian in non-native
packages.
debian/package.doc-base
Installed as doc-base control files. Note that the doc-id will be determined from the Document: entry in the doc-base control file in
question. In the event that multiple doc-base files in a single source package share the same doc-id, they will be installed to
usr/share/doc-base/package instead of usr/share/doc-base/doc-id.
debian/package.doc-base.*
If your package needs to register more than one document, you need multiple doc-base files, and can name them like this. In the event
that multiple doc-base files of this style in a single source package share the same doc-id, they will be installed to
usr/share/doc-base/package-* instead of usr/share/doc-base/doc-id.
OPTIONS
-A, --all
Install all files specified by command line parameters in ALL packages acted on.
-Xitem, --exclude=item
Exclude files that contain item anywhere in their filename from being installed. Note that this includes doc-base files.
--sourcedir=dir
Look in the specified directory for files to be installed. This option requires compat 11 or later (it is silently ignored in compat
10 or earlier).
Note that this is not the same as the --sourcedirectory option used by the dh_auto_* commands. You rarely need to use this option,
since dh_installman automatically looks for files in debian/tmp in debhelper compatibility level 11 and above.
--doc-main-package=main-package
Set the main package for a documentation package. This is used to install the documentation of the documentation package in
/usr/share/doc/main-package as recommended by the Debian policy manual 3.9.7 in S12.3.
In compat 11 (or later), this option is only useful if debhelper's auto-detection of the main package is wrong. The option can also be
used to silence a warning from debhelper when the auto-detection fails but the default happens to be correct.
This option cannot be used when dh_installdocs is instructed to act on multiple packages. If you need this option, you will generally
need to combine it with -p to ensure exactly one package is acted on.
Please keep in mind that some documentation (the copyright file, README.Debian, etc.) will be unaffected by this option.
--link-doc=package
Make the documentation directory of all packages acted on be a symlink to the documentation directory of package. This has no effect
when acting on package itself, or if the documentation directory to be created already exists when dh_installdocs is run. To comply
with policy, package must be a binary package that comes from the same source package.
debhelper will try to avoid installing files into linked documentation directories that would cause conflicts with the linked package.
The -A option will have no effect on packages with linked documentation directories, and copyright, changelog, README.Debian, and TODO
files will not be installed.
(An older method to accomplish the same thing, which is still supported, is to make the documentation directory of a package be a
dangling symlink, before calling dh_installdocs.)
Please note that this option only applies to the documentation directory for the package itself. When the package ships documentation
for another package (e.g. see --doc-main-package), it will not use a symlink for the documentation of the other package.
CAVEAT 1: If a previous version of the package was built without this option and is now built with it (or vice-versa), it requires a
"dir to symlink" (or "symlink to dir") migration. Since debhelper has no knowledge of previous versions, you have to enable this
migration itself.
This can be done by providing a "debian/package.maintscript" file and using dh_installdeb(1) to provide the relevant maintainer script
snippets.
CAVEAT 2: The use of --link-doc should only be done when the packages have same "architecture" type. A link from a architecture
independent package to a architecture dependent package (or vice versa) will not work. Since compat 10, debhelper will actively reject
unsupported combinations.
file ...
Install these files as documentation into the first package acted on. (Or in all packages if -A is specified).
EXAMPLES
This is an example of a debian/package.docs file:
README
TODO
debian/notes-for-maintainers.txt
docs/manual.txt
docs/manual.pdf
docs/manual-html/
NOTES
Note that dh_installdocs will happily copy entire directory hierarchies if you ask it to (similar to cp -a). If it is asked to install a
directory, it will install the complete contents of the directory.
SEE ALSO
debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
11.1.6ubuntu2 2018-05-10 DH_INSTALLDOCS(1)