unrar on MPRAS (UNIX)


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers unrar on MPRAS (UNIX)
# 1  
Old 07-21-2008
unrar on MPRAS (UNIX)

I am wanting to compile unrar on our MPRAS UNIX system. The currently available source (from www.rarlab.com) does not support this system and I am not sure how to configure the makefile to work.

Has anyone been able to get this to work on MPRAS and can supply me with some direction?

Thanks in advance.

Last edited by Mr C; 07-22-2008 at 08:04 PM..
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to install unrar?

I need to extract a ,rar file and getting the below error while using unrar e filename.rar error: ksh: unrar: not found. I guess I need to install unrar. please let me know how to install unrar. my os is - SunOS e08k24 5.10 Generic_141444-09 sun4u sparc SUNW,Sun-Fire-880 (1 Reply)
Discussion started by: lohithsunny
1 Replies

2. Fedora

Problem installing rar and unrar

Good day all, I am trying to install rar and unrar on fedora 16. In terminal root, when I try to do : # cp rar unrar /bin I get the following error message: cp: cannot stat `rar': No such file or directory cp: cannot stat `unrar': No such file or directory can anyone please... (7 Replies)
Discussion started by: peter_071
7 Replies

3. Shell Programming and Scripting

unrar files

Hi, I have two .rar files on unix server. but how to unrar these files ?? (6 Replies)
Discussion started by: milink
6 Replies

4. Shell Programming and Scripting

unrar - get the name of extracted file

If I have a script that is using unrar e file.part1.rar How does the script get the name of the extracted file if I don't know the extension of the file? In my example the name would be file.***, but I wouldn't know the extension. ---------- Post updated at 05:13 PM ---------- Previous... (0 Replies)
Discussion started by: locoroco
0 Replies

5. Solaris

unrar doesn't seem to install properly

Hi, I downloaded unrar from sun-freeware website (unrar-3.68-sol8-sparc-local.gz). After gunzip, I then did: install -c /usr/local unrar-3.68-sol8-sparc-local I'm not sure if that was right. Am I installing it correctly? Hope you can help as I need to open .rar files immediately. ... (4 Replies)
Discussion started by: daytripper1021
4 Replies

6. Shell Programming and Scripting

Simple unrar script

I am not a programer so I need a litle help here. On linux I have installed unrar. What I need is a script which will unrar all rar files in folders and subfolders and subfolders of subfolders, then check this files which are unpacked and then delete this rar files if check is ok. If someone can... (2 Replies)
Discussion started by: blisk
2 Replies

7. UNIX for Dummies Questions & Answers

Mpras

Hi, I want information on MPRAS machines. I dont know anything about that. Please provide more details if possible. thanks in advance. (1 Reply)
Discussion started by: amult
1 Replies

8. UNIX for Dummies Questions & Answers

Unrar Multiple Files with Command

I work with multiple archive files, mostly rar. I understand the basics of rar and zip. I'm looking for a way to decompress multiple rar files with a single command. Hopefully each file would be unrared into dir with same name as archive. I normally just do this manually, but sometimes I'm... (2 Replies)
Discussion started by: dobbs
2 Replies

9. UNIX for Dummies Questions & Answers

malloc returning NULL if freemem high & swapmem low (MPRAS version 3.03 )

Hi All,:) In my application malloc is returning NULL even though there is sufficient amount of free memory available but the swap memory is low. Is this possible that, if free memory is high & swap memory is low, malloc will not be able to allocate memory & return NULL ? Few details: ... (4 Replies)
Discussion started by: Ritesh Kumar
4 Replies

10. UNIX for Advanced & Expert Users

Records mismatch while sorting in MPRAS and SunOS

Hi, As part of migrating a script from SunOS to MP RAS, the following script is not functioning in desired way. sort -t\| -u +6 -7 +12 -14 textfile1.out > \ textfile2uniq.out The -u is fetching unique records differently on SunOS and MP RAS Pentium IV. And thus the records... (1 Reply)
Discussion started by: RRVARMA
1 Replies
Login or Register to Ask a Question
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