On 4/20/21 5:37 AM, Yi-yo Chiang wrote:
> Interesting. Probably because our previous for-loop takes input from regular
> file. The GNU implementation seems to treat only special files (block and char
> devices) differently as a "magnetic tape".
Ah. The test infrastructure is already doing echo ""
Interesting. Probably because our previous for-loop takes input from
regular file. The GNU implementation seems to treat only special files
(block and char devices) differently as a "magnetic tape".
On Tue, Apr 20, 2021 at 5:33 PM Rob Landley wrote:
> On 4/20/21 3:23 AM, Yi-yo Chiang via Toybox
On 4/20/21 3:23 AM, Yi-yo Chiang via Toybox wrote:
> Why do we need setsid in the new cpio testcase though?
Because without it TEST_HOST=1 calls the gnu/dammit cpio which does:
$ cpio -i < /dev/null
Found end of tape. To continue, type device/file name when ready.
And then hangs waiting for
On 4/19/21 4:22 PM, enh via Toybox wrote:
> I've been using hexedit quite a lot, mainly for _corrupting_ files, and
> have been meaning to send this collection of changes for far too long
> now. I saw a bug requesting editing in the ASCII pane (which this patch
> _doesn't_ add), and wanted to get t
Why do we need setsid in the new cpio testcase though?
On Tue, Apr 20, 2021 at 3:50 AM enh via Toybox
wrote:
> The new cpio test that uses setsid fails if you're using the toybox
> setsid. Move the setpgrp() call before the vfork() but after the
> setsid().
> ---
> toys/other/setsid.c | 9 +
On 4/18/21 9:03 PM, scsijon wrote:
> Just wondering what the status is for the init currently in pending please?
> I've got a linux microbuild underway that currently works with busybox and
> uses
> busybox's init to run and I would like to at least create a test build with
> toybox as it looks li
