Sponsored Content
Full Discussion: Per and Hardware
Top Forums UNIX for Dummies Questions & Answers Per and Hardware Post 19913 by killerserv on Wednesday 17th of April 2002 10:54:15 PM
Old 04-17-2002
Depends on how and what type of Proggram or code you want to write. Here is a little definition on what perl can do and capabale of:

Perl works with existing C libraries
- Through either the XS or SWIG interfaces, Perl programs can use your legacy C libraries.

Perl handles memory management internally
- Perl handles memory management so that programmers don't have to spend time creating memory management bugs which are the most frequent source of security holes.

If you would like something that control H/Ware basically you may try to write codes on Assembly Language. Python can do the trick too. All Depends on your needs.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hardware

Hi I have a problem to start up my Solaris Ultra 5. When it boots up I get a strange clicking sound, sounds like the hard drive that is "thinking" very hard. On the screen I get these messages: Boot device: Files and Args: Please check cable and try again Network link setup fail Time out... (8 Replies)
Discussion started by: Orange
8 Replies

2. UNIX Desktop Questions & Answers

hardware 3d

How do I check my system to see if the graphics are using hardware 3d suport or not. I have a TNT2 on RH 7.1 kernel 2.4.9-?(can't remember off top of my head)I'm running all the latest updates from RH. Also I now have a dvd drive and I am trying to find a player that will play all movies and not... (1 Reply)
Discussion started by: MaxCat
1 Replies

3. Filesystems, Disks and Memory

identify hardware

Does anyone know a good script/tool for remote identification of hardware on a linux-based system (RH9/NLD) ? I'd like to know all the specifics like amount of memory, motherboard vendor, chipset and so on.... (0 Replies)
Discussion started by: patrickb
0 Replies

4. HP-UX

Hardware Recommendation

My J-Class system seems to have killed its onboard NIC. Does anyone have any good suggestions for a *cost effective* :p NIC for this machine? I am currently running 11i v1 on it, and have available PCI-X 5v slots. Alternatively, perhaps someone knows of where I might find a list of supported... (1 Reply)
Discussion started by: ipaddict
1 Replies

5. UNIX Benchmarks

HP hardware benchmark

CPU: 1 x PA8600, 440MHz RAM: 1GB Hardware model: 9000/800/N4000-44 BYTE UNIX Benchmarks (Version 3.11) System -- HP-UX xxx B.11.11 U 9000/800 615379343 unlimited-user license Start Benchmark Run: Tue Apr 4 05:43:42 IST 2006 1 interactive users. Dhrystone 2 without register... (0 Replies)
Discussion started by: blowtorch
0 Replies

6. Programming

Hardware information

How would I write a program in C that prints out the hardware the current computer has? And what about information about it? Thank you for your time. (4 Replies)
Discussion started by: cubics
4 Replies

7. Programming

C and hardware !

Hello ! I have a friend , in one day he tell me this : some guy made a cool program in C , for some sort or hardware control . I say : wow ! Maybe someone , can give me an example , how can C control hardware so good ( as I hear ) , and maybe some cool information , where to learn the idea ,... (1 Reply)
Discussion started by: !_30
1 Replies

8. Solaris

Hardware

Hi, I'm looking to run Sun Solaris 8 or 9, but have been running windows :mad: .can anyone give me advice about the hardware needed for solaris and possably any software i may need, the type of model and where i may be able to buy these within the uk. :confused: ... (3 Replies)
Discussion started by: franz
3 Replies

9. AIX

New Hardware

Can someone help me with what I am guessing is a simple job for an AIX admin. However I am 100% HP-UX and not touched AIX before the start of this week. I am trying to connect an IBM Blade (JS22) to our HP Enterprise Tape Library. I have done all the SAN zoning and this appears to be happy... (5 Replies)
Discussion started by: Andyp2704
5 Replies

10. Solaris

Hardware faulty, but which hardware?

Hi folk, I have this hardware faunty message, but dont know which hardware is this ? can you guide me ? --------------- ------------------------------------ -------------- --------- TIME EVENT-ID MSG-ID SEVERITY ---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies
vparefiutil(1M) 														   vparefiutil(1M)

NAME
vparefiutil - display, update, or delete HP-UX hardware path to EFI path mappings of bootable disks in the virtual partition database SYNOPSIS
db_file] hw_path] DESCRIPTION
The command displays the HP-UX hardware path to EFI path mappings that are stored in the virtual partition database. Legacy and agile hardware paths will be displayed, if available, as provided by HP-UX. If the virtual partition database is not specified, then the live database or by default is used. It can also be used to update the hw_path to EFI_path mappings from to the database. The behavior without any options is to display the HP-UX hardware path to EFI path mappings. This command is not supported on PA-RISC systems. Options and Arguments recognizes the following command line options and arguments: Specifies the alternate database from which the HP-UX hardware path to EFI path mappings need to be displayed, updated, or deleted. or live is default if this is not specified. Updates the database from the info available (from Displays the HP-UX hardware path to EFI path mapping in machine readable format. Each mapping is displayed in a separate line as follows: Deletes the HP-UX hardware path to EFI path mappings in the database. Note: In live database, this deletes only the HP-UX hardware paths owned by the vpar on which this command is executed. If this is specified, only the HP-UX hardware paths at or below the given hw_path are displayed, updated, or deleted. SECURITY RESTRICTIONS
This command is restricted to processes owned by superuser. RETURN VALUE
returns the following values: Successful completion. Error condition occurred. EXAMPLES
Display the hw_path to EFI_path mappings from the live database. # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : 2.0.0.2.0.6.0 EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.0.6.0 : 2.0.0.3.0.6.0 EFI path : Acpi(HWP0002,200)/Pci(3|0)/Scsi(Pun6,Lun0)/ HD(Part1,Sig471031FC-6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.1.2.0 : 2.0.0.3.1.2.0 EFI path : Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1kk0)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(3|0)/Scsi(Pun6,Lun0)/ HD(Part1,Sig471031FC-6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.1.2.0 : EFI path : Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/ EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1kk0)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Display the hw_path to EFI_path mappings from the alternate database in machine readable format. # vparefiutil -M -D vpdb_foo 2.0.0.2.0.6.0:Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI::2.0.0.2.0.6.0 2.0.0.3.0.6.0:Acpi(HWP0002,200)/Pci(3|0)/ Scsi(Pun6,Lkk6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::2.0.0.3.0.6.0 2.0.0.3.1.2.0:Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI::2.0.0.3.1.2.0 2.0.8.1.0.3.4.0.0.1.6:Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/ EFIHPUXHPUX.EFI::2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 2.0.12.1.0.4.1.8.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.10.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunA,Lun0)/ EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.12.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: # vparefiutil -M -D vpdb_foo 2.0.0.2.0.6.0:Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI:: 2.0.0.3.0.6.0:Acpi(HWP0002,200)/Pci(3|0)/ Scsi(Pun6,Lkk6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: 2.0.0.3.1.2.0:Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI:: 2.0.8.1.0.3.4.0.0.1.6:Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/ EFIHPUXHPUX.EFI::2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 2.0.12.1.0.4.1.8.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.10.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/ Scsi(PunA,Lun0)/EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.12.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: Delete the HP-UX hardware-path paths to EFI path mappings at or below the HP-UX hardware path 2/0/0/3 of the current vpar. # vparefiutil -d -H 2/0/0/3 # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunA,Lun0)/ EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path pdb|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI # vparefiutil -d -H 2/0/0/3 # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/ Scsi(PunA,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path pdb|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI For Serial Attach SCSI (SAS) devices, the SAS address is displayed along with the hardware path and the EFI path. Hardware path : 0.0.14.0.0.0.0.0.0.2.0 EFI path : Acpi(HPQ0002,PNP0A08,E)/Pci(0|0)/Pci(0|0)/ VenMsg(D487DDB4-008B-11D9-AFDC-001083FFCA4D)/ HD(Part1,SigC6B41C20-01BE-11DC-8000-D6217B60E588)/EFIHPUXHPUX.EFI SAS Address : 0x500000e01200d3f2 The SAS hardware path can potentially change from one OS instance to another, but the SAS address will remain the same. To locate SAS devices in different OS instances (for example, an nPar OS instance and a vPar OS instance), use the SAS address instead of the hardware path. WARNING
The option is provided only to remove the stale HP-UX hardware path to EFI path mappings. If you remove the valid HP-UX hardware path to EFI path mappings, you may not be able to load vpars. It is always better to follow the operation with a operation to update the database with the valid HP-UX hardware path to EFI path mappings available from AUTHOR
was developed by the Hewlett-Packard Company. SEE ALSO
vparadmin(1M), vparboot(1M), vparconfig(1M), vparcreate(1M), vpardump(1M), vparenv(1M), vparextract(1M), vparmodify(1M), vparreloc(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), privileges(5), vparresources(5), vpartition(5), vpmon(5). Itanium(R)-Based Systems vparefiutil(1M)
All times are GMT -4. The time now is 08:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy