From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/dropbear
Date: Tue, 08 Apr 2008 20:59:02 +0200 [thread overview]
Message-ID: <87abk4i361.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20080408174730.2CAEB3C379@busybox.net> (nkukard@uclibc.org's message of "Tue\, 8 Apr 2008 10\:47\:30 -0700 \(PDT\)")
>>>>> "nkukard" == nkukard <nkukard@uclibc.org> writes:
nkukard> Author: nkukard
nkukard> Date: 2008-04-08 10:47:29 -0700 (Tue, 08 Apr 2008)
nkukard> New Revision: 21673
nkukard> Log:
nkukard> * Generate keys for dropbear only when starting
nkukard> * Generate keys silently
Is that good? Generating keys takes a LONG time on most embedded
systems, so having a bit of feedback would be good.
nkukard> Modified:
nkukard> trunk/buildroot/package/dropbear/dropbear-init.patch
Having this init script as a patch is kinda silly, let's simply add it
under package/dropbear and copy it over to TARGET_DIR, E.G. like it's
done for avahi.
(Yes, I know you didn't add the patch in the first place).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-04-08 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 17:47 [Buildroot] svn commit: trunk/buildroot/package/dropbear nkukard at uclibc.org
2008-04-08 18:59 ` Peter Korsgaard [this message]
2008-04-08 19:17 ` Nigel Kukard
2008-04-08 19:32 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2008-11-14 11:06 correa at uclibc.org
2008-11-14 8:47 jacmet at uclibc.org
2008-06-30 13:35 jacmet at uclibc.org
2008-04-09 7:35 nkukard at uclibc.org
2008-04-09 22:33 ` Hamish Moffatt
2008-04-10 7:03 ` Peter Korsgaard
2008-03-27 15:59 jacmet at uclibc.org
2007-09-19 14:11 aldot at uclibc.org
2007-08-11 18:43 ulf at uclibc.org
2007-04-24 13:42 jacmet at uclibc.org
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=87abk4i361.fsf@macbook.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.