01-04-2020
Thanks for the reply.
Yeah the guy that runs openpa.net, which is an awesome resource thinks that many drivers are already built in.....so I guess we shall see!
Good luck in the mountains.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Dear All
Can somebody help me how H/W and H/W drivers will affect the application?
When I port my application from HP-UX to Solaris should I take care this area? What are the application touch point in H/W or H/W drivers on these two O.S.? (1 Reply)
Discussion started by: charlcy
1 Replies
2. HP-UX
HI ALL,
I am new tp HPUX and i am looking for command that will retive me the following information on HPUX:
Chassis Name & Serial Number:
Monitor
Name
BIOS
Name
EthernetPort
Name
IPEndpoint
Name
PointingDevice
Name
Keyboard
NetworkPrinter
Name
LocalPrinter (5 Replies)
Discussion started by: Veenak15
5 Replies
3. UNIX for Dummies Questions & Answers
Please, I'm From Argentina, And I Need To Know If The Drivers Of Program Unix, Version 5.01 Is Compatible Whit Drivers Of The Printer Epson Fx-2190
Thanks, And I Hope Yuor Answer. (0 Replies)
Discussion started by: juan alberghina
0 Replies
4. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies
5. HP-UX
I am new for HPUX OS and want to pursue my career in HPUX Administration.
I could not able to get following information from HP.com site, that why I need an assistance to know that - can I install HPUX 11i V3 OS on old HP B2000 & B1000 workstations (these workstation are 4 to 5 year old) or not,... (5 Replies)
Discussion started by: girish.batra
5 Replies
6. Solaris
Hi guru
I want to know which company's hardware is more stable means in term of H/W faults or replacement, in case of IBM (AIX), HP (HPUX) & SUN MICROSYSTEM (Solaris) & which order also, if we go through more stable to less stable system.
Regards (1 Reply)
Discussion started by: girish.batra
1 Replies
7. HP-UX
I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email.
original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies
8. Solaris
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
9. HP-UX
We would like to know a HP Utility or any Unix command that can give the exact status of PCI Gigabit Ethernet cable (lan cable) We had tried to execute
lanscan
ioscan -fnC lan
The status appears to be the same when the cable is plugged & unplugged and also when the lan is disabled &... (5 Replies)
Discussion started by: siva3492
5 Replies
10. HP-UX
I am trying to reload a RP4440 with 2x300gb disks and dual Port Network card, with HPUX 11.11 Sept 2003. When the os boots and and gets to the main menu to install HPUX or run recovery, it cannot find the disks or NIC.
At the OS prompt (after loading files), ioscan shows the Class ba, and shows... (0 Replies)
Discussion started by: mrmurdock
0 Replies
LEARN ABOUT MOJAVE
data::dumper::concise::sugar
Data::Dumper::Concise::Sugar(3) User Contributed Perl Documentation Data::Dumper::Concise::Sugar(3)
NAME
Data::Dumper::Concise::Sugar - return Dwarn @return_value
SYNOPSIS
use Data::Dumper::Concise::Sugar;
return Dwarn some_call(...)
is equivalent to:
use Data::Dumper::Concise;
if (wantarray) {
my @return = some_call(...);
warn Dumper(@return);
return @return;
} else {
my $return = some_call(...);
warn Dumper($return);
return $return;
}
but shorter. If you need to force scalar context on the value,
use Data::Dumper::Concise::Sugar;
return DwarnS some_call(...)
is equivalent to:
use Data::Dumper::Concise;
my $return = some_call(...);
warn Dumper($return);
return $return;
If you need to force list context on the value,
use Data::Dumper::Concise::Sugar;
return DwarnL some_call(...)
is equivalent to:
use Data::Dumper::Concise;
my @return = some_call(...);
warn Dumper(@return);
return @return;
If you want to label your output, try DwarnN
use Data::Dumper::Concise::Sugar;
return DwarnN $foo
is equivalent to:
use Data::Dumper::Concise;
my @return = some_call(...);
warn '$foo => ' . Dumper(@return);
return @return;
If you want to output a reference returned by a method easily, try $Dwarn
$foo->bar->{baz}->$Dwarn
is equivalent to:
my $return = $foo->bar->{baz};
warn Dumper($return);
return $return;
If you want to format the output of your data structures, try DwarnF
my ($a, $c) = DwarnF { "awesome: $_[0] not awesome: $_[1]" } $awesome, $cheesy;
is equivalent to:
my @return = ($awesome, $cheesy);
warn DumperF { "awesome: $_[0] not awesome: $_[1]" } $awesome, $cheesy;
return @return;
If you want to immediately die after outputting the data structure, every Dwarn subroutine has a paired Ddie version, so just replace the
warn with die. For example:
DdieL 'foo', { bar => 'baz' };
DESCRIPTION
use Data::Dumper::Concise::Sugar;
will import Dwarn, $Dwarn, DwarnL, DwarnN, and DwarnS into your namespace. Using Exporter, so see its docs for ways to make it do something
else.
Dwarn
sub Dwarn { return DwarnL(@_) if wantarray; DwarnS($_[0]) }
$Dwarn
$Dwarn = &Dwarn
$DwarnN
$DwarnN = &DwarnN
DwarnL
sub Dwarn { warn Data::Dumper::Concise::Dumper @_; @_ }
DwarnS
sub DwarnS ($) { warn Data::Dumper::Concise::Dumper $_[0]; $_[0] }
DwarnN
sub DwarnN { warn '$argname => ' . Data::Dumper::Concise::Dumper $_[0]; $_[0] }
Note: this requires Devel::ArgNames to be installed.
DwarnF
sub DwarnF (&@) { my $c = shift; warn &Data::Dumper::Concise::DumperF($c, @_); @_ }
TIPS AND TRICKS
global usage
Instead of always just doing:
use Data::Dumper::Concise::Sugar;
Dwarn ...
We tend to do:
perl -MData::Dumper::Concise::Sugar foo.pl
(and then in the perl code:)
::Dwarn ...
That way, if you leave them in and run without the "use Data::Dumper::Concise::Sugar" the program will fail to compile and you are less
likely to check it in by accident. Furthmore it allows that much less friction to add debug messages.
method chaining
One trick which is useful when doing method chaining is the following:
my $foo = Bar->new;
$foo->bar->baz->Data::Dumper::Concise::Sugar::DwarnS->biff;
which is the same as:
my $foo = Bar->new;
(DwarnS $foo->bar->baz)->biff;
SEE ALSO
You probably want Devel::Dwarn, it's the shorter name for this module.
perl v5.18.2 2013-12-31 Data::Dumper::Concise::Sugar(3)