02-20-2002
Almost all the unix variants are compatible and suits for the 3D rendering and 3D Animation. All depends on the user how to make use of it. You may try one of it depends on your H/Ware requirement.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Okee problems...!!
What is happening: Unix server with some programms, workstations are windows 2000, the workstations work good but when you start a programm on the Unix server the CPU of the workstations go to 100% usage resulting that the system gets very slow. The programm well its running so... (2 Replies)
Discussion started by: zerocool
2 Replies
2. What is on Your Mind?
What are the different flavors of Linux? (1 Reply)
Discussion started by: SubbaraoV
1 Replies
3. UNIX for Dummies Questions & Answers
could anybody tell me what is a unix flavor? (4 Replies)
Discussion started by: human
4 Replies
4. Shell Programming and Scripting
Hi ,
I need to run a script on different flavors, namely
1) Linux
2) AIX
3) Solaris
4) HP-UX
Almost the entire script is the same except at a few places where commands specific to that OS are to be run. Is it possible to have a single script that runs on all the platforms?
Sth... (5 Replies)
Discussion started by: tcsprak
5 Replies
5. UNIX for Dummies Questions & Answers
How does unix system administration, unix programming, unix network programming differ?
Please help. (0 Replies)
Discussion started by: thulasidharan2k
0 Replies
6. Shell Programming and Scripting
Hello - Is there a command/way we can find out, what shells are supported on a Unix machine?
Please let me know.
Thanks,
Manju (3 Replies)
Discussion started by: manju--
3 Replies
7. UNIX for Dummies Questions & Answers
Hello everyone. This is an awesome forum. Glad to have joined! :)
I use Linux mostly, even for Desktop usage. I just love everything about it, all the way down to how the font looks while browsing. Its just so sleek and sexy.
But I also boot Windows for those programs I just need that only... (23 Replies)
Discussion started by: insomnia
23 Replies
8. Shell Programming and Scripting
Hello All,
I am in process of migrating all my scripts from AIX box to Linux box. In one of my script I calculate my last week date with the below command
$ TZ=EDT+172 date +%F
2012-12-13
$ uname -a
AIX 1 7 000B29AAD400
Now when I tried running the same in Linux, it gives a false... (2 Replies)
Discussion started by: sathyaonnuix
2 Replies
9. Shell Programming and Scripting
Dear All,
Can someone help to command or program to transfer the file from windows to Unix server and from one unix server to another Unix server in secure way.
I would request no samba client. (4 Replies)
Discussion started by: yadavricky
4 Replies
LEARN ABOUT OPENDARWIN
unix
UNIX(4) BSD Kernel Interfaces Manual UNIX(4)
NAME
unix -- UNIX-domain protocol family
SYNOPSIS
#include <sys/types.h>
#include <sys/un.h>
DESCRIPTION
The UNIX-domain protocol family is a collection of protocols that provides local (on-machine) interprocess communication through the normal
socket(2) mechanisms. The UNIX-domain family supports the SOCK_STREAM and SOCK_DGRAM socket types and uses filesystem pathnames for address-
ing.
ADDRESSING
UNIX-domain addresses are variable-length filesystem pathnames of at most 104 characters. The include file <sys/un.h> defines this address:
struct sockaddr_un {
u_char sun_len;
u_char sun_family;
char sun_path[104];
};
Binding a name to a UNIX-domain socket with bind(2) causes a socket file to be created in the filesystem. This file is not removed when the
socket is closed--unlink(2) must be used to remove the file.
The UNIX-domain protocol family does not support broadcast addressing or any form of ``wildcard'' matching on incoming messages. All
addresses are absolute- or relative-pathnames of other UNIX-domain sockets. Normal filesystem access-control mechanisms are also applied
when referencing pathnames; e.g., the destination of a connect(2) or sendto(2) must be writable.
PROTOCOLS
The UNIX-domain protocol family is comprised of simple transport protocols that support the SOCK_STREAM and SOCK_DGRAM abstractions.
SOCK_STREAM sockets also support the communication of UNIX file descriptors through the use of the msg_control field in the msg argument to
sendmsg(2) and recvmsg(2).
Any valid descriptor may be sent in a message. The file descriptor(s) to be passed are described using a struct cmsghdr that is defined in
the include file <sys/socket.h>. The type of the message is SCM_RIGHTS, and the data portion of the messages is an array of integers repre-
senting the file descriptors to be passed. The number of descriptors being passed is defined by the length field of the message; the length
field is the sum of the size of the header plus the size of the array of file descriptors.
The received descriptor is a duplicate of the sender's descriptor, as if it were created with a call to dup(2). Per-process descriptor
flags, set with fcntl(2), are not passed to a receiver. Descriptors that are awaiting delivery, or that are purposely not received, are
automatically closed by the system when the destination socket is closed.
SEE ALSO
socket(2), intro(4)
"An Introductory 4.3 BSD Interprocess Communication Tutorial", PS1, 7.
"An Advanced 4.3 BSD Interprocess Communication Tutorial", PS1, 8.
BSD
June 9, 1993 BSD