ok im trying to upgrade but i keep geting an error and 1 says it ned the other to install but nethere will install heres what im getting now though
now i have 4.2.2-17.2 installed now do i have to unintall everything to get this to install or how do i go about it thank you for your help (3 Replies)
Hi all
I have a HP B1000 with HP-UX 11 installed but recently I have aqquired 11i on CD, after reading the documentation it states that 11i can be installed on a B1000 with a firmware update, which is included on the 11i media, but I have been told it will be impossible to install 11i on my... (3 Replies)
Hey All
We are having ORacle 8.1.7 and ORacle 9.2.0.4 installed in our Sun sparc Servers(oON SOLARIS 8).
We are going to upgrade our servers to SOLARIS Ver 9
Solaris ver 9 supports the above mentioned Oracle versions. Can any one help me out how to upgrade from solaris 8 to solaris 9.
... (2 Replies)
How can I find out what options were used to build the apache currently running on my computer?
I'd like to upgrade and want to make sure not to break any sites running on it.
I've been going through the sites to figure out just what is needed, but want to be sure not to miss anything before... (2 Replies)
As a fairly new Administrator to AIX i am a little leary of the OS upgrade I need to do on one of our servers. I have already upgraded the microcode to the lastest level and now need to do the OS. I have the docs and discs from IBM and have determined that I dont want to do a new installation but... (5 Replies)
Hello,
I am using Redhat Linux Enterprise 4 AS.
To upgrade NFS, I had to browse the internet and finally I got the latest rpm https://rhn.redhat.com/errata/RHBA-2005-727.html
That was a time-consuming procedure. On Solaris, I am used to go to sunfreeware.sun.com and download the latest... (3 Replies)
Hello,
I read and search through this wonderful forum and tried different approaches but it seems I lack some knowledge and neurones ^^
Here is what I'm trying to achieve :
file1:
test filea 3495;
test fileb 4578;
test filec 7689;
test filey 9978;
test filez 12300;
file2:
test filea... (11 Replies)
We currently have test and production servers running AIX 5.2, DB2 8.1(Prod), DB2 8.2(Test),Websphere 6.1 on both. We need to upgrade to DB2 to version 9, but to do that we also need to upgrade the operating system to 5.3 and go from 32 bit kernel to 64 bit kernal. Looking for information on any... (3 Replies)
Hey guys,
since AIX 5.3 reaches EOS on april 2012, I really need to update my systems asap.
Any experience on upgrading directly to 7.1, with sap/db2/oracle?
could do fresh installs and import my sap/db vgs, but this would be a lot of work
cheers Funksen (4 Replies)
Hi
I've just upgraded OS - using "Migration with nimadm". The Nim master is a Power 6 server, and the source is 6100-09-04-1441.
The migration was successful with a Power 6 - Nim client, but there was a problem with Power 5 - Nim client : the OS remained 6100-00-09-0920
icapp1:/]oslevel -s... (1 Reply)
Discussion started by: bobochacha29
1 Replies
LEARN ABOUT MOJAVE
encoding::warnings
encoding::warnings(3pm) Perl Programmers Reference Guide encoding::warnings(3pm)NAME
encoding::warnings - Warn on implicit encoding conversions
VERSION
This document describes version 0.11 of encoding::warnings, released June 5, 2007.
SYNOPSIS
use encoding::warnings; # or 'FATAL' to raise fatal exceptions
utf8::encode($a = chr(20000)); # a byte-string (raw bytes)
$b = chr(20000); # a unicode-string (wide characters)
# "Bytes implicitly upgraded into wide characters as iso-8859-1"
$c = $a . $b;
DESCRIPTION
Overview of the problem
By default, there is a fundamental asymmetry in Perl's unicode model: implicit upgrading from byte-strings to unicode-strings assumes that
they were encoded in ISO 8859-1 (Latin-1), but unicode-strings are downgraded with UTF-8 encoding. This happens because the first 256
codepoints in Unicode happens to agree with Latin-1.
However, this silent upgrading can easily cause problems, if you happen to mix unicode strings with non-Latin1 data -- i.e. byte-strings
encoded in UTF-8 or other encodings. The error will not manifest until the combined string is written to output, at which time it would be
impossible to see where did the silent upgrading occur.
Detecting the problem
This module simplifies the process of diagnosing such problems. Just put this line on top of your main program:
use encoding::warnings;
Afterwards, implicit upgrading of high-bit bytes will raise a warning. Ex.: "Bytes implicitly upgraded into wide characters as iso-8859-1
at - line 7".
However, strings composed purely of ASCII code points (0x00..0x7F) will not trigger this warning.
You can also make the warnings fatal by importing this module as:
use encoding::warnings 'FATAL';
Solving the problem
Most of the time, this warning occurs when a byte-string is concatenated with a unicode-string. There are a number of ways to solve it:
o Upgrade both sides to unicode-strings
If your program does not need compatibility for Perl 5.6 and earlier, the recommended approach is to apply appropriate IO disciplines,
so all data in your program become unicode-strings. See encoding, open and "binmode" in perlfunc for how.
o Downgrade both sides to byte-strings
The other way works too, especially if you are sure that all your data are under the same encoding, or if compatibility with older
versions of Perl is desired.
You may downgrade strings with "Encode::encode" and "utf8::encode". See Encode and utf8 for details.
o Specify the encoding for implicit byte-string upgrading
If you are confident that all byte-strings will be in a specific encoding like UTF-8, and need not support older versions of Perl, use
the "encoding" pragma:
use encoding 'utf8';
Similarly, this will silence warnings from this module, and preserve the default behaviour:
use encoding 'iso-8859-1';
However, note that "use encoding" actually had three distinct effects:
o PerlIO layers for STDIN and STDOUT
This is similar to what open pragma does.
o Literal conversions
This turns all literal string in your program into unicode-strings (equivalent to a "use utf8"), by decoding them using the
specified encoding.
o Implicit upgrading for byte-strings
This will silence warnings from this module, as shown above.
Because literal conversions also work on empty strings, it may surprise some people:
use encoding 'big5';
my $byte_string = pack("C*", 0xA4, 0x40);
print length $a; # 2 here.
$a .= ""; # concatenating with a unicode string...
print length $a; # 1 here!
In other words, do not "use encoding" unless you are certain that the program will not deal with any raw, 8-bit binary data at all.
However, the "Filter => 1" flavor of "use encoding" will not affect implicit upgrading for byte-strings, and is thus incapable of
silencing warnings from this module. See encoding for more details.
CAVEATS
For Perl 5.9.4 or later, this module's effect is lexical.
For Perl versions prior to 5.9.4, this module affects the whole script, instead of inside its lexical block.
SEE ALSO
perlunicode, perluniintro
open, utf8, encoding, Encode
AUTHORS
Audrey Tang
COPYRIGHT
Copyright 2004, 2005, 2006, 2007 by Audrey Tang <cpan@audreyt.org>.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
See <http://www.perl.com/perl/misc/Artistic.html>
perl v5.18.2 2013-11-04 encoding::warnings(3pm)