- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Adding non-HP or non-core software to Ignite d...
Operating System - HP-UX
1753816
Members
8396
Online
108805
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
Discussions
Discussions
Forums
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
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
тАО06-13-2002 11:06 AM
тАО06-13-2002 11:06 AM
This is my first attempt at using an Ignite/UX server. Here is how I set it up:
Instead of using make_depots, I used swcopy to put all the relevent stuff from all the CDs (core, support plus, and some applications) and some third party bundles into a single depot at
/var/opt/ignite/depots/Rel_B.11.00/core.
Then I used
make_config -s /var/opt/ignite/depots/Rel_B.11.00/core -c /var/opt/ignite/data/Rel_B.11.00/core_cfg
and
manage_index -a -f /var/opt/ignite/data/Rel_B.11.00/core_cfg
Then I started up Ignite for the first time and configure it to use the newly created depot.
Finally, all of these bundles (except for the third party stuff like Legato Networker and EMC PowerPath) were available during a new install in the software tab... Wonderful! And the kernel was built only once!
All I need now is to figure out how to make the software from others vendors available as well. Any ideas?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-14-2002 08:35 AM
тАО06-14-2002 08:35 AM
Solution
Hello!
I found out that copying
everything to one depot
isn't a good idea because
some software products
(checkinstall script?) may
rely on the fact something
is already installed when
they are installed.
(I already got more error
messages after installing
core os and support plus cd
from one depot)
Better put different
sources (e.g. CDs) to
different depots and use
make_config for every
depot. For every
new config files add a line to
the cfg clause in the
INDEX file and use
parameter 'load_order' in
the sw_source clause of
the config file to control
what is installed when.
(e.g. 0=core os CD, 1=support cd, 2= 3rd Party CDs, ...)
The Ignite-UX Administration
Guide has some examples
about using an Ignite-Server
and non SD-UX software. Continue there ...
Eri
I found out that copying
everything to one depot
isn't a good idea because
some software products
(checkinstall script?) may
rely on the fact something
is already installed when
they are installed.
(I already got more error
messages after installing
core os and support plus cd
from one depot)
Better put different
sources (e.g. CDs) to
different depots and use
make_config for every
depot. For every
new config files add a line to
the cfg clause in the
INDEX file and use
parameter 'load_order' in
the sw_source clause of
the config file to control
what is installed when.
(e.g. 0=core os CD, 1=support cd, 2= 3rd Party CDs, ...)
The Ignite-UX Administration
Guide has some examples
about using an Ignite-Server
and non SD-UX software. Continue there ...
Eri
if power_on; then
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2002 07:59 AM
тАО06-18-2002 07:59 AM
Re: Adding non-HP or non-core software to Ignite depots.
Thanks Erik. I've downloaded the latest available Support Plus bundles and will build a new set of depots as you have advised.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2002 09:36 AM
тАО06-18-2002 09:36 AM
Re: Adding non-HP or non-core software to Ignite depots.
Thanks again Erik. That works great. I also had to run make_bundles on the non-HP depots just to make them proper bundles.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP