07-24-2006
What does no CR-LF mean? Does it also rule out the '\n' character? If it does, then how do you differentiate between lines?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
Does anybody know or guide me on how to remove the first N bytes and the last N bytes from a binary file? Is there any AWK or SED or any command that I can use to achieve this?
Your help is greatly appreciated!!
Best Regards,
Naveen. (1 Reply)
Discussion started by: naveendronavall
1 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
I want to find zero byte files in the given folder for the given day.
I know we can use find . -size 0 -mtime 0
But is there an option for file creation.?
ls -lart | grep ' 0 Apr 24' will also work.
Also is there any alternative using awk ?
I want to know how to use awk in... (1 Reply)
Discussion started by: preethgideon
1 Replies
3. Shell Programming and Scripting
Hi Guyz,
I need to capture first N Bytes from the first line of my file.
Eg. If i have following data in File1
414d51204541495052475731202020204a910846230e420c Hello 3621363663212 Help Required
Then, i want the value of first 48 Bytes to be stored in a variable.
That is, variable... (5 Replies)
Discussion started by: DTechBuddy
5 Replies
4. Shell Programming and Scripting
While running script I am getting an error like
Few lines in data are not being processed.
After googling it I came to know that adding such line would give some memory to it
ini_set("memory_limit","64M");
my input file size is 1 GB.
Is that memory limit is based on RAM we have on... (1 Reply)
Discussion started by: elamurugu
1 Replies
5. Programming
Hi,
If I want to copy a 1024 byte data stream in to the target location in 3-bytes chunk, I guess I can use the following script.
dd bs=1024 count=3 if=/src of=/dest
But, I would like to know, how to do it via a C program. I have tried this with memcpy(), that did not help. (3 Replies)
Discussion started by: royalibrahim
3 Replies
6. Shell Programming and Scripting
Guys,
I want to get the high CPU utilization from top.
I am using below code :
top -d2 >> /home/dba_monitoring/host_top_output.txt
echo "Script started `date`" > $runlog
usage=`grep "^ *$1" /home/dba_monitoring/host_top_output.txt | awk '{print $12}' | sed 's/%//'`
And getting below... (7 Replies)
Discussion started by: wahab
7 Replies
7. UNIX for Dummies Questions & Answers
Hello guys. I really hope someone will help me with this one..
So, I have to write this script who:
- creates a file home/student/vmdisk of 10 mb
- formats that file to ext3
- mounts that partition to /mnt/partition
- creates a file /mnt/partition/data. In this file, there will... (1 Reply)
Discussion started by: razolo13
1 Replies
8. Shell Programming and Scripting
hello,
suppose, entered input is of 1-40 bytes, i need it to be converted to 40 bytes exactly.
example: if i have entered my name anywhere between 1-40 i want it to be stored with 40 bytes exactly.
enter your name:
donald duck (this is of 11 bytes)
expected is as below - display 11... (3 Replies)
Discussion started by: shravan.300
3 Replies
9. Shell Programming and Scripting
is there a better way to do this:
head -c 10000k /var/dump.log | head -c 6000k
unfortunately, the "-c" option is not available on sun solaris. so i'm looking at "dd". but i dont know how to use it to achieve the same exact goal as the above head command.
this needs to work on both solaris... (5 Replies)
Discussion started by: SkySmart
5 Replies
10. Programming
say that i have strings that end in "text"
foo.9.text, bar.10.text, baz.11.text
and i want a C function to chop off the last four characters and replace each string with a '\0'; obviously with error-checking. Any ideas?
TIA! (7 Replies)
Discussion started by: Gary Kline
7 Replies
uuencode(5) File Formats Manual uuencode(5)
NAME
uuencode file format
DESCRIPTION
The command generates files in a format that allows them to be successfully transferred by systems which strip the high bit from an 8-bit
byte. decodes uuencoded files.
The uuencode file format consists of three sections: header, body, and trailer. The header is a line is of the form:
begin 644 "filename.ext"
where "644" is a -format permissions byte for the file and "filename.ext" is the name of the encoded file.
The body section is the encoded representation of the source file. Three bytes of input file data are encoded into four bytes of output
data.
The 24 input bits are divided up into four pieces of six bits each. The integer value 32 (the ASCII value for the space character) is added
to each of these pieces to move them outside of the range of control characters. To avoid using the space character in the encoding, pieces
with value zero are encoded using backquote (ASCII value 96) instead of zero. The resulting character is one of the this set (ASCII values
96,33-95):
A line itself contains three segments: a length character (encoded using the "add a space" algorithm described above), the body of the
line, typically (although not required to be) 60 output characters long, representing 45 input bytes, and (of course) a linefeed. The
length character specifies the number of valid input bytes on the line (so, for a line which is 60 encoded bytes, the length value would be
45). Decoding programs should decode no further than the specified length on a single line.
The trailer, which must exist, consists of a single backquote ("`", ASCII 96) character on a line by itself, directly followed by on a line
by itself.
is the canonical filename extension for uuencoded files.
BUGS
uudecode does not read all permutations of the file format described in this man page.
Ancient versions of uuencode used a space character (ASCII 32) in the encoding to represent zero. Many (arguably broken) mailers and trans-
port agents stripped, rewrapped, or otherwise mangled this format, so the space was later changed to the backquote, ASCII 96. Decoders may
attempt to read the older format if they wish, though it's unlikely to be encountered in practice at this point in time.
The uuencode encoding method is highly ASCII-centric. In particular, the character set used doesn't work well on EBCDIC-based systems.
(EBCDIC, generally used by IBM mainframes, is an old alternative character encoding; most computers use ASCII instead).
Many variants of uuencode on various platforms generate different forms of line checksums, using to represent the checksum one or more
encoded characters after the last counted character in a line. Because these formats are different and impossible to distinguish (with
certainty), such characters should be ignored by decoding implementations.
The uuencode encoding format has no provisions for segmented files. Writers of segmenting utilities should be careful to avoid using char-
acter sequences that may naturally occur in the encoding (such as sequences of dashes ("---")) to divide sections.
SEE ALSO
The MIME Base64 encoding (documented in RFC 2045) is a consistent, cross-platform-savvy message encoding which should be used in place of
UUEncode wherever possible.
The Unix-Hater's Handbook (IDG, 1994) identifies the folly of the older zero-encoded-as-space versions of uuencode.
Apple Computer, Inc. May, 2001 uuencode(5)