10 More Discussions You Might Find Interesting
1. Solaris
Hi
sorry for the novice question.
i need to install Solaris 10 32bit version.
i downloaded the ISO from oracle website.
as i understand the same ISO is for the 64bit as well as the 32bit install???
i ran the install and didn't have the option to choose which architecture to choose?
Thanks... (9 Replies)
Discussion started by: guy3145
9 Replies
2. UNIX for Advanced & Expert Users
Hi all,
So, I have a 32 bit gtk2.22 application that I run flawlessly in Fedora 14.
When I compile it on the 32bit machine run it on Fedora 20 64bit machine I get:
(myprogram:6736): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
(myprogram.:6736): Gtk-WARNING **:... (15 Replies)
Discussion started by: fedora18
15 Replies
3. SuSE
Hello, I am trying to use a worktool on SLES 10 (32-bit) and it is saying I do not have libcap.so.2:
error while loading shared libraries: libcap.so.2: cannot open shared object file: No such file or directory
Is there an easy way for me to install this library? A quick Google search... (4 Replies)
Discussion started by: bstring
4 Replies
4. Solaris
Hi Gurus,
I need to check whether the compiler installed in my system supports 64bit compilation.
Server - Sun fire v490
OS - Solaris 5.9
Processor - Sparcv9 (64bit)
Install Directory - /opt/SUNWSpro
Compiler Model - Sun Forte C Compiler.
My development team is claiming that there... (20 Replies)
Discussion started by: Hari_Ganesh
20 Replies
5. Solaris
Not really a Unix question as such :o, but what advantages or disadvantages are there between using 32bit or 64bit applications on a T5220 running Solaris 10? What about mixing them e.g. 64 bit app using 32 bit libraries or vice versa? (1 Reply)
Discussion started by: JerryHone
1 Replies
6. Programming
Is there an 'easy' way to convert 32Bit code to 64Bit code. I have this benchmark i need to run on different machines and it would be nice if i could run it on the 64 bit machines ass wel.
The output when compiling(1) and running(2) are the following:
(1)
linux:/home/user1/subbench/heapsort #... (7 Replies)
Discussion started by: demuynckr
7 Replies
7. Linux
Hi,
I want to know what is command to know which will tell wheather linux is 32 or 64 bit (5 Replies)
Discussion started by: manoj.solaris
5 Replies
8. UNIX for Dummies Questions & Answers
when using the command :
cat /proc/cpuinfo I get some basic info back on the cpu..
but it doesn't tell me if I am using a 64 or 32 bit processor ..
a) is this the right command to find this ?
b) if it is not what is ? and how do I get that information..
thanx moxxx68 (2 Replies)
Discussion started by: moxxx68
2 Replies
9. UNIX for Dummies Questions & Answers
Whats the difference between 32bit and 64bit OS's or applications. I understand it a little but its just not clicking the way the teacher explained to me
thanks, any info would be much appreciated (1 Reply)
Discussion started by: eloquent99
1 Replies
10. UNIX for Dummies Questions & Answers
Hi
Any one know how to change solaris 7 from 64 bit, back to 32 bit,,
i know its on sunsolve somewhere but i cant see it.
thanks:D (2 Replies)
Discussion started by: thangorn
2 Replies
IPL(4) Kernel Interfaces Manual IPL(4)
NAME
ipl - IP packet log device
DESCRIPTION
The ipl pseudo device's purpose is to provide an easy way to gather packet headers of packets you wish to log. If a packet header is to be
logged, the entire header is logged (including any IP options - TCP/UDP options are not included when it calculates header size) or not at
all. The packet contents is also logged after the header.
Prepending every packet header logged is a structure containing information relevant to the packet following and why it was logged. The
structure's format is as follows:
struct ipl_ci {
u_long sec; /* time when the packet was logged */
u_long usec;
u_long plen; /* length of packet data logged */
u_short hlen; /* length of headers logged */
u_short rule; /* rule number (for log ...) or 0 if result = log */
u_long flags:24; /* XXX FIXME do we care about the extra bytes? */
#if (defined(OpenBSD) && (OpenBSD <= 1991011) && (OpenBSD >= 199606))
u_long filler:8; /* XXX FIXME do we care? */
u_char ifname[IFNAMSIZ];
#else
u_long unit:8;
u_char ifname[4];
#endif
};
In the case of the header causing the buffer to finish on a non-32bit
boundary, padding will be `appended' to ensure that the next log entry
is aligned to a 32bit boundary.
If the packet contents is more then 128 bytes, then only 128 bytes of the
packet contents is logged. Should the packet contents finish on a non-32bit
boundary, then the last few bytes are not logged to ensure the log entry
is aligned to a 32bit boundary.
ipl is a read-only (sequential) character pseudo-device.
The ioctls which are loaded with this device can be found under ipf(4).
The only ioctl which is used for logging and doesn't affect the filter is:
ioctl(fd, SIOCIPFFB, int *)
This ioctl flushes the log buffer and returns the number of bytes flushed.
There is currently no support for non-blocking IO with this device, meaning all read operations should be considered blocking in nature (if
there is no data to read, it will sleep until some is made available).
SEE ALSO
ipf(4)
BUGS
Packet headers are dropped when the internal buffer (static size) fills.
FILES
/dev/ipl0
IPL(4)