[PATCH] ln: --no-target-directory implies --no-dereference

as in GNU coreutils --- coreutils/ln.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/coreutils/ln.c b/coreutils/ln.c index ea2d10eab..f2a1941b9 100644 --- a/coreutils/ln.c +++ b/coreutils/ln.c @@ -85,10 +85,7 @@ int ln_main(int argc, char **argv) src_name

[PATCH] ip: print dadfailed flag

Signed-off-by: Kaarle Ritvanen --- networking/libiproute/ipaddress.c | 4 1 file changed, 4 insertions(+) diff --git a/networking/libiproute/ipaddress.c b/networking/libiproute/ipaddress.c index 9ec665b69..d088caf4c 100644 --- a/networking/libiproute/ipaddress.c +++ b/networking

[PATCH] ifupdown: do not fail if interface disappears during ifdown

Interface may not exist because it got deleted by an ifdown hook script earlier. This may happen when a virtual interface, such as VLAN, has multiple iface blocks defined. Signed-off-by: Kaarle Ritvanen <kaarle.ritva...@datakunkku.fi> --- networking/ifupdown.c | 3 +++ 1 file chan

Re: [PATCH 3/3] ash: exec: -a option for setting zeroth arg

On Wed, 12 Apr 2017, Denys Vlasenko wrote: > I committed a change which implements "exec -a" > in a slightly different way. Please try current git. Works for me. Thanks a lot! BR, Kaarle ___ busybox mailing list busybox@busybox.net

Re: [PATCH 3/3] ash: exec: -a option for setting zeroth arg

On Wed, 12 Apr 2017, Kang-Che Sung wrote: > Back in January 2017, a person named Patrick Pief has suggested a similar > patch > to add "exec -a" support: > > http://lists.busybox.net/pipermail/busybox/2017-January/085146.html > > Is your patch same as his or is there any difference? My patch

[PATCH 2/3] ash: shellexec: rename variable

Signed-off-by: Kaarle Ritvanen <kaarle.ritva...@datakunkku.fi> --- shell/ash.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/shell/ash.c b/shell/ash.c index 983f7b1..58ae950 100644 --- a/shell/ash.c +++ b/shell/ash.c @@ -7748,7 +7748,7 @@ static void shellexe

[PATCH 1/3] libbb: GETOPT_RESET macro

Signed-off-by: Kaarle Ritvanen <kaarle.ritva...@datakunkku.fi> --- include/libbb.h| 19 +++ libbb/getopt32.c | 8 +--- libbb/vfork_daemon_rexec.c | 28 ++-- runit/sv.c | 7 +-- shell/shell_common.c

[PATCH 0/3] ash: exec: -a option for setting zeroth arg

-- (add/remove: 0/0 grow/shrink: 3/0 up/down: 99/0) Total: 99 bytes Kaarle Ritvanen (3): libbb: GETOPT_RESET macro ash: shellexec: rename variable ash: exec: -a option for setting zeroth arg include/libbb.h

[PATCH 3/3] ash: exec: -a option for setting zeroth arg

Signed-off-by: Kaarle Ritvanen <kaarle.ritva...@datakunkku.fi> --- shell/ash.c | 42 -- 1 file changed, 32 insertions(+), 10 deletions(-) diff --git a/shell/ash.c b/shell/ash.c index 58ae950..b799b85 100644 --- a/shell/ash.c +++ b/shell/ash.c @@ -

[PATCH] ntpd: postpone hostname resolution if fails on startup

Signed-off-by: Kaarle Ritvanen <kaarle.ritva...@datakunkku.fi> --- function old new delta resolve_peer_hostname - 85 +85 static.set_next- 23 +23 ste

[PATCH 0/3] su: FEATURE_SU_NULLOK_SECURE

: 4/1 up/down: 147/-129) Total: 18 bytes Kaarle Ritvanen (3): login: move check_securetty to libbb libbb: allow_blank argument for ask_and_check_password_extended() su: FEATURE_SU_NULLOK_SECURE include/libbb.h | 3 ++- libbb/Kbuild.src | 1 + libbb

[PATCH 1/3] login: move check_securetty to libbb

Signed-off-by: Kaarle Ritvanen <kaarle.ritva...@datakunkku.fi> --- include/libbb.h| 1 + libbb/Kbuild.src | 1 + libbb/securetty.c | 27 +++ loginutils/login.c | 19 --- 4 files changed, 29 insertions(+), 19 deletions(-) create mode 100644

[PATCH 2/3] libbb: allow_blank argument for ask_and_check_password_extended()

Signed-off-by: Kaarle Ritvanen <kaarle.ritva...@datakunkku.fi> --- include/libbb.h | 2 +- libbb/correct_password.c | 6 +++--- loginutils/sulogin.c | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/include/libbb.h b/include/libbb.h index e607b8f..4c43c72

[PATCH 3/3] su: FEATURE_SU_NULLOK_SECURE

When this feature is enabled, blank passwords are not accepted by su unless the user is on a secure TTY defined in /etc/securetty. This resembles the default PAM configuration of some Linux distros which specify the nullok_secure option for pam_unix.so. Signed-off-by: Kaarle Ritvanen

[PATCH 2/3] libbb: allow_blank argument for ask_and_check_password_extended()

--- include/libbb.h | 2 +- libbb/correct_password.c | 6 +++--- loginutils/sulogin.c | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/include/libbb.h b/include/libbb.h index e607b8f..4c43c72 100644 --- a/include/libbb.h +++ b/include/libbb.h @@ -1356,7 +1356,7

[PATCH 1/3] login: move check_securetty to libbb

--- include/libbb.h| 1 + libbb/Kbuild.src | 1 + libbb/securetty.c | 27 +++ loginutils/login.c | 19 --- 4 files changed, 29 insertions(+), 19 deletions(-) create mode 100644 libbb/securetty.c diff --git a/include/libbb.h b/include/libbb.h

[PATCH 3/3] su: FEATURE_SU_NULLOK_SECURE

When this feature is enabled, blank passwords are not accepted by su unless the user is on a secure TTY defined in /etc/securetty. This resembles the default PAM configuration of some Linux distros which specify the nullok_secure option for pam_unix.so. --- loginutils/su.c | 18 +-

Re: [PATCH] su: support denying accounts with blank password

On Wed, 10 Jun 2015, Timo Teras wrote: > On Tue, 09 Jun 2015 22:20:30 +0200 > Laurent Bercot wrote: > > > IOW, if a computer gets hacked because its root password was > > blank or default, it's not a problem you can solve by choosing > > the other solution. :) > >

Re: [PATCH v2] sendmail: automatically determine sender if not specified

On Wed, 5 Feb 2014, Denys Vlasenko wrote: I just committed the following change: http://git.busybox.net/busybox/commit/?id=07f417b6ab92e0429f302ff6783bb9681b60120e but I'm unsure it is good enough for your use case. This is probably good enough for the use case I have now at hand because

[PATCH] sendmail: use FQDN in default envelope sender

RFC 5321 requires the return path to be supplied with a proper domain name. Signed-off-by: Kaarle Ritvanen kaarle.ritva...@datakunkku.fi --- mailutils/sendmail.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/mailutils/sendmail.c b/mailutils/sendmail.c index 824109d

Re: Interworking of cron and sendmail applets

On Tue, 4 Feb 2014, Denys Vlasenko wrote: I am looking at Fedora's man sendmail and it says that -fSENDER is optional. When it's absent, sender is derived from From: header. Verbatim quote from the man page: Sets the name of the 'from' person (i.e., the envelope sender of the mail). This

[PATCH] sendmail: automatically determine sender if not specified

Make the -f option optional. If not given, construct the sender address from the username and fully qualified hostname. This is required to interoperate with the cron applet. --- mailutils/sendmail.c | 16 +++- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git

Re: Interworking of cron and sendmail applets

On Tue, 21 Jan 2014, Harald Becker wrote: Beside modifying the Busybox binary, you can create a script file for sendmail: #!/bin/sh exec /bin/busybox sendmail -f ... $@ install this script as your sendmail and make it executable (chmod +x). Then cron shall pickup this script for sendmail and

Re: [PATCH] ifupdown: support 'link' address family

On Sun, 29 Dec 2013, Kaarle Ritvanen wrote: Does not configure anything. L2 configuration hook scripts should do their job on receiving ADDRFAM=link. Configuration will be done only once, irrespective of L3 protocols used. Using the 'link' family in the interfaces file conforms to the Debian

[PATCH] ifupdown: support 'link' address family

/ifupdown/0.7.47.1/link.defn Signed-off-by: Kaarle Ritvanen kaarle.ritva...@datakunkku.fi --- networking/ifupdown.c | 13 + 1 file changed, 13 insertions(+) diff --git a/networking/ifupdown.c b/networking/ifupdown.c index 0f0857c..91a786d 100644 --- a/networking/ifupdown.c +++ b