HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Device files DAT with make_sys_image
Operating System - HP-UX
1837409
Members
3661
Online
110116
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
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-05-2004 04:08 AM
02-05-2004 04:08 AM
Device files DAT with make_sys_image
I am currently migrating an application HP-UX 9.07 under HP-UX 11.11.
This application will be then installed on 120 B2600/785 machines
by a user who didn't know UNIX.
I created a DVD bootable using the following orders:
make_sys_image -d /var/tmp/cdroot -s local -m t -c g -l 1
/opt/ignite/lbin/archive_impact -t -g /var/tmp/cdroot/socref.gz
/opt/ignite/bin/save_config -f /var/opt/ignite/config.local
/opt/ignite/bin/make_medialif -f /opt/ignite/data/Rel_B.11.11/config
-f /var/tmp/cdroot/archive_cfg
-f /var/opt/ignite/config.local
-a -l /var/tmp/cdroot/ilif
/opt/OpenSource/xcdroast_0.98/bin/mkisofs -U -max-iso9660-filenames -D -o /var/tmp/cdroot/cdfs.iso -no-emul-boot -b EFI_CD_image -eltorito-alt-boot -no-emul-boot -b ilif /var/tmp/cdroot
/opt/ignite/lbin/instl_combine -C /var/tmp/cdroot/cdfs.iso
When I created this image of the machine, a DAT was connected and the device files existed for this DAT in the directory /dev/rmt.
When I install this DVD on a machine which doesn't have a DAT, these device files are not created.
When I connect a DAT on this machine, I must carry out the orders:
ioscan - fnC tape
insf
The problem is that the user can connect a DAT after the installation and I don't want that he uses UNIX commands.
How can I make to force creation of these device files with the DVD created by make_sys_image without connected DAT?
This application will be then installed on 120 B2600/785 machines
by a user who didn't know UNIX.
I created a DVD bootable using the following orders:
make_sys_image -d /var/tmp/cdroot -s local -m t -c g -l 1
/opt/ignite/lbin/archive_impact -t -g /var/tmp/cdroot/socref.gz
/opt/ignite/bin/save_config -f /var/opt/ignite/config.local
/opt/ignite/bin/make_medialif -f /opt/ignite/data/Rel_B.11.11/config
-f /var/tmp/cdroot/archive_cfg
-f /var/opt/ignite/config.local
-a -l /var/tmp/cdroot/ilif
/opt/OpenSource/xcdroast_0.98/bin/mkisofs -U -max-iso9660-filenames -D -o /var/tmp/cdroot/cdfs.iso -no-emul-boot -b EFI_CD_image -eltorito-alt-boot -no-emul-boot -b ilif /var/tmp/cdroot
/opt/ignite/lbin/instl_combine -C /var/tmp/cdroot/cdfs.iso
When I created this image of the machine, a DAT was connected and the device files existed for this DAT in the directory /dev/rmt.
When I install this DVD on a machine which doesn't have a DAT, these device files are not created.
When I connect a DAT on this machine, I must carry out the orders:
ioscan - fnC tape
insf
The problem is that the user can connect a DAT after the installation and I don't want that he uses UNIX commands.
How can I make to force creation of these device files with the DVD created by make_sys_image without connected DAT?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2004 04:39 AM
02-05-2004 04:39 AM
Re: Device files DAT with make_sys_image
In put the two commands in your post config section of the Ignite configuration.
That way the user doesn't have to type them.
SEP
That way the user doesn't have to type them.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2004 04:42 AM
02-05-2004 04:42 AM
Re: Device files DAT with make_sys_image
Hi
Look at restricted sam, you can set up access for a user to do this.
Create a login that runs straight into this restricted sam.
Or create a user that runs automatically the
ioscan - fnC tape, insf - your will have to pick up the correct info from the ioscan and parse it to the insf command, then after completion exit automatically.
In the above routine you will have to place an "if exist" check - so if done dont do it again.
HTH
Paula
Look at restricted sam, you can set up access for a user to do this.
Create a login that runs straight into this restricted sam.
Or create a user that runs automatically the
ioscan - fnC tape, insf - your will have to pick up the correct info from the ioscan and parse it to the insf command, then after completion exit automatically.
In the above routine you will have to place an "if exist" check - so if done dont do it again.
HTH
Paula
If you can spell SysAdmin then you is one - anon
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