Sponsored Content
Full Discussion: vpath fbvol relationship
Operating Systems AIX vpath fbvol relationship Post 302095037 by samaks on Friday 3rd of November 2006 02:04:10 AM
Old 11-03-2006
found the answer

I found the answer. If you use lsattr -El vpathx the last four digits of the serial number is the ID you give in DSCLI.
 

8 More Discussions You Might Find Interesting

1. AIX

vpath to an hdisk

Is there a simply way for me to map a vpath to an hdisk on AIX 5.2? (5 Replies)
Discussion started by: 2dumb
5 Replies

2. Shell Programming and Scripting

vpath directive in make

Hi all, I need to check the contents of my vpath directive in my file. Is it possible to check the contents of the vpath directive as we do for a variable like @echo '$vpath' . Please let me know the above is correct or suggest me the correct one. Thanks in advance. -Jerry (6 Replies)
Discussion started by: jerryragland
6 Replies

3. AIX

AIX vpath lun

Hi everyone, how can I check if I have LUNs in a server and the LUNīs vpath in AiX? thx (5 Replies)
Discussion started by: jcpetela
5 Replies

4. AIX

vpath and sharks

Hello everyone: just want to know how to get the name of the shark in which the vpath is? thanks (2 Replies)
Discussion started by: jcpetela
2 Replies

5. AIX

lscfg -vl vpath - error

Hello all, I need to run successfully this command : 1:root@abcd:/root # lscfg -vl vpathXY lscfg: device vpathXY not found. 1:root@abcd:/root # echo $? 1 If I run it on another server I will get no output which is ok : 1:root@efgh:/root # lscfg -vl vpathAB 1:root@efgh:/root # echo... (0 Replies)
Discussion started by: phobus
0 Replies

6. AIX

lscfg -vl vpath - error

Hello all, I need to run successfully this command : 1:root@abcd:/root # lscfg -vl vpathXY lscfg: device vpathXY not found. 1:root@abcd:/root # echo $? 1 If I run it on another server I will get no output which is ok : 1:root@efgh:/root # lscfg -vl vpathAB 1:root@efgh:/root # echo $?... (4 Replies)
Discussion started by: phobus
4 Replies

7. Programming

Relationship between exceptions and signals

Hi everyone, I am using AIX 6.1. There are exception codes defined in header file sys/m_except.hAlso, in the documentation (in "Understanding exception handling") it says: If no exception handler is currently defined when an exception occurs, typically one of two things happens. If... (0 Replies)
Discussion started by: manolo123
0 Replies

8. UNIX for Dummies Questions & Answers

Identify process/file relationship

Hey guys. So, I've got an issue on my Debian box. Problem is I ran out of disc space as a process (?) has been creating millions of folders in one place which has led to me having 0 bytes of free space and started messing with my ability to get online, I believe this is to do with INODES? I... (3 Replies)
Discussion started by: 3therk1ll
3 Replies
epm(1)							      Easy Software Products							    epm(1)

NAME
epm - create software packages. SYNOPSIS
epm [ -a architecture ] [ -f format ] [ -g ] [ -k ] [ -m name ] [ -n[mrs] ] [ -s setup.xpm ] [ --depend ] [ --help ] [ --keep-files ] [ --output-dir directory ] [ --setup-image setup.xpm ] [ --setup-program /foo/bar/setup ] [ --setup-types setup.types ] [ -v ] [ name=value ... name=value ] product [ listfile ] DESCRIPTION
epm generates software packages complete with installation, removal, and (if necessary) patch scripts. Unless otherwise specified, the files required for product are read from a file named "product.list". The -a option ("architecture") specifies the actual architecture for the software. Without this option the generic processor architecture is used ("intel", "sparc", "mips", etc.) The -f option ("format") specifies the distribution format: aix Generate an AIX distribution suitable for installation on an AIX system. bsd Generate a BSD distribution suitable for installation on a FreeBSD, NetBSD, or OpenBSD system. deb Generate a Debian distribution suitable for installation on a Debian Linux system. inst, tardist Generate an IRIX distribution suitable for installation on an system running IRIX. lsb, lsb-signed Generate RPM packages for LSB-conforming systems. The lsb-signed format uses the GPG private key you have defined in the ~/.rpmmacros file. native Generate an native distribution. This uses rpm for Linux, inst for IRIX, pkg for Solaris, swinstall for HP-UX, bsd for FreeBSD, Net- BSD, and OpenBSD, and osx for MacOS X. All other operating systems default to the portable format. osx Generate a MacOS X software package. pkg Generate an AT&T software package. These are used primarily under Solaris. portable Generate a portable distribution based on shell scripts and tar files. The resulting distribution is installed and removed the same way on all operating systems. [default] rpm, rpm-signed Generate a Red Hat Package Manager ("RPM") distribution suitable for installation on a Red Hat Linux system. The rpm-signed format uses the GPG private key you have defined in the ~/.rpmmacros file. setld Generate a Tru64 (setld) software distribution. slackware Generate a Slackware Linux software distribution. swinstall, depot Generate a HP-UX software distribution. Executable files in the distribution are normally stripped of debugging information when packaged. To disable this functionality use the -g option. Intermediate (spec, etc.) files used to create the distribution are normally removed after the distribution is created. The -k option keeps these files in the distribution directory. The -s and --setup-image options ("setup") include the ESP Software Wizard with the specified GIF or XPM image file with the distribution. This option is currently only supported by portable and RPM distributions. The --setup-program option specifies the setup executable to use with the distribution. This option is currently only supported by portable distributions. The --setup-types option specifies the setup.types file to include with the distribution. This option is currently only supported by porta- ble distributions. The --output-dir option specifies the directory to place output file into. The default directory is based on the operating system, version, and architecture. The -v option ("verbose") increases the amount of information that is reported. Use multiple v's for more verbose output. The --depend option lists the dependent (source) files for all files in the package. Distributions normally are named "product-version-system-release-machine.ext" and "product-version-system-release-machine-patch.ext" (for patch distributions.) The "system-release-machine" information can be customized or eliminated using the -n option with the appropriate trailing letters. Using -n by itself will remove the "system-release-machine" string from the filename entirely. The "system-release- machine" information can also be customized by using the -m option with an arbitrary string. Debian, IRIX, portable, and Red Hat distributions use the extensions ".deb", ".tardist", "tar.gz", and ".rpm" respectively. LIST FILES
The EPM list file format is now described in the epm.list(5) man page. KNOWN BUGS
EPM does not currently support generation of IRIX software patches. SEE ALSO
epminstall(1) - add a directory, file, or symlink to a list file mkepmlist(1) - make an epm list file from a directory epm.list(5) - epm list file format setup(1) - graphical setup program for the esp package manager COPYRIGHT
Copyright 1999-2008 by Easy Software Products, All Rights Reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. 26 August 2008 ESP Package Manager epm(1)
All times are GMT -4. The time now is 01:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy