From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dropbear: add vfork fix
Date: Wed, 03 Apr 2013 23:00:31 +0200 [thread overview]
Message-ID: <871uar5nyo.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <515C95A6.7090203@zacarias.com.ar> (Gustavo Zacarias's message of "Wed, 03 Apr 2013 17:48:38 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Gustavo> On 04/03/2013 05:47 PM, Peter Korsgaard wrote:
>> Do we need the /dev/urandom write fix as well?
Gustavo> I don't think so, we default to 0666 for it in the device table...
Gustavo> Regards.
Ok, great.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-04-03 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 22:29 [Buildroot] [PATCH] dropbear: add vfork fix Gustavo Zacarias
2013-04-03 20:47 ` Peter Korsgaard
2013-04-03 20:48 ` Gustavo Zacarias
2013-04-03 21:00 ` Peter Korsgaard [this message]
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=871uar5nyo.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