*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->IRIX man pages -> installf (1)              
Title
Content
Arch
Section
 

Contents


installf(1M)							  installf(1M)


NAME    [Toc]    [Back]

     installf -	add a file to the software installation	database

SYNOPSIS    [Toc]    [Back]

     installf [-c class] pkginst pathname [ftype [[major minor]
	  [mode	owner group]]]

     installf [-c class] pkginst <b>-
     installf -f [-c class] pkginst

DESCRIPTION    [Toc]    [Back]

     installf informs the system that a	pathname not listed in the pkgmap file
     is	being created or modified.  It should be invoked before	any file
     modifications have	occurred.

     When the second synopsis is used, the pathname descriptions will be read
     from standard input.  These descriptions are the same as would be given
     in	the first synopsis but the information is given	in the form of a list.
     (The descriptions should be in the	form:  pathname	[ftype [[major minor]
     [mode owner group]]].)





     After all files have been appropriately created and/or modified, installf
     should be invoked with the	-f synopsis to indicate	that installation is
     final.  Links will	be created at this time	and, if	attribute information
     for a pathname was	not specified during the original invocation of
     installf or was not already stored	on the system, the current attribute
     values for	the pathname will be stored.  Otherwise, installf verifies
     that attribute values match those given on	the command line, making
     corrections as necessary.	In all cases, the current content information
     is	calculated and stored appropriately.

     -c	class  Class to	which installed	objects	should be associated.  Default
	       class is	none.

     pkginst   Name of package instance	with which the pathname	should be
	       associated.

     pathname  Pathname	that is	being created or modified.  Special
	       characters, such	as an equal sign (=), are included in
	       pathnames by surrounding	the entire pathname in single quotes
	       (as in, for example, '/usr/lib/~=').  When a pathname is
	       specified on a shell command line, the single quotes must be
	       preceded	by backslashes so they're not interpreted by the
	       shell.

     ftype     A one-character field that indicates the	file type.  Possible
	       file types include:




									Page 1






installf(1M)							  installf(1M)



		   f  a	standard executable or data file
		   e  a	file to	be edited upon installation or removal
		   v  volatile file (one whose contents	are expected to
		      change)
		   d  directory
		   x  an exclusive directory
		   l  linked file
		   p  named pipe
		   c  character	special	device
		   b  block special device
		   s  symbolic link

     major     The major device	number.	 The field is only specified for block
	       or character special devices.

     minor     The minor device	number.	 The field is only specified for block
	       or character special devices.

     mode      The octal mode of the file (for example,	0664).	A question
	       mark (?)	 indicates that	the mode will be left unchanged,
	       implying	that the file already exists on	the target machine.
	       This field is not used for linked or symbolically linked	files.

     owner     The owner of the	file (for example, bin or root).  The field is
	       limited to 14 characters	in length.  A question mark (?)
	       indicates that the owner	will be	left unchanged,	implying that
	       the file	already	exists on the target machine.  This field is
	       not used	for linked or symbolically linked files.

     group     The group to which the file belongs (for	example, bin or	sys).
	       The field is limited to 14 characters in	length.	 A question
	       mark (?)	indicates that the group will be left unchanged,
	       implying	that the file already exists on	the target machine.
	       This field is not used for linked or symbolically linked	files.





















									Page 2






installf(1M)							  installf(1M)



     -f	       Indicates that installation is complete.	 This option is	used
	       with the	final invocation of installf (for all files of a given
	       class).

NOTES    [Toc]    [Back]

     When ftype	is specified, all applicable fields, as	shown below, must be
     defined:
	  cf2 cf2 lf4 lf4.  ftype     Required Fields p	x d f v	or e mode
	  owner	group c	or b	major minor mode owner group


     The installf command will create directories, named pipes and special
     devices on	the original invocation.  Links	are created when installf is
     invoked with the -f option	to indicate installation is complete.

     Links should be specified as path1<b>=path2.	path1 indicates	the
     destination and path2 indicates the source	file.

     For symbolically linked files, path2 can be a relative pathname, such as
     ./	or ../.	 For example, if you enter a line such as

	  s /foo/bar/etc/mount=../usr/sbin/mount

     path2 (/foo/bar/etc/mount)	will be	a symbolic link	to ../usr/sbin/mount.

     Files installed with installf will	be placed in the class none, unless a
     class is defined with the command.	 Subsequently, they will be removed
     when the associated package is deleted.  If this file should not be
     deleted at	the same time as the package, be certain to assign it to a
     class which is ignored at removal time.  If special action	is required
     for the file before removal, a class must be defined with the command and
     an	appropriate class action script	delivered with the package.

     When classes are used, installf must be used as follows:

       installf	-c class1 . . .	 installf -f -c	class1 . . .  installf -c
       class2 .	. .  installf -f -c class2 . . .


















									Page 3






installf(1M)							  installf(1M)


EXAMPLE    [Toc]    [Back]

     The following example shows the use of installf invoked from an optional
     preinstall	or postinstall script:

     #create /dev/xt directory
     #(needs to	be done	before drvinstall)
     installf $PKGINST /dev/xt d 755 root sys ||
	  exit 2
     majno=`/usr/sbin/drvinstall -m /etc/master.d/xt
	  -d $BASEDIR/data/xt.o	-v1.0` ||
	  exit 2
     i=00
     while [ $i	-lt $limit ]
     do
       for j in	0 1 2 3	4 5 6 7
       do
	 echo /dev/xt$i$j c $majno `expr $i * 8	+ $j` 644 root sys
	 echo /dev/xt$i$j=/dev/xt/$i$j
       done
       i=`expr $i + 1`
       [ $i -le	9 ] && i="0$i" #add leading zero
     done | installf $PKGINST -	|| exit	2
     # finalized installation, create links
     installf -f $PKGINST || exit 2

SEE ALSO    [Toc]    [Back]

      
      
     pkgadd(1M), pkgask(1M), pkgchk(1),	pkginfo(1), pkgmk(1), pkgparam(1),
     pkgproto(1), pkgtrans(1), pkgrm(1M), removef(1M)


									PPPPaaaaggggeeee 4444
[ Back ]
 Similar pages
Name OS Title
swinstall HP-UX install and configure software products; software products for subsequent installation or distribution; respec
swcopy HP-UX install and configure software products; software products for subsequent installation or distribution; respec
inst IRIX software installation tool
share_setup IRIX diskless software installation tools
roboinst IRIX automatic software installation tool
share_inst IRIX diskless software installation tools
cl_init IRIX init program for diskless software installation
cp_dirs Tru64 Database configuration file used by worldwide support software
sd HP-UX Software Distributor, commands to create, distribute, install, monitor, and manage software
mailwrapper FreeBSD invoke appropriate MTA software based on configuration file
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service