Sponsored Content
Operating Systems Solaris problem in creating flash archive Post 302214989 by System Shock on Tuesday 15th of July 2008 09:33:25 AM
Old 07-15-2008
That's a common message. It's "normal". It won't affect your flar.
 

8 More Discussions You Might Find Interesting

1. Solaris

things to include in a flash archive

I am making a flash archive to use as a base to lay down on all incoming servers. I am wondering about Sun Explorer and Sun CST. Is it ok to install these (but not configure them) on my source machine and create the archive? Im just not sure if it would cause problems down the line, like... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

2. UNIX for Dummies Questions & Answers

Flash Archive Retrival Method

Need a little help figuring out how to restore a .flar image using the Flash Archive Retrival Method. I am using Solaris 8 on a Sun V240. I boot the system using the Solaris 8 disk 1of2 and provide the necessary information asked. When the screen gets to the Flash Archive Retrival Method screen... (2 Replies)
Discussion started by: Kevin1166
2 Replies

3. Solaris

creat flash archive

I want take a flash backup by flar command for specific files like: / , /boot, /tmp I am trying this command but its not working # flar -n archive1 -f /,/boot,/tmp -F -c /home/arc1.flar Please can any body help me __.____._ (2 Replies)
Discussion started by: kmuqalled
2 Replies

4. Solaris

How to convert .iso into flash archive

Hello Gururz, I downloaded sol-10-u7-ga-sparc-dvd.iso from Sun site Solaris Operating System - Get Solaris 10 But my jet build images are in .flar Could someone tell me how to convert .iso into .flar? Please help me on this (1 Reply)
Discussion started by: bullz26
1 Replies

5. Solaris

How to install flash archive over the netwrok

Hi Gurus I've to install the flash archive over the network. The archive is created and directory has been shared, what else all i have to do. Once i go to install option on other system and choose FTP( flash archive only) . Will appreciate if some one can help me or directed me towards some... (9 Replies)
Discussion started by: kumarmani
9 Replies

6. Solaris

difference between flash archive and jumpstart

Hi, Can anyone explains me the difference between solaris flash archive and jumpstart installation. Both are used to install many systems frm a centralized location , correct me if am wrong,. Clear view on this is really appreciable. Thanks in advance (3 Replies)
Discussion started by: rogerben
3 Replies

7. Solaris

Flash archive with VxVM

I'm writing a design doc and I got this feedback. "Apparently flash archives have issues with VXVM root F/S's - May also impact licensing for “kick” systems. SVM may be more sensible / flexible option" The VxVM will be use global zones. i intend on using flash archives of solaris 8/9... (3 Replies)
Discussion started by: frustin
3 Replies

8. Solaris

Jump Start vs Flash Archive

Hi I'm trying to understand the difference between installation methods of Solaris 10, Jump Start vs Flash Archive ? thx for help. (6 Replies)
Discussion started by: presul
6 Replies
Devel::DollarAt(3pm)					User Contributed Perl Documentation				      Devel::DollarAt(3pm)

NAME
Devel::DollarAt - Give magic abilities to $@ SYNOPSIS
use Devel::DollarAt; eval "0/0"; print $@, $@->backtrace; $@->redie; DESCRIPTION
Using eval {}, you may catch Perl exceptions almost like you do it with try {} in Java. However there are days when you miss some features of exceptions. The only thing you know about the error that occured is the string $@, which combines the error message and technical data like the line number. The Devel::DollarAt module gives some functionality to the $@ scalar. Once you say "use Devel::DollarAt", the module is active program- wide. If an exception occurs anywhere in any module, $@ will be globally set to an object of class Devel::DollarAt. Apart from performance, this shouldn't be a problem because $@ tries to be downwardly compatible to the normal $@. However using this package in CPAN modules or large software projects is discouraged. DISCLAIMER
Use this module only for debugging. Don't think of it as an exception framework for Perl or something like that. It just gives magic abilities to $@, that's all. METHODS
backtrace Returns a Devel::Backtrace object, which lets you inspect the callers of the fatality. filename Returns the name of the file in which the error occured. inputhandle Returns the file handle which has most recently be read from at the time of the error. inputline Returns the line number of "$@->inputhandle" (which is $.) at the time of the error. line Returns the number of the line in which the error occured. redie Redispatches this exception to the next eval{}. redispatch_points Returns a list of objects with informations about when this exception was redispatched. Each object has got the accessors "package", "filename" and "line". In string context, the objects will look like "redispatched from FooPackage at file.pl:17 ". to_string Returns a string that looks quite like the normal $@, e. g. "Illegal division by zero at foo.pl line 42, <> line 13." Devel::DollarAt overloads the "" (stringification) operator to this method. EXAMPLES
A very simple (and pointless) way to use Devel::DollarAt is this oneliner: perl -MDevel::DollarAt -e '0/0' It bails out with "Illegal division by zero at -e line 1." and an exit status of 1, just like it would have done if you hadn't supplied -MDevel::DollarAt. This is because the magically modified $@ variable gets stringified when perl prints it as exit reason. If you actually want to see the difference, use perl -MDevel::DollarAt=frame -e '0/0' This bails out with "[[Illegal division by zero at -e line 1.]]" so you can see that something has happened. KNOWN PROBLEMS
This module requires that no other code tampers with $SIG{__DIE__} or *CORE::GLOBAL::die. A not widely known feature of Perl is that it can propagate $@. If you call die() without parameters or with an empty string or an undefined value, the error message will be "Died". However, if $@ was set to some value before this, the previous error message will be used with " ...propagated" appended: perl -e '$@="7"; die" 7 ...propagated at -e line 1. Devel::DollarAt emulates this behaviour. If you use the above example but leave out the double quotes, perl's behaviour is different as of version 5.8.8: perl -e '$@=7; die' 7 at -e line 1. Devel::DollarAt does not emulate this behaviour: perl -MDevel::DollarAt -e '$@=7; die' 7 ...propagated at -e line 1. If a previous $@ is propagated, inputhandle and inputline won't work. They won't be interpolated into the stringified $@, either. If perl comes across syntax errors, $@ appears to be just a string as usual. Apparently $SIG{__DIE__} won't be called for syntax errors. AUTHOR
Christoph Bussenius <pepe@cpan.org> If you use this module, I'll be glad if you drop me a note. You should mention this module's name in the subject of your mails, in order to make sure they won't get lost in all the spam. LICENSE
This module is in the public domain. If your country's law does not allow this module being in the public domain or does not include the concept of public domain, you may use the module under the same terms as perl itself. perl v5.10.0 2009-01-27 Devel::DollarAt(3pm)
All times are GMT -4. The time now is 09:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy