Sponsored Content
Full Discussion: Latest patches for HPUX 11
Operating Systems HP-UX Latest patches for HPUX 11 Post 302195550 by vbe on Thursday 15th of May 2008 10:50:31 AM
Old 05-15-2008
start by
swlist | more

Then look if you have any quality pack installed, then depending its date look for the latest available
 

10 More Discussions You Might Find Interesting

1. Solaris

OS Patches

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

2. UNIX for Dummies Questions & Answers

Installing Patches in HPux

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

3. HP-UX

HPUX 10.20 and fx5 which patches for vue

Which patches or bundles must be installed to use an fx5 grafic in a HP C3600 WS. We use 10.20 from Dez 99 thanks for :confused: (0 Replies)
Discussion started by: dlanor
0 Replies

4. Solaris

OS patches

Hi all, I am working on SUN-fire server solaris-10 How to find out what & how much " OS patches " installed on it?? plz help me out .:( (3 Replies)
Discussion started by: saurabh84g
3 Replies

5. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies

6. Solaris

OS Patches

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

7. Solaris

Roll back latest Solaris Patches

Is there an easy way to roll back or uninstall the latest Solaris patch cluster? I'm hoping I don't have to go into each patch that was applied and uninstall them one-by-one. Thanks! (0 Replies)
Discussion started by: bluescreen
0 Replies

8. HP-UX

pwage-hpux-T for Trusted HPUX servers

I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email. original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies

9. HP-UX

Patches 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

List of Installed patches for AIX from given set of patches

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
inc::latest(3)						User Contributed Perl Documentation					    inc::latest(3)

NAME
inc::latest - use modules bundled in inc/ if they are newer than installed ones SYNOPSIS
# in Build.PL use inc::latest 'Module::Build'; DESCRIPTION
The "inc::latest" module helps bootstrap configure-time dependencies for CPAN distributions. These dependencies get bundled into the "inc" directory within a distribution and are used by Build.PL (or Makefile.PL). Arguments to "inc::latest" are module names that are checked against both the current @INC array and against specially-named directories in "inc". If the bundled version is newer than the installed one (or the module isn't installed, then, the bundled directory is added to the start of <@INC> and the module is loaded from there. There are actually two variations of "inc::latest" -- one for authors and one for the "inc" directory. For distribution authors, the "inc::latest" installed in the system will record modules loaded via "inc::latest" and can be used to create the bundled files in "inc", including writing the second variation as "inc/latest.pm". This second "inc::latest" is the one that is loaded in a distribution being installed (e.g. from Build.PL). This bundled "inc::latest" is the one that determines which module to load. Special notes on bundling The "inc::latest" module creates bundled directories based on the packlist file of an installed distribution. Even though "inc::latest" takes module name arguments, it is better to think of it as bundling and making available entire distributions. When a module is loaded through "inc::latest", it looks in all bundled distributions in "inc/" for a newer module than can be found in the existing @INC array. Thus, the module-name provided should usually be the "top-level" module name of a distribution, though this is not strictly required. For example, Module::Build has a number of heuristics to map module names to packlists, allowing users to do things like this: use inc::latest 'Devel::AssertOS::Unix'; even though Devel::AssertOS::Unix is contained within the Devel-CheckOS distribution. At the current time, packlists are required. Thus, bundling dual-core modules may require a 'forced install' over versions in the latest version of perl in order to create the necessary packlist for bundling. USAGE
When calling "use", the bundled "inc::latest" takes a single module name and optional arguments to pass to that module's own import method. use 'inc::latest' 'Foo::Bar' qw/foo bar baz/; Author-mode You are in author-mode inc::latest if any of the Author-mode methods are available. For example: if ( inc::latest->can('write') ) { inc::latest->write('inc'); } loaded_modules() my @list = inc::latest->loaded_modules; This takes no arguments and always returns a list of module names requested for loading via "use inc::latest 'MODULE'", regardless of whether the load was successful or not. write() inc::latest->write( 'inc' ); This writes the bundled version of inc::latest to the directory name given as an argument. It almost all cases, it should be '"inc"'. bundle_module() for my $mod ( inc::latest->loaded_modules ) { inc::latest->bundle_module($mod, $dir); } If $mod corresponds to a packlist, then this function creates a specially-named directory in $dir and copies all .pm files from the modlist to the new directory (which almost always should just be 'inc'). For example, if Foo::Bar is the name of the module, and $dir is 'inc', then the directory would be 'inc/inc_Foo-Bar' and contain files like this: inc/inc_Foo-Bar/Foo/Bar.pm Currently, $mod must have a packlist. If this is not the case (e.g. for a dual-core module), then the bundling will fail. You may be able to create a packlist by forced installing the module on top of the version that came with core Perl. As bundled in inc/ All methods are private. Only the "import" method is public. AUTHOR
Eric Wilhelm <ewilhelm@cpan.org>, David Golden <dagolden@cpan.org> COPYRIGHT
Copyright (c) 2009 by Eric Wilhelm and David Golden This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
Module::Build perl v5.16.3 2014-06-10 inc::latest(3)
All times are GMT -4. The time now is 08:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy