All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] isar error log
Date: Fri, 12 Apr 2019 12:59:57 +0100	[thread overview]
Message-ID: <1555070397.3557.19.camel@codethink.co.uk> (raw)
In-Reply-To: <20190412133736.5f3b257f@md1za8fc.ad001.siemens.net>

On Fri, 2019-04-12 at 13:37 +0200, Henning Schild wrote:
[...]
> Just had a look at a ubuntu 16.04. It does support the fs but it is
> not mounted. So a pseudo-code patch for the docker entry could be:
> 
> if not mounted
> ?if grep binfmt_misc /proc/filesystems
> ? mount
> ?else
> ? echo "Get a real and recent distro"
> ?fi
> fi

Actual code should be something like:

if ! mountpoint -q /proc/sys/fs/binfmt_misc \
   && ! mount -t binfmt_misc binfmt_misc /proc/sys/fs/binfmt_misc; then
    echo >&2 "E: Unable to mount binfmt_misc"
    exit 1
fi

Ben.

-- 
Ben Hutchings, Software Developer                ?        Codethink Ltd
https://www.codethink.co.uk/                 Dale House, 35 Dale Street
                                     Manchester, M1 2HF, United Kingdom

  reply	other threads:[~2019-04-12 11:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02  3:17 [cip-dev] isar error log daniel.sangorrin at toshiba.co.jp
2019-04-02  6:13 ` Jan Kiszka
2019-04-03  0:56   ` daniel.sangorrin at toshiba.co.jp
2019-04-03  5:55     ` Jan Kiszka
2019-04-11  9:08       ` daniel.sangorrin at toshiba.co.jp
2019-04-11  9:15         ` Jan Kiszka
2019-04-11 10:05           ` daniel.sangorrin at toshiba.co.jp
2019-04-11 10:13             ` daniel.sangorrin at toshiba.co.jp
2019-04-11 12:42               ` Jan Kiszka
2019-04-12 11:37                 ` Henning Schild
2019-04-12 11:59                   ` Ben Hutchings [this message]
2019-04-16  2:47                     ` daniel.sangorrin at toshiba.co.jp
2019-04-16  3:04                       ` daniel.sangorrin at toshiba.co.jp
2019-04-03 13:53     ` Ben Hutchings
2019-04-05  7:44       ` daniel.sangorrin at toshiba.co.jp

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=1555070397.3557.19.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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.