On 12/17/20 10:07 PM, Andre McCurdy wrote:
On Thu, Dec 17, 2020 at 7:52 PM Khem Raj wrote:
On Thu, Dec 17, 2020 at 3:59 PM Andre McCurdy wrote:
On Thu, Dec 17, 2020 at 2:54 PM Khem Raj wrote:
When busybox is used for device management, kernel needs to support
older/obsolete mechanism v
On Thu, Dec 17, 2020 at 7:52 PM Khem Raj wrote:
>
> On Thu, Dec 17, 2020 at 3:59 PM Andre McCurdy wrote:
> >
> > On Thu, Dec 17, 2020 at 2:54 PM Khem Raj wrote:
> > >
> > > When busybox is used for device management, kernel needs to support
> > > older/obsolete mechanism via CONFIG_UEVENT_HELPER
On Thu, Dec 17, 2020 at 3:59 PM Andre McCurdy wrote:
>
> On Thu, Dec 17, 2020 at 2:54 PM Khem Raj wrote:
> >
> > When busybox is used for device management, kernel needs to support
> > older/obsolete mechanism via CONFIG_UEVENT_HELPER and
> > CONFIG_UEVENT_HELPER_PATH to enable /proc/sys/kernel/h
Afaik, running a daemon in foreground mode and instructing start-stop-daemon to
background it is common practice if the daemon doesn’t support writing a
pidfile itself, so start-stop-daemon can handle it itself. Without using
foregrounded process + -b, it wouldn’t know the resulting process id.
On Thu, Dec 17, 2020 at 2:54 PM Khem Raj wrote:
>
> When busybox is used for device management, kernel needs to support
> older/obsolete mechanism via CONFIG_UEVENT_HELPER and
> CONFIG_UEVENT_HELPER_PATH to enable /proc/sys/kernel/hotplug but this
> would require kernel defconfig change and will a
When busybox is used for device management, kernel needs to support
older/obsolete mechanism via CONFIG_UEVENT_HELPER and
CONFIG_UEVENT_HELPER_PATH to enable /proc/sys/kernel/hotplug but this
would require kernel defconfig change and will always be needed when
mdev is used, intead run it in daemon
