Sponsored Content
Full Discussion: unconfigure using cfgadm
Operating Systems Solaris unconfigure using cfgadm Post 302316653 by reborg on Friday 15th of May 2009 05:18:14 PM
Old 05-15-2009
In this case

c2::2100000087140f53 is your attachment point ( look at the path on the line after the disk name and compare the identifiers )
 

4 More Discussions You Might Find Interesting

1. Solaris

cfgadm - is this an error?

# cfgadm -al Ap_Id Type Receptacle Occupant Condition c0 scsi-bus connected configured unknown c0::dsk/c0t0d0 CD-ROM connected configured unknown c1 scsi-bus ... (8 Replies)
Discussion started by: robsonde
8 Replies

2. Solaris

Issue with cfgadm

I have an issue with on T3-Lun where Veritas dont like it anymore and OS-system have issues with it too. So I thought to unconfigure it but even that does not work cfgadm -al | grep c17 c17::50020f230000eae0 disk connected unconfigured unkown then I tried a cfgadm -c unconfigure... (2 Replies)
Discussion started by: manni2
2 Replies

3. Solaris

Remove old subpaths from vxvm/format/cfgadm

Hi, I`m having a server, that was initially having 2 HBA`s, and dmpnodes were creates with 2 subpaths: # vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online invalid c0t1d0s2 auto:none - ... (5 Replies)
Discussion started by: masloff
5 Replies

4. Solaris

Hot swapping disks on V240 - blue light not lit after cfgadm -c unconfigure

Hot swapping a drive on V240. So, I do cfgadm -c unconfigure <disk>. Then cfgadm -al reports disk as unconfigured as expected. format then tells me there is no disk. BUT, blue light does not come on. Done the exact same command on my V440 and blue light does come on. V240 Server Admin... (0 Replies)
Discussion started by: psychocandy
0 Replies
Font::TTF::GDEF(3pm)					User Contributed Perl Documentation				      Font::TTF::GDEF(3pm)

NAME
Font::TTF::GDEF - Opentype GDEF table support DESCRIPTION
The GDEF table contains various global lists of information which are apparantly used in other places in an OpenType renderer. But precisely where is open to speculation... INSTANCE VARIABLES
There are 4 tables in the GDEF table, each with their own structure: GLYPH This is an Font::TTF::Coverage Class Definition table containing information as to what type each glyph is. ATTACH The attach table consists of a coverage table and then attachment points for each glyph in the coverage table: COVERAGE This is a coverage table POINTS This is an array of point elements. Each element is an array of curve points corresponding to the attachment points on that glyph. The order of the curve points in the array corresponds to the attachment point number specified in the MARKS coverage table (see below). LIG This contains the ligature caret positioning information for ligature glyphs COVERAGE A coverage table to say which glyphs are ligatures LIGS An array of elements for each ligature. Each element is an array of information for each caret position in the ligature (there being number of components - 1 of these, generally) FMT This is the format of the information and is important to provide the semantics for the value. This value must be set correctly before output VAL The value which has meaning according to FMT DEVICE For FMT = 3, a device table is also referenced which is stored here MARKS Due to confusion in the GDEF specification, this field is currently withdrawn until the confusion is resolved. That way, perhaps this stuff will work! This class definition table stores the mark attachment point numbers for each attachment mark, to indicate which attachment point the mark attaches to on its base glyph. METHODS
$t->read Reads the table into the data structure $t->out($fh) Writes out this table. perl v5.10.1 2009-01-29 Font::TTF::GDEF(3pm)
All times are GMT -4. The time now is 09:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy