• Re: Zip list

    From 25B.R866@21:1/5 to Bobbie Sellers on Sat Feb 18 03:59:16 2023
    On 2/16/23 11:12 AM, Bobbie Sellers wrote:
    On 2/16/23 07:57, db wrote:
    This might be the wrong ng but anyway...
    I refer to using typed commands in Linux.
    With tar, I can use the option -t to get a list of a
    tarred file's contents.
    I can't however find such an option for zip, so I have
    to go into GUI and click on the zip file to see the contents.
    Am I missing that option,  or isn't there one?

    Oh there is one but the option is -h ands you can see the result.


    [bliss@box ~]$ zip -h
    Copyright (c) 1990-2008 Info-ZIP - Type 'zip "-L"' for software license.
    Zip 3.0 (July 5th 2008). Usage:
    zip [-options] [-b path] [-t mmddyyyy] [-n suffixes] [zipfile list] [-xi list]
      The default action is to add or replace zipfile entries from list, which
      can include the special name - to compress standard input.
      If zipfile and list are omitted, zip compresses stdin to stdout.
      -f   freshen: only changed files  -u   update: only changed or new files
      -d   delete entries in zipfile    -m   move into zipfile (delete OS
    files)
      -r   recurse into directories     -j   junk (don't record) directory
    names
      -0   store only                   -l   convert LF to CR LF (-ll CR LF
    to LF)
      -1   compress faster              -9   compress better
      -q   quiet operation              -v   verbose operation/print
    version info
      -c   add one-line comments        -z   add zipfile comment
      -@   read names from stdin        -o   make zipfile as old as latest
    entry
      -x   exclude the following names  -i   include only the following names
      -F   fix zipfile (-FF try harder) -D   do not add directory entries
      -A   adjust self-extracting exe   -J   junk zipfile prefix (unzipsfx)
      -T   test zipfile integrity       -X   eXclude eXtra file attributes
      -y   store symbolic links as the link instead of the referenced file
      -e   encrypt                      -n   don't compress these suffixes
      -h2  show more help

        The -h option is short for help.  No doubt an artifact
    of the English language dominance in early computer development.


    7-zip is better than old-fashioned zip and ALMOST as
    portable these days. You can easily get 7-zip for
    linux and Winders.

    If you're into Python you can use one of its ZIP
    libraries to create/fill a zip file. First you
    create the 'container', the zip file, then you
    stuff files into it.

    Note that "real" zips MAY have size limitations -
    used to be about 2gb though the more recent versions
    seem to be able to do more. 7-zips can be as big
    as your disk is. Same goes for the linux-centric
    ".gz" and ".bz" files. Winders DOES have an easy
    ".gz" utility ... next to pure old-fashioned zips
    I'd say they're the "most portable".

    ".tar.gz" seems to still be very popular for
    mass storage. The '.tar' (it used to mean
    "tape archive"), just mashes files into one
    file ... and the ".gz" tries to compress the
    whole thing. This is NOT very efficient with
    binary or especially encrypted files though
    since they look like "binary white noise" and
    the zipping algo's can't DO much with that
    kind of data. If you are gonna try to compress
    those, do it FIRST - before encryption/zipping.
    Backups are one of My Things and I make a LOT
    of those kinds of files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From The Natural Philosopher@21:1/5 to Charlie Gibbs on Sat Feb 18 10:12:13 2023
    On 17/02/2023 19:32, Charlie Gibbs wrote:
    I was becoming so tired of the proliferation of file archiving
    formats (ARC, ZOO, ARJ, etc.) that I was relieved to see the
    world finally settle on ZIP as a standard archiving format.
    (Uh-oh, here comes 7Zip...)

    And this is all separate from the Unix world, which had
    tar, cpio, gzip...

    RAR was my pet hate...

    --
    Climate is what you expect but weather is what you get.
    Mark Twain

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to The Natural Philosopher on Sat Feb 18 12:43:42 2023
    On 2023-02-18 11:12, The Natural Philosopher wrote:
    On 17/02/2023 19:32, Charlie Gibbs wrote:
    I was becoming so tired of the proliferation of file archiving
    formats (ARC, ZOO, ARJ, etc.) that I was relieved to see the
    world finally settle on ZIP as a standard archiving format.
    (Uh-oh, here comes 7Zip...)

    And this is all separate from the Unix world, which had
    tar, cpio, gzip...

    RAR was my pet hate...


    Why? :-? :-o

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From The Natural Philosopher@21:1/5 to Carlos E.R. on Sat Feb 18 13:15:31 2023
    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:
    On 17/02/2023 19:32, Charlie Gibbs wrote:
    I was becoming so tired of the proliferation of file archiving
    formats (ARC, ZOO, ARJ, etc.) that I was relieved to see the
    world finally settle on ZIP as a standard archiving format.
    (Uh-oh, here comes 7Zip...)

    And this is all separate from the Unix world, which had
    tar, cpio, gzip...

    RAR was my pet hate...


    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    --
    If I had all the money I've spent on drink...
    ..I'd spend it on drink.

    Sir Henry (at Rawlinson's End)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Robert Heller@21:1/5 to tnp@invalid.invalid on Sat Feb 18 14:46:56 2023
    At Sat, 18 Feb 2023 13:15:31 +0000 The Natural Philosopher <tnp@invalid.invalid> wrote:


    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:
    On 17/02/2023 19:32, Charlie Gibbs wrote:
    I was becoming so tired of the proliferation of file archiving
    formats (ARC, ZOO, ARJ, etc.) that I was relieved to see the
    world finally settle on ZIP as a standard archiving format.
    (Uh-oh, here comes 7Zip...)

    And this is all separate from the Unix world, which had
    tar, cpio, gzip...

    RAR was my pet hate...


    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    Like zip, rar came from outside the UNIX world, so there is unrar.



    --
    Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
    Deepwoods Software -- Custom Software Services
    http://www.deepsoft.com/ -- Linux Administration Services
    heller@deepsoft.com -- Webhosting Services

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to The Natural Philosopher on Sat Feb 18 17:39:26 2023
    On 2023-02-18 14:15, The Natural Philosopher wrote:
    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:
    On 17/02/2023 19:32, Charlie Gibbs wrote:
    I was becoming so tired of the proliferation of file archiving
    formats (ARC, ZOO, ARJ, etc.) that I was relieved to see the
    world finally settle on ZIP as a standard archiving format.
    (Uh-oh, here comes 7Zip...)

    And this is all separate from the Unix world, which had
    tar, cpio, gzip...

    RAR was my pet hate...


    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    :-O


    unrar.

    Unix, or Linux?


    cer@Telcontar:~> whatis unrar
    unrar (1) - extract, test, and view RAR archives
    cer@Telcontar:~> rpm -qi unrar
    Name : unrar
    Version : 6.1.6
    Release : lp154.1.1
    Architecture: x86_64
    Install Date: 2022-11-29T21:26:35 CET
    Group : Productivity/Archiving/Compression
    Size : 315707
    License : NonFree
    Signature : RSA/SHA256, 2022-05-11T13:38:46 CEST, Key ID b88b2fd43dbdc284 Source RPM : unrar-6.1.6-lp154.1.1.src.rpm
    Build Date : 2022-05-11T13:38:41 CEST
    Build Host : sheep85
    Relocations : (not relocatable)
    Packager : https://bugs.opensuse.org
    Vendor : openSUSE
    URL : https://www.rarlab.com
    Summary : A program to extract, test, and view RAR archives
    Description :
    The unRAR utility is a freeware program distributed with source code
    and developed for extracting, testing, and viewing the contents of
    archives created with the RAR archiver.
    Distribution: openSUSE:Leap:15.4:NonFree
    cer@Telcontar:~>


    This is built, I understand, from the published sources. There is no
    equivalent "rar" that is free to use. However, for openSUSE, we can get
    "rar" from the packman external repository.



    Notice the difference in the versions reported:


    cer@Telcontar:~> unrar -v

    UNRAR 6.11 freeware Copyright (c) 1993-2022 Alexander Roshal

    Usage: unrar <command> -<switch 1> -<switch N> <archive> <files...>
    <@listfiles...> <path_to_extract\>

    <Commands>
    e Extract files without archived paths
    ...
    y Assume Yes on all queries
    cer@Telcontar:~>




    cer@Telcontar:~> rar -v

    RAR 6.02 Copyright (c) 1993-2021 Alexander Roshal 11 Jun 2021
    Trial version Type 'rar -?' for help

    Usage: rar <command> -<switch 1> -<switch N> <archive> <files...>
    <@listfiles...> <path_to_extract\>

    <Commands>
    a Add files to archive
    c Add archive comment
    ch Change archive parameters
    ...
    cer@Telcontar:~>





    The only problem with using "rar" in Linux is that it doesn't support
    Linux filesystem attributes and permissions :-(





    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Eric Pozharski@21:1/5 to Charlie Gibbs on Sat Feb 18 14:55:44 2023
    with <vDQHL.690236$Tcw8.307288@fx10.iad> Charlie Gibbs wrote:
    On 2023-02-17, Carlos E. R. <robin_listas@es.invalid> wrote:
    On 2023-02-17 17:28, Robert Heller wrote:

    Zip / Unzip have a bit of a history and came from outside of the
    UNIX world (they originated in the MS-DOS world). I suspect that due
    to MS-DOS memory / disk limitations the *original* programs for Zip
    files had to be limited to single functions (just building the zip
    file, just extracting, just listing, etc.). Along with a different
    philosophy about how to organize software.
    Er... that's not my remembrance. I recall a single program, called
    "pkzip". Maybe there was an older zip/unzip, but what we used before
    pkzip was another format, arc.
    I recall there being two separate programs, PKZIP.EXE and PKUNZIP.EXE.
    In fact, I just dug around on my system and found them both. They're
    dated 1993-02-01.
    <https://en.wikipedia.org/wiki/PKZIP>
    Note that the label on the floppy disk in the photo mentions both
    PKZIP and PKUNZIP.

    I cast doubts on memory constraints (think about it, makes no sense).
    What The Industry had settled for was: fully functional executable with restrictive license (with or without un-archiver functionality) and
    freeware un-archiver.

    *CUT*

    p.s. I was huge fan of arj back then. It's all history now anyway.

    --
    Torvalds' goal for Linux is very simple: World Domination
    Stallman's goal for GNU is even simpler: Freedom

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Kohlbach@21:1/5 to The Natural Philosopher on Sat Feb 18 16:17:50 2023
    On Sat, 18 Feb 2023 10:12:13 +0000, The Natural Philosopher wrote:

    On 17/02/2023 19:32, Charlie Gibbs wrote:
    I was becoming so tired of the proliferation of file archiving
    formats (ARC, ZOO, ARJ, etc.) that I was relieved to see the
    world finally settle on ZIP as a standard archiving format.
    (Uh-oh, here comes 7Zip...)
    And this is all separate from the Unix world, which had
    tar, cpio, gzip...

    RAR was my pet hate...

    Try lha. ;-)
    --
    Andreas

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Kohlbach@21:1/5 to The Natural Philosopher on Sat Feb 18 16:18:51 2023
    On Sat, 18 Feb 2023 13:15:31 +0000, The Natural Philosopher wrote:

    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:

    RAR was my pet hate...

    Why? :-? :-o

    Could never find an unpacking program that ran on Unix.

    unrar x file.rar

    should deflate the content into the PWD.
    --
    Andreas

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Kohlbach@21:1/5 to All on Sat Feb 18 16:16:21 2023
    On Sat, 18 Feb 2023 03:59:16 -0500, 25B.R866 wrote:

    7-zip is better than old-fashioned zip and ALMOST as
    portable these days. You can easily get 7-zip for
    linux and Winders.

    Possible.

    But I notice some people send me a file with a ZIP extension. Often
    turns out it's 7-zip, so "unzip" fails. I have 7z installed though and it works. Would be nice though if (un)zip not just fails in these cases, but
    uses 7z then. Otherwise I have to let 7z do it.
    --
    Andreas

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25B.R866@21:1/5 to Andreas Kohlbach on Sat Feb 18 21:40:19 2023
    On 2/18/23 4:16 PM, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 03:59:16 -0500, 25B.R866 wrote:

    7-zip is better than old-fashioned zip and ALMOST as
    portable these days. You can easily get 7-zip for
    linux and Winders.

    Possible.

    But I notice some people send me a file with a ZIP extension. Often
    turns out it's 7-zip, so "unzip" fails. I have 7z installed though and it works. Would be nice though if (un)zip not just fails in these cases, but uses 7z then. Otherwise I have to let 7z do it.

    PROPERLY, you use the ".7z" extension when making
    zips with p7. Not everybody does that however.

    It IS a good, efficient and versatile compression
    utility. IMHO it should replace olde-tyme .zip
    but I know it won't.

    I haven't even tried with Win-11 yet ... does it
    recognize, and properly handle, .tar.gz/.tar.bz2 ???
    They kind of sneaked in support for common -ix
    archive/compression schemes over the years.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From The Natural Philosopher@21:1/5 to Andreas Kohlbach on Sun Feb 19 11:13:01 2023
    On 18/02/2023 21:18, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 13:15:31 +0000, The Natural Philosopher wrote:

    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:

    RAR was my pet hate...

    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    unrar x file.rar

    should deflate the content into the PWD.

    Today yes, not in 1993, to run on SCO Unix.


    --
    "In our post-modern world, climate science is not powerful because it is
    true: it is true because it is powerful."

    Lucas Bergkamp

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From The Natural Philosopher@21:1/5 to Carlos E.R. on Sun Feb 19 11:10:20 2023
    On 18/02/2023 16:39, Carlos E.R. wrote:
    On 2023-02-18 14:15, The Natural Philosopher wrote:
    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:
    On 17/02/2023 19:32, Charlie Gibbs wrote:
    I was becoming so tired of the proliferation of file archiving
    formats (ARC, ZOO, ARJ, etc.) that I was relieved to see the
    world finally settle on ZIP as a standard archiving format.
    (Uh-oh, here comes 7Zip...)

    And this is all separate from the Unix world, which had
    tar, cpio, gzip...

    RAR was my pet hate...


    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    :-O


    unrar.

    Unix, or Linux?

    Unix.
    I cant remember when Linux first appeared on the desktops - I believe
    that Mr Kettlewell was among the first in our company to espouse it, but
    it was preceded by a lot of SCO Unix and SUNoS .

    Curiously the advent of wide area networking and ultimately the Internet propelled both the RAR format and Linux into popularity. It is hard to
    see how co-operative development of Linux would have taken place without
    the Internet and the ability to download and upload files globally, and
    the need for RAR was IIRC driven by the first 'torrents' of pirated
    software...

    Anyway, for a long time it remained a DOS/WIN only program.


    --
    I would rather have questions that cannot be answered...
    ...than to have answers that cannot be questioned

    Richard Feynman

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to The Natural Philosopher on Sun Feb 19 12:48:12 2023
    On 2023-02-19 12:13, The Natural Philosopher wrote:
    On 18/02/2023 21:18, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 13:15:31 +0000, The Natural Philosopher wrote:

    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:

    RAR was my pet hate...

    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    unrar x file.rar

    should deflate the content into the PWD.

    Today yes, not in 1993, to run on SCO Unix.

    Well, RAR for DOS appeared on 1993! :-D

    So in 1993 there wasn't a version for Linux, either.


    I believe the sources were published with version 2, or version 2
    sources were published when version 3 appeared. The wikipedia article
    doesn't have dates for these. But as soon as those sources appeared,
    anybody could compile a version for Unix.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to The Natural Philosopher on Sun Feb 19 12:42:49 2023
    On 2023-02-19 12:10, The Natural Philosopher wrote:
    On 18/02/2023 16:39, Carlos E.R. wrote:
    On 2023-02-18 14:15, The Natural Philosopher wrote:
    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:
    On 17/02/2023 19:32, Charlie Gibbs wrote:
    I was becoming so tired of the proliferation of file archiving
    formats (ARC, ZOO, ARJ, etc.) that I was relieved to see the
    world finally settle on ZIP as a standard archiving format.
    (Uh-oh, here comes 7Zip...)

    And this is all separate from the Unix world, which had
    tar, cpio, gzip...

    RAR was my pet hate...


    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    :-O


    unrar.

    Unix, or Linux?

    Unix.
    I cant remember when Linux first appeared on the desktops - I believe
    that Mr Kettlewell was among the first in our company to espouse it, but
    it was preceded by a lot of SCO Unix and SUNoS .

    I suppose that unrar can be compiled in Unix, the source is available.


    unrar for unix is mentioned here, for instance:

    <https://www.cyberciti.biz/faq/open-rar-file-or-extract-rar-files-under-linux-or-unix/>

    +++··················
    If you are using FreeBSD Unix, use the pkg command:
    # pkg install unrar

    If you are using OpenBSD Unix, use the pkg_add command:
    # pkg_add -v unrar

    If you are using macOS Unix and Homebrew, use the brew command. First,
    install Homebrew on macOS and then type the following brew command:
    $ brew install unrar
    ··················++-



    Curiously the advent of wide area networking and ultimately the Internet propelled both the RAR format and Linux into popularity. It is hard to
    see how co-operative development of Linux would have taken place without
    the Internet and the ability to download and upload files globally, and
    the need for RAR was IIRC driven by the first 'torrents' of pirated software...

    Anyway, for a long time it remained a DOS/WIN only program.

    Certainly Linux development came with Internet. That is known history.

    RAR was very popular in the DOS world, but it started in 1993, so the
    same era as Linux.

    https://en.wikipedia.org/wiki/RAR_(file_format)

    «RAR is a proprietary archive file format that supports data
    compression, error correction and file spanning.[3] It was developed in
    1993 by Russian software engineer Eugene Roshal and the software is
    licensed by win.rar GmbH.[3] The name RAR stands for Roshal Archive.»


    RAR had good features before internet. It could easily create archives
    spanning several floppies, it had forward error recovery... It had some
    sort of support for script running with decompress, useful for
    installation of programs.


    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Kohlbach@21:1/5 to All on Sun Feb 19 21:13:50 2023
    On Sat, 18 Feb 2023 21:40:19 -0500, 25B.R866 wrote:

    On 2/18/23 4:16 PM, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 03:59:16 -0500, 25B.R866 wrote:

    7-zip is better than old-fashioned zip and ALMOST as
    portable these days. You can easily get 7-zip for
    linux and Winders.
    Possible.
    But I notice some people send me a file with a ZIP extension. Often
    turns out it's 7-zip, so "unzip" fails. I have 7z installed though and it
    works. Would be nice though if (un)zip not just fails in these cases, but
    uses 7z then. Otherwise I have to let 7z do it.

    PROPERLY, you use the ".7z" extension when making
    zips with p7. Not everybody does that however.

    I have no control over what others send me.

    My idea was that if unzip discovers a file you try to deflate is not in
    ZIP format that it would automatically look into the file and for example
    finds out it's 7Z. Then calls 7z, or if not installed recommends it and
    aborts.
    --
    Andreas

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Computer Nerd Kev@21:1/5 to Andreas Kohlbach on Mon Feb 20 17:19:56 2023
    Andreas Kohlbach <ank@spamfence.net> wrote:
    My idea was that if unzip discovers a file you try to deflate is not in
    ZIP format that it would automatically look into the file and for example finds out it's 7Z. Then calls 7z, or if not installed recommends it and aborts.

    I suggest writing a script that looks at the output of the 'file'
    command and picks the program based on that.

    Something like:

    f="`file \"$1\"`"
    echo "$f" | grep -q '7z archive data' && p7zip -d "$1" && exit
    echo "$f" | grep -q 'Zip archive data' && unzip "$1" && exit
    echo "No program known to decompress: $f"

    Personally I hardly ever see 7z format archives, and never any
    pretending to ZIP. Or if I did, then I probably just assumed they'd
    been corrupted.

    --
    __ __
    #_ < |\| |< _#

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E. R.@21:1/5 to Computer Nerd Kev on Mon Feb 20 11:38:52 2023
    On 2023-02-20 08:19, Computer Nerd Kev wrote:
    Andreas Kohlbach <ank@spamfence.net> wrote:
    My idea was that if unzip discovers a file you try to deflate is not in
    ZIP format that it would automatically look into the file and for example
    finds out it's 7Z. Then calls 7z, or if not installed recommends it and
    aborts.

    I suggest writing a script that looks at the output of the 'file'
    command and picks the program based on that.

    I believe there are meta-archivers that automate all that. There is one
    in Pascal, I think.


    --
    Cheers,
    Carlos E.R.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25B.E866@21:1/5 to Carlos E.R. on Wed Feb 22 00:58:58 2023
    On 2/19/23 6:42 AM, Carlos E.R. wrote:
    On 2023-02-19 12:10, The Natural Philosopher wrote:
    On 18/02/2023 16:39, Carlos E.R. wrote:
    On 2023-02-18 14:15, The Natural Philosopher wrote:
    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:
    On 17/02/2023 19:32, Charlie Gibbs wrote:
    I was becoming so tired of the proliferation of file archiving
    formats (ARC, ZOO, ARJ, etc.) that I was relieved to see the
    world finally settle on ZIP as a standard archiving format.
    (Uh-oh, here comes 7Zip...)

    And this is all separate from the Unix world, which had
    tar, cpio, gzip...

    RAR was my pet hate...


    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    :-O


    unrar.

    Unix, or Linux?

    Unix.
    I cant remember when Linux first appeared on the desktops - I believe
    that Mr Kettlewell was among the first in our company to espouse it,
    but it was preceded by a lot of SCO Unix and SUNoS .

    I suppose that unrar can be compiled in Unix, the source is available.


    unrar for unix is mentioned here, for instance:

    <https://www.cyberciti.biz/faq/open-rar-file-or-extract-rar-files-under-linux-or-unix/>


    +++··················
    If you are using FreeBSD Unix, use the pkg command:
    # pkg install unrar

    If you are using OpenBSD Unix, use the pkg_add command:
    # pkg_add -v unrar

    If you are using macOS Unix and Homebrew, use the brew command. First, install Homebrew on macOS and then type the following brew command:
    $ brew install unrar
    ··················++-



    Curiously the advent of wide area networking and ultimately the
    Internet propelled both the RAR format and Linux into popularity. It
    is hard to see how co-operative development of Linux would have taken
    place without the Internet and the ability to download and upload
    files globally, and the need for RAR was IIRC driven by the first
    'torrents' of pirated software...

    Anyway, for a long time it remained a DOS/WIN only program.

    Certainly Linux development came with Internet. That is known history.

    RAR was very popular in the DOS world, but it started in 1993, so the
    same era as Linux.

    https://en.wikipedia.org/wiki/RAR_(file_format)

    «RAR is a proprietary archive file format that supports data
    compression, error correction and file spanning.[3] It was developed in
    1993 by Russian software engineer Eugene Roshal and the software is
    licensed by win.rar GmbH.[3] The name RAR stands for Roshal Archive.»


    RAR had good features before internet. It could easily create archives spanning several floppies, it had forward error recovery... It had some
    sort of support for script running with decompress, useful for
    installation of programs.


    Well, even plain old zip could make floppy-spanning
    archives WAY back.

    THESE days I'd rec 7zip. Does pretty much anything
    you'd ever need and it's snappier than RAR or zip
    and compresses a bit better.

    Alas a legacy of the past is that there were maybe
    50 unique compression/archive schemes - some totally
    proprietary like "Squeeze!". Finding unzippers for
    all those schemes is a hopeless task - so, hate to
    say it, some of that old data just has to be let go.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E. R.@21:1/5 to All on Wed Feb 22 18:54:37 2023
    On 2023-02-22 06:58, 25B.E866 wrote:
    On 2/19/23 6:42 AM, Carlos E.R. wrote:
    On 2023-02-19 12:10, The Natural Philosopher wrote:
    On 18/02/2023 16:39, Carlos E.R. wrote:
    On 2023-02-18 14:15, The Natural Philosopher wrote:
    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:
    On 17/02/2023 19:32, Charlie Gibbs wrote:
    I was becoming so tired of the proliferation of file archiving >>>>>>>> formats (ARC, ZOO, ARJ, etc.) that I was relieved to see the
    world finally settle on ZIP as a standard archiving format.
    (Uh-oh, here comes 7Zip...)

    And this is all separate from the Unix world, which had
    tar, cpio, gzip...

    RAR was my pet hate...


    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    :-O


    unrar.

    Unix, or Linux?

    Unix.
    I cant remember when Linux first appeared on the desktops - I believe
    that Mr Kettlewell was among the first in our company to espouse it,
    but it was preceded by a lot of SCO Unix and SUNoS .

    I suppose that unrar can be compiled in Unix, the source is available.


    unrar for unix is mentioned here, for instance:

    <https://www.cyberciti.biz/faq/open-rar-file-or-extract-rar-files-under-linux-or-unix/>

    +++··················
    If you are using FreeBSD Unix, use the pkg command:
    # pkg install unrar

    If you are using OpenBSD Unix, use the pkg_add command:
    # pkg_add -v unrar

    If you are using macOS Unix and Homebrew, use the brew command. First,
    install Homebrew on macOS and then type the following brew command:
    $ brew install unrar
    ··················++-



    Curiously the advent of wide area networking and ultimately the
    Internet propelled both the RAR format and Linux into popularity. It
    is hard to see how co-operative development of Linux would have taken
    place without the Internet and the ability to download and upload
    files globally, and the need for RAR was IIRC driven by the first
    'torrents' of pirated software...

    Anyway, for a long time it remained a DOS/WIN only program.

    Certainly Linux development came with Internet. That is known history.

    RAR was very popular in the DOS world, but it started in 1993, so the
    same era as Linux.

    https://en.wikipedia.org/wiki/RAR_(file_format)

    «RAR is a proprietary archive file format that supports data
    compression, error correction and file spanning.[3] It was developed
    in 1993 by Russian software engineer Eugene Roshal and the software is
    licensed by win.rar GmbH.[3] The name RAR stands for Roshal Archive.»


    RAR had good features before internet. It could easily create archives
    spanning several floppies, it had forward error recovery... It had
    some sort of support for script running with decompress, useful for
    installation of programs.


      Well, even plain old zip could make floppy-spanning
      archives WAY back.

      THESE days I'd rec 7zip. Does pretty much anything
      you'd ever need and it's snappier than RAR or zip
      and compresses a bit better.

    Except, AFAIK, forward error recovery.


      Alas a legacy of the past is that there were maybe
      50 unique compression/archive schemes - some totally
      proprietary like "Squeeze!". Finding unzippers for
      all those schemes is a hopeless task - so, hate to
      say it, some of that old data just has to be let go.

    Can be.

    --
    Cheers,
    Carlos E.R.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Kohlbach@21:1/5 to All on Wed Feb 22 17:00:24 2023
    On Wed, 22 Feb 2023 00:58:58 -0500, 25B.E866 wrote:

    On 2/19/23 6:42 AM, Carlos E.R. wrote:
    On 2023-02-19 12:10, The Natural Philosopher wrote:

    Certainly Linux development came with Internet. That is known
    history.
    RAR was very popular in the DOS world, but it started in 1993, so
    the same era as Linux.
    https://en.wikipedia.org/wiki/RAR_(file_format)
    RAR is a proprietary archive file format that supports data
    compression, error correction and file spanning.[3] It was developed
    in 1993 by Russian software engineer Eugene Roshal and the software
    is licensed by win.rar GmbH.[3] The name RAR stands for Roshal
    Archive.

    RAR had good features before internet. It could easily create
    archives spanning several floppies, it had forward error
    recovery... It had some sort of support for script running with
    decompress, useful for installation of programs.


    Well, even plain old zip could make floppy-spanning
    archives WAY back.

    RAR seems so yesterday. Thus I just installed ARJ and LHA for good manners! :-D

    THESE days I'd rec 7zip. Does pretty much anything
    you'd ever need and it's snappier than RAR or zip
    and compresses a bit better.

    Still I say ZIP is a common noun. Many people refer to "zip" when ever something comes compressed in an archive. Therefor the program unzip
    should not abort if it finds something else than a zip compressed
    archive. Instead find out what it is (Linux' command "file" can do that)
    and delegate the job to the appropriate program (like 7z).

    Yes, there was suggested to write a wrapper. But in my opinion that
    should be included into the program unzip, as ZIP still a common noun.

    But then, ZIP here has a date from April 2009, so i don't think there'll
    be ever any updates.
    --
    Andreas

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Computer Nerd Kev@21:1/5 to Andreas Kohlbach on Thu Feb 23 09:23:37 2023
    Andreas Kohlbach <ank@spamfence.net> wrote:
    On Wed, 22 Feb 2023 00:58:58 -0500, 25B.E866 wrote:

    THESE days I'd rec 7zip. Does pretty much anything
    you'd ever need and it's snappier than RAR or zip
    and compresses a bit better.

    Still I say ZIP is a common noun. Many people refer to "zip" when ever something comes compressed in an archive. Therefor the program unzip
    should not abort if it finds something else than a zip compressed
    archive. Instead find out what it is (Linux' command "file" can do that)
    and delegate the job to the appropriate program (like 7z).

    Yes, there was suggested to write a wrapper. But in my opinion that
    should be included into the program unzip, as ZIP still a common noun.

    Not in my world it isn't, it sounds like you just know some very
    confused people. But what's with the obsession for changing unzip
    when you could just switch to using 7-Zip for all the various
    "zips" by default instead?

    From the 7z man page:
    "7-Zip is a file archiver supporting 7z (that implements LZMA
    compression algorithm featuring very high compression ratio),
    LZMA2, XZ, ZIP, Zip64, CAB, RAR (if the non-free p7zip-rar package
    is installed), ARJ, GZIP, BZIP2, TAR, CPIO, RPM, ISO, most
    filesystem images and DEB formats."

    --
    __ __
    #_ < |\| |< _#

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Kohlbach@21:1/5 to Computer Nerd Kev on Wed Feb 22 19:43:29 2023
    On 23 Feb 2023 09:23:37 +1000, Computer Nerd Kev wrote:

    Andreas Kohlbach <ank@spamfence.net> wrote:
    On Wed, 22 Feb 2023 00:58:58 -0500, 25B.E866 wrote:

    THESE days I'd rec 7zip. Does pretty much anything
    you'd ever need and it's snappier than RAR or zip
    and compresses a bit better.

    Still I say ZIP is a common noun. Many people refer to "zip" when ever
    something comes compressed in an archive. Therefor the program unzip
    should not abort if it finds something else than a zip compressed
    archive. Instead find out what it is (Linux' command "file" can do that)
    and delegate the job to the appropriate program (like 7z).

    Yes, there was suggested to write a wrapper. But in my opinion that
    should be included into the program unzip, as ZIP still a common noun.

    Not in my world it isn't, it sounds like you just know some very
    confused people. But what's with the obsession for changing unzip
    when you could just switch to using 7-Zip for all the various
    "zips" by default instead?

    From the 7z man page:
    "7-Zip is a file archiver supporting 7z (that implements LZMA
    compression algorithm featuring very high compression ratio),
    LZMA2, XZ, ZIP, Zip64, CAB, RAR (if the non-free p7zip-rar package
    is installed), ARJ, GZIP, BZIP2, TAR, CPIO, RPM, ISO, most
    filesystem images and DEB formats."

    That I didn't know. That removes my concerns. Thanks. :-)

    It even handles ARJ as I see from that excerpt. *g*
    --
    Andreas

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25B.E866@21:1/5 to Andreas Kohlbach on Thu Feb 23 01:08:06 2023
    On 2/22/23 7:43 PM, Andreas Kohlbach wrote:
    On 23 Feb 2023 09:23:37 +1000, Computer Nerd Kev wrote:

    Andreas Kohlbach <ank@spamfence.net> wrote:
    On Wed, 22 Feb 2023 00:58:58 -0500, 25B.E866 wrote:

    THESE days I'd rec 7zip. Does pretty much anything
    you'd ever need and it's snappier than RAR or zip
    and compresses a bit better.

    Still I say ZIP is a common noun. Many people refer to "zip" when ever
    something comes compressed in an archive. Therefor the program unzip
    should not abort if it finds something else than a zip compressed
    archive. Instead find out what it is (Linux' command "file" can do that) >>> and delegate the job to the appropriate program (like 7z).

    Yes, there was suggested to write a wrapper. But in my opinion that
    should be included into the program unzip, as ZIP still a common noun.

    Not in my world it isn't, it sounds like you just know some very
    confused people. But what's with the obsession for changing unzip
    when you could just switch to using 7-Zip for all the various
    "zips" by default instead?

    From the 7z man page:
    "7-Zip is a file archiver supporting 7z (that implements LZMA
    compression algorithm featuring very high compression ratio),
    LZMA2, XZ, ZIP, Zip64, CAB, RAR (if the non-free p7zip-rar package
    is installed), ARJ, GZIP, BZIP2, TAR, CPIO, RPM, ISO, most
    filesystem images and DEB formats."

    That I didn't know. That removes my concerns. Thanks. :-)

    It even handles ARJ as I see from that excerpt. *g*


    7-zip is *very* versatile - WORTH using. A good
    step up from age-old Zip (but you CAN do those
    age-old Zips with it too).

    It's SUPPOSED to come with a dedicated GUI too, but
    for some reason it doesn't seem to be included in
    the Deb repos - or at least I can't find/run it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrei Z.@21:1/5 to All on Thu Feb 23 13:32:26 2023
    25B.E866 wrote:
      7-zip is *very* versatile - WORTH using. A good
      step up from age-old Zip (but you CAN do those
      age-old Zips with it too).

      It's SUPPOSED to come with a dedicated GUI too, but
      for some reason it doesn't seem to be included in
      the Deb repos - or at least I can't find/run it.

    Details of package p7zip-full in bullseye https://packages.debian.org/en/bullseye/p7zip-full

    How to Install 7-Zip on Debian 11 or 10 - LinuxCapable https://www.linuxcapable.com/how-to-install-7-zip-on-debian-linux/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25B.E866@21:1/5 to Andrei Z. on Thu Feb 23 11:23:00 2023
    On 2/23/23 5:32 AM, Andrei Z. wrote:
    25B.E866 wrote:
       7-zip is *very* versatile - WORTH using. A good
       step up from age-old Zip (but you CAN do those
       age-old Zips with it too).

       It's SUPPOSED to come with a dedicated GUI too, but
       for some reason it doesn't seem to be included in
       the Deb repos - or at least I can't find/run it.

    Details of package p7zip-full in bullseye https://packages.debian.org/en/bullseye/p7zip-full

    How to Install 7-Zip on Debian 11 or 10 - LinuxCapable https://www.linuxcapable.com/how-to-install-7-zip-on-debian-linux/


    Been there, no luck. Weird.

    Maybe I'll be inspired to write my own
    front end :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrei Z.@21:1/5 to All on Thu Feb 23 20:29:03 2023
    25B.E866 wrote:
    On 2/23/23 5:32 AM, Andrei Z. wrote:
    25B.E866 wrote:
       7-zip is *very* versatile - WORTH using. A good
       step up from age-old Zip (but you CAN do those
       age-old Zips with it too).

       It's SUPPOSED to come with a dedicated GUI too, but
       for some reason it doesn't seem to be included in
       the Deb repos - or at least I can't find/run it.

    Details of package p7zip-full in bullseye
    https://packages.debian.org/en/bullseye/p7zip-full

    How to Install 7-Zip on Debian 11 or 10 - LinuxCapable
    https://www.linuxcapable.com/how-to-install-7-zip-on-debian-linux/


      Been there, no luck. Weird.

      Maybe I'll be inspired to write my own
      front end  :-)

    "p7zip-full provides utilities to pack and unpack 7z archives within a
    shell or using a GUI (such as Ark, File Roller or Nautilus)."

    Details of package file-roller in bullseye https://packages.debian.org/en/bullseye/file-roller

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25B.E866@21:1/5 to Andrei Z. on Thu Feb 23 21:22:54 2023
    On 2/23/23 12:29 PM, Andrei Z. wrote:
    25B.E866 wrote:
    On 2/23/23 5:32 AM, Andrei Z. wrote:
    25B.E866 wrote:
       7-zip is *very* versatile - WORTH using. A good
       step up from age-old Zip (but you CAN do those
       age-old Zips with it too).

       It's SUPPOSED to come with a dedicated GUI too, but
       for some reason it doesn't seem to be included in
       the Deb repos - or at least I can't find/run it.

    Details of package p7zip-full in bullseye
    https://packages.debian.org/en/bullseye/p7zip-full

    How to Install 7-Zip on Debian 11 or 10 - LinuxCapable
    https://www.linuxcapable.com/how-to-install-7-zip-on-debian-linux/


       Been there, no luck. Weird.

       Maybe I'll be inspired to write my own
       front end  :-)

    "p7zip-full provides utilities to pack and unpack 7z archives within a
    shell or using a GUI (such as Ark, File Roller or Nautilus)."

    But I don't LIKE them .... :-(

    Xarchiver crashes if you try to bring in LOTS of
    files, Ark isn't clear about the order in which
    to do things and sometimes complains that you
    can't archive "that kind of file" when, really,
    there's no reason not to, File-roller ... umm ...
    and I never use Nautilus for anything.

    So I'll have to write one I *do* like. Basically
    it just has to build up the CL command based
    on whatever params/options you select and then do
    a System() call.

    Next weeks project ....

    I had gotten the impression that the 7zip people
    had written their very own GUI front end, but it
    looks like they rely on others.

    Details of package file-roller in bullseye https://packages.debian.org/en/bullseye/file-roller

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Computer Nerd Kev@21:1/5 to 25B.E866@noaaba.net on Fri Feb 24 13:18:33 2023
    25B.E866 <25B.E866@noaaba.net> wrote:

    I had gotten the impression that the 7zip people
    had written their very own GUI front end, but it
    looks like they rely on others.

    Only on Linux. I quite like the Windows GUI for 7-Zip, it can be
    set up in a commander-style layout and almost works as a general
    purpose file manager. I use 7-Zip in Windows much more than in
    Linux, because it opens tar.* files. In Linux the files I deal with
    are almost always ZIP, GZIP, BZIP2, or XZ, and the standard tools
    do fine for them, as well as the decompression support built into
    GUI file managers (which is sometimes user-customisable for adding
    missing formats like 7Zip as well).

    7-Zip for Windows will run in WINE: https://appdb.winehq.org/objectManager.php?sClass=version&iId=40417

    --
    __ __
    #_ < |\| |< _#

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrei Z.@21:1/5 to All on Fri Feb 24 07:58:22 2023
    25B.E866 wrote:
      Next weeks project ....

      I had gotten the impression that the 7zip people
      had written their very own GUI front end, but it
      looks like they rely on others.

    p7zip looks abandoned.
    https://sourceforge.net/projects/p7zip/

    7-Zip for Linux first release 2021-03-10 https://sourceforge.net/p/sevenzip/discussion/45797/thread/cec5e63147/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25A.I866@21:1/5 to Computer Nerd Kev on Sat Feb 25 00:13:18 2023
    On 2/23/23 10:18 PM, Computer Nerd Kev wrote:
    25B.E866 <25B.E866@noaaba.net> wrote:

    I had gotten the impression that the 7zip people
    had written their very own GUI front end, but it
    looks like they rely on others.

    Only on Linux.

    How discriminatory !!!

    I quite like the Windows GUI for 7-Zip, it can be
    set up in a commander-style layout and almost works as a general
    purpose file manager. I use 7-Zip in Windows much more than in
    Linux, because it opens tar.* files. In Linux the files I deal with
    are almost always ZIP, GZIP, BZIP2, or XZ, and the standard tools
    do fine for them, as well as the decompression support built into
    GUI file managers (which is sometimes user-customisable for adding
    missing formats like 7Zip as well).

    7-Zip for Windows will run in WINE: https://appdb.winehq.org/objectManager.php?sClass=version&iId=40417

    I don't use Winders.

    So, gotta write my own alas ....

    Again ...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25A.I866@21:1/5 to Andrei Z. on Sat Feb 25 00:15:06 2023
    On 2/23/23 11:58 PM, Andrei Z. wrote:
    25B.E866 wrote:
       Next weeks project ....

       I had gotten the impression that the 7zip people
       had written their very own GUI front end, but it
       looks like they rely on others.

    p7zip looks abandoned.
    https://sourceforge.net/projects/p7zip/

    7-Zip for Linux first release 2021-03-10 https://sourceforge.net/p/sevenzip/discussion/45797/thread/cec5e63147/

    "Abandoned" - or just "perfected" ???

    Once you Get It Right .....

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25A.I866@21:1/5 to Carlos E.R. on Sat Feb 25 00:51:19 2023
    On 2/19/23 6:48 AM, Carlos E.R. wrote:
    On 2023-02-19 12:13, The Natural Philosopher wrote:
    On 18/02/2023 21:18, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 13:15:31 +0000, The Natural Philosopher wrote:

    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:

    RAR was my pet hate...

    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    unrar x file.rar

    should deflate the content into the PWD.

    Today yes, not in 1993, to run on SCO Unix.

    Well, RAR for DOS appeared on 1993! :-D

    So in 1993 there wasn't a version for Linux, either.

    I believe the sources were published with version 2, or version 2
    sources were published when version 3 appeared. The wikipedia article
    doesn't have dates for these. But as soon as those sources appeared,
    anybody could compile a version for Unix.


    Always SOUNDS so simple :-)

    I always wind up having to write fill-ins for the
    missing/very-different library routines between
    Win and Lin.

    Anyway, I'm not sure about the fascination with RAR.
    It is good, but then so are many others that are more
    modern/portable/supported.

    Found an interesting "loop-based" approach to an Str2Int64()
    today. Basically it does powers of ten on each digit (derived
    from the ASCII values of the digits minus-48). It MAY be a bit
    faster than the one I wrote the other day for Pascal that
    involves 'shrinking down' the presented number. I'll have
    to benchmark. Mine only used integer subtraction and ONE
    modulo. Not AS many steps. But, we'll see.

    I was writing a "disk visualizer" the other day (turned out
    pretty well) but Int64 numbers/functions ARE involved. Today
    I took that to write a 'C' "Disk Blaster" ... kinda like using
    'dd' to zero (or pattern-write) a whole drive but because it's
    not as complex it's about 30% quicker. Added a 'skitter' option
    that's applied AFTER the prescribed number of bytes are
    overwritten ... 'skittering' means writing yer zero/pattern
    block roughly (a little randomness added to annoy) every
    50mb on the REST of the disk area. It is not 'erasure'
    per-se, but kinda 'corrupts' and is 50x as fast. You can
    go thru a 1tb disk in an external USB3.0 fixture in about
    five minutes with 'skittering'. So, you totally obliterate
    the X-bytes you're most paranoid about and then randomly
    insert junk in the rest.

    Just gotta smooth-out the params ... there's no slack
    right now. Something like 'dd' params would be good.
    It always uses the equiv of "bs=1M" ... seems the best
    compromise after some experimentation. My visualizer
    made it easy to see if the blaster util was doing it
    right.

    FYI - I have a PILE of old HDDs ... some just Too Old,
    others Flakey. They NEED to be wiped, or at least
    quasi-wiped, before disposal. If I have the time I
    strip them of the magnets and pretty platters, but
    that takes 20-30 minutes per so sometimes I'll just
    trash the whole thing. (a cold-chisel and big
    hammer will also trash old hdd's really well :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrei Z.@21:1/5 to All on Sat Feb 25 09:34:17 2023
    25A.I866 wrote:
    On 2/23/23 11:58 PM, Andrei Z. wrote:
    25B.E866 wrote:
       Next weeks project ....

       I had gotten the impression that the 7zip people
       had written their very own GUI front end, but it
       looks like they rely on others.

    p7zip looks abandoned.
    https://sourceforge.net/projects/p7zip/

    7-Zip for Linux first release 2021-03-10
    https://sourceforge.net/p/sevenzip/discussion/45797/thread/cec5e63147/

      "Abandoned" - or just "perfected" ???

      Once you Get It Right .....

    p7zip
    https://github.com/btolab/p7zip
    "7z archiver with source history"

    "A new p7zip fork with additional codecs and improvements" https://github.com/jinfeihan57/p7zip/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rich@21:1/5 to 25A.I866@noacba.net on Sat Feb 25 06:15:51 2023
    25A.I866 <25A.I866@noacba.net> wrote:
    FYI - I have a PILE of old HDDs ... some just Too Old, others
    Flakey. They NEED to be wiped, or at least quasi-wiped, before
    disposal.

    A degaussing coil is the usual method to do this, and does not
    involve disassembly nor writing Pascal or C code.

    And, for your 'flakey' drives, trying to overwrite by using the drive
    itself may not work at all. While the degaussing coil just scrambles
    the magnetic domains on the platters.

    Search for one meant for erasing disks, ones meant for mag-tape may not
    be powerful enough for the magnetic material used in disks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25A.I866@21:1/5 to Andrei Z. on Sat Feb 25 02:33:22 2023
    On 2/25/23 1:34 AM, Andrei Z. wrote:
    25A.I866 wrote:
    On 2/23/23 11:58 PM, Andrei Z. wrote:
    25B.E866 wrote:
       Next weeks project ....

       I had gotten the impression that the 7zip people
       had written their very own GUI front end, but it
       looks like they rely on others.

    p7zip looks abandoned.
    https://sourceforge.net/projects/p7zip/

    7-Zip for Linux first release 2021-03-10
    https://sourceforge.net/p/sevenzip/discussion/45797/thread/cec5e63147/

       "Abandoned" - or just "perfected" ???

       Once you Get It Right .....

    p7zip
    https://github.com/btolab/p7zip
    "7z archiver with source history"

    "A new p7zip fork with additional codecs and improvements" https://github.com/jinfeihan57/p7zip/

    Sounds good.

    But why do people keep re-inventing the wheel ???
    There's VERY little improvement in 'zipping' in
    terms of speed/compression/ease in the last 20
    years. Basically, what you get is not "improved",
    just "different".

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25A.I866@21:1/5 to Rich on Sat Feb 25 02:30:42 2023
    On 2/25/23 1:15 AM, Rich wrote:
    25A.I866 <25A.I866@noacba.net> wrote:
    FYI - I have a PILE of old HDDs ... some just Too Old, others
    Flakey. They NEED to be wiped, or at least quasi-wiped, before
    disposal.

    A degaussing coil is the usual method to do this, and does not
    involve disassembly nor writing Pascal or C code.

    I don't have one big enough to affect modern HDD platters.

    But the cold-chisel method .........

    And, for your 'flakey' drives, trying to overwrite by using the drive
    itself may not work at all. While the degaussing coil just scrambles
    the magnetic domains on the platters.

    Search for one meant for erasing disks, ones meant for mag-tape may not
    be powerful enough for the magnetic material used in disks.

    The only one I have was meant for floppies.

    But a little Bang Bang with the silver hammer :-)

    It is BEST to disassemble. It's almost a sin to waste
    those rare-earth magnets and the platters are SO
    attractive. But, if there's just no time .....

    However, regardless of the final method, some kind of
    software wipe beforehand IS wise.

    I don't think old HDDs are AS likely to be found/exploited
    as some alarmists would like us to believe. However there
    is still "good practice" ... you need to be able to SAY
    you put in The Effort to prevent piracy.

    Strictly, from the electronic angle, a hand "Stun Gun"
    at 50000-100000 volts played across the contacts in
    the back will make a BIG mess of things. Someone would
    literally have to physically remove the platters and
    insert them in the same model of drive or own custom
    hardware that'll scan/decode any platter ($$$$$$!!!).

    Now CDs/DVDs ... just put 'em in the microwave and set it
    for five seconds. The results are VERY artistic. Lotsa
    sparks. OR, just snap 'em in half (not as fun).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From The Natural Philosopher@21:1/5 to Rich on Sat Feb 25 10:09:18 2023
    On 25/02/2023 06:15, Rich wrote:
    25A.I866 <25A.I866@noacba.net> wrote:
    FYI - I have a PILE of old HDDs ... some just Too Old, others
    Flakey. They NEED to be wiped, or at least quasi-wiped, before
    disposal.

    A degaussing coil is the usual method to do this, and does not
    involve disassembly nor writing Pascal or C code.

    Actually it isn't.
    In commercial cleanups of old machine rooms data centres and offices,
    the usual method is a crusher. My ex BIL in charge of IT rollouts to
    replace obsolescent kit in huge companies used to be able to get cheap
    machines from the recyclers, but never hard drives
    Amateurs may use a sledge hammer.



    And, for your 'flakey' drives, trying to overwrite by using the drive
    itself may not work at all. While the degaussing coil just scrambles
    the magnetic domains on the platters.

    Typically sector read errors are either caused by the most commonly used sectors - the one carrying the file inode indices - having rust flakes,
    or more often by simple bearing wear on the main spindle, making the
    head to track relationship unreliable.

    Neither of these are recoverable conditions.

    Some of us have tried, and failed.

    Today we do what we advise anyone else to do - at the first sign of pre
    fail error rates becoming non zero, replace the drive.

    And take the old one and put it on hard surface and hit it with a heavy
    hard object.

    Then throw it in the bin



    Search for one meant for erasing disks, ones meant for mag-tape may not
    be powerful enough for the magnetic material used in disks.

    --
    The New Left are the people they warned you about.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From The Natural Philosopher@21:1/5 to All on Sat Feb 25 10:00:57 2023
    On 25/02/2023 05:15, 25A.I866 wrote:
    On 2/23/23 11:58 PM, Andrei Z. wrote:
    25B.E866 wrote:
       Next weeks project ....

       I had gotten the impression that the 7zip people
       had written their very own GUI front end, but it
       looks like they rely on others.

    p7zip looks abandoned.
    https://sourceforge.net/projects/p7zip/

    7-Zip for Linux first release 2021-03-10
    https://sourceforge.net/p/sevenzip/discussion/45797/thread/cec5e63147/

      "Abandoned" - or just "perfected" ???

      Once you Get It Right .....

    "After decades of innovation, Microsoft discovered that round wheels
    work best, but managed to keep reintroducing them as new by painting
    them different colors, and adding white walls to the tyres. Since
    Windows Round was obsoleted 20 years ago, we have had windows Red, Blue, Yellow, Green and LBGT!. "

    --
    “But what a weak barrier is truth when it stands in the way of an hypothesis!”

    Mary Wollstonecraft

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From The Natural Philosopher@21:1/5 to All on Sat Feb 25 10:19:42 2023
    On 25/02/2023 07:33, 25A.I866 wrote:
    On 2/25/23 1:34 AM, Andrei Z. wrote:


    "A new p7zip fork with additional codecs and improvements"
    https://github.com/jinfeihan57/p7zip/

      Sounds good.

      But why do people keep re-inventing the wheel ???

    Marketing. This is not just *any* wheel, this is a wheel whose extra
    roundness, and superlative styling makes your existing wheel - well -
    simply *passé*, darlings

    --
    To ban Christmas, simply give turkeys the vote.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to All on Sat Feb 25 12:04:55 2023
    On 2023-02-25 08:33, 25A.I866 wrote:
    On 2/25/23 1:34 AM, Andrei Z. wrote:
    25A.I866 wrote:
    On 2/23/23 11:58 PM, Andrei Z. wrote:
    25B.E866 wrote:
       Next weeks project ....

       I had gotten the impression that the 7zip people
       had written their very own GUI front end, but it
       looks like they rely on others.

    p7zip looks abandoned.
    https://sourceforge.net/projects/p7zip/

    7-Zip for Linux first release 2021-03-10
    https://sourceforge.net/p/sevenzip/discussion/45797/thread/cec5e63147/

       "Abandoned" - or just "perfected" ???

       Once you Get It Right .....

    p7zip
    https://github.com/btolab/p7zip
    "7z archiver with source history"

    "A new p7zip fork with additional codecs and improvements"
    https://github.com/jinfeihan57/p7zip/

      Sounds good.

      But why do people keep re-inventing the wheel ???
      There's VERY little improvement in 'zipping' in
      terms of speed/compression/ease in the last 20
      years. Basically, what you get is not "improved",
      just "different".

    No, there are new compression methods that handle better this or that
    type of files. Also ones that do compression in parallel, which is faster.

    Notice that decompressing in parallel is not a thing yet, so there is
    room for improvement.

    Then there are features like having error recovery or not.


    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to All on Sat Feb 25 12:10:13 2023
    On 2023-02-25 06:51, 25A.I866 wrote:
    On 2/19/23 6:48 AM, Carlos E.R. wrote:
    On 2023-02-19 12:13, The Natural Philosopher wrote:
    On 18/02/2023 21:18, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 13:15:31 +0000, The Natural Philosopher wrote:

    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:

    RAR was my pet hate...

    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    unrar x file.rar

    should deflate the content into the PWD.

    Today yes, not in 1993, to run on SCO Unix.

    Well, RAR for DOS appeared on 1993! :-D

    So in 1993 there wasn't a version for Linux, either.

    I believe the sources were published with version 2, or version 2
    sources were published when version 3 appeared. The wikipedia article
    doesn't have dates for these. But as soon as those sources appeared,
    anybody could compile a version for Unix.


      Always SOUNDS so simple  :-)

      I always wind up having to write fill-ins for the
      missing/very-different library routines between
      Win and Lin.

      Anyway, I'm not sure about the fascination with RAR.
      It is good, but then so are many others that are more
      modern/portable/supported.

      Found an interesting "loop-based" approach to an Str2Int64()
      today. Basically it does powers of ten on each digit (derived
      from the ASCII values of the digits minus-48). It MAY be a bit
      faster than the one I wrote the other day for Pascal that
      involves 'shrinking down' the presented number. I'll have
      to benchmark. Mine only used integer subtraction and ONE
      modulo. Not AS many steps. But, we'll see.

      I was writing a "disk visualizer" the other day (turned out
      pretty well) but Int64 numbers/functions ARE involved. Today
      I took that to write a 'C' "Disk Blaster" ... kinda like using
      'dd' to zero (or pattern-write) a whole drive but because it's
      not as complex it's about 30% quicker. Added a 'skitter' option
      that's applied AFTER the prescribed number of bytes are
      overwritten ... 'skittering' means writing yer zero/pattern
      block roughly (a little randomness added to annoy) every
      50mb on the REST of the disk area. It is not 'erasure'
      per-se, but kinda 'corrupts' and is 50x as fast. You can
      go thru a 1tb disk in an external USB3.0 fixture in about
      five minutes with 'skittering'. So, you totally obliterate
      the X-bytes you're most paranoid about and then randomly
      insert junk in the rest.

      Just gotta smooth-out the params ... there's no slack
      right now. Something like 'dd' params would be good.
      It always uses the equiv of "bs=1M" ... seems the best
      compromise after some experimentation. My visualizer
      made it easy to see if the blaster util was doing it
      right.

    I wrote a tool in pascal to write an entire device with nearly random
    data, and does so at the SATA speed of the (mechanical) disk, about 190
    MB/S last time I tried. I have done 4 TB disks.


    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From The Natural Philosopher@21:1/5 to All on Sat Feb 25 10:17:45 2023
    On 25/02/2023 07:30, 25A.I866 wrote:
    On 2/25/23 1:15 AM, Rich wrote:
    25A.I866 <25A.I866@noacba.net> wrote:
       FYI - I have a PILE of old HDDs ...  some just Too Old, others
       Flakey.  They NEED to be wiped, or at least quasi-wiped, before
       disposal.

    A degaussing coil is the usual method to do this, and does not
    involve disassembly nor writing Pascal or C code.

      I don't have one big enough to affect modern HDD platters.

      But the cold-chisel method .........

    And, for your 'flakey' drives, trying to overwrite by using the drive
    itself may not work at all.  While the degaussing coil just scrambles
    the magnetic domains on the platters.

    Search for one meant for erasing disks, ones meant for mag-tape may not
    be powerful enough for the magnetic material used in disks.

      The only one I have was meant for floppies.

      But a little Bang Bang with the silver hammer  :-)

    +1

      It is BEST to disassemble. It's almost a sin to waste
      those rare-earth magnets and the platters are SO
      attractive. But, if there's just no time .....

    Really? We all did in *one* time, to see what was inside.
    Rare earth magnets are ten a penny.


      However, regardless of the final method, some kind of
      software wipe beforehand IS wise.

    If you say so. I mean really who honestly cares?

      I don't think old HDDs are AS likely to be found/exploited
      as some alarmists would like us to believe. However there
      is still "good practice" ... you need to be able to SAY
      you put in The Effort to prevent piracy.

    That's just hand wavy nonsense. The sort of person who can take -
    particularly a Linux hard drive - even in perfect working order and reconstruct an erased file, is unlikely to be so short of money that he
    prowls junk yards looking for drives that might have something on them,
    and the people that did are looking for someone who left a full windows
    install in there with all their bank passwords encoded into IE6, that is accessible by a script within 30 seconds. If it isn't recognised because
    its ext2/3/4 they will toss the drive anyway. Or reformat it and sell it
    on ebay



      Strictly, from the electronic angle, a hand "Stun Gun"
      at 50000-100000 volts played across the contacts in
      the back will make a BIG mess of things. Someone would
      literally have to physically remove the platters and
      insert them in the same model of drive or own custom
      hardware that'll scan/decode any platter ($$$$$$!!!).

    ER no, what WE did, was to take an identical drive with drive errors,
    remove its whole circuit board and replace the buggered one on OUR
    drive, long enough to get the data off. It is actually reasonably simple
    - or was at that time.


      Now CDs/DVDs ... just put 'em in the microwave and set it
      for five seconds. The results are VERY artistic. Lotsa
      sparks. OR, just snap 'em in half (not as fun).

    --
    There is something fascinating about science. One gets such wholesale
    returns of conjecture out of such a trifling investment of fact.

    Mark Twain

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Eric Pozharski@21:1/5 to The Natural Philosopher on Sat Feb 25 13:43:00 2023
    with <ttcnbu$279gm$17@dont-email.me> The Natural Philosopher wrote:
    On 25/02/2023 07:33, 25A.I866 wrote:
    On 2/25/23 1:34 AM, Andrei Z. wrote:


    "A new p7zip fork with additional codecs and improvements"
    https://github.com/jinfeihan57/p7zip/
    Sounds good.
    But why do people keep re-inventing the wheel ???
    Marketing. This is not just *any* wheel, this is a wheel whose extra roundness, and superlative styling makes your existing wheel - well -
    simply *passé*, darlings

    One single way -- that would be dreamy. Unfortunately, without single authority seems to be impossible.

    --
    Torvalds' goal for Linux is very simple: World Domination
    Stallman's goal for GNU is even simpler: Freedom

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Computer Nerd Kev@21:1/5 to 25A.I866@noacba.net on Sun Feb 26 12:01:56 2023
    25A.I866 <25A.I866@noacba.net> wrote:
    On 2/23/23 10:18 PM, Computer Nerd Kev wrote:
    25B.E866 <25B.E866@noaaba.net> wrote:

    I had gotten the impression that the 7zip people
    had written their very own GUI front end, but it
    looks like they rely on others.

    Only on Linux.

    How discriminatory !!!

    Turns out I'm wrong, there's a fork of p7zip that includes the 7zip
    GUI from the Windows version:

    https://github.com/ErnyTech/p7zip
    https://snapcraft.io/p7zip-desktop

    --
    __ __
    #_ < |\| |< _#

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25A.I866@21:1/5 to The Natural Philosopher on Sat Feb 25 23:08:26 2023
    On 2/25/23 5:17 AM, The Natural Philosopher wrote:
    On 25/02/2023 07:30, 25A.I866 wrote:
    On 2/25/23 1:15 AM, Rich wrote:
    25A.I866 <25A.I866@noacba.net> wrote:
       FYI - I have a PILE of old HDDs ...  some just Too Old, others
       Flakey.  They NEED to be wiped, or at least quasi-wiped, before
       disposal.

    A degaussing coil is the usual method to do this, and does not
    involve disassembly nor writing Pascal or C code.

       I don't have one big enough to affect modern HDD platters.

       But the cold-chisel method .........

    And, for your 'flakey' drives, trying to overwrite by using the drive
    itself may not work at all.  While the degaussing coil just scrambles
    the magnetic domains on the platters.

    Search for one meant for erasing disks, ones meant for mag-tape may not
    be powerful enough for the magnetic material used in disks.

       The only one I have was meant for floppies.

       But a little Bang Bang with the silver hammer  :-)

    +1

       It is BEST to disassemble. It's almost a sin to waste
       those rare-earth magnets and the platters are SO
       attractive. But, if there's just no time .....

    Really? We all did in *one* time, to see what was inside.
    Rare earth magnets are ten a penny.


    Why pay the Chinese twice ? A 'free' supermagnet is a
    free supermagnet ........


       However, regardless of the final method, some kind of
       software wipe beforehand IS wise.

    If you say so. I mean really who honestly cares?


    The Overlords. There's an actual question on
    their semi-annual eval form ......


       I don't think old HDDs are AS likely to be found/exploited
       as some alarmists would like us to believe. However there
       is still "good practice" ... you need to be able to SAY
       you put in The Effort to prevent piracy.

    That's just hand wavy nonsense. The sort of person who can take - particularly a Linux hard drive  - even in perfect working order and reconstruct an erased file, is unlikely to be so short of money that he prowls junk yards looking for drives that might have something on them,


    Well, that's The Truth .... which has nothing to do
    with corporate reality.

    Actually, conventionally erased files are pretty EASY
    to get at ... because they're not actually "erased",
    just that their entries in the file-allocation table
    get removed. The files are still perfectly intact
    until/if something re-uses their old clusters. There's
    been software for reconstructing those FAT entries
    since forever.

    THEOretically, you should e-wipe an old disk entirely
    even if it DOES take 48 hours. Then only the spooks can
    get at it, looking for the weaker magnetic sigs of the
    previous values too. SSDs are much harder to erase because
    of the wear-leveling system. For them the silver hammer -
    or the microwave. I've got a 50kv transformer rigged up
    with a couple of electrodes (tungsten plasma-torch)
    that's mostly for putting on a light show - but you
    COULD put devices between the electrodes .....


    and the people that did are looking for someone who left a full windows install in there with all their bank passwords encoded into IE6, that is accessible by a script within 30 seconds. If it isn't recognised because
    its ext2/3/4 they will toss the drive anyway. Or reformat it and sell it
    on ebay

    The minimal method with Winders disks IS to repartition and
    then format ext2. Ext3/4 are faster, but Ext2 seems to do a
    LOT more work during formatting setting things up it's way.
    No hope for the little hacks there.

    But the Overlords read paranoia-inducing articles about
    somebody, somewhere, some time, stealing Vital Info from
    a discarded disk - so ......

       Strictly, from the electronic angle, a hand "Stun Gun"
       at 50000-100000 volts played across the contacts in
       the back will make a BIG mess of things. Someone would
       literally have to physically remove the platters and
       insert them in the same model of drive or own custom
       hardware that'll scan/decode any platter ($$$$$$!!!).

    ER no, what WE did, was to take an identical drive with drive errors,
    remove its whole circuit board and replace the buggered one on OUR
    drive, long enough to get the data off. It is actually reasonably simple
    - or was at that time.

    Can indeed be done ... and if you send a screwed-up disk to
    a recovery service that's exactly what they do. The kind of
    hardware involving floating-probe heads that can deal with
    even warped platters and/or detect a few generations of those
    overwritten magnetic domains are insanely expensive and I
    suspect only the spooks could do that now.

    There's a vid on YT somewhere about someone with a dead
    WD MYBook USB drive. For some reason, WD *encrypts* the
    (already portable) disk anybody anywhere can STILL read
    just by plugging it in. The instructor had to physically
    de-solder the teenie-tiny dedicated encryption chip from
    the old board and install it in the new. As tiny as those
    chips are it took *dexterity* ....


       Now CDs/DVDs ... just put 'em in the microwave and set it
       for five seconds. The results are VERY artistic. Lotsa
       sparks. OR, just snap 'em in half (not as fun).


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Robert Riches@21:1/5 to 25A.I866@noacba.net on Sun Feb 26 03:46:13 2023
    On 2023-02-25, 25A.I866 <25A.I866@noacba.net> wrote:
    ...
    Now CDs/DVDs ... just put 'em in the microwave and set it
    for five seconds. The results are VERY artistic. Lotsa
    sparks. OR, just snap 'em in half (not as fun).

    If snapping them in half isn't as much fun, you're not doing it
    right--if you have a little spare lumber and (non-digital)
    hardware to build a device to do the snapping:

    Ingredients:
    1. a chunk of 2x12 or 4x6 or something of around that weight
    as a base;
    2. two pieces of 2x4, each around 15 inches long
    3. four lag screws;
    4. a regular door hinge;
    5. a piece of metal rod to replace the hinge pin plus an inch
    or three on each end;
    6. a couple of mend strips or similar;
    7. screws to attach the 2x4s to the hinge;
    8. misc h/w to attach the rod to the mend strips or similar.

    Assembly:
    1. Attach the end of each piece of 2x4 to one side of the
    hinge so that the 2x4 pieces can lie flat or fold upward.
    2. Replace the hinge pin with the metal rod.
    3. Attach the mend strips or similar to hold the hinge pin
    rod high enough above the large board so the 2x4s can
    swing upward freely.
    4. Partially sink the lag screws into the 2x4s so that a
    whole optical disc can be placed in the middle of the tops
    of the lag screws.

    Use:
    1. Put on GOOD safety goggles.
    2. Work gloves are recommended.
    3. Place a disc in the middle of lag screws.
    4. Quickly pull the outer ends of the 2x4s upward.
    5. After doing as many disc as desired, try to find the
    shrapnel to dispose of it.

    Recommendation: The shattering of the discs is better if the
    temperatures are cooler to make the plastic more brittle.

    Caution: If you do more than a few dozen discs with the above
    method in a non-empty residential garage, you'll likely be
    finding little pieces of disc shrapnel in odd places for years
    thereafter.

    If fun isn't your objective, there are shredders rated to do
    optical discs, and at least the one I have works very nicely.

    --
    Robert Riches
    spamtrap42@jacob21819.net
    (Yes, that is one of my email addresses.)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25A.I866@21:1/5 to Carlos E.R. on Sat Feb 25 23:41:41 2023
    On 2/25/23 6:10 AM, Carlos E.R. wrote:
    On 2023-02-25 06:51, 25A.I866 wrote:
    On 2/19/23 6:48 AM, Carlos E.R. wrote:
    On 2023-02-19 12:13, The Natural Philosopher wrote:
    On 18/02/2023 21:18, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 13:15:31 +0000, The Natural Philosopher wrote:

    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:

    RAR was my pet hate...

    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    unrar x file.rar

    should deflate the content into the PWD.

    Today yes, not in 1993, to run on SCO Unix.

    Well, RAR for DOS appeared on 1993! :-D

    So in 1993 there wasn't a version for Linux, either.

    I believe the sources were published with version 2, or version 2
    sources were published when version 3 appeared. The wikipedia article
    doesn't have dates for these. But as soon as those sources appeared,
    anybody could compile a version for Unix.


       Always SOUNDS so simple  :-)

       I always wind up having to write fill-ins for the
       missing/very-different library routines between
       Win and Lin.

       Anyway, I'm not sure about the fascination with RAR.
       It is good, but then so are many others that are more
       modern/portable/supported.

       Found an interesting "loop-based" approach to an Str2Int64()
       today. Basically it does powers of ten on each digit (derived
       from the ASCII values of the digits minus-48). It MAY be a bit
       faster than the one I wrote the other day for Pascal that
       involves 'shrinking down' the presented number. I'll have
       to benchmark. Mine only used integer subtraction and ONE
       modulo. Not AS many steps. But, we'll see.

       I was writing a "disk visualizer" the other day (turned out
       pretty well) but Int64 numbers/functions ARE involved. Today
       I took that to write a 'C' "Disk Blaster" ... kinda like using
       'dd' to zero (or pattern-write) a whole drive but because it's
       not as complex it's about 30% quicker. Added a 'skitter' option
       that's applied AFTER the prescribed number of bytes are
       overwritten ... 'skittering' means writing yer zero/pattern
       block roughly (a little randomness added to annoy) every
       50mb on the REST of the disk area. It is not 'erasure'
       per-se, but kinda 'corrupts' and is 50x as fast. You can
       go thru a 1tb disk in an external USB3.0 fixture in about
       five minutes with 'skittering'. So, you totally obliterate
       the X-bytes you're most paranoid about and then randomly
       insert junk in the rest.

       Just gotta smooth-out the params ... there's no slack
       right now. Something like 'dd' params would be good.
       It always uses the equiv of "bs=1M" ... seems the best
       compromise after some experimentation. My visualizer
       made it easy to see if the blaster util was doing it
       right.

    I wrote a tool in pascal to write an entire device with nearly random
    data, and does so at the SATA speed of the (mechanical) disk, about 190
    MB/S last time I tried. I have done 4 TB disks.


    Free Pascal (I love Pascal) can indeed write an entire
    terabyte disk full of zeros or whatever. However what
    I discovered is that their "seek" function - despite
    docs to the contrary - seems to be only longint. So,
    you can't seek beyond 2.4gb, the counter just wraps
    into negative numbers. Even tried the 'relative' offset
    approach ... no good and a lot more counters to keep
    track of.

    Had to make a 'C' "helper" because, with some flags
    and such, you CAN lseek64(). If you just wanna melt
    a disk then FPC is ok, but if you wanna SEE/search for
    what's ON the disk at the 3.345tb mark then you have
    to cheat.

    My experimental disk was an old UServer drive. There
    WERE some recognizable passwords and such WAY out
    in the diskspace (maybe the swap partition ?)

    As I discussed with Mr. Natural, wiping an old disk
    is considered "good practice". However literally
    writing zeros or whatever over a whole 4/8/12tb
    disk can involve DAYS. Physical destruction is
    quicker. You can disassemble and save the magnets
    and pretty platters OR use a cold-chisel ....
    (WD drives. just off center at about the 8 o-clock
    position) ...

    A *fairly* easy approach is to use gparted ... create
    a new partition table and then reformat EXT2. Now it's
    faster to reformat EXT3/4 but EXT2 does a LOT more
    work redoing of the disk to it's own special, and now
    rarely-used, way. No hope for the casual hacks after that ...

    SSDs, physically destroy - the wear-leveling scheme
    thwarts the usual overwrite methods.

    CD/DVD - five secs in an old microwave. Very artistic
    results too.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 25A.I866@21:1/5 to The Natural Philosopher on Sun Feb 26 00:12:23 2023
    On 2/25/23 5:09 AM, The Natural Philosopher wrote:
    On 25/02/2023 06:15, Rich wrote:
    25A.I866 <25A.I866@noacba.net> wrote:
       FYI - I have a PILE of old HDDs ...  some just Too Old, others
       Flakey.  They NEED to be wiped, or at least quasi-wiped, before
       disposal.

    A degaussing coil is the usual method to do this, and does not
    involve disassembly nor writing Pascal or C code.

    Actually it isn't.
    In commercial cleanups of old machine rooms data centres and offices,
    the usual method is a crusher. My ex BIL in charge of IT rollouts to
    replace obsolescent kit in huge companies used to be able to get cheap machines from the recyclers, but never hard drives
    Amateurs may use a sledge hammer.

    Half-inch cold-chisel, just off-center, at about
    the 8-oClock position (WDs). One good whack. It'll
    crush two or three platters AND the head mechanism.
    Only the spooks are gonna get anything off THAT train
    wreck. If you put a hole in the top, sprinkle-in a
    little salt and water too :-)

    Some Seagate's, the 4-oClock position ...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to An experiment would be to on Sun Feb 26 20:22:48 2023
    On 2023-02-26 05:41, 25A.I866 wrote:
    On 2/25/23 6:10 AM, Carlos E.R. wrote:
    On 2023-02-25 06:51, 25A.I866 wrote:
    On 2/19/23 6:48 AM, Carlos E.R. wrote:
    On 2023-02-19 12:13, The Natural Philosopher wrote:
    On 18/02/2023 21:18, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 13:15:31 +0000, The Natural Philosopher wrote: >>>>>>>
    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:

    RAR was my pet hate...

    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    unrar x file.rar

    should deflate the content into the PWD.

    Today yes, not in 1993, to run on SCO Unix.

    Well, RAR for DOS appeared on 1993! :-D

    So in 1993 there wasn't a version for Linux, either.

    I believe the sources were published with version 2, or version 2
    sources were published when version 3 appeared. The wikipedia
    article doesn't have dates for these. But as soon as those sources
    appeared, anybody could compile a version for Unix.


       Always SOUNDS so simple  :-)

       I always wind up having to write fill-ins for the
       missing/very-different library routines between
       Win and Lin.

       Anyway, I'm not sure about the fascination with RAR.
       It is good, but then so are many others that are more
       modern/portable/supported.

       Found an interesting "loop-based" approach to an Str2Int64()
       today. Basically it does powers of ten on each digit (derived
       from the ASCII values of the digits minus-48). It MAY be a bit
       faster than the one I wrote the other day for Pascal that
       involves 'shrinking down' the presented number. I'll have
       to benchmark. Mine only used integer subtraction and ONE
       modulo. Not AS many steps. But, we'll see.

       I was writing a "disk visualizer" the other day (turned out
       pretty well) but Int64 numbers/functions ARE involved. Today
       I took that to write a 'C' "Disk Blaster" ... kinda like using
       'dd' to zero (or pattern-write) a whole drive but because it's
       not as complex it's about 30% quicker. Added a 'skitter' option
       that's applied AFTER the prescribed number of bytes are
       overwritten ... 'skittering' means writing yer zero/pattern
       block roughly (a little randomness added to annoy) every
       50mb on the REST of the disk area. It is not 'erasure'
       per-se, but kinda 'corrupts' and is 50x as fast. You can
       go thru a 1tb disk in an external USB3.0 fixture in about
       five minutes with 'skittering'. So, you totally obliterate
       the X-bytes you're most paranoid about and then randomly
       insert junk in the rest.

       Just gotta smooth-out the params ... there's no slack
       right now. Something like 'dd' params would be good.
       It always uses the equiv of "bs=1M" ... seems the best
       compromise after some experimentation. My visualizer
       made it easy to see if the blaster util was doing it
       right.

    I wrote a tool in pascal to write an entire device with nearly random
    data, and does so at the SATA speed of the (mechanical) disk, about
    190 MB/S last time I tried. I have done 4 TB disks.


      Free Pascal (I love Pascal) can indeed write an entire
      terabyte disk full of zeros or whatever. However what
      I discovered is that their "seek" function - despite
      docs to the contrary - seems to be only longint. So,
      you can't seek beyond 2.4gb, the counter just wraps
      into negative numbers. Even tried the 'relative' offset
      approach ... no good and a lot more counters to keep
      track of.

    Yes, you said so, but I have not noticed this. I may do the experiment
    the next time I get an empty hard disk and free time.

    I use this call:

    repeat

    ...


    {$I-}write(Fout,BigData[RandomIndex]);{$I+}
    gotresult:= ioresult;
    until gotresult <> 0;

    Each write writes a 1 GiB array of bytes, stored in RAM.

    where:

    const

    shuflecount = 1024;
    arraysize = 1023;
    ChunkSz=1048576;


    type
    tCacho= array [1..ChunkSz] of byte;

    var
    RandomIndex, RandomizeIndex: integer;

    BigData : array [1..shuflecount] of tCacho;

    Fin, Fout: file of tCacho;


    My notes say do not use blockread.BlockRead


    An experiment would be to write each sector with its LBA number, then
    use dd to verify.



      Had to make a 'C' "helper" because, with some flags
      and such, you CAN lseek64(). If you just wanna melt
      a disk then FPC is ok, but if you wanna SEE/search for
      what's ON the disk at the 3.345tb mark then you have
      to cheat.

      My experimental disk was an old UServer drive. There
      WERE some recognizable passwords and such WAY out
      in the diskspace (maybe the swap partition ?)

      As I discussed with Mr. Natural, wiping an old disk
      is considered "good practice". However literally
      writing zeros or whatever over a whole 4/8/12tb
      disk can involve DAYS. Physical destruction is
      quicker. You can disassemble and save the magnets
      and pretty platters OR use a cold-chisel ....
      (WD drives. just off center at about the 8 o-clock
      position) ...

      A *fairly* easy approach is to use gparted ... create
      a new partition table and then reformat EXT2. Now it's
      faster to reformat EXT3/4 but EXT2 does a LOT more
      work redoing of the disk to it's own special, and now
      rarely-used, way. No hope for the casual hacks after that ...

      SSDs, physically destroy - the wear-leveling scheme
      thwarts the usual overwrite methods.

      CD/DVD - five secs in an old microwave. Very artistic
      results too.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 28A.I873@21:1/5 to Carlos E.R. on Sun Feb 26 23:56:21 2023
    On 2/26/23 2:22 PM, Carlos E.R. wrote:
    On 2023-02-26 05:41, 25A.I866 wrote:
    On 2/25/23 6:10 AM, Carlos E.R. wrote:
    On 2023-02-25 06:51, 25A.I866 wrote:
    On 2/19/23 6:48 AM, Carlos E.R. wrote:
    On 2023-02-19 12:13, The Natural Philosopher wrote:
    On 18/02/2023 21:18, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 13:15:31 +0000, The Natural Philosopher wrote: >>>>>>>>
    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:

    RAR was my pet hate...

    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    unrar x file.rar

    should deflate the content into the PWD.

    Today yes, not in 1993, to run on SCO Unix.

    Well, RAR for DOS appeared on 1993! :-D

    So in 1993 there wasn't a version for Linux, either.

    I believe the sources were published with version 2, or version 2
    sources were published when version 3 appeared. The wikipedia
    article doesn't have dates for these. But as soon as those sources
    appeared, anybody could compile a version for Unix.


       Always SOUNDS so simple  :-)

       I always wind up having to write fill-ins for the
       missing/very-different library routines between
       Win and Lin.

       Anyway, I'm not sure about the fascination with RAR.
       It is good, but then so are many others that are more
       modern/portable/supported.

       Found an interesting "loop-based" approach to an Str2Int64()
       today. Basically it does powers of ten on each digit (derived
       from the ASCII values of the digits minus-48). It MAY be a bit
       faster than the one I wrote the other day for Pascal that
       involves 'shrinking down' the presented number. I'll have
       to benchmark. Mine only used integer subtraction and ONE
       modulo. Not AS many steps. But, we'll see.

       I was writing a "disk visualizer" the other day (turned out
       pretty well) but Int64 numbers/functions ARE involved. Today
       I took that to write a 'C' "Disk Blaster" ... kinda like using
       'dd' to zero (or pattern-write) a whole drive but because it's
       not as complex it's about 30% quicker. Added a 'skitter' option
       that's applied AFTER the prescribed number of bytes are
       overwritten ... 'skittering' means writing yer zero/pattern
       block roughly (a little randomness added to annoy) every
       50mb on the REST of the disk area. It is not 'erasure'
       per-se, but kinda 'corrupts' and is 50x as fast. You can
       go thru a 1tb disk in an external USB3.0 fixture in about
       five minutes with 'skittering'. So, you totally obliterate
       the X-bytes you're most paranoid about and then randomly
       insert junk in the rest.

       Just gotta smooth-out the params ... there's no slack
       right now. Something like 'dd' params would be good.
       It always uses the equiv of "bs=1M" ... seems the best
       compromise after some experimentation. My visualizer
       made it easy to see if the blaster util was doing it
       right.

    I wrote a tool in pascal to write an entire device with nearly random
    data, and does so at the SATA speed of the (mechanical) disk, about
    190 MB/S last time I tried. I have done 4 TB disks.


       Free Pascal (I love Pascal) can indeed write an entire
       terabyte disk full of zeros or whatever. However what
       I discovered is that their "seek" function - despite
       docs to the contrary - seems to be only longint. So,
       you can't seek beyond 2.4gb, the counter just wraps
       into negative numbers. Even tried the 'relative' offset
       approach ... no good and a lot more counters to keep
       track of.

    Yes, you said so, but I have not noticed this. I may do the experiment
    the next time I get an empty hard disk and free time.

    Please do.

    There MAY be some compiler directive in FPC, as in GCC, that
    smooths out this problem. If so I'd like to know, but a lot
    of searching didn't reveal anything.

    Anyway, I spent the past week messing around with the seek()
    problem in FPC and had to give up and run the external 'C'
    helper pgm instead.


    I use this call:

       repeat

          ...


          {$I-}write(Fout,BigData[RandomIndex]);{$I+}
          gotresult:= ioresult;
       until gotresult <> 0;

    Each write writes a 1 GiB array of bytes, stored in RAM.

    where:

    const

         shuflecount = 1024;
         arraysize = 1023;
         ChunkSz=1048576;


    type
        tCacho= array [1..ChunkSz] of byte;

    var
       RandomIndex, RandomizeIndex: integer;

       BigData : array [1..shuflecount] of tCacho;

       Fin, Fout: file of tCacho;


    My notes say do not use blockread.BlockRead


    As I hoped to say, I had no problems WRITING to int64
    sized devices. The problem was SEEKING a particular
    byte on the things. If you do a search you want to
    put up a display of EXACTLY where the match was found
    and that gets ugly if you can't do an int64 seek().
    My visualizer app also lets you manually input a
    specific int64 value (decimal or hex) and it'll pop
    you right there. I'll build another app on this to
    allow exact editing of the disk contents (more
    dangerous, of course).


    An experiment would be to write each sector with its LBA number, then
    use dd to verify.

    I can now see exactly - numeric and (as possible) ascii dumps
    to the GUI including the specific byte point on the drive.
    App-1 helped me build/debug App-2. The display kinda reminds
    of ghex, with a few extra param boxes and you can see a
    whole 512kb in one swoop in dec or hex.

    ANYway, if there's some way to make FPC do a real int64
    seek then I'd be very interested. I just don't think the
    design team ever imagined anyone wanting/needing to DO that.
    Everything was 2gb limit for SO long ... but in this case
    the "file" may be an entire 12tb drive and random access
    is required.

    DID spiff the CL for my DiskBlaster ... you can now
    specify "of=/dev/sdb" or "zap=12000000000000" bytes
    and such in any order.

    Practical note : My blaster WILL overwrite the first
    'zap=' bytes with zeros or a specified pattern. However
    the outer reaches of the disk tend to have a little data
    with a lot of zeros in there. So, if doing the shotgun
    'skitter' (or as my comment says "add jitter to the skitter")
    it is best to dump the pattern and do all zeros. That way
    it's impossible to know if the zeros were ALWAYS there or
    whether they were writ by the Blaster. So, if 'skittering'
    is enabled I just first replace any pattern in the output
    buffer with zeros "bzero(oBuf,bSz)". Anyway, about 5 minutes
    per TB with an i5 with an old USB-3.0 external drive adapter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to All on Mon Feb 27 19:26:30 2023
    On 2023-02-27 05:56, 28A.I873 wrote:
    On 2/26/23 2:22 PM, Carlos E.R. wrote:
    On 2023-02-26 05:41, 25A.I866 wrote:
    On 2/25/23 6:10 AM, Carlos E.R. wrote:
    On 2023-02-25 06:51, 25A.I866 wrote:
    On 2/19/23 6:48 AM, Carlos E.R. wrote:
    On 2023-02-19 12:13, The Natural Philosopher wrote:
    On 18/02/2023 21:18, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 13:15:31 +0000, The Natural Philosopher wrote: >>>>>>>>>
    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:

    RAR was my pet hate...

    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    unrar x file.rar

    should deflate the content into the PWD.

    Today yes, not in 1993, to run on SCO Unix.

    Well, RAR for DOS appeared on 1993! :-D

    So in 1993 there wasn't a version for Linux, either.

    I believe the sources were published with version 2, or version 2
    sources were published when version 3 appeared. The wikipedia
    article doesn't have dates for these. But as soon as those sources >>>>>> appeared, anybody could compile a version for Unix.


       Always SOUNDS so simple  :-)

       I always wind up having to write fill-ins for the
       missing/very-different library routines between
       Win and Lin.

       Anyway, I'm not sure about the fascination with RAR.
       It is good, but then so are many others that are more
       modern/portable/supported.

       Found an interesting "loop-based" approach to an Str2Int64()
       today. Basically it does powers of ten on each digit (derived
       from the ASCII values of the digits minus-48). It MAY be a bit
       faster than the one I wrote the other day for Pascal that
       involves 'shrinking down' the presented number. I'll have
       to benchmark. Mine only used integer subtraction and ONE
       modulo. Not AS many steps. But, we'll see.

       I was writing a "disk visualizer" the other day (turned out
       pretty well) but Int64 numbers/functions ARE involved. Today
       I took that to write a 'C' "Disk Blaster" ... kinda like using
       'dd' to zero (or pattern-write) a whole drive but because it's
       not as complex it's about 30% quicker. Added a 'skitter' option >>>>>    that's applied AFTER the prescribed number of bytes are
       overwritten ... 'skittering' means writing yer zero/pattern
       block roughly (a little randomness added to annoy) every
       50mb on the REST of the disk area. It is not 'erasure'
       per-se, but kinda 'corrupts' and is 50x as fast. You can
       go thru a 1tb disk in an external USB3.0 fixture in about
       five minutes with 'skittering'. So, you totally obliterate
       the X-bytes you're most paranoid about and then randomly
       insert junk in the rest.

       Just gotta smooth-out the params ... there's no slack
       right now. Something like 'dd' params would be good.
       It always uses the equiv of "bs=1M" ... seems the best
       compromise after some experimentation. My visualizer
       made it easy to see if the blaster util was doing it
       right.

    I wrote a tool in pascal to write an entire device with nearly
    random data, and does so at the SATA speed of the (mechanical) disk,
    about 190 MB/S last time I tried. I have done 4 TB disks.


       Free Pascal (I love Pascal) can indeed write an entire
       terabyte disk full of zeros or whatever. However what
       I discovered is that their "seek" function - despite
       docs to the contrary - seems to be only longint. So,
       you can't seek beyond 2.4gb, the counter just wraps
       into negative numbers. Even tried the 'relative' offset
       approach ... no good and a lot more counters to keep
       track of.

    Yes, you said so, but I have not noticed this. I may do the experiment
    the next time I get an empty hard disk and free time.

      Please do.

      There MAY be some compiler directive in FPC, as in GCC, that
      smooths out this problem. If so I'd like to know, but a lot
      of searching didn't reveal anything.

      Anyway, I spent the past week messing around with the seek()
      problem in FPC and had to give up and run the external 'C'
      helper pgm instead.

    It will not be before August that I get the time to play with a little
    project with a self made file server, and I use encrypted disks. I will
    need buying the hardware first.

    You may remind me of this in August or September ;-)


    ...

    ...
    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 28A.I873@21:1/5 to Carlos E.R. on Mon Feb 27 22:20:57 2023
    On 2/27/23 1:26 PM, Carlos E.R. wrote:
    On 2023-02-27 05:56, 28A.I873 wrote:
    On 2/26/23 2:22 PM, Carlos E.R. wrote:
    On 2023-02-26 05:41, 25A.I866 wrote:
    On 2/25/23 6:10 AM, Carlos E.R. wrote:
    On 2023-02-25 06:51, 25A.I866 wrote:
    On 2/19/23 6:48 AM, Carlos E.R. wrote:
    On 2023-02-19 12:13, The Natural Philosopher wrote:
    On 18/02/2023 21:18, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 13:15:31 +0000, The Natural Philosopher wrote: >>>>>>>>>>
    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:

    RAR was my pet hate...

    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    unrar x file.rar

    should deflate the content into the PWD.

    Today yes, not in 1993, to run on SCO Unix.

    Well, RAR for DOS appeared on 1993! :-D

    So in 1993 there wasn't a version for Linux, either.

    I believe the sources were published with version 2, or version 2 >>>>>>> sources were published when version 3 appeared. The wikipedia
    article doesn't have dates for these. But as soon as those
    sources appeared, anybody could compile a version for Unix.


       Always SOUNDS so simple  :-)

       I always wind up having to write fill-ins for the
       missing/very-different library routines between
       Win and Lin.

       Anyway, I'm not sure about the fascination with RAR.
       It is good, but then so are many others that are more
       modern/portable/supported.

       Found an interesting "loop-based" approach to an Str2Int64()
       today. Basically it does powers of ten on each digit (derived >>>>>>    from the ASCII values of the digits minus-48). It MAY be a bit >>>>>>    faster than the one I wrote the other day for Pascal that
       involves 'shrinking down' the presented number. I'll have
       to benchmark. Mine only used integer subtraction and ONE
       modulo. Not AS many steps. But, we'll see.

       I was writing a "disk visualizer" the other day (turned out
       pretty well) but Int64 numbers/functions ARE involved. Today
       I took that to write a 'C' "Disk Blaster" ... kinda like using >>>>>>    'dd' to zero (or pattern-write) a whole drive but because it's >>>>>>    not as complex it's about 30% quicker. Added a 'skitter' option >>>>>>    that's applied AFTER the prescribed number of bytes are
       overwritten ... 'skittering' means writing yer zero/pattern
       block roughly (a little randomness added to annoy) every
       50mb on the REST of the disk area. It is not 'erasure'
       per-se, but kinda 'corrupts' and is 50x as fast. You can
       go thru a 1tb disk in an external USB3.0 fixture in about
       five minutes with 'skittering'. So, you totally obliterate
       the X-bytes you're most paranoid about and then randomly
       insert junk in the rest.

       Just gotta smooth-out the params ... there's no slack
       right now. Something like 'dd' params would be good.
       It always uses the equiv of "bs=1M" ... seems the best
       compromise after some experimentation. My visualizer
       made it easy to see if the blaster util was doing it
       right.

    I wrote a tool in pascal to write an entire device with nearly
    random data, and does so at the SATA speed of the (mechanical)
    disk, about 190 MB/S last time I tried. I have done 4 TB disks.


       Free Pascal (I love Pascal) can indeed write an entire
       terabyte disk full of zeros or whatever. However what
       I discovered is that their "seek" function - despite
       docs to the contrary - seems to be only longint. So,
       you can't seek beyond 2.4gb, the counter just wraps
       into negative numbers. Even tried the 'relative' offset
       approach ... no good and a lot more counters to keep
       track of.

    Yes, you said so, but I have not noticed this. I may do the
    experiment the next time I get an empty hard disk and free time.

       Please do.

       There MAY be some compiler directive in FPC, as in GCC, that
       smooths out this problem. If so I'd like to know, but a lot
       of searching didn't reveal anything.

       Anyway, I spent the past week messing around with the seek()
       problem in FPC and had to give up and run the external 'C'
       helper pgm instead.

    It will not be before August that I get the time to play with a little project with a self made file server, and I use encrypted disks. I will
    need buying the hardware first.

    You may remind me of this in August or September ;-)

    I will keep worrying about it - I'd *like* FPC to handle
    the entire process but damned if their seek() doesn't look
    like native 32-bit instead of 64. As said somewhere, when
    seeking through, the same stuff (ClamAV virus defs) would
    start coming up again right around the 2gb mark, and
    4gb mark and ....

    Of course my app sounds rather different than yours - I'm
    writing a "disk utility" rather than a file server. At least
    files on file servers RARELY exceed the magic 32-bit length.
    The only things that get THAT bad QUICK are security-cam
    videos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rich@21:1/5 to 28A.I873@noabzba.net on Tue Feb 28 15:21:49 2023
    28A.I873 <28A.I873@noabzba.net> wrote:

    I will keep worrying about it - I'd *like* FPC to handle
    the entire process but damned if their seek() doesn't look
    like native 32-bit instead of 64.

    Given that libc (or at least glibc) built out their 64 bit file seeking
    as a separate, 64-bit, API, leaving their legacy 32-bit API untouched, presumably for compatibility sake, is it possible that FPC followed a
    similar path?

    In which case, check FPC's docs to see if they have an alternate
    "lseek" or "fseek64" or "lseek64" or some such.

    For glibc, if it is compiled for a 32-bit system, the default is the
    32-bit file offset API. C code has to add a #define to "turn on"
    64-bit support in a 32-bit environment. There is also an additional
    #define that, when also enabled, swaps the API's so that fseek() is
    really 64-bit, even on a 32-bit cpu. It is possible that FPC copied
    some of this pattern themselves and you need to enable some flag or
    compile directive in FPC to "switch to" 64-bit file offsets.

    It is also possible you need to recompile FPC itself with some flags
    set differently to gain 64-bit file seek support.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to All on Wed Mar 1 23:23:56 2023
    On 2023-02-28 04:20, 28A.I873 wrote:
    On 2/27/23 1:26 PM, Carlos E.R. wrote:
    On 2023-02-27 05:56, 28A.I873 wrote:
    On 2/26/23 2:22 PM, Carlos E.R. wrote:
    On 2023-02-26 05:41, 25A.I866 wrote:
    On 2/25/23 6:10 AM, Carlos E.R. wrote:
    On 2023-02-25 06:51, 25A.I866 wrote:
    On 2/19/23 6:48 AM, Carlos E.R. wrote:
    On 2023-02-19 12:13, The Natural Philosopher wrote:
    On 18/02/2023 21:18, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 13:15:31 +0000, The Natural Philosopher >>>>>>>>>> wrote:

    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote:

    RAR was my pet hate...

    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix.

    unrar x file.rar

    should deflate the content into the PWD.

    Today yes, not in 1993, to run on SCO Unix.

    Well, RAR for DOS appeared on 1993! :-D

    So in 1993 there wasn't a version for Linux, either.

    I believe the sources were published with version 2, or version >>>>>>>> 2 sources were published when version 3 appeared. The wikipedia >>>>>>>> article doesn't have dates for these. But as soon as those
    sources appeared, anybody could compile a version for Unix.


       Always SOUNDS so simple  :-)

       I always wind up having to write fill-ins for the
       missing/very-different library routines between
       Win and Lin.

       Anyway, I'm not sure about the fascination with RAR.
       It is good, but then so are many others that are more
       modern/portable/supported.

       Found an interesting "loop-based" approach to an Str2Int64() >>>>>>>    today. Basically it does powers of ten on each digit (derived >>>>>>>    from the ASCII values of the digits minus-48). It MAY be a bit >>>>>>>    faster than the one I wrote the other day for Pascal that
       involves 'shrinking down' the presented number. I'll have
       to benchmark. Mine only used integer subtraction and ONE
       modulo. Not AS many steps. But, we'll see.

       I was writing a "disk visualizer" the other day (turned out >>>>>>>    pretty well) but Int64 numbers/functions ARE involved. Today >>>>>>>    I took that to write a 'C' "Disk Blaster" ... kinda like using >>>>>>>    'dd' to zero (or pattern-write) a whole drive but because it's >>>>>>>    not as complex it's about 30% quicker. Added a 'skitter' option >>>>>>>    that's applied AFTER the prescribed number of bytes are
       overwritten ... 'skittering' means writing yer zero/pattern >>>>>>>    block roughly (a little randomness added to annoy) every
       50mb on the REST of the disk area. It is not 'erasure'
       per-se, but kinda 'corrupts' and is 50x as fast. You can
       go thru a 1tb disk in an external USB3.0 fixture in about
       five minutes with 'skittering'. So, you totally obliterate
       the X-bytes you're most paranoid about and then randomly
       insert junk in the rest.

       Just gotta smooth-out the params ... there's no slack
       right now. Something like 'dd' params would be good.
       It always uses the equiv of "bs=1M" ... seems the best
       compromise after some experimentation. My visualizer
       made it easy to see if the blaster util was doing it
       right.

    I wrote a tool in pascal to write an entire device with nearly
    random data, and does so at the SATA speed of the (mechanical)
    disk, about 190 MB/S last time I tried. I have done 4 TB disks.


       Free Pascal (I love Pascal) can indeed write an entire
       terabyte disk full of zeros or whatever. However what
       I discovered is that their "seek" function - despite
       docs to the contrary - seems to be only longint. So,
       you can't seek beyond 2.4gb, the counter just wraps
       into negative numbers. Even tried the 'relative' offset
       approach ... no good and a lot more counters to keep
       track of.

    Yes, you said so, but I have not noticed this. I may do the
    experiment the next time I get an empty hard disk and free time.

       Please do.

       There MAY be some compiler directive in FPC, as in GCC, that
       smooths out this problem. If so I'd like to know, but a lot
       of searching didn't reveal anything.

       Anyway, I spent the past week messing around with the seek()
       problem in FPC and had to give up and run the external 'C'
       helper pgm instead.

    It will not be before August that I get the time to play with a little
    project with a self made file server, and I use encrypted disks. I
    will need buying the hardware first.

    You may remind me of this in August or September ;-)

      I will keep worrying about it - I'd *like* FPC to handle
      the entire process but damned if their seek() doesn't look
      like native 32-bit instead of 64. As said somewhere, when
      seeking through, the same stuff (ClamAV virus defs) would
      start coming up again right around the 2gb mark, and
      4gb mark and ....

      Of course my app sounds rather different than yours - I'm
      writing a "disk utility" rather than a file server. At least
      files on file servers RARELY exceed the magic 32-bit length.
      The only things that get THAT bad QUICK are security-cam
      videos.

    Oh, no, I'm not writing a file server. I just initialize the big disk
    (raw) with almost random data, using a program from me. And the next
    time I play with it, hopefully next august, I will try to experiment if
    I truly can access it any place, 2GB, 2 TB, etc.

    Once the disk is randomized, I just encrypt it with LUKS, and format it
    as compressed btrfs. Then I implement a file server with a mini PC and
    those disks.

    :-D

    Kind of self made NAS.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From 28A.I873@21:1/5 to Carlos E.R. on Thu Mar 2 00:02:52 2023
    On 3/1/23 5:23 PM, Carlos E.R. wrote:
    On 2023-02-28 04:20, 28A.I873 wrote:
    On 2/27/23 1:26 PM, Carlos E.R. wrote:
    On 2023-02-27 05:56, 28A.I873 wrote:
    On 2/26/23 2:22 PM, Carlos E.R. wrote:
    On 2023-02-26 05:41, 25A.I866 wrote:
    On 2/25/23 6:10 AM, Carlos E.R. wrote:
    On 2023-02-25 06:51, 25A.I866 wrote:
    On 2/19/23 6:48 AM, Carlos E.R. wrote:
    On 2023-02-19 12:13, The Natural Philosopher wrote:
    On 18/02/2023 21:18, Andreas Kohlbach wrote:
    On Sat, 18 Feb 2023 13:15:31 +0000, The Natural Philosopher >>>>>>>>>>> wrote:

    On 18/02/2023 11:43, Carlos E.R. wrote:
    On 2023-02-18 11:12, The Natural Philosopher wrote: >>>>>>>>>>>>>>
    RAR was my pet hate...

    Why? :-?  :-o

    Could never find an unpacking program that ran on Unix. >>>>>>>>>>>
    unrar x file.rar

    should deflate the content into the PWD.

    Today yes, not in 1993, to run on SCO Unix.

    Well, RAR for DOS appeared on 1993! :-D

    So in 1993 there wasn't a version for Linux, either.

    I believe the sources were published with version 2, or version >>>>>>>>> 2 sources were published when version 3 appeared. The wikipedia >>>>>>>>> article doesn't have dates for these. But as soon as those
    sources appeared, anybody could compile a version for Unix.


       Always SOUNDS so simple  :-)

       I always wind up having to write fill-ins for the
       missing/very-different library routines between
       Win and Lin.

       Anyway, I'm not sure about the fascination with RAR.
       It is good, but then so are many others that are more
       modern/portable/supported.

       Found an interesting "loop-based" approach to an Str2Int64() >>>>>>>>    today. Basically it does powers of ten on each digit (derived >>>>>>>>    from the ASCII values of the digits minus-48). It MAY be a bit >>>>>>>>    faster than the one I wrote the other day for Pascal that >>>>>>>>    involves 'shrinking down' the presented number. I'll have >>>>>>>>    to benchmark. Mine only used integer subtraction and ONE
       modulo. Not AS many steps. But, we'll see.

       I was writing a "disk visualizer" the other day (turned out >>>>>>>>    pretty well) but Int64 numbers/functions ARE involved. Today >>>>>>>>    I took that to write a 'C' "Disk Blaster" ... kinda like using >>>>>>>>    'dd' to zero (or pattern-write) a whole drive but because it's >>>>>>>>    not as complex it's about 30% quicker. Added a 'skitter' option >>>>>>>>    that's applied AFTER the prescribed number of bytes are
       overwritten ... 'skittering' means writing yer zero/pattern >>>>>>>>    block roughly (a little randomness added to annoy) every
       50mb on the REST of the disk area. It is not 'erasure'
       per-se, but kinda 'corrupts' and is 50x as fast. You can
       go thru a 1tb disk in an external USB3.0 fixture in about >>>>>>>>    five minutes with 'skittering'. So, you totally obliterate >>>>>>>>    the X-bytes you're most paranoid about and then randomly
       insert junk in the rest.

       Just gotta smooth-out the params ... there's no slack
       right now. Something like 'dd' params would be good.
       It always uses the equiv of "bs=1M" ... seems the best
       compromise after some experimentation. My visualizer
       made it easy to see if the blaster util was doing it
       right.

    I wrote a tool in pascal to write an entire device with nearly
    random data, and does so at the SATA speed of the (mechanical)
    disk, about 190 MB/S last time I tried. I have done 4 TB disks.


       Free Pascal (I love Pascal) can indeed write an entire
       terabyte disk full of zeros or whatever. However what
       I discovered is that their "seek" function - despite
       docs to the contrary - seems to be only longint. So,
       you can't seek beyond 2.4gb, the counter just wraps
       into negative numbers. Even tried the 'relative' offset
       approach ... no good and a lot more counters to keep
       track of.

    Yes, you said so, but I have not noticed this. I may do the
    experiment the next time I get an empty hard disk and free time.

       Please do.

       There MAY be some compiler directive in FPC, as in GCC, that
       smooths out this problem. If so I'd like to know, but a lot
       of searching didn't reveal anything.

       Anyway, I spent the past week messing around with the seek()
       problem in FPC and had to give up and run the external 'C'
       helper pgm instead.

    It will not be before August that I get the time to play with a
    little project with a self made file server, and I use encrypted
    disks. I will need buying the hardware first.

    You may remind me of this in August or September ;-)

       I will keep worrying about it - I'd *like* FPC to handle
       the entire process but damned if their seek() doesn't look
       like native 32-bit instead of 64. As said somewhere, when
       seeking through, the same stuff (ClamAV virus defs) would
       start coming up again right around the 2gb mark, and
       4gb mark and ....

       Of course my app sounds rather different than yours - I'm
       writing a "disk utility" rather than a file server. At least
       files on file servers RARELY exceed the magic 32-bit length.
       The only things that get THAT bad QUICK are security-cam
       videos.

    Oh, no, I'm not writing a file server. I just initialize the big disk
    (raw) with almost random data, using a program from me.

    'Zactly what I just wrote. If you keep it kinda simple
    and write it in 'C' it can be notably faster than 'dd'.

    Assuming by 'initialize' you mean "overwriting everything
    important that WAS there ...".

    My parallel app is a disk "visualizer". That's in Laz/FPC.
    That's where the seek issue really came to light. However
    the 'C' fix also encouraged me to write a "disk destroyer"
    concurrently since I have so MANY old disks around (like
    a 3' stack at this point) that really ought to go to
    public auction. Need to add a "zap from the bottom" option
    though to nuke where swap parts often go.

    And the next
    time I play with it, hopefully next august, I will try to experiment if
    I truly can access it any place, 2GB, 2 TB, etc.

    There MAY be an update/upgrade by then. The DOCS say their
    seek is int64 - but, for the fairly recent versions, it
    just AIN'T.

    Oh, note that the Bullseye archives for Laz/FPC are
    DEFECTIVE. There's an illegal mix of versions. You
    have to go to the actual site and download the three
    main debs, then install in the correct order. THEN
    it works.

    Once the disk is randomized, I just encrypt it with LUKS, and format it
    as compressed btrfs. Then I implement a file server with a mini PC and
    those disks.

    I've kinda stayed away from encryption - though it DOES have
    its place. In my particular situation no disk is ever gonna
    leave the premises without me knowing about it. My concern
    about encryption is that, and the prob varies per method, even
    a single bit/byte error can trash the entire decryption process.
    Encryption where what follows is tightly based to what just was ...
    there's the most vulnerable scene.

    :-D

    Kind of self made NAS.


    Try OpenMediaVault. It's really pretty good at this point
    and a LOT easier to use than the remaining freebies. Light
    on the CPU too, it'll actually run OK on a Pi.

    Note that if you have scripts for like copying some other
    box/nas you must create TWO mountpoints - one to the other
    box and one to localhost. Otherwise the imported data does
    not "go through the OMV system" and winds up with really
    weird permissions/indexing that makes it kinda unusable.

    I have an OMV box that backs-up a commercial NAS a few times
    a day. In case the magic smoke ever escapes the commercial box
    you only have to make three(.3) minor tweaks to OMV and it becomes
    the clone of the commercial system - all users/shares/PWs/perms/
    addresses/aliases/etc and such exactly the same. Their pwecious
    little WinBoxes will never know the diff. A five-minute disaster
    fix. A good use for a decent Gen-7 board that won't run Win-11.

    The commercial box IS "nicer", and you $$$ for that, but for most
    of our uses the OMV clone will get it done very well. USED to
    use OMV as the primary NAS, so I remembered how it worked. You
    could also spend a lot of time writing smb.conf share defs and
    craft yer own NAS (been there, done that) but NAS systems make
    all that a LOT easier and more transparent/error-free.

    With RHEL it's apparently possible to create "hot fall-over"
    servers but GEEZ ... the need/complexity is WAY beyond the
    need/scope of my current org. My alternate guy has instructions
    on how to do the change-over .. it's ONE page with some
    screenshots... the other six pages are 'technical' notes, the
    lower-level background on how it all works. I hope to
    enhance his understanding ....

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)