09-10-2003
A) Usually updated packages are a good thing. They fix security exploits, add features, and fix bugs. Of course, when you patch a program that directly affects a production environement such as MySQL, Apache, etc etc... you have to make sure that your system will continue to opearate properly.
B) AFAIK, it is not necessary to switch to single user mode to install the patches. But I have not worked w/ a Solaris server recently.
C) My feelings on whether its the best way are: "If it works the way you expected it to and solved the problem, then its the best way". Keep in mind, its definetely not the only way.
My 2 cents
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello all,
I'm hoping someone might be able to help me here. After installing Solaris, we use a script to copy site sepcific files over the machine. Now I want the script add the appropiate Sun patches as well. As the script hits that part it errors out, now the script finishes but the Patch... (3 Replies)
Discussion started by: viRaven
3 Replies
2. Solaris
I'm attempting to install a Sun patch and keep getting an error:
# patchadd /tmp/patches/110722-03
Checking installed patches...
One or more patch packages included in
110722-03 are not installed on this system.
Patchadd is terminating.
#
How can I find out what are the "One or... (7 Replies)
Discussion started by: FredSmith
7 Replies
3. UNIX for Dummies Questions & Answers
Hi, guys !
I usually run this task without even thinking on outcome, because it never failed. But this time when I tried installation of patches for Solaris 8 OS on my old machine, I received this message:
"pkgadd: ERROR: no packages were found in </var/spool/pkg>"
I compared the contents... (5 Replies)
Discussion started by: Deicide5997
5 Replies
4. Solaris
Hi all,
We are planning to install Oracle 10g in the Sun Solaris 10 (64 bit Sun Sparc ).
Can any one please tell me what are the OS level patches that has to be installed in the OS before starting installation of Oracle 10g.
Thanks and Regards,
Prashanth (1 Reply)
Discussion started by: prashanth_gs
1 Replies
5. UNIX for Dummies Questions & Answers
Hi admins....
I want to install 100 Patches in Hpux.. is it possible to install using single command....
if possible ple give me the solution... (1 Reply)
Discussion started by: Prem
1 Replies
6. Linux
Hi all,
I wanted to install the latest version of firefox 2 but it seems when I attempt to install it, it seems to be saying it is looking for c libraries version 2.3? I believe I currently have an older version of the c libraries. I am currently running Sun's JDS Linux 2003. My Mozilla web... (1 Reply)
Discussion started by: scriptingmani
1 Replies
7. Solaris
# /usr/sbin/patchadd -p | grep 119961
Patch: 119961-02 Obsoletes: Requires: Incompatibles: Packages: SUNWsprot
Patch: 119961-04 Obsoletes: Requires: Incompatibles: Packages: SUNWsprot
I was trying to check if i have the above patch on my system when i got the result as shown above, does this... (1 Reply)
Discussion started by: seyiisq
1 Replies
8. Solaris
Hi,
Please let me know how to check all the opearating system patches that were applied on an Sun Solaris machine.
Thanks. (2 Replies)
Discussion started by: jjoy
2 Replies
9. HP-UX
Hi,
I donīt have support HP, so I donīt get download patches on itrc.
Somebody know a free site to download HP-UX patches? (3 Replies)
Discussion started by: quimera
3 Replies
10. AIX
I need to find out list of installed patches from given list of patches.
I have tried using instfix -f <File containing list of patches> -i -c
But I was not able to understand the output of this command. It was like below.
bos.perf.tools: :0.0.0.0:?:
bos.rte.libc: :0.0.0.0:?: ... (4 Replies)
Discussion started by: Saurabh Agrawal
4 Replies
LEARN ABOUT MOJAVE
cpanplus::hacking5.18
CPANPLUS::Hacking(3pm) Perl Programmers Reference Guide CPANPLUS::Hacking(3pm)
NAME
CPANPLUS::Hacking - developing CPANPLUS
DESCRIPTION
This document attempts to describe how to develop with the CPANPLUS environment most easily, how certain things work and why.
This is basically a quick-start guide to people who want to add features or patches to CPANPLUS.
OBTAINING CPANPLUS
Checkout CPANPLUS from its GIT repository at <https://github.com/jib/cpanplus-devel> .
INSTALLING CPANPLUS
CPANPLUS follows the standard perl module installation process:
perl Makefile.PL
make
make test
make install
CONFIGURING CPANPLUS
When running "perl Makefile.PL" you will be prompted to configure. If you have already done so, and merely wish to update the "Makefile",
simply run:
perl Makefile.PL JFDI=1
This will keep your configuration intact. Note however, if there are changes to the default configuration file "Config.pm-orig", you should
either delete your current config file and reconfigure, or patch your config file from the new entries in "Config.pm-orig".
RUNNING CPANPLUS FROM DEVELOPMENT ENVIRONMENT
If you'd rather not install the development version to your "site_perl" directory, that's no problem. You can set your "PERL5LIB"
environment variable to CPANPLUS' "lib" directory, and you can run it from there.
RUNNING CPANPLUS TESTS
Tests are what tells us if CPANPLUS is working. If a test is not working, try to run it explicitly like this:
perl -I/path/to/cpanplus/lib t/XX_name_of_test.t 1
The extra '1' makes sure that all the messages and errors (they might be errors we're testing for!) are being printed rather than kept
quiet. This is a great way to find out the context of any failures that may occur.
If you believe this test failure proves a bug in CPANPLUS, the long output of the test file is something we'd like to see alongside your
bug report.
FINDING BUGS
Sometimes you might find bugs in CPANPLUS' behaviour. If you encounter these in a development snapshot, we'd appreciate a complete patch
(as described below in the "SENDING PATCHES" section.
If it's way over your head, then of course reporting the bug is always better than not reporting it at all. Before you do so though, make
sure you have the latest development snapshot, and the bug still persists there. If so, report the bug to this address:
bug-cpanplus@rt.cpan.org
A good "patch" would have the following characteristics:
Problem description
Describe clearly what the bug is you found, and what it should have done instead.
Program demonstrating the bug
Show us how to reproduce the bug, in a simple of a program as possible
[OPTIONAL] A patch to the test suite to test for the bug
Amend our test suite by making sure this bug will be found in this, and future versions of CPANPLUS (see "SUPPLYING PATCHES")
[OPTIONAL] A patch to the code + tests + documentation
Fix the bug, update the docs & tests. That way your bug will be gone forever :)
SUPPLYING PATCHES
Patches are a good thing, and they are welcome. Especially if they fix bugs you've found along the way, or that others have reported.
We prefer patches in the following format:
o In "diff -u" or "diff -c" format
o From the root of the snapshot
o Including patches for code + tests + docs
o Sent per mail to bug-cpanplus@rt.cpan.org
o With subject containing "[PATCH]" + description of the patch
You will always be informed if a patch is applied or rejected, and in case of rejection why that is (perhaps you can tweak the patch to
have it accepted after all).
perl v5.18.2 2014-01-06 CPANPLUS::Hacking(3pm)