From: Nigel Kukard <nkukard@lbsd.net>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/dropbear
Date: Tue, 08 Apr 2008 19:17:22 +0000 [thread overview]
Message-ID: <1207682242.6817.277.camel@nigel-x60> (raw)
In-Reply-To: <87abk4i361.fsf@macbook.be.48ers.dk>
> Is that good? Generating keys takes a LONG time on most embedded
> systems, so having a bit of feedback would be good.
I can add something about generating keys on the same line?
Staring dropbear sshd: generating host keys...OK
how does that look? normal startup would be...
Starting dropbear sshd: OK
> 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).
Duly noted, will add in my next commit together with a fix for the
above.
-N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://busybox.net/lists/buildroot/attachments/20080408/caa944a0/attachment.pgp
next prev parent reply other threads:[~2008-04-08 19:17 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
2008-04-08 19:17 ` Nigel Kukard [this message]
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=1207682242.6817.277.camel@nigel-x60 \
--to=nkukard@lbsd.net \
--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