[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Help fixing NativeMessaging host: read 32-bit message length in nati
From: |
Greg Wooledge |
Subject: |
Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order |
Date: |
Sat, 24 Jun 2023 20:39:02 -0400 |
On Sat, Jun 24, 2023 at 05:06:23PM -0700, guest271314 wrote:
> I am not privy to the all of the gory details of Linux versus GNU/Core
> Utilities other than the threads I have read on the subject-matter.
> Politics.
Nobody is talking about "politics" here.
> When you suggest to stick with using dd, my reply is the same as I
> previously stated: dd didn't work in this case.
>
> It would help if you actually tried the code you suggested, so you can
> reproduce the code I wrote and verify your own claims - more importantly,
> so I can verify your claims.
unicorn:~$ seq 1865 | { head -n1; cat; }
1
1861
1862
1863
1864
1865
unicorn:~$ seq 1865 | { dd bs=2 count=1 2>/dev/null; cat; }
1
2
3
4
[...]
> I am not sure what you mean by "portable"? Use Chimera Linux. Busybox, and
> not the default Bash shell shipped on *buntu distributions?
There are systems that aren't GNU/Linux. Mac OS X, FreeBSD, OpenBSD,
Solaris, AIX, etc. "Portable" means the code should work on all of these,
and more.
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, (continued)
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order,
Greg Wooledge <=
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Lawrence Velázquez, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Lawrence Velázquez, 2023/06/25
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/25