Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: What Cinderella did - sorting the bytes
Top Forums Shell Programming and Scripting What Cinderella did - sorting the bytes Post 302148445 by fedusr on Saturday 1st of December 2007 06:28:30 PM
Old 12-01-2007
Quote:
Originally Posted by Perderabo
I think you also need a z to extract it then. You might try that. I rather doubt it will work, but it's easy enough to try.
"Reading compressed archive is even simpler: you don't need to specify any additional options as GNU tar recognizes its format automatically." (GNU tar manual)

Quote:
Originally Posted by Perderabo
Examine the octal dump to find out how the listing is clustered. Is it arranged as lines? Is is always a buffer of exactly 8196 characters? You might be able to develop a workable algorithm with more information.
Allright, that will be my Sunday amusement tomorrow. Again, thank you for your support.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Remove first N bytes and last N bytes from a binary file on AIX.

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. Shell Programming and Scripting

80 bytes per line ???

I am creating ASCII file from Oracle procedure into Unix box. I undertstand there is NO CRLF as I am writing it into one complete string .. but need to know what is best way to format the file with 80bytes per line only before handing over to another program. Thanks in advance regards... (14 Replies)
Discussion started by: u263066
14 Replies

3. UNIX for Dummies Questions & Answers

Files with zero bytes

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

4. Shell Programming and Scripting

Printing bytes

Hi, I have packed fields for which I am trying to print bytes. when I try cut -b2 it does print the 2nd byte besides that it also prints additional byte that I am not aware off:confused: data looks something like this Input: 135 246 when I try cut -b2 it gives me 30 4A but I... (12 Replies)
Discussion started by: ahmedwaseem2000
12 Replies

5. Shell Programming and Scripting

Error PHP Fatal error: Allowed memory size of 67108864 bytes exhausted(tried to allocate 401 bytes)

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

6. Programming

Copying 1024 bytes data in 3-bytes chunk

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

7. UNIX for Dummies Questions & Answers

X bytes of 0, Y bytes of random data, Z bytes of 5, T bytes of 1. ??

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

Shell script - entered input(1-40 bytes) needs to be converted exactly 40 bytes

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. Programming

Best way to axe N bytes from the right?

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

LEARN ABOUT FREEBSD

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)
All times are GMT -4. The time now is 06:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy