Re: crc16
Quoting Grzesiek Sójka (2019-09-11 11:37:11) > Is there any utility to calculate crc16 (not the crc32) in Debian? Yes. For command-line use: jacksum radare2 node-crc libdigest-crc-perl: python3-crcelk python3-crcmod tcllib Latter part above are not really utilities, but can probably all of them be used for oneliners - like this: echo foobar|perl -MDigest::CRC=crc16 -nE'chomp;say "$_: ", crc16($_)' - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: crc16
Hello, On Wed, Sep 11, 2019 at 11:37:11AM +0200, Grzesiek Sójka wrote: > Is there any utility to calculate crc16 (not the crc32) in Debian? It should be trivial in almost any scripting language available in Debian. Here is a Perl example. $ sudo apt install libdigest-crc-perl Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: libdigest-crc-perl 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 14.2 kB of archives. After this operation, 51.2 kB of additional disk space will be used. Get:1 http://deb.debian.org/debian buster/main amd64 libdigest-crc-perl amd64 0.22.2-1+b1 [14.2 kB] Fetched 14.2 kB in 0s (93.0 kB/s) Selecting previously unselected package libdigest-crc-perl. (Reading database ... 127754 files and directories currently installed.) Preparing to unpack .../libdigest-crc-perl_0.22.2-1+b1_amd64.deb ... Unpacking libdigest-crc-perl (0.22.2-1+b1) ... Setting up libdigest-crc-perl (0.22.2-1+b1) ... Processing triggers for man-db (2.8.5-2) ... $ perl -MDigest::CRC -e '$ctx = Digest::CRC->new(type=>"crc16"); $ctx->addfile(*STDIN); print $ctx->b64digest' < /etc/os-release lzA= Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: crc16
On 2019-09-11, Curt wrote: > On 2019-09-11, Grzesiek Sójka wrote: >> Hi there, >> >> Is there any utility to calculate crc16 (not the crc32) in Debian? > > > curty@einstein:~$ apt-cache search crc16 > node-crc - module for calculating Cyclic Redundancy Check (CRC) On second thought, maybe it's wiser to install 'python-crcmod' (available from the repositories, I believe). http://crcmod.sourceforge.net/crcmod.html >> Thanks in advance for any help >> >> > > -- Thug: This is a stickup! Now come on. Your money or your life. [long pause] Thug: [repeating] Look, bud, I said, 'Your money or your life.' Jack Benny: I'm thinking, I'm thinking!
Re: crc16
On 2019-09-11, Grzesiek Sójka wrote: > Hi there, > > Is there any utility to calculate crc16 (not the crc32) in Debian? curty@einstein:~$ apt-cache search crc16 node-crc - module for calculating Cyclic Redundancy Check (CRC) > Thanks in advance for any help > > -- Thug: This is a stickup! Now come on. Your money or your life. [long pause] Thug: [repeating] Look, bud, I said, 'Your money or your life.' Jack Benny: I'm thinking, I'm thinking!
crc16
Hi there, Is there any utility to calculate crc16 (not the crc32) in Debian? Thanks in advance for any help
Got a ccl : lib/crc16.mod.c : Input/output error when compiling the 2.6.16.14 kernel
Hi everyone, I was running a custom 2.4 kernel on my laptop (Dell Inspiron 4000; P3 800Mhz) and recently decided to upgrade it to the most recent 2.6 kernel (2.6.16.14 from www.kernel.org). It compiled successfully, however after rebooting with the new kernel, I realized my laptop didn't have any PCMCIA support. Checking the options again, I realized that in the 2.6 kernel, the option for PCMCIA support was off by default. I thought "no problem, I'll just enable it and recompile". So under the heading "Bus options (PCI, PCMCIA, EISA, MCA, ISA)", I enabled PCCard (PCMCIA / CardBus) support which included: 16-bit PCMCIA support 32-bit CardBus support i82092 compatible bridge support i82365 compatible bridge support Databook TCIC host bridge support I began recompiling and some time later I got the error: ccl : lib/crc16.mod.c : Input/output error Does anybody know why it happened? I'm guessing it's probably because of the PCCard support option that I enabled, but I don't see why. Thanks, -Glen -- Glen Yu | 416-739-4861 | [EMAIL PROTECTED] --
