The definition of how file decides on filetype is:
from man file, q.v.
One could create one's own file command and add the GS control character as an exception -- I have not done it, but I think the file magic could be so changed. Otherwise, one could replace the GS (say with sed) to something innocuous before feeding the resulting copy of the data file to the file commend.
Hi All
I am simulating a problem in the production where i faced a situation.
Please find the following example program which i simulated.
#include<stdio.h>
#include<stdlib.h>
#include<string.h>
int main()
{
char str1; (3 Replies)
i have no idea abount shell script but i need need shell script to get last 10 char from a file name and write in to a new file.
consider u hav 5 files in a particular dir i script should get last 10 char of each file n write the 10 char in separate files (2 Replies)
I've this file and need to sort the data in each group
File would look like this ...
cat file1.txt
Reason : ABC
12345-0023
32123-5400
32442-5333
Reason : DEF
42523-3453
23345-3311
Reason : HIJ
454553-0001
I would like to sort each group on the last 4 fileds and print them... (11 Replies)
Hi all,
I'm reading a file with this layout:
First_Col Second_Col
The Second_Col has values as 1000, -1, 10, 43...
While reading the file I'm getting the second column value with awk command, but it is including the CR control char.
do
item_saved=`echo $b | awk '{print... (4 Replies)
hi
I have the below code to convert hexa to binary. It is working fine, but i want to store the binary in char or int. The below program is printing the result.
void ConvertHexToBinary(char sHexValue)
{
int i;
printf("Binary Equivalent=");
for(i=0;sHexValue!=NULL;i++)
{
... (1 Reply)
Hi
I am using sed command to make SCORE=somevalue to SCORE=blank in a file.
Please see the attached lastline.txt file. After executing the below command on the file, it removes the last line.
cat lastline.txt | sed 's/SCORE=.*$/SCORE=/g' > newfile.txt
Why does sed command remove the... (3 Replies)
I am trying to add a unique identifier to two file extensions .bam and .vcf in a directory located at /home/cmccabe/Desktop/index/R_2016_09_21_14_01_15_user_S5-00580-9-Medexome.
The identifier is in $2 of the input file. What the code below is attempting to do is strip off the last portion... (21 Replies)
Unix File is pipe delimited with 17 fields. We may get extra pipes in data also.
We may get \n char (1 or more \n in one field or multi fileds) in data in any field.
Need to replace \n true ( line separator) with 'space and bell char space' chars (' \a ') Not data \n.
Input:... (1 Reply)
Discussion started by: rajeshkumare
1 Replies
LEARN ABOUT PLAN9
deb
deb(5) dpkg suite deb(5)NAME
deb - Debian binary package format
SYNOPSIS
filename.deb
DESCRIPTION
The .deb format is the Debian binary package file format. It is understood since dpkg 0.93.76, and is generated by default since dpkg 1.2.0
and 1.1.1elf (i386/ELF builds).
The format described here is used since Debian 0.93; details of the old format are described in deb-old(5).
FORMAT
The file is an ar archive with a magic value of !<arch>. Only the common ar archive format is supported, with no long file name
extensions, but with file names containing an optional trailing slash, which limits their length to 15 characters (from the 16 allowed).
File sizes are limited to 10 ASCII decimal digits, allowing for up to approximately 9536.74 MiB member files.
The tar archives currently allowed are, the old-style (v7) format, the pre-POSIX ustar format, a subset of the GNU format (new style long
pathnames and long linknames, supported since dpkg 1.4.1.17; large file metadata since dpkg 1.18.24), and the POSIX ustar format (long
names supported since dpkg 1.15.0). Unrecognized tar typeflags are considered an error. Each tar entry size inside a tar archive is
limited to 11 ASCII octal digits, allowing for up to 8 GiB tar entries. The GNU large file metadata support permits 95-bit tar entry sizes
and negative timestamps, and 63-bit UID, GID and device numbers.
The first member is named debian-binary and contains a series of lines, separated by newlines. Currently only one line is present, the
format version number, 2.0 at the time this manual page was written. Programs which read new-format archives should be prepared for the
minor number to be increased and new lines to be present, and should ignore these if this is the case.
If the major number has changed, an incompatible change has been made and the program should stop. If it has not, then the program should
be able to safely continue, unless it encounters an unexpected member in the archive (except at the end), as described below.
The second required member is named control.tar. It is a tar archive containing the package control information, either not compressed
(supported since dpkg 1.17.6), or compressed with gzip (with .gz extension), xz (with .xz extension, supported since 1.17.6) or zstd (with
.zst extension, supported since 1.19.0.5ubuntu2), as a series of plain files, of which the file control is mandatory and contains the core
control information, the conffiles, triggers, shlibs and symbols files contain optional control information, and the preinst, postinst,
prerm and postrm files are optional maintainer scripts. The control tarball may optionally contain an entry for '.', the current
directory.
The third, last required member is named data.tar. It contains the filesystem as a tar archive, either not compressed (supported since
dpkg 1.10.24), or compressed with gzip (with .gz extension), xz (with .xz extension, supported since dpkg 1.15.6), zstd (with .zst
extension, supported since 1.19.0.5ubuntu2), bzip2 (with .bz2 extension, supported since dpkg 1.10.24) or lzma (with .lzma extension,
supported since dpkg 1.13.25).
These members must occur in this exact order. Current implementations should ignore any additional members after data.tar. Further members
may be defined in the future, and (if possible) will be placed after these three. Any additional members that may need to be inserted after
debian-binary and before control.tar or data.tar and which should be safely ignored by older programs, will have names starting with an
underscore, '_'.
Those new members which won't be able to be safely ignored will be inserted before data.tar with names starting with something other than
underscores, or will (more likely) cause the major version number to be increased.
MEDIA TYPE
Current
application/vnd.debian.binary-package
Deprecated
application/x-debian-package
application/x-deb
SEE ALSO deb-old(5), dpkg-deb(1), deb-control(5), deb-conffiles(5)deb-triggers(5), deb-shlibs(5), deb-symbols(5), deb-preinst(5), deb-postinst(5),
deb-prerm(5), deb-postrm(5).
1.19.0.5 2018-04-16 deb(5)