This comes up all too often. Windows has text files. Unix does not. Unix is not Windows. In Unix a file is a file is a file. It's a bag of bytes. Period.
Because a standard C string uses ASCII zero (nul character) as the end of string, that data from files that contain nuls (in Windows these are binary files, in Unix they are just files) cannot be parsed as strings because the nuls confuse everything.
To the OP: try
to find out what is in the file. Then you will know if you can read it using standard string C calls like fgets(). Or if you will have to use fread().
After you've programmed for a while you tend to bypass fread and fgets, especially when you're dealing with large files that may contain interesting stuff.
This reads an entire file containing anything into a buffer:
This User Gave Thanks to jim mcnamara For This Post:
Hi,
Please can any one tell me how to convert binary data to text format and vice versa.
If possible give me the algorithm or C program.
Thanks in advance
Waiting for reply
Bye:o (5 Replies)
Hello,
How to i determine via ftp commandline if files on ftp server is ascii or binary files. Like every other comon windows ftp program does it automatically.
regards
Thomas (5 Replies)
Hi
I have a file which has ascii , binary, binary decimal coded,decimal & hexadecimal data with lot of special characters (like öƒ.ƒ.„İİ¡Š·œƒ.„İİ¡Š· ) in it. I want to standardize the file into ASCII format & later use that as source .
Can any one suggest a way a logic to convert such... (5 Replies)
I want to verify the file is Binary or ascii file and accordingly I want to switch the program with ret code
ie 0 or success and 1 for failure
Can any one help me is this a correct syntex...i am getting error
#!/bin/ksh
$file filename
if
echo "ascii fie Found"
else
echo " binary... (6 Replies)
Hi all,
I have been trying to convert a binary file to TEXT/ASCII file in linux/solaries.and commands like string are no good.Also i am not sure how the how output of the file looks like...
I am attaching the binary file as zip since i couldnt load it in its original form in the post incase... (1 Reply)
Hello *nix specialists,
Im working for a non profit organisation in Germany to transport DSL over WLAN to people in areas without no DSL. We are using Linksys WRT 54 router with DD-WRT firmware There are at the moment over 180 router running but we have to change some settings next time. So my... (7 Replies)
what is the diff between ascii and binary file.
my understand is that..
ascii file - has only line feed - \n in it
where as
binary file - has both line feed and carriage return in it- \r\n
is that correct.
also,what is the ksh command to identify whether it is a binary or ascii... (1 Reply)
Hi All,
Need your help!!
I have particular host file with below format:
172.34.45.67 Host1 Host2
134.45.56.67 Host3 Host4 Host5
I need shell script snippet which read this file and change the format of the file to the below format
172.34.45.67 Host1
172.34.45.67 ... (9 Replies)
Hi All,
I have a binary file which is being exported from a Database, and i need to convert that to ASCII format. How can i achieve that? And this solution should work for any file which is given to us; means they will give different files from different tables.
Thanks in advance. (8 Replies)
I need to convert a binary file which in encoded using base32 encoding technique and convert that into readible ASCII so that i can load the same in DB.
is there any command to do the same.
sample from the binary file lools like :
... (18 Replies)
Discussion started by: krk
18 Replies
LEARN ABOUT XFREE86
deb-old
deb-old(5) dpkg suite deb-old(5)NAME
deb-old - old style Debian binary package format
SYNOPSIS
filename.deb
DESCRIPTION
The .deb format is the Debian binary package file format. This manual page describes the old format, used before Debian 0.93. Please see
deb(5) for details of the new format.
FORMAT
The file is two lines of format information as ASCII text, followed by two concatenated gzipped ustar files.
The first line is the format version number padded to 8 digits, and is 0.939000 for all old-format archives.
The second line is a decimal string (without leading zeroes) giving the length of the first gzipped tarfile.
Each of these lines is terminated with a single newline character.
The first tarfile contains the control information, as a series of ordinary files. The file control must be present, as it contains the
core control information.
In some very old archives, the files in the control tarfile may optionally be in a DEBIAN subdirectory. In that case, the DEBIAN
subdirectory will be in the control tarfile too, and the control tarfile will have only files in that directory. Optionally the control
tarfile may contain an entry for '.', that is, the current directory.
The second gzipped tarfile is the filesystem archive, containing pathnames relative to the root directory of the system to be installed on.
The pathnames do not have leading slashes.
SEE ALSO deb(5), dpkg-deb(1), deb-control(5).
1.19.0.5 2018-04-16 deb-old(5)