From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] zsh: security bump to version 5.0.7
Date: Wed, 08 Oct 2014 20:42:45 +0200 [thread overview]
Message-ID: <8738aycsii.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <54357611.2050005@zacarias.com.ar> (Gustavo Zacarias's message of "Wed, 08 Oct 2014 14:36:17 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Hi,
>> Same comment as for dash, who should "win" the /bin/sh symlink?
>>
>> maybe busybox -> dash -> zsh -> bash?
> Forgot to cc the list ;)
Ups, apparently - Sorry.
> It's not really/only a matter of which one wins, it's an init system
> nightmare that i'm solving.
> Say you've got:
> busybox-init + some better shell = the better shell should win.
Agreed.
> sysvinit + busybox + some better shell = same as above
Agreed.
> sysvinit + no busybox + some better shell = oops since there's no /bin/sh
As long as all shells install a /bin/sh (symlink), that should be fine -
But it should also be reproducible, so with a fixed priority.
> I don't care which of the better is "betterer", it's pretty subjective,
> i just want the crazy combinations to work :)
> Of course there's sysvinit + no busybox + no shell but that's another
> problem.
Such a setup is pretty unlikely to ever happen on purpose imho.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-10-08 18:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 13:19 [Buildroot] [PATCH 1/5] dash: bump to version 0.5.8-1 Gustavo Zacarias
2014-10-08 13:19 ` [Buildroot] [PATCH 2/5] zsh: security bump to version 5.0.7 Gustavo Zacarias
[not found] ` <87a956eadv.fsf@dell.be.48ers.dk>
2014-10-08 17:36 ` Gustavo Zacarias
2014-10-08 18:42 ` Peter Korsgaard [this message]
2014-10-12 10:50 ` Peter Korsgaard
2014-10-08 13:19 ` [Buildroot] [PATCH 3/5] bash: minor install tweaks Gustavo Zacarias
2014-10-08 17:32 ` Peter Korsgaard
2014-10-08 13:19 ` [Buildroot] [PATCH 4/5] procps-ng: bump to version 3.3.10 Gustavo Zacarias
2014-10-08 17:32 ` Peter Korsgaard
2014-10-08 13:19 ` [Buildroot] [PATCH 5/5] sysklogd: security bump to version 1.5.1 Gustavo Zacarias
2014-10-08 17:36 ` Peter Korsgaard
2014-10-08 17:27 ` [Buildroot] [PATCH 1/5] dash: bump to version 0.5.8-1 Peter Korsgaard
2014-10-08 17:29 ` Gustavo Zacarias
2014-10-08 18:05 ` Peter Korsgaard
2014-10-08 18:21 ` Gustavo Zacarias
2014-10-08 18:46 ` Peter Korsgaard
2014-10-08 19:16 ` Gustavo Zacarias
2014-10-11 14:28 ` Arnout Vandecappelle
2014-10-12 10:50 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738aycsii.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox