03-31-2006
I think you can easily check it using a C code where you create a union made of an integer and a char array that matches the integer size (4 bytes in x86, for example).
Then you assign the number 1 to the union's integer.
Checking the value of the first element of the array, and looking wether it's zero or one, you can determine system's endianess (i think it will be 1 in little endian).
Hope this helps
Salut
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all
I know AIX is big-endian machine.But does it read bytes in normal way from LSB.
Does it happen in some machine that at multi-byte integer level it is Little-endian and while reading a single byte it is Big-Endian.
This is urgent
Thanks in advance. (3 Replies)
Discussion started by: Shobhit
3 Replies
2. UNIX for Dummies Questions & Answers
1 . Thanks everyone who read the post first.
2 . I have a log file which size is 143M , I can not use vi open it .I can not use xedit open it too.
How to view it ?
If I want to view 200-300 ,how can I implement it
3 . Thanks (3 Replies)
Discussion started by: chenhao_no1
3 Replies
3. Programming
We are developing an application using TLI for network communication.The Server Code is developed in Sun and client in SCO unix. When we route data from Client to Server we encrypt the data using DES algotithm utility.The problem we are facing that Sun uses Big Endian methodology to store data in... (1 Reply)
Discussion started by: S.P.Prasad
1 Replies
4. UNIX for Advanced & Expert Users
Hi everybody,
I met this week a problem.
For now, we used TRU64 system based on alpha. Now, we're installing UP-UX systems (on Itanium). And we have problem with our files. Indeed, we use file with COMP-3, COMP-5 data. These files are used on both platforms. (we use also TXT files which... (1 Reply)
Discussion started by: bigmike59270
1 Replies
5. UNIX and Linux Applications
Hi,
We are trying to migrate an oracle database from Sun Solaris (SunOS 5.9 Generic_118558-28 sun4u sparc SUNW,Ultra-60) to Linux 2.6.18-53.1.19.el5 #1 SMP Tue Apr 22 03:01:10 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux which is basically a Big Endian to Little Endian conversion.
We shutdown... (3 Replies)
Discussion started by: luft
3 Replies
6. Solaris
hi folks, in the sparc v9 manul , it says it is possible to access the memory data in little-endian mode, but there is only privilaged instruction that could set the PSTATE ( the cle bit ) regist. if I'm in the user mode , is it possible for me to access the data in little-endian mode? (10 Replies)
Discussion started by: zerocool_08
10 Replies
7. UNIX for Dummies Questions & Answers
I have a 5000 line config.log file with several "maybe" errors. Any reccomendations on finding solvable problems? (2 Replies)
Discussion started by: NeedLotsofHelp
2 Replies
8. UNIX and Linux Applications
Hi
Endian firewall free version if we do compare pfsense
For a LAN network with active user 1000
Which do you recommend
Share (0 Replies)
Discussion started by: mnnn
0 Replies
LEARN ABOUT SUSE
net::dns::question
Net::DNS::Question(3) User Contributed Perl Documentation Net::DNS::Question(3)
NAME
Net::DNS::Question - DNS question class
SYNOPSIS
"use Net::DNS::Question"
DESCRIPTION
A "Net::DNS::Question" object represents a record in the question section of a DNS packet.
METHODS
new
$question = Net::DNS::Question->new("example.com", "MX", "IN");
Creates a question object from the domain, type, and class passed as arguments.
RFC4291 and RFC4632 IP address/prefix notation is supported for queries in in-addr.arpa and ip6.arpa subdomains.
parse
($question, $offset) = Net::DNS::Question->parse($data, $offset);
Parses a question section record at the specified location within a DNS packet. The first argument is a reference to the packet data. The
second argument is the offset within the packet where the question record begins.
Returns a Net::DNS::Question object and the offset of the next location in the packet.
Parsing is aborted if the question object cannot be created (e.g., corrupt or insufficient data).
qname, zname
print "qname = ", $question->qname, "
";
print "zname = ", $question->zname, "
";
Returns the domain name. In dynamic update packets, this field is known as "zname" and refers to the zone name.
qtype, ztype
print "qtype = ", $question->qtype, "
";
print "ztype = ", $question->ztype, "
";
Returns the record type. In dymamic update packets, this field is known as "ztype" and refers to the zone type (must be SOA).
qclass, zclass
print "qclass = ", $question->qclass, "
";
print "zclass = ", $question->zclass, "
";
Returns the record class. In dynamic update packets, this field is known as "zclass" and refers to the zone's class.
print
$question->print;
Prints the question record on the standard output.
string
print $qr->string, "
";
Returns a string representation of the question record.
data
$qdata = $question->data($packet, $offset);
Returns the question record in binary format suitable for inclusion in a DNS packet.
Arguments are a "Net::DNS::Packet" object and the offset within that packet's data where the "Net::DNS::Question" record is to be stored.
This information is necessary for using compressed domain names.
COPYRIGHT
Copyright (c) 1997-2002 Michael Fuhr.
Portions Copyright (c) 2002-2004 Chris Reinhardt.
Portions Copyright (c) 2003,2006-2009 Dick Franks.
All rights reserved.
This program is free software; you may redistribute it and/or modify it under the same terms as Perl itself.
SEE ALSO
perl(1), Net::DNS, Net::DNS::Resolver, Net::DNS::Packet, Net::DNS::Update, Net::DNS::Header, Net::DNS::RR, RFC 1035 Section 4.1.2
perl v5.12.1 2009-12-30 Net::DNS::Question(3)