From: "Cédric Le Goater" <clg@fr.ibm.com>
To: OpenBMC Patches <openbmc-patches@stwcx.xyz>, openbmc@lists.ozlabs.org
Subject: Re: [PATCH openbmc 0/3] Re-enable obmc-console and add a ssh endpoint
Date: Thu, 14 Apr 2016 16:15:13 +0200 [thread overview]
Message-ID: <570FA5F1.1020201@fr.ibm.com> (raw)
In-Reply-To: <1460615435-26806-1-git-send-email-openbmc-patches@stwcx.xyz>
Hello,
I tried it on a palmetto. Very nice. This is perfect for me.
For my education on the topic, what are the plans for the OpenBMC
host console ? Is obmc-console a temporary or a final solution ?
May be adding websockets would provide an easier integration in
a www ui.
Thanks.
C.
On 04/14/2016 08:30 AM, OpenBMC Patches wrote:
> Following the previous disable, this bumps us to a working obmc-console version, and adds infrastructure for a ssh-based remote console connection.
>
> <!-- Reviewable:start -->
> ---
> This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/openbmc/openbmc/232)
> <!-- Reviewable:end -->
>
>
> https://github.com/openbmc/openbmc/pull/232
>
> Jeremy Kerr (3):
> Enable obmc-console project
> dropbear: Add patch for -c <command> option to dropbear
> obmc-console: Add ssh endpoint
>
> meta-phosphor/classes/obmc-phosphor-image.bbclass | 1 +
> ...d-c-command-option-to-force-a-specific-co.patch | 91 ++++++++++++++++++++++
> .../recipes-core/dropbear/dropbear_%.bbappend | 3 +-
> .../recipes-phosphor/obmc-console/obmc-console.bb | 22 +++++-
> .../obmc-console/obmc-console-ssh.socket | 11 +++
> .../obmc-console/obmc-console-ssh@.service | 11 +++
> 6 files changed, 136 insertions(+), 3 deletions(-)
> create mode 100644 meta-phosphor/common/recipes-core/dropbear/dropbear/0001-dropbear-Add-c-command-option-to-force-a-specific-co.patch
> create mode 100644 meta-phosphor/common/recipes-phosphor/obmc-console/obmc-console/obmc-console-ssh.socket
> create mode 100644 meta-phosphor/common/recipes-phosphor/obmc-console/obmc-console/obmc-console-ssh@.service
>
next prev parent reply other threads:[~2016-04-14 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 6:30 [PATCH openbmc 0/3] Re-enable obmc-console and add a ssh endpoint OpenBMC Patches
2016-04-14 6:30 ` [PATCH openbmc 1/3] Enable obmc-console project OpenBMC Patches
2016-04-14 6:30 ` [PATCH openbmc 2/3] dropbear: Add patch for -c <command> option to dropbear OpenBMC Patches
2016-04-14 6:30 ` [PATCH openbmc 3/3] obmc-console: Add ssh endpoint OpenBMC Patches
2016-04-14 14:15 ` Cédric Le Goater [this message]
2016-04-15 8:29 ` [PATCH openbmc 0/3] Re-enable obmc-console and add a " Jeremy Kerr
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=570FA5F1.1020201@fr.ibm.com \
--to=clg@fr.ibm.com \
--cc=openbmc-patches@stwcx.xyz \
--cc=openbmc@lists.ozlabs.org \
/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.