swconvert man page on DigitalUNIX

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
DigitalUNIX logo
[printable version]

swconvert(8)							  swconvert(8)

NAME
       swconvert  -  converts setld software subsets into SysMan Software Man‐
       ager packages

SYNOPSIS
       /usr/sbin/swconvert -s mount_point [-a | subset_name [subset_name  ...]
       ]

       /usr/sbin/swconvert -k key_filename kit_directory

       /usr/sbin/swconvert -h

FLAGS
       Used  in conjunction with the -s flag, specifies that all software sub‐
       sets on the distribution media are to be converted.   Displays  command
       usage  statements.   Converts  an  entire product kit. The key_filename
       argument is the file that defines the product on	 the  kit.   The  file
       naming  convention  for the key file is PRODUCT_CODE.k.	The kit_direc‐
       tory is the location of the kit source files.  Specifies the source  or
       mount  point  of the distribution media or software subsets to convert.
       When used in conjunction with the -a otion, converts all subsets on the
       source.

DESCRIPTION
       The  swconvert command converts traditional setld software subsets into
       SysMan Software Manager packages.  The swconvert command can convert  a
       subset from an existing distribution and copy it into a depot or create
       a Product Specification File (PSF) from a traditional setld  key	 file.
       When  packaging	into a depot, the swconvert command copies the product
       into the default depot at /var/spool/sw.

       Due to differences between SysMan Software Manager control scripts  and
       setld  subset  control  programs	 (SCP), there is no guarantee that the
       converted subset's SCP will function correctly. If the SCP is  interac‐
       tive  or	 performs  unusual  tasks such as check setld private areas or
       invoke setld resulting in nested setld  calls, there is a  high	proba‐
       bility  that  the  converted subset control scripts will not be accept‐
       able.  All OSF subsets are for the most part safe to convert.

       You must be logged in as the user root or have superuser privileges  to
       to convert a software subset.

RESTRICTIONS
       Once  a	setld software subset is converted and a product specification
       file (PSF) is created, the PSF file cannot be  used  to	repackage  the
       product again with the swpackage command.

       Only  PSF files from kit areas are safe to reuse.  Converted subset PSF
       files are for reference only.

EXAMPLES
       Convert	the  OSPXV310  software	 subset	 in  the  current   directory:
       /usr/sbin/swconvert -s . OSPXV310

       Convert the OSPXV310 software subset on the distribution mounted at the
       /cdrom mount point: /usr/sbin/swconvert -s /cdrom OSPXV310

       Convert an entire kit: /usr/sbin/swconvert -k OSP.k /usr/opt/src/OSP

FILES
       Default depot for converted software packages.  Log file	 containing  a
       record of conversion activity.  Location of the installed product data‐
       base after the converted subset is installed.

RELATED INFORMATION
       Commands: sd(4), sd(5), swask(8), swpackage(8), swinstall(8)

								  swconvert(8)
[top]

List of man pages available for DigitalUNIX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net