[PATCH 1/1] switch_root: When console doesn't exist don't bail out

Busybox is very often used in initramfs at the end of which usually there is a switch_root to the actual rootfs. There are many cases where the console kernel argument is either just a placeholder (for example RaspberryPi uses serial0 and serial1) or configured as null to avoid any console

Re: mdev change no longer supporting v2.6.2x kernels by using /sys/dev

Mattias Schlenker wrote: Am 23.03.2017 um 17:32 schrieb Ralf Friedl: Busybox is often used in embedded devices, where kernels (and other software) are not changed that often. Firmware may contain kernel modules without full source, so a change to a newer kernel is not an option. As an

Re: mdev change no longer supporting v2.6.2x kernels by using /sys/dev

Am 23.03.2017 um 17:32 schrieb Ralf Friedl: Busybox is often used in embedded devices, where kernels (and other software) are not changed that often. Firmware may contain kernel modules without full source, so a change to a newer kernel is not an option. As an example, I have a router with

Re: Busybox httpd sends output of stderr to the Website

inetd is tying stdout and stderr together. Personally I think this is wrong since it generally means that inetd services must be careful never to write to stderr. Use tcpserver instead of inetd. It allows you to use the "inetd mode" in applets, and does not exhibit the problems that inetd

Re: init - sysvinit vs BusyBox

On Sun, Mar 19, 2017 at 9:03 PM, Shay Hofman wrote: > A novice question - > > Is it possible to tweak and change busybox on an existing embedded device? > To be exact I'm referring to Dlink home router device which has a very > limited and stripped down busybox os. > Very

Re: AW: Busybox httpd sends output of stderr to the Website

On Thursday 23 March 2017 07:51:05 Dirk Lohse wrote: > A workaround for me is to not use inetd mode. But the reason for this > behavior should be found and fixed - I think. If not httpd does this, could it be that inetd maps stdout & stderr both to stdout before forking itself into httpd? That

Re: mdev change no longer supporting v2.6.2x kernels by using /sys/dev

Peter Korsgaard wrote: "Richard" == Richard Moore writes: > Hi, > Would it be possible to please make the recent mdev change in v1.26 an > option? > * mdev (mdev: create devices from /sys/dev) commit 20a3262 (Sep 7, 2016) > I am stuck with a v2.6.2x kernel and I am

Re: [PATCH] add paste implementation

On Tue, Mar 21, 2017 at 7:00 PM, Maxime Coste wrote: > Hello, > > Any update on this ? > > Here is the latest version of the patch, still waiting on a clear decision > regarding loop variable definition location. Applied this version. Please review. Thanks! /* vi: set sw=4

Re: mdev change no longer supporting v2.6.2x kernels by using /sys/dev

> "Richard" == Richard Moore writes: > Hi, > Would it be possible to please make the recent mdev change in v1.26 an > option? > * mdev (mdev: create devices from /sys/dev) commit 20a3262 (Sep 7, 2016) > I am stuck with a v2.6.2x kernel and I am sure other people must

mdev change no longer supporting v2.6.2x kernels by using /sys/dev

Hi, Would it be possible to please make the recent mdev change in v1.26 an option? * mdev (mdev: create devices from /sys/dev) commit 20a3262 (Sep 7, 2016) I am stuck with a v2.6.2x kernel and I am sure other people must be too who have no /sys/dev support in their kernel ? Cheers Rich

Re: Busybox httpd sends output of stderr to the Website

> On 23 Mar 2017, at 5:51 PM, Dirk Lohse wrote: > > A workaround for me is to not use inetd mode. But the reason for this > behavior should be found and fixed - I think. > > Dirk > See networking/inetd.c: /* manpages of inetd I managed to find either say

AW: Busybox httpd sends output of stderr to the Website

A workaround for me is to not use inetd mode. But the reason for this behavior should be found and fixed - I think. Dirk -Ursprüngliche Nachricht- Von: Guillermo Rodriguez Garcia [mailto:guille.rodrig...@gmail.com] Gesendet: Mittwoch, 22. März 2017 18:40 An: Dirk Lohse Cc: