Hi busybox folks!
I have discovered a situation on a particularly slow
device where the system's init (openrc) is starting busybox acpid
BEFORE the kernel is done loading modules for devices. This results in
a race between my input device initializing (and creating itself in
/dev/input/eventN) and
inotify would be a good way to address this I would think. It looks
like other applets in BB are using it.
-Clayton
On Thu, Jul 20, 2017 at 09:45:53AM +0300, Lauri Kasanen wrote:
Hi,
Big acpid seems to use inotify on /dev/input. Or perhaps you can set up
an udev rule that sends a signal to acp
This fixes a problem where the contents of the previous line were output
when the previous line was long enough to cause buf to be extended.
The buffer is re-used/rewritten for each line, instead of appending to it.
---
util-linux/rev.c | 13 +++--
1 file changed, 7 insertions(+), 6 deleti
I tried to report this to bugzilla but recieved the
following error:
Invalid Content-Type 'subtype' parameter at Bugzilla/BugMail.pm line 471.
Clayton Craft (1):
rev: handle cases where lines are too long for buffer
util-linux/rev.c | 13 +++--
1 file changed, 7 inser
On Mon, 09 Aug 2021 21:57:00 +0100 Ron Yorston wrote:
> Or how about this?
>
> Ron
> ---
> util-linux/rev.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/util-linux/rev.c b/util-linux/rev.c
> index d439b4da8..63b005c67 100644
> --- a/util-linux/rev.c
> +++ b/util-linux/rev.c
> @@ -10
On Wed, 23 Oct 2024 15:11:20 +0200 Natanael Copa
wrote:
> I git bisected the bug to:
> commit e2287f99fe6f21fd6435ad04340170ad4ba5f6b3
I found that if this one byte is reverted from the patch you blamed, then your
test passes:
diff --git a/libbb/dump.c b/libbb/dump.c
index b406a2428..92b0d762c
On Thur, 24 Oct 2024 08:32:58 UTC David Laight wrote:
> On Wed, 23 Oct 2024 15:11:20 +0200 Natanael Copa
> wrote:
> > - byte_count_str = "\010\004\002\001";
> > + byte_count_str = "\004\002\001";
>
> Without actually checking is that a
