Sponsored Content
Full Discussion: large files in 32 bits?
Top Forums UNIX for Advanced & Expert Users large files in 32 bits? Post 23784 by Perderabo on Friday 28th of June 2002 10:55:15 PM
Old 06-28-2002
You can't. You need 64 bit mode for large files. Remember that there is a pointer to the next byte to be read. If this is a 32 bit entity, it just won't work. You gotta fix or replace that library. Or live with small files.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Changing 24 bits to 8 bits display

Hello all, I was wondering if anyone can tell me how to change 24 bits depth display to 8 bits depth display for Sun Ultra1, running Solaris 8? THANKS in advance. I think that the command is ffbconfig, but it has nothing about depth. (4 Replies)
Discussion started by: larry
4 Replies

2. UNIX for Dummies Questions & Answers

Large files

I am trying to understand the webserver log file for an error which has occured on my live web site. The webserver access file is very big in size so it's not possible to open this file using vi editor. I know the approximate time the error occured, so i am interested in looking for the log file... (4 Replies)
Discussion started by: sehgalniraj
4 Replies

3. UNIX for Dummies Questions & Answers

large files?

How do we check 'large files' is enabled on a Unix box -- HP-UX B11.11 (2 Replies)
Discussion started by: ranj@chn
2 Replies

4. AIX

How to convert a partition usin 64 bits kernel to 32 bits kernel?

Hello there: I know that exist a procedure to convert an OS using 32bits kernel to 64 bits kernel. But, exist a procedure to convert an OS using 64bits to 32 bits kernel? Please help me. Regards. (2 Replies)
Discussion started by: GEIER
2 Replies

5. UNIX for Dummies Questions & Answers

32 bits procesaor with 64 bits Solaris

people i have a problem i have a 32 bits sparc processor, and solaris 64 bits processor, i install a oracle data base 64 bits, but my oracle will not run because my processor is from 32 bits this is ok??, i know if i have x86 i cannot install a 64 bits operatin system in a 32 bits processor. ... (0 Replies)
Discussion started by: enkei17
0 Replies

6. Shell Programming and Scripting

Divide large data files into smaller files

Hello everyone! I have 2 types of files in the following format: 1) *.fa >1234 ...some text... >2345 ...some text... >3456 ...some text... . . . . 2) *.info >1234 (7 Replies)
Discussion started by: ad23
7 Replies

7. Solaris

How to safely copy full filesystems with large files (10Gb files)

Hello everyone. Need some help copying a filesystem. The situation is this: I have an oracle DB mounted on /u01 and need to copy it to /u02. /u01 is 500 Gb and /u02 is 300 Gb. The size used on /u01 is 187 Gb. This is running on solaris 9 and both filesystems are UFS. I have tried to do it using:... (14 Replies)
Discussion started by: dragonov7
14 Replies

8. What is on Your Mind?

Place Bits & Win Bits!!! - 17th Annual Satellite Awards

Ten movies have been nominated as best motion picture by the International Press Academy, presentation of the 2012 Satellite Awards will be held on 16th December at Los Angeles, CA. Place your bits here on one of the below nominated movie of your choice:- Argo ... (0 Replies)
Discussion started by: Yoda
0 Replies
compress(1)						      General Commands Manual						       compress(1)

Name
       compress, uncompress, zcat - compress and expand data

Syntax
       compress [ -f ] [ -v ] [ -c ] [ -b bits ] [ name ...  ]
       uncompress [ -f ] [ -v ] [ -c ] [ name ...  ]
       zcat [ name ...	]

Description
       The  command reduces the size of the named files using adaptive Lempel-Ziv coding.  Whenever possible, each file is replaced by one
       with the extension .Z, while keeping the same ownership modes, access, and modification times.  If  no  files  are  specified,  the
       standard input is compressed to the standard output.  Compressed files can be restored to their original form using or

       The  -f	option	will  force  compression  of  name, even if it does not actually shrink name, or if the corresponding name .Z file
       already exists.	If the -f option is omitted, the user is asked whether an existing name.Z file should be  overwritten  (unless	is
       run in the background under

       The -c (cat) option makes compress/uncompress write to the standard output without changing any files.  Neither -c nor alter files.

       The  command  uses  the modified Lempel-Ziv algorithm.  Common substrings in the file are first replaced by 9-bit codes 257 and up.
       When code 512 is reached, the algorithm switches to 10-bit codes and continues to use more bits until the limit specified by the -b
       flag is reached (default 16).  The bits must be between 9 and 16.  The default can be changed in the source to allow to be run on a
       smaller machine.

       After the bits limit is attained, periodically checks the compression ratio.  If the ratio is  increasing,  continues  to  use  the
       existing  code  dictionary.   However,  if  the	compression ratio decreases, discards the table of substrings and rebuilds it from
       scratch.  This allows the algorithm to adapt to the next block of the file.

       Note that the -b flag is omitted for since the bits parameter specified during compression is encoded within the output along  with
       a number that ensures that neither decompression of random data nor recompression of compressed data is attempted.

       How much each file is compressed depends on the size of the input, the number of bits per code, and the distribution of common sub-
       strings.  Typically, text such as source code or English is reduced by 50-60%.  Compression is  generally  much	better	than  that
       achieved by Huffman coding or adaptive Huffman coding, and takes less time to compute.

       The -v option displays the percent reduction of each file.

       If  an  error  occurs,  exit  status is 1.  However, if the last file was not compressed because it became larger, the status is 2.
       Otherwise, the status is 0.

Options
       -f   Forces compression of name.

       -c   Makes compress/uncompress write to the standard output.

       -b   Specifies the allowable bits limit.  The default is 16.

       -v   Displays the percent reduction of each file.

Diagnostics
       Usage: compress [-fvc] [-b maxbits] [file ...]
       Invalid options were specified on the command line.

       Missing maxbits
       Maxbits must follow -b.

       file: not in compressed format
       The file specified to uncompress has not been compressed.

       file: compressed with xx bits, can only handle yy bits
       The file was compressed by a program that could deal with more bits than the compress code on this machine.   Recompress  the  file
       with smaller bits.

       file: already has .Z suffix -- no change
       The file is assumed to be compressed already.  Rename the file and try again.

       file already exists; do you wish to overwrite (y or n)?
       Type y if you want the output file to be replaced; type n if you do not.

       uncompress: corrupt input
       A SIGSEGV violation was detected which usually means that the input file is corrupted.

       Compression: xx.xx%
       Percent of the input saved by compression.  (For the -v option only.)

       -- not a regular file: unchanged
       If the input file is not a regular file (for example, a directory), it remains unchanged.

       -- has xx other links: unchanged
       The input file has links; it is left unchanged.	See for more information.

       -- file unchanged
       No savings is achieved by compression.  The input remains unchanged.

Restrictions
       Although compressed files are compatible between machines with large memory, -b12 should be used for file transfer to architectures
       with a small process data space (64KB or less).

								       RISC							       compress(1)
All times are GMT -4. The time now is 03:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy