HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Install of HP-UX 11.00 from latest install CD's
Operating System - HP-UX
1830820
Members
2760
Online
110016
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2002 02:38 AM
02-28-2002 02:38 AM
This is not really a problem which needs answering but more of an observation requireing views.
I don't know if anybody else has noticed this, but following an install of 11.00 from either Sept 2001 or Dec 2001 install CD's if you do a "swlist -l fileset -a state" you see a number of patches with a state of installed and not configured.
I have already raised this issue with HP support desk as a swconfig \* doesn't configure them.
Apparantly it is due to the new instalation procedure requesting for the support CD to be inserted and automatically installing patches from the CD before it has configured the patches which come as part of the Core OS Install CD. It now means in a normal working state you will always have a number of patches with a state of installed.
I don't know about anybody else but I was lead to believe that this was not a good state to be in. Also what is the first thing the HP responce centre tell you to do when they are checking a problem, perform a swlist -a state -l fileset and check that all the patches have a state of configured.
How about getting a pertition to get the labs to change things back to the original way of working ??
I don't know if anybody else has noticed this, but following an install of 11.00 from either Sept 2001 or Dec 2001 install CD's if you do a "swlist -l fileset -a state" you see a number of patches with a state of installed and not configured.
I have already raised this issue with HP support desk as a swconfig \* doesn't configure them.
Apparantly it is due to the new instalation procedure requesting for the support CD to be inserted and automatically installing patches from the CD before it has configured the patches which come as part of the Core OS Install CD. It now means in a normal working state you will always have a number of patches with a state of installed.
I don't know about anybody else but I was lead to believe that this was not a good state to be in. Also what is the first thing the HP responce centre tell you to do when they are checking a problem, perform a swlist -a state -l fileset and check that all the patches have a state of configured.
How about getting a pertition to get the labs to change things back to the original way of working ??
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2002 07:34 AM
02-28-2002 07:34 AM
Solution
From our patch guru:
The issue is that during an install or update session in which multiple depots are used (i.e. multiple pieces of media) swconfig
is only executed once at the end of the entire session. If during the install/update session patches were installed from a second depot that
supersede patches in the first depot, the superseded patches won't be configured. This is because at the time swconfig is run, the older patches have been overwritten by the newer patches so swconfig does not configure them. Doing so could cause harm to the newer patches.
The best recommendation is to configure SD
on the system such that superseded patches are not displayed by default with swlist. This would essentially hide the superseded patches that were never configured.
To verify this is the situation, you can execute the command:
swlist -l fileset -a state -a patch_state
If the only patch filesets that have a state of installed also have a patch_state of superseded, then this is the situation. If you have the version of SD provided in PHCO_20078 or later, you can configure
swlist so that superseded patches are not displayed. If the following command does not complain about an unrecognized option:
swlist -l fileset -a state -a patch_state -x show_superseded_patches=false
then you have the requisite version of swlist and you can set this option by default in the /var/adm/sw/defaults file:
swlist.show_superseded_patches = false
which permanently hides the superseded patch information.
Bill Hassell, sysadmin
The issue is that during an install or update session in which multiple depots are used (i.e. multiple pieces of media) swconfig
is only executed once at the end of the entire session. If during the install/update session patches were installed from a second depot that
supersede patches in the first depot, the superseded patches won't be configured. This is because at the time swconfig is run, the older patches have been overwritten by the newer patches so swconfig does not configure them. Doing so could cause harm to the newer patches.
The best recommendation is to configure SD
on the system such that superseded patches are not displayed by default with swlist. This would essentially hide the superseded patches that were never configured.
To verify this is the situation, you can execute the command:
swlist -l fileset -a state -a patch_state
If the only patch filesets that have a state of installed also have a patch_state of superseded, then this is the situation. If you have the version of SD provided in PHCO_20078 or later, you can configure
swlist so that superseded patches are not displayed. If the following command does not complain about an unrecognized option:
swlist -l fileset -a state -a patch_state -x show_superseded_patches=false
then you have the requisite version of swlist and you can set this option by default in the /var/adm/sw/defaults file:
swlist.show_superseded_patches = false
which permanently hides the superseded patch information.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2002 12:58 AM
03-01-2002 12:58 AM
Re: Install of HP-UX 11.00 from latest install CD's
Bill,
Many thanks for the information.
I had already come up the reason why this had happened myself, but the extra information about the -a patch_state -x show_superseded_patches=false is extreamly helpful.
You have to wonder why HP labs have decided to change things in this way. I agree with progression, but only for the better, in my opinion, this is definiatly NOT for the better. I also have to wonder if it works correctly, I now have discovered I am missing the -D option on the lvcreate command which was fixed by a patch included on the Dec 2001 patch CD, but will not configure as it has been superseded
Many thanks for the information.
I had already come up the reason why this had happened myself, but the extra information about the -a patch_state -x show_superseded_patches=false is extreamly helpful.
You have to wonder why HP labs have decided to change things in this way. I agree with progression, but only for the better, in my opinion, this is definiatly NOT for the better. I also have to wonder if it works correctly, I now have discovered I am missing the -D option on the lvcreate command which was fixed by a patch included on the Dec 2001 patch CD, but will not configure as it has been superseded
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP